case-studystable
Evidence before answers
A confident financial answer is useless when I cannot tell which source, statement, or correction produced it.
Ledgerglass keeps immutable account and transaction observations, statement facts, corrections, and derived explanations separate so an agent can show its work without trusting a mutable source cache.
Public proof and references
Artifacts: ledger architecture · MCP response contract · trust model · observability privacy boundary
Research IDs: simplefin-protocol · mcp-security · cloudflare-workers-logs
Checked: 2026-08-20
case-studystable
Money that adds up
Floating-point totals and mixed currencies can make a tidy dashboard mathematically wrong.
Arithmetic uses integer minor units and keeps currencies separate unless an explicit conversion exists.
Public proof and references
Artifacts: money contract · cashflow architecture · synthetic evidence
Research IDs: actual-architecture
Checked: 2026-08-12
case-studystable
Boring, bounded synchronization
Late settlement, exclusive date boundaries, and provider limits make a naive daily fetch lose rows.
The connector uses bounded windows, inclusive human dates, an exclusive API boundary, and overlapping incremental reads.
Public proof and references
Artifacts: connector contract · sync-window architecture
Research IDs: simplefin-protocol
Checked: 2026-08-12
case-studystable
Pending is not forever
Some providers stop reporting pending purchases without saying whether they settled or disappeared.
Old pending rows can expire from operational totals, return when observed again, or link to a later posted transaction without erasing history.
Public proof and references
Artifacts: pending lifecycle contract · synthetic settlement story
Research IDs: simplefin-protocol
Checked: 2026-08-12
case-studystable
Statements can correct the feed
A connected card can still omit posted transactions or report rows that the closed statement does not support.
A complete closed statement is matched one-to-one against the ledger, exact gaps are repaired, and excess connected candidates fail closed with explainable owner-review evidence instead of an arbitrary match. Later provider evidence can replace overlays or refresh a deficient no-overlay component.
Public proof and references
Artifacts: statement workflow contract · synthetic repair story · synthetic exact-collision story
Research IDs: actual-architecture · plaid-pattern
Checked: 2026-08-21
case-studystable
One place for every unresolved difference
Statement gaps, provider differences, conflicting card terms, and repair cases become dangerous when each subsystem keeps its own idea of what is unresolved.
Ledgerglass gives closed statement cycles stable identity, preserves field-level fact lineage, proves adjacent-cycle continuity, and routes every unresolved difference through one append-only discrepancy history with deterministic repair postconditions.
Public proof and references
Artifacts: truth-closure architecture · synthetic cycle-continuity case · correction receipt contract
Research IDs: cfpb-periodic-statements · open-banking-statements · w3c-prov · cloudflare-d1-batch
Checked: 2026-08-13
case-studystable
The totals do not need a model
Spending, debt, transfers, and recurring commitments should not change because a language model phrased them differently.
Deterministic read models calculate cashflow, debt, net worth, merchants, transfers, and recurring cadence before narrative is added. Statement-scoped APR allocations support read-only payment and payoff previews, while unknown issuer priority or deferred-interest behavior causes explicit abstention.
Public proof and references
Artifacts: finance-query architecture · analysis contracts · APR evidence and abstention contract · synthetic household
Research IDs: actual-architecture · actual-schedules · cfpb-credit-card-interest · cfpb-payment-allocation · cfpb-repayment-disclosures
Checked: 2026-08-22
coreexperimental
A forecast that knows what it does not know
A calendar of recurring charges is not the same thing as a promise, and one future balance hides missing evidence and mixed currencies.
Wave 4 keeps owner and statement schedules separate from detected candidates, expands deterministic occurrences, and projects committed, expected, and possible paths per account and currency. A private post-sync scout may activate only mature derived patterns in the expected scenario behind deterministic evidence gates; it cannot create committed authority or ledger facts. The reusable public subset exports dependency-free recurrence, integer-minor-unit forecast, and backtest arithmetic with synthetic vectors and private/public parity proof; live adapters and orchestration remain private.
Public proof and references
Artifacts: public forecast core source · synthetic forecast vectors · schedule and occurrence architecture · synthetic forecast-range case · backtest contract · graduated schedule-autonomy case study
Research IDs: actual-schedules · cloudflare-workflows · actual-architecture · rfc5545-recurrence · plaid-pending-transactions · plaid-recurring-transactions · cfpb-recurring-debits · cfpb-available-balance · cfpb-cash-flow · cfpb-bill-calendar · forecast-prediction-intervals · forecast-distributional-accuracy · forecast-time-series-cv · cloudflare-workflow-rules · cloudflare-workflow-retries · cloudflare-d1-retry · cloudflare-d1-time-travel
Checked: 2026-08-22
case-studystable
Corrections that can be undone
A useful correction should teach the system without silently rewriting old evidence or poisoning evaluation data.
Owner corrections and exact statement facts can produce narrow rules with provenance, impact checks, and automatic suspension after contradiction.
Public proof and references
Artifacts: rule contracts · evaluation boundary · synthetic correction story
Research IDs: mcp-security
Checked: 2026-08-12
case-studystable
The same financial habits in every agent
Connecting the tools is not enough if every agent guesses a different workflow or trust policy.
Portable skills teach agents how to start, which evidence to prefer, when to ask before writing, and how to qualify incomplete data.
Public proof and references
Artifacts: Agent Plugin architecture · skill-routing contract
Research IDs: mcp-security
Checked: 2026-08-12
case-studyexperimental
A steward for the boring repair work
Indexes, enrichment, briefings, and derived views fail independently and should not wait for me to notice.
A durable agent coordinates bounded retries and cases while the ledger remains the source of financial truth.
Public proof and references
Artifacts: architecture · deterministic steward simulator · recovery story
Research IDs: cloudflare-agents · cloudflare-workflows
Checked: 2026-08-12
case-studyexperimental
Research without leaking the ledger
An unfamiliar merchant may need the web, but the web does not need my account or transaction identifiers.
Only a sanitized merchant signal leaves the ledger, and researched claims remain derived evidence rather than transaction truth.
Public proof and references
Artifacts: privacy boundary · synthetic merchant investigation
Research IDs: mcp-security
Checked: 2026-08-12
private-noteexperimental
Model routing from a real deployment
Different finance tasks have different latency, structure, and failure needs.
The private deployment uses task-specific routing and fallbacks; the public package explains a provider-neutral boundary instead of publishing personal quotas or credentials.
Public proof and references
Artifacts: provider-neutral contract · architecture note
Research IDs: cloudflare-ai-gateway
Checked: 2026-08-12
private-notestable
A private operator console
The owner needs a visual way to inspect evidence and authorize existing ledger operations without creating a second financial backend.
The private deployment has an authenticated console over the same finance application services, with typed evidence workflows, read-only review queues, revision-bound previews, and a separate assistant that can cite evidence or prepare a draft but cannot apply it. Only the architectural and authority boundary is documented publicly.
Public proof and references
Artifacts: privacy boundary · architecture note
Research IDs: cloudflare-access-self-hosted · cloudflare-access-paths · cloudflare-access-jwt · cloudflare-worker-routes · cloudflare-service-bindings · cloudflare-chat-agents · cloudflare-agents-client-sdk · cloudflare-agents-human-loop · actual-reconciliation
Checked: 2026-08-14