A requirement is only as strong as its evidence.
Inspect all 20 requirements, the evidence in the supplied reference package, and the validation an adopter needs to perform.
How to read this assessment.
This is a source-review coverage map. “Partial demonstration” means only part of a requirement is illustrated. A file-presence check is not proof that a control works. No complete-conformance or certification claim is made.
The specification requires mandatory requirements to be satisfied or formally excepted; the requirements list distinguishes Critical and High priority. Record the interpretation, responsible approver and any accepted exception with your assessment.
| ID | Requirement | Coverage | Evidence in this release | Adopter validation |
|---|---|---|---|---|
| CR-001 | Engineering Constitution exists and is authoritative Critical | Artifact only | Constitution template exists; precedence enforcement is not exercised. Inspect artifact | Attempt a conflicting action and retain its rejection record. |
| CR-002 | Root Agent exists and is identifiable Critical | Partial demonstration | The demo registers an identifiable Root agent. Inspect artifact | Bind the actual coordinator to a durable identity record. |
| CR-003 | Feature Agent ownership exists for meaningful domains Critical | Partial demonstration | The routing test looks up one feature owner. Inspect artifact | Test missing and duplicate owners across all registered domains. |
| CR-004 | Specialist delegation is bounded Critical | Partial demonstration | Declared limits are compared; live runtime limits are not metered. Inspect artifact | Exercise depth, cost, time, tool and scope boundaries. |
| CR-005 | Delegation contracts are auditable Critical | Partial demonstration | A contract model and in-memory event references exist. Inspect artifact | Persist complete contracts and verify retrieval by delegation ID. |
| CR-006 | Root does not silently bypass Feature Agent ownership Critical | Manual validation required | The role template defines coordination expectations. Inspect artifact | Attempt a Root write across a feature boundary without approval. |
| CR-007 | AI-SDLC state is represented High | Manual validation required | No software-lifecycle transition test is supplied. Inspect artifact | Trace a real task through each required lifecycle gate. |
| CR-008 | ADLC state is represented for agents High | Model only | Lifecycle states are specified, not enforced by the demo. Inspect artifact | Reject an invalid transition and record the governing policy. |
| CR-009 | Agent identity is separate from model identity High | Partial demonstration | Agent identity is modeled separately from provider/model choice. Inspect artifact | Demonstrate an identity surviving a model change. |
| CR-010 | Agent permissions are explicit Critical | Partial demonstration | Permission escalation is rejected in one supplied test. Inspect artifact | Test all enabled tools and environments against delegated permissions. |
| CR-011 | Autonomy/delegation budgets are enforced Critical | Partial demonstration | Step and cost declarations are checked against parent limits. Inspect artifact | Measure consumption; stop execution at each actual budget limit. |
| CR-012 | Agent creation is bounded Critical | Manual validation required | Declared depth is checked; recursion and parallelism are not enforced. Inspect artifact | Apply repeated spawn pressure and verify hard termination limits. |
| CR-013 | State and handoff are persisted High | Manual validation required | Handoff records are modeled; persistence is host responsibility. Inspect artifact | Restart the host and recover complete state and handoff records. |
| CR-014 | Requirement-to-evidence traceability exists High | Manual validation required | The figure describes traceability; no end-to-end assertion is supplied. Inspect artifact | Resolve a requirement through task, change, test and release IDs. |
| CR-015 | Audit trail records delegation and material actions High | Partial demonstration | In-memory demo events exist; durable and denied-action audit is absent. Inspect artifact | Record allowed and denied actions in tamper-resistant durable storage. |
| CR-016 | Cross-feature changes are controlled Critical | Manual validation required | The template expresses include/exclude boundaries. Inspect artifact | Reject a cross-domain write without explicit coordination. |
| CR-017 | Failure / timeout handling exists High | Manual validation required | Failure and timeout states are modeled; no scheduler is bundled. Inspect artifact | Inject timeout and tool failure; verify stop, cleanup and handoff. |
| CR-018 | Fresh-session resumability is demonstrated High | Manual validation required | No fresh-session recovery experiment is included. Inspect artifact | Resume in an independent session using persisted artifacts only. |
| CR-019 | No claimed completion without validation evidence Critical | Manual validation required | The deterministic specialist returns COMPLETE without an evidence gate. Inspect artifact | Reject completion when required validation evidence is missing. |
| CR-020 | Conformance results are reproducible High | Partial demonstration | The supplied tests are repeatable; full conformance evidence is absent. Inspect artifact | Publish environment, commands and results for all requirements. |
Reproduce and extend.
Download the coverage map / JSONRun the included Python unit tests and file-presence script from the extracted package. Then add host-level tests for the controls above. Preserve your environment, version, outputs and exceptions alongside the evidence.