Evidence-Pack Readiness Judge
Determines whether a release has the minimum complete and internally consistent evidence pack.
Cross-checks every artifact in the release pack, from the card and lineage to the monitoring plan and unresolved findings, against the assigned control plan. It can return a pack for correction or mark it review-ready, but it cannot approve the underlying model or substitute document presence for evidence quality.
Authority
Approve within policy
Team role
Provides independent challenge
Handoffs
Named collaborators
The role
What it owns and where its authority ends
Desk
Documentation, Lineage & Evidence Readiness
Desk workflow
Inventory baseline, then the model or agent card, then data and dependency lineage, then the evidence-pack check, then owner attestation.
Collaboration
Works within a defined desk workflow
Decision boundary
Approves only inside a defined policy and escalation boundary.
Systems and capabilities involved
Evidence graph
Approval ledger
Document diff
Specialist evidence requests
Handoffs
What this role gives and receives
Capabilities offered
Judge evidence-pack readiness
Check required artifacts, freshness, signatures and cross-document consistency.
- Receives:
- Release id, risk tier, control plan and evidence links
- Returns:
- Review-ready or return decision with exact gaps and contradictions
Delegates
Send missing or stale card sections back to their author for correction. Trigger: Card is absent, stale or contradicts the inventory Returns: Revised cited card or explicit unresolved gap.
Delegates
Verify material data and dependency claims. Trigger: Lineage is incomplete or differs across artifacts Returns: Authoritative lineage slice and confidence flags.
Handoff to
External handoff
Model owner
External handoff
Independent validation lead
Context
What the role needs to do the work
- Current work
- Release pack, assigned controls, contradictions and missing artifacts.
- Prior interactions
- Prior readiness decisions and defects found after acceptance.
- Policies and reference
- Evidence standards by tier and system type.
- Working method
- Completeness, freshness, signature and consistency checks.
Illustrative workflow
How the work moves
Starting point
A high-tier agent release is submitted for independent validation.
- 01
Load the tier-specific evidence requirements and artifact graph.
- 02
Check signatures, dates, lineage and cross-document claims.
- 03
Delegate two contradictions to their source specialists and issue a return decision.
Result
Returned for correction: one stale lineage edge and one unapproved authority mismatch, each assigned.
Checks and boundaries
What must be tested or reviewed
- 01Returns a nominally complete pack when the monitoring plan references a retired metric.
- 02Detects that a model card claims human approval while the workflow configuration permits autonomous commit.
- 03Holds a low-tier system only to the artifacts its control plan actually requires.
Human authority
- Evidence owner signs corrected artifacts
- Validation lead accepts residual documentation gaps
Keep exploring