RFC-032: Post-Hoc Evaluation Loop — 15. Implementation Priority
AIGP Specification › RFC-032: Post-Hoc Evaluation Loop › 15. Implementation Priority
← 14. Relationship to Existing RFCs · Section index · 16. Quality Moderator — Consumer Tier Deliverable →
15. Implementation Priority
| Component | Effort | Dependency |
|---|---|---|
| ANTICIPATE message type + storage | Medium | RFC-024 (D-DNA signing) |
| Seal-on-execution logic | Low | Governance engine modification |
| CODE grader engine | Medium | Restricted expression language |
| VERIFY message type + governance actions | Medium | ANTICIPATE must exist first |
| Behavioral baseline computation | Low | 30+ VERIFY results per agent |
| MODEL grader integration | High | Isolated model invocation infrastructure |
| Calibration program | High | Human labeling workflow |
| API endpoints | Low | Standard AIGP route pattern |
Recommended implementation order: ANTICIPATE → seal logic → CODE grader → VERIFY → governance actions → baseline → API → MODEL grader → calibration → Quality Moderator.
← 14. Relationship to Existing RFCs · Section index · 16. Quality Moderator — Consumer Tier Deliverable →