DemoTONY ▾
Dashboard ×
Metadata request ×
AI change review ×
Data governance request ×
⚡ AI change review Review cycle 1 Action ▾   ⟳   💬   💾
CHG-024187
🤖 AI Guardian
claude-opus-4 · gov v2.3 · prompt p-118
06/20/2026 14:02
TONY
Material · ICFR scope
OneStream · GolfStream
CTRL-AI-014
In review · commit blocked
Model confidence: 0.92indicative only; not audit evidence. Guardrail results and reviewer validation are the control signals.
🤖 Agent rationale Generated by AI Guardian · logged to evidence record
Proposed adding Brazil_Ops under LATAM in the Entity dimension to mirror the new ERP cost-center load completed at 13:58. Pattern matches 3 previously approved entity additions for the region; no conflicting or duplicate members were found. One open item flagged for the reviewer: effective dating was not supplied on the source load — confirm the effective date before commit.
Proposed changes 3 lines · proposed by agent · disposition each line to proceed
LineActionDimensionMemberParent GuardrailSource matchConf.Disposition
1AddEntityBrazil_OpsLATAM Pass ✓ ERP CC-4410 0.94
2AddEntityBrazil_SalesBrazil_Ops Pass ✓ ERP CC-4411 0.91
3MoveEntityChile_OpsLATAM → SOUTH_AM Warning ✗ No source record 0.78
Line 3 — reviewer disposition comment Required for flagged lines
Comment is written to the outlier resolution record (root cause, action, owner, timestamp) and linked to the original evidence package.
⇄ Source comparison — ERP-CC-20260620 output validation vs. source
ERP source recordCost centerCurrencyProposed lineMatch
CC-4410 · Brazil Operations4410BRLLine 1 · Add Brazil_OpsMatch
CC-4411 · Brazil Sales4411BRLLine 2 · Add Brazil_SalesMatch
— no record —Line 3 · Move Chile_OpsNo match
Side-by-side lets the reviewer perform output validation against source data (higher assurance than a reasonableness read of the rationale alone). 2 of 3 proposed lines reconcile to the source load.
🛡 Guardrail checks 1 open flag
Hierarchy balances after change
Mappings reconcile to ERP source
No orphaned members introduced
Segregation of duties — agent scope valid
Accounting structure rule — no leaf under shared
!
Effective dating not set — blocks commit until resolved
Resolving requires a root-cause classification (AI vs. non-AI issue), action taken, and links the resolution back to this evidence package. Repeated flags of the same type escalate per outlier triage policy.
🔗 Impact & lineage AI Data Map
3 consolidations recalculate with this change
2 board reports reference the LATAM rollup
1 ERP → GolfStream mapping is updated
▣ Evidence record — assembled continuously immutable · retained per SOX policy
14:02:11Proposal created by AI Guardian · model claude-opus-4 · gov v2.3 · prompt p-118 · inputs: ERP-CC-20260620
14:02:14Guardrail suite v41 executed — 6 checks · 5 pass · 1 warning
14:06:02Reviewer TONY opened review · source comparison viewed
14:09:47Lines 1–2 approved by TONY (validated vs. ERP CC-4410 / CC-4411)
14:11:20Line 3 sent back · outlier record OTL-0331 opened · root cause: source gap (non-AI)
Pending: commit of approved lines · attestation capture
🔒
Segregation of duties. This change was proposed by an agent. Per policy, the proposing agent cannot approve its own change and cannot modify its governing policy or prompts — a human reviewer must disposition it. Changes to gov policy v2.3 or prompt p-118 route through change management (separate approval, versioned, logged).
⛔ Commit-all locked until line 3 flag is resolved
🛡 Attestation on approval: “I, TONY, attest that I compared each approved line against source load ERP-CC-20260620, reviewed the guardrail results, and dispositioned all flagged items, performing this review under control CTRL-AI-014 (ICFR). I did not rely on model confidence scores as evidence of accuracy.” · 06/20/2026 · logged to Audit with model/policy/prompt versions for this cycle.
Sent-back lines return as Review cycle 2 with a fresh guardrail run and a new evidence record linked to this one.