Skip to content

renderResilience

reference
1 min readUpdated

Kind: Function

Source: atloria-monorepo/libs/parser-core/src/techdocs/subsystem-narrative.ts

How the subsystem behaves when work cannot proceed, counted across every member.

The flow section says this about the handful of components on ONE traced path, several of which belong to other subsystems. This says it about all of this subsystem's own members, which is a different set and a different number — so the sentence names its scope rather than letting a reader carry the path's counts over.

No denominator is given for "N components record a refusal or a handler". metadata.controlFlow is written only where a parser both looked and found something, so an entity without it may equally be one no extractor examined — "20 of 134" would be counting a missing field as a zero.

Signature

ts
function renderResilience(evidence: SubsystemEvidence | undefined): string

Parameters

NameType
evidence`SubsystemEvidence

Returns: string

Was this page helpful?

Download as PDF