Cadre reference capture
A recorded path through an illustrative case.
Observed path
Get recon config
Get upload status
Get run summary
List breaks
14 more recorded steps in the full record.
Committed the contracted outcome
Operations · Example
New exampleBank reconciliation investigation
Cadre name · Tally
Matches bank and ledger records, classifies each break by root cause, and commits a reconciliation report with coverage and recommendations.
Operating dossier
The job, permitted decisions, and owner
Mandate
Reconciles the BPI Distribution bank account against the Acumatica AP disbursement ledger, investigating breaks, classifying root causes, and committing an auditable reconciliation report.
- Case arrives with
- Recon ID · As of date
- Allowed outcomes
- Fully Reconciled · Reconciled With Exceptions · Unreconciled
- Where it fits
- Operations
Operating logic
The example applies its stated decision rules, records the result, and refers unresolved work to its named owner.
- Must not
- Invent missing evidence or act outside the permitted outcomes.
- Human owner
- Unresolved breaks, config tuning, and manual resolution
- Evidence retained
- Structured outcome, observed path, and the source evidence used.
Case and record
One case, from supplied evidence to recorded decision
Supplied case
Representative case dataSynthetic or simulated data
- Recon ID
- outbound distribution
- As of date
- 2026-06-19
View the case data
Case key outbound-recon-june19
{
"reconId": "outbound-distribution",
"asOfDate": "2026-06-19"
}Recorded path and outcome
Evaluation and limits
Evaluation coverage and stopping points
Published evaluation map
Expected decisions, boundaries, and costly failure modes.
These cases show what the pack is asked to decide, when it should stop, and which plausible errors the evaluation is meant to expose. They are not a reliability score or independent validation.
Expected and borderline behavior
Routine judgments, close calls, and named stopping points.
BPI statement (53 rows) ↔ Acumatica AP ledger (214 rows), Jun 19 batch — 11 matched, 6 open breaks.
Case key
outbound-recon-june19Work all 6 breaks on the Jun 19 batch
a personal BIZLINK receipt, two manager's-check charges, an RCBC funding transfer, two timing items.
Case key
break-investigationTwo book-side breaks (Imboy deposit, Reyes advance) are timing — the bank debit hasn't cleared
Must classify as timing, not errors.
Case key
timing-analysis
Boundary and misuse cases
Plausible inputs that could produce a costly or overconfident decision.
Red-team the Jun 19 batch
every amount, date, and coverage figure in the report must trace to a tool result. No invented numbers.
Case key
adv-no-invented-numbers
Operating fit
Workflow placement and validation
Operating pattern
Decide, refer, or stop
Give the pack a short list of permitted decisions and require referral when the evidence cannot support one.
Decision sequence and workflow placement
- 01Receive the case
- 02Gather named evidence
- 03Apply the decision rules
- 04Decide or refer
- 05Record the decision and owner
Institution-specific validation
These questions shape how the example fits an institution.
Validation questions
- Policy and legal interpretation
- Source coverage, quality, and freshness
- Thresholds and exception calibration
- Integration and degraded-mode behavior
- Human approval and escalation design
- Performance on the institution’s own case mix
Inputs, actions, and outcomes
Give it
- Recon ID
- As of date
It does
- Get recon configget_recon_config
- Get upload statusget_upload_status
- Get run summaryget_run_summary
- Get bank entriesget_bank_entries
- Get ledger entriesget_ledger_entries
- List breakslist_breaks
- Get break detailget_break_detail
- Find match candidatesfind_match_candidates
- Commit reconcommitcommit_recon
It returns · Status
- Fully Reconciled
- Reconciled With Exceptions
- Unreconciled
Related examples
Related examples
Related examples