Follow a single sample case through all six stages of IDRYN — a claim checked against the record, a history that becomes a profile, a score with its factors showing, the exact moment it went wrong, the fix re-verified, and the evidence package that ends a dispute.
MS
Meridian Support AgentSAMPLE AGENT
DEPLOYED BY NORTHWIND RETAIL (SAMPLE) · CUSTOMER SUPPORT · REFUNDS · PAYMENTS · CRM
Sample history since Mar 2026
Stage 01 · Verify
Verify the Outcome
Compare the agent's claimed result against authoritative records to detect mismatches before they become downstream risk.
Agent claim
“Payment sent in full — $4,800.00”
To: Vendor B · via finance agent · Case NW-4471 (sample)
System of record (sample) — Internal ledger
Field
Claim
Record
Amount
$4,800.00
$4,080.00
Recipient
Vendor B
Vendor B
Status
Sent in full
Posted
Uses sample data for demonstration
Step 1 — Read the claim
Step 2 — Check the system of record (sample record)
Step 3 — Compare the evidence
Step 4 — Issue verification outcome
MISMATCHClaimed amount does not match the sample ledger record.
The first row is the stage 1 case — traced in stage 4, closed in stage 5
Stage 03 · Score
Quantify Reliability
Translate observed behavior into an illustrative reliability score and the factors driving it.
Illustrative IDRYN Score
764 / 1000
Sample scoring framework — not production calibrated
Sample score history: 701 → 738 → 764 over the last three sample months — computed from the record in stage 2, never from the agent's own reports.
Factors behind the score
Completion consistency
94.9%
Mismatch frequency
3.2%
Largest observed discrepancy
$720
Remediation speed
89% ≤ 48h
No black box: every factor traces to entries in the verified record.
A score is earned, not assigned. Deployments without sufficient verified history are not scored at all — they show NOT YET SCORED until the record is deep enough to mean something.
Stage 04 · Diagnose
Trace the Failure
Trace the mismatch through the execution timeline to identify where the outcome diverged from the intended action.
09:14 · SAMPLE TRACE
Agent begins a payment run for Vendor B's invoice — intended amount $4,800.00.
09:15 · TOOL CALL A
Payment created correctly: $4,800.00 to Vendor B.
09:15 · TOOL CALL B (RETRY) — DIVERGENCE POINT
A retry re-submits the payment using a stale draft. The amount field is overwritten: $4,800.00 → $4,080.00.
09:16 · LEDGER
The ledger posts $4,080.00. The vendor is underpaid by $720.00.
09:16 · AGENT REPORT
The agent reports from its first call, not the final state: “Payment sent in full — $4,800.00.”
09:16 · IDRYN CHECK
Claim vs. record compared field by field — MISMATCH, discrepancy $720.00, evidence preserved.
Observed failure pattern (sample trace)
Conflicting tool calls
The amount was overwritten by a second, conflicting tool call before submission. The agent's report described the intended action — the record shows the action that actually happened. That gap is exactly what IDRYN exists to catch.
Stage 05 · Remediate
Verify the Remediation
Track the corrective action, re-verify the outcome, and record whether the incident was successfully remediated.
MISMATCH→REMEDIATION IN PROGRESS→REMEDIATED
T+0H
Discrepancy flagged. Sample Evidence Package DEMO-0142 is delivered to the operator with the field-level comparison.
T+3H
Operator acknowledges the case and confirms the failure pattern from the trace in stage 4.
T+26H
Corrective action: a supplementary payment of $720.00 is posted to the ledger for Vendor B.
T+26H · RE-VERIFICATION
IDRYN checks again: $4,080.00 + $720.00 = $4,800.00 — the record now matches the original claim. Outcome: VERIFIED.
RECORD UPDATED
Case NW-4471 is marked REMEDIATED in the behavioral profile, and the correction counts toward the remediation factor in the score.
REMEDIATEDRemediated within 26h— inside the 48-hour window counted by the score. Flagging an error is not the end of the loop; the verified fix is.
Stage 06 · Evidence
Assemble the Evidence
Package the underlying records into an auditable evidence trail for dispute review without making the final adjudication.
Weeks later, the $240 refund from the record (NW-4468) is disputed: the customer says it never arrived and files a chargeback (sample case). Nobody has to argue from memory — the verified record is already there.
“The refund of $240.00 never arrived.” Chargeback filed (sample).
Agent claim
Refund issued — $240.00 · Case NW-4468 · outcome VERIFIED at the time.
Processor record
Refund settled on Oct. 12 · Reference ARN ····4821 (sample) · not reversed.
Ledger entry
$240.00 posted to the original payment method on Oct. 12 (sample).
Notification
Refund email delivered to the customer on Oct. 12 (sample delivery receipt).
Evidence assessment — based on available records
MERCHANT CLAIM SUPPORTED
The available evidence is consistent with the merchant's account. Evidence supports the merchant's refund-processing claim; processor records indicate the refund settled on Oct. 12.
Sample Evidence Package DEMO-0143 · Sample data only · IDRYN assembles the evidence — the final adjudication stays with the payment network and the parties involved.
Stage 1 of 6
VERIFY → PROFILE → SCORE → TRACE → REMEDIATE → EVIDENCE
One claim, followed all the way through.