Audited cases
75
Context Layer Audit Console - IRIS
Completeness, lineage, and usage proof for enterprise context
AuditContext usageDecision gating
Context Layer Audit Console
This console answers the credibility question enterprise reviewers will ask: is enterprise context complete, and is it actually used by agents, policies, evidence, decisions, replay, and the UI? It scores context completeness deterministically and shows the signal-to-outcome trace.
Avg completeness
40%
Context usage
26%
Agent bypasses
174
Critical gaps
359
Replayable
18
What this audits
Enterprise context is treated as a governed runtime asset: entities, relationships, policies, evidence, decisions, outcomes, and learning. The page checks whether those assets are present and whether they influence the decision.
| Concept coverage | Required entities are present for the case type |
|---|---|
| Relationship coverage | Supplier -> PO -> Invoice -> Receipt -> Payment -> Exception trace |
| Policy linkage | Policy ID/version linked to decision ledger |
| Evidence linkage | Evidence hash/source refs available for audit |
| Replay linkage | Replay hash available with context version |
| Agent usage | Agents show the context queries and returned objects |
| Bypass detection | Missing context usage is flagged |
| Negative simulation | Mask context and prove the recommendation changes |
Why this matters
Without this proof, an Enterprise Context page can look like selected metadata. With it, bp can see that context is complete, auditable, used in decisions, and able to block or degrade actions when key context is missing.
| Completeness score | Required context present / required context expected |
|---|---|
| Decision gate | Missing policy or evidence can block execution |
| Usage proof | Agent context queries are visible |
| Lineage trace | Signal -> Context -> Policy -> Evidence -> Recommendation -> Outcome |
| Replay with context | Decision can be reconstructed with exact context hashes |
| Safe degradation | Missing context forces warning, review, or block |
Live Context Completeness + Usage Audit
Live runtime
Audited cases
75
Avg completeness
40%
Context usage rate
26%
Agent bypasses
174
Missing critical context
359
Replayable decisions
18
Scoring model
Deterministic
Persistence
persisted
Case completeness map
| Case | Type | Score | Status | Assets | Policy |
|---|---|---|---|---|---|
| INV-UDP-CERT-001 | Invoice | 22% | blocked | 3/12 | policy missing |
| INV-UDP-CERT-001 | Invoice | 22% | blocked | 3/12 | policy missing |
| INV-UDP-CERT-001 | Invoice | 22% | blocked | 3/12 | policy missing |
| INV-UDP-CERT-001 | Invoice | 22% | blocked | 3/12 | policy missing |
| INV-UDP-CERT-001 | Invoice | 22% | blocked | 3/12 | policy missing |
| INV-UDP-CERT-001 | Invoice | 22% | blocked | 3/12 | policy missing |
| sphere:finance:invoice:INV-00914 | invoice | 22% | blocked | 3/12 | policy missing |
| sphere:upstream:well:WELL-104 | well | 15% | blocked | 2/12 | policy missing |
Lineage trace · INV-UDP-CERT-001
| Business Signal | resolved context snapshot |
|---|---|
| Context Objects Loaded | Invoice INV-UDP-CERT-001; 0 source refs |
| Relationships Loaded | 0 relationship links captured |
| Policies Applied | No policy linked |
| Evidence Retrieved | 56f9dbb865e55658e113d324b9279836b7880f2a22004dbcce79b390f38fde65 |
| Agent Reasoning | Snapshot resolved without decision narrative |
| Recommendation | No action linked |
| Outcome | No outcome linked |
| Replay | Replay hash not linked |
| Learning | Learning signal pending |
Agent context usage
| Agent | Query | Objects | Used | Impact |
|---|---|---|---|---|
| enterprise-context-runtime | Invoice context + policy + evidence | 0 | No | Resolved context used to create decision/evidence/replay proof. |
| Policy Agent | governing policy | 0 | No | Policy missing linked to the decision. |
| Evidence Agent | source refs and lineage | 0 | No | Source lineage supports replay and audit. |
Skills + Policy Framework Audit
Skills represent enterprise capabilities. Policies represent enterprise guardrails. The runtime proves that an agent can act only when a skill is authorized by policy, supported by evidence, and governed through replay.
Skill
Hold Duplicate Payment
Authority
recommend + controlled execute
Policy
Policy missing
Authorization
not authorized
Context
Skill Activated: Hold Duplicate Payment (SKILL-P2P-DUP-HOLD)
Policy Evaluation: Policy missing
Evidence Collection
Decision Recommendation: No governed action linked
Human / Agent Action
Replay & Audit
Learning
Skill audit questions
| Skill ID | SKILL-P2P-DUP-HOLD |
|---|---|
| Version | 2026.06 |
| Owner | P2P Control Owner |
| Risk Class | High financial control |
| Purpose | Prevent duplicate supplier payment before release. |
| Inputs | Invoice, Supplier master, PO, Prior payment, Evidence pack |
| Outputs | Hold recommendation, Supplier validation request, Payment release control |
| Policies | Policy missing |
| Authority | recommend + controlled execute |
| Execution Mode | governed action |
| Evidence | Invoice, Purchase order, Receipt, Prior payment, Supplier history |
| Explainability | Review required |
| Replay | Missing |
| Learning | Pending outcome feedback |
| Human Override | Analyst can hold; supervisor required for release override. |
Policy audit questions
| Source | Policy Runtime / authority matrix |
|---|---|
| Owner | Finance Governance |
| Scope | Invoice |
| Enforcement | Blocked until policy exists |
| Version | Version missing |
| Versioning | Version missing |
| Exception Handling | Analyst can hold; supervisor required for release override. |
| Evidence Requirement | Invoice, Purchase order, Receipt, Prior payment |
| Monitoring | Compliance measured through ledger, usage proof, and replay |
| Auditability | Replay missing |
Negative context dependency simulation
Simulation masks context in the audit evaluator only. It does not delete source records, evidence, or snapshots.
Run a simulation to prove the recommendation changes when context is missing.
Enterprise positioning
The runtime does not treat context as documents or embeddings. It treats context as governed enterprise assets that every agent decision must prove it used.
Implementation boundary
This first version derives completeness and usage from resolved snapshots and the decision ledger. Persistent agent-context usage records should be added next for production-grade ContextOps.