Requirement claims in the order produced by the builder. Decision claims
preserve input decision order (mirrors
AnalyzeDecisionLedger.dumpValidDecisions() insertion order); structured
non-decision claims follow in file/extractor output order. 00-toc.md
claims are excluded by the builder — TOC is navigation context, not a
claim.
OptionalprojectionsAdditive projection edges from claims back to rendered Analyze sections. New producers emit an empty array when no projected claims exist. Optional because callers may build minimal claim snapshots without projection data.
Authoritative machine-readable SRS requirement registry for this analyze run. Producers emit this from scenario defaults, decisions, and structured claims.
OptionaltocOptional TOC navigation context. Absent when the run produced no TOC, or when reading an older history that pre-dates this feature.
Run-level snapshot of analyze's structured requirement claims, attached to
AutoBeAnalyzeHistory.document.requirementsIRandAutoBeAnalyzeCompleteEvent.requirementsIR.Contains the SRS requirement registry, structured claims, and an optional TOC navigation context. Each claim carries SRS contract semantics such as support, obligation, acceptance criteria, verification method, priority, and status. Per-file grouping, conflict status, version, and confidence flags are deliberately excluded — see the spec's "거짓 신호 회피" principle.
Author
Juntak