RFC-011: Agentic Context Protocol (ACP) — 12. Post-Hoc Evaluation Context (RFC-032 Integration)

AIGP Specification › RFC-011: Agentic Context Protocol (ACP) › 12. Post-Hoc Evaluation Context (RFC-032 Integration)

← 11. Protocol Summary · Section index

12. Post-Hoc Evaluation Context (RFC-032 Integration)

ACP provides context to the post-hoc evaluation loop (RFC-032). When the VERIFY grader evaluates anticipation criteria against execution evidence, it requires assembled context from multiple sources:

12.1 Verification Context Assembly

Assembler → governance-server: AIGP REQUEST (can evidence-analyzer fetch execution_evidence for session-xyz?)
governance-server → Assembler: ALLOW
Assembler → governance-server: ACP GET /acp/v1/context/anticipation/{anticipation_id}
Assembler → governance-server: ACP GET /acp/v1/context/session_evidence/{session_id}
Assembler → Quality Moderator: Deliver assembled verification context
Quality Moderator → governance-server: VERIFY result + QUALITY_POSTURE

12.2 Context Types for Evaluation

Context Type	Provider	Consumer	Purpose
anticipation	governance-server	Quality Moderator / Grader	The sealed ANTICIPATE declaration (criteria, grading policy)
session_evidence	governance-server	Quality Moderator / Grader	RECORD + TRACE + STEP_COMPLETE data for a session
agent_baseline	governance-server	Quality Moderator	Behavioral baseline for drift comparison
quality_posture_history	governance-server	Quality Moderator	Historical posture transitions for trend analysis

12.3 Governance of Evaluation Context

Evaluation context is itself governed by AIGP:

1. The Quality Moderator MUST have an active scope envelope authorizing it to read anticipation and evidence data
2. Evidence context containing PII is subject to the same consent tier filtering as RECORD messages
3. The Quality Moderator’s scope is narrowed to read-only — it cannot modify anticipations, evidence, or governance decisions directly
4. All evaluation context fetches produce AIGP RECORD entries (meta-governance: governance of the governance evaluator)

This ensures the evaluation layer cannot become a governance bypass — it observes and scores, but enforcement remains exclusively with the Governance Engine.

---

← 11. Protocol Summary · Section index