RFC-032: Post-Hoc Evaluation Loop — 14. Relationship to Existing RFCs
AIGP Specification › RFC-032: Post-Hoc Evaluation Loop › 14. Relationship to Existing RFCs
← 13. Security Considerations · Section index · 15. Implementation Priority →
14. Relationship to Existing RFCs
| RFC | Relationship |
|---|---|
| RFC-010 (Base Protocol) | ANTICIPATE and VERIFY extend the message type vocabulary alongside REGISTER, REQUEST, RECORD, TRACE |
| RFC-010a (Multi-Agent) | ANTICIPATE may be issued per-agent in a delegation chain; VERIFY aggregates across the workflow |
| RFC-010b (Temporal Chaining) | VERIFY results are linked via session_id, enabling longitudinal quality analysis |
| RFC-024 (D-DNA) | ANTICIPATE and VERIFY are D-DNA signed entities in the evidence chain |
| RFC-026 (Human Feedback) | FEEDBACK (user signal) and VERIFY (system signal) are complementary quality indicators |
← 13. Security Considerations · Section index · 15. Implementation Priority →