The new method covers goal reconstruction, deliverable design, dependencies, parallel handoffs and integration review, with a fictional ledger and an offline consistency checker.
Code, live operation and business outcomes are assessed separately. Stale, conflicting or mismatched evidence and unmet dependencies cannot support completion claims. Duplicate JSON keys are rejected to prevent silent state replacement.
Structural checks do not establish evidence authenticity, replace acceptance, close formal actions or send notifications. The method scales to the task; a small, clear assignment needs no full governance system.