Repository navigation
AIM 4.7.7 — Graph reporting bound to recorded evidence
Keep /aim graph explanations bound to the selected recorded evidence.
- Identify the selected delivery and its source; draw factual arrows only from recorded edges. An empty graph does not establish safe parallelism or the absence of blockers.
- Keep proposed sequencing separate as recommendations. Surface observation/staleness limits and conflicting labels without silently rewriting them or implying native acceptance.
- Clarify that native plans can be unapproved and that lifecycle fallback applies specifically to native deliveries without an execution plan.
- Preserve these facts in an actual-command regression and regenerate the public skill from canonical guidance.
Validation: 832 tests, repository/package checks, official skills CLI validation and source/assembled publication checks pass. Separate review covers the original correction and release metadata.
The evidence establishes bounded data preservation and reporting-contract correctness. Universal future model adherence is unproved. UI, runtime projection, roles, gates, authority boundaries and schemas remain unchanged; no migration is required.