Dalteno← Back to the proof section

This is the report every partner receives from us on Friday, unchanged in format from pilot to year three. One page, written by the person who did the work. The two reports shown here are real but cover a two-day build rather than two weeks: one per deliverable (docrecon on 15 October, docflow on 16 October). They are shown so you know what you would get, not what we would promise. Week 2 →

Delivery report — docrecon

ON TRACK
Report
1 · deliverable: docrecon · 2026-10-15
Scope
Open-source reconciliation engine, two implementations, parity-tested
Demo
dalteno.com/lab/docrecon/
Repo
github.com/dalteno/docrecon

Done this week — against the agreed acceptance criteria

CriterionStatusEvidence
Visitor can enter values we never anticipated and get an explained verdict✅Live demo; every finding carries rule, field, expected, actual, reason
Rules identical in .NET 10 and JS✅52 golden reports; .NET parity test compares every field
≥ 40 shared cases incl. adversarial, expectations hand-written✅52 cases, 15 adversarial, cases/generate.mjs
CI green on both engines✅.github/workflows/ci.yml — JS, .NET, generator drift check, golden coverage check. Update 18 Oct: first real run green — GitHub Actions run #3, commit 99c5257, 33 s total; dotnet test on CI: Dalteno.DocRecon.Tests Passed 145, Failed 0 (305 ms, net10.0)
Documented decisions✅ADR-0001 pure engine · ADR-0002 integer arithmetic · ADR-0003 cases as spec

Not done / changed

Found and fixed

Measured

Decisions needed from you

  • None blocking. Optional: should weight tolerance default stay at 2 % or follow your broker's practice? One-line change in ReconcileOptions.

Risks

Next week (if this were a continuing engagement)

Format: one page, every Friday, from the person who did the work. Questions: hello@dalteno.com.