program-requirements.csv
Synthetic unclassified requirements
Workflow explorerIllustrative walkthrough · synthetic data
01 / Define the context
A bounded source packet.
These files were authored for this example. No customer documents are included.
Synthetic
02 / Ask a specific question
The task sets the scope.
Which program requirements lack supporting reports?
Review only the supplied packet. Keep units and versions explicit. When evidence is missing, show the gap.
This instruction is part of an authored demonstration. It has not been executed against the native product in this build.
03 / Inspect the intended output
REQ-102 has no supplied evidence
| Requirement | Report | Status |
|---|---|---|
| REQ-101 | REPORT-12 | Reviewed |
| REQ-102 | Not supplied | Evidence gap |
| REQ-103 | REPORT-14 | Reviewed |
A missing source is an evidence gap. It does not establish that the requirement has failed.
Inspect the supporting source04 / Follow the source
The context behind the result.
program-requirements.csvrequirements
requirement,evidence,status REQ-101,REPORT-12,Reviewed REQ-102,,No evidence supplied REQ-103,REPORT-14,Reviewed
A missing source is an evidence gap. It does not establish that the requirement has failed.
Methodology & current evidence status
Native product evaluation pending. This is an authored example of the intended workflow, not a recording of model output or a customer result.
The displayed tables are authored expected outputs derived from the synthetic packet. No accuracy, latency, customer impact, or product pass rate is reported. Native recorded artifacts will replace examples after evaluation.
Unclassified administrative examples only. This demonstration makes no classified-deployment, certification, or operational decision claim.