RFC-032: Post-Hoc Evaluation Loop — 6. Protocol Flow
AIGP Specification › RFC-032: Post-Hoc Evaluation Loop › 6. Protocol Flow
← 5. Grader Types · Section index · 7. Governance Stage Extension →
6. Protocol Flow
6.1 Complete Lifecycle with Post-Hoc Loop
sequenceDiagram participant App as Application participant Gov as Governance Server participant Agent as Agent Runtime participant Grader as Grader (CODE/MODEL/HUMAN)
App->>Gov: 1. PLAN_SUBMIT Gov-->>App: 2. APPROVED App->>Gov: 3. ANTICIPATE Note over Gov: Seal + D-DNA sign
Agent->>Gov: 4. TOOL_REQUEST Gov-->>Agent: 5. ALLOW Note over Agent: Execute Agent->>Gov: 6. STEP_COMPLETE
Note over Gov,Agent: ... repeat 4-6 ...
App->>Gov: 7. RECORD
Gov->>Grader: 8. VERIFY request (ANTICIPATE + evidence bundle) Grader-->>Gov: 9. VERIFY result (verdict + scores)
Note over Gov: 10. Governance action (LOG/ALERT/BREAK)
Gov-->>App: 11. VERIFY receipt6.2 Temporal Ordering Constraints
| Constraint | Requirement |
|---|---|
| ANTICIPATE before execution | ANTICIPATE.timestamp < first TOOL_REQUEST.timestamp for the plan |
| ANTICIPATE immutable after execution starts | Governance server rejects modifications after first STEP_COMPLETE |
| VERIFY after execution completes | VERIFY.timestamp > final RECORD.timestamp for the session |
| VERIFY references sealed ANTICIPATE | VERIFY.anticipation_id must reference an immutable, D-DNA-signed ANTICIPATE |
| Grader cannot be the agent | grader_metadata.grader_id ≠ agent_id |
← 5. Grader Types · Section index · 7. Governance Stage Extension →