Honesty layer

Status, facts & the ledger

Current technical results, historical captures and unfinished work are kept separate. Every fact has a stable ID and its own evidence date; a passing technical candidate does not erase an older failure or sign off delivery and human experience.

01

Current bank technical pass; historical failures retained

Content updated ; technical evidence captured . Read the sanitized technical acceptance summary. The maintainer reviewed the local reports and checked their hashes; the original reports and complete matched materials are not public.

technical pass, rechecked Owner bank030-relocated-20261112-02 passed source, anchors, code and service after actual source relocation. The report records fullPipelinePassed=true and no diagnostics (F-24).

Scope: native Darwin x64 / JDK11, one owner. Source inputs stayed unchanged; this owner's resources exited and its lease was released. That outcome does not describe other sessions or certify production, concurrent writers, other platforms or a real fund-company connection (F-28). The CLI tool is 0.5.0; the engines are 0.3.0 — different version dimensions (F-29, F-23).

ACCEPTANCE BOUNDARIES

not accepted Public matched materials (DEF-15), independent human usability (DEF-16) and independent start/status/page-operation/stop experience (DEF-07) remain separate. Session03 did not reach readiness; manual slot cleanup was not a pass. The later session-fix candidate is recorded as not executed. Automated browser observations do not certify human experience.

historical failure P23/service02's replay failure remains failed (DEF-06); it is superseded for the current technical assessment, not relabelled. Maven Central publication alone is not bank service acceptance (F-23).

02

Verified facts — dated and scoped

Capture dates belong to individual facts, not to a blanket re-verification. The 2026-11-11 captures retain bank fix/pending-replay-20261111 and tool fix/pending-reconciliation-20261111; current owner-02 evidence has its own inputs and scope. Source of truth: SITE-FACTS.md. A reproduction command is not a promise of publicly available matched materials.

Count scope checked : F-10 counts physical author files, including system.yaml. Its 59 independent VO atom files plus 59 VOs expanded from structures (payment 29, refund 20, effect 10) give 118 VO nodes in F-03, not simple copies of same-name nodes. Reconcile the shipped SQLite nodes and meta.canonical with matching source declarations read-only; no expander or graph regeneration is needed. Original capture dates and F-24–F-29 technical evidence are unchanged.

IDFactValueCapturedEvidence / reproduction
F-01Bank truth tree compilesverified 0 hard findingsnpm run validate (bank repo)
F-02Roundtrip byte-identityverified 157 atomspart of the validate gate
F-03Canonical graphstoreverified 389 nodes / 413 edges; count scope checked Original capture: truthsrc graph --tree truth/bank-wealth --out <db>. Read-only VO reconciliation.
F-04Code generationverified 235 filesgenerate-project
F-05Anchor verificationverified passed, 792 anchorsverify-project
F-06Generated Scala compilesverified 0 errors / 534 sourcessbt compile
F-07Generated unit testsverified 23/23 passed; not the independent bank business suites or handwritten test expectationssbt test in generated project; handwritten production sources are compiled
F-08Handwritten zoneverified 35 files, complete implementations (not stubs)filesystem count
F-09Rule declarations, not independently proved invariants or testsverified 149 @rule declarations across 3 aggregatesgrep over truth tree
F-10Physical author-file censusverified 157 YAML atoms: 59 VO · 27 slice · 36 formal-product · 8 structure · 4 pipeline · 4 story · 6 read-model · 3 aggregate · 2 saga · 1 use-cases · 1 context · 5 inbox notes · 1 system root (system.yaml); count scope checked Filesystem count recorded in SITE-FACTS; physical files versus expanded VO nodes.
F-11Sagas declaredverified 2: bank cash saga and bank-independent refund sagatruth tree filesystem
F-12Counter tutorialverified Node-only; no JVM, database or network requiredtruthsrc init counter-lab --format human; TUTORIAL.md
F-13Toolchain footprintverified 0 npm runtime dependencies · Node ≥ 22.13.0 (built-in node:sqlite)package.json
F-14Relation registryverified 22 relations (R1–R22) with propagates flagslib/shared.mjs
F-15Atom kinds / note typesverified 12 atom kinds, 15 note typeslib/shared.mjs
F-16MCP toolsverified 26 tools, stdio JSON-RPCtruthsrc mcp
F-17Workshop HTML snapshot, distinct from Explorersnapshot scope checked Single-file, 2.18 MB, offline, zh-CN; 120 exported nodes / 183 edges, declared project-view totals 861 / 737; 741 nodes omitted; scope checked Embedded workshop-view in the snapshot: truthsrc.project-view/v1, not the F-03 graphstore. Inspect exported arrays, totals and truncation; this historical snapshot does not contain the new service-acceptance report.
F-18 / F-19 / F-20Licensesverified Engines: Apache-2.0, tag v0.3.0 · truthsrc: MIT · bank: Apache-2.0F-18:
F-19/20:
per-repo LICENSE; engine tags
F-21Blast radius, SipInstallmentFailed d3verified 55 nodes — site SQL preset ≡ CLI verbMCP blast_radius over bank canonical
F-22Orphansverified Canonical: 11 sourceless events. Raw query: 23 nodes / 13 names, including 2 qualified request aliases with local producersMCP orphans
F-23Engines on Maven Centralpublication verified net.imadz saga-core / monarch-core / monarch-persistence 0.3.0; JAR SHA-256 550fbd5c… / 0c7a25ee… / f42f1b99…. Publication is not bank service acceptance.Public JAR/POM responses and pinned bytes; fetch versioned artifacts and compare SHA-256. Acceptance summary
F-24Relocated bank technical acceptancepassed and rechecked Source / anchors / code / service; fullPipelinePassed=true; no diagnosticsbank030-relocated-20261112-02; bank ce51d0e6 plus 16 pinned source-overlay files, tool cb860b5c. Scope and prerequisites: private paired materials required, not a public one-command reproduction.
F-25Actor and readside test scopespassed Actor 64; readside 47; share 23 generated tests, not 111 distinct casesSame relocated candidate; separate actor/readside builds in verify --through service; approved fixed business expectations retained. F-24 prerequisites apply.
F-26Relocated recovery and service observationspassed 24 three-JVM recovery windows (72 JVMs); 4 real database/HTTP phases; 3 automated browser observations; 5 MySQL negativesSame sealed candidate: initial, restart, refund and fresh SQL rebuild. Explicit service verification; automated checks do not sign off independent or human experience.
F-27Fresh SQL rebuild readinessgate passed 66.847 s within unchanged 90 s; initial / restart / refund: 2.132 / 14.251 / 13.667 sOwner-02 readinessMs.replay=66847; isolated service setup required. Not the previous candidate's result or a general performance promise.
F-28Candidate scope, source stability and resource exitverified for owner-02 Native Darwin x64 / JDK11, one owner; source unchanged, owned resources exited and lease releasedLocally reviewed driver and input-before/after evidence; does not describe other sessions. Sanitized evidence summary
F-29CLI installation and Counter relocationfunctional checks passed Tool package 0.5.0: package-pin verification, offline install, actual prefix relocation, Counter 0→2 update; 40 command observationstool-install-counter-review; matched package required. Tool version differs from engines 0.3.0. Zero repeated generated-source writes does not mean zero evidence/graph writes; delivery and newcomer usability remain separate (DEF-15, DEF-16).
F-30Matched bank Graph / Code snapshotsource/anchors verified 389 nodes / 413 edges; 866 knowledge identities; 792 anchor keys, 2,898 locations, 669 spans; 385 browsable files (228 generated + 157 author), 1 withheld; 374 bridged nodesSnapshot evidence and scope; real ReserveFunds and LEDGER_SUFFICIENT round-trips in Chromium/WebKit. Build/service not run; does not re-sign historical runtime results.
03

The ledger — open, deferred, resolved and historical

Status applies only to the named scope. A newer passing candidate does not rewrite an older failed receipt. Source of truth: LEDGER.md. Items referenced across this site link here.

IDCategoryItemStatusNote
DEF-01behaviorBDD / Gherkin behavior specsdeferredPositioned as a derivative of the truth tree; guards/folds formalization took priority. Generated Gherkin is not an independently authored oracle. Function-level cases, call resolution and real implementation tests belong to DEF-21; behavior projection remains deferred.
DEF-02toolingVisual truth-tree authoring (Qlerify / Miro import, reverse extraction into a tree)deferredLanguage layer first; editing UX is separate. Awaits early-adopter validation of the strategy/scope layer.
DEF-03publishingtruthsrc npm releaseblockedCurrently local tgz / source only, not published to a registry. Requires an owner release-ready decision.
DEF-04publishingmonarch-* / saga-* Maven Central releaseresolved 2026-11-12All three net.imadz engines are published as 0.3.0; public bytes match the pins (F-23). This does not close material delivery or all downstream observations.
DEF-05demosfab-simulator-demo, bank-batch-transactor-demo open-sourcingdeferredVersion alignment follows the current four-repo set: alignment wave 2.
DEF-06bank-serviceHistorical P23/service02 full-service gatehistorical failure Superseded for current technical assessmentThe 2026-11-06 replay missed 90 s; that receipt remains failed. New owner bank030-relocated-20261112-02 passed all four technical layers on its own patched, relocated inputs, including a 66.847 s SQL rebuild (F-24–F-28). Never relabel the old run.
DEF-07bank-experienceIndependent start/status/page-operation/stop experience and original manual smokeopenOwner-02 automated HTTP/browser observations do not certify original manual sbt run or independent experience. Session03 did not reach readiness; later manual slot cleanup was not a pass. The 2026-11-13 session-fix candidate is recorded as not executed. Requires a new independent accepted-run receipt, including shutdown/lease outcome.
DEF-08hostingBank demo hosted on a free web servicedeferredCandidate-specific technical acceptance exists; independent experience, distribution and hosting remain separate. No hosted service is claimed. Requires independent experience, a delivery channel and an explicit hosting decision.
DEF-09examplesEnd-to-end business example threading Saga/Monarch through the original transfer flowdeferredBank example declares saga + monarch; a dedicated cross-cutting narrative must still be authored in truth.
DEF-10i18nChinese site editionresolved 2026-11-11Full /zh/ mirror shipped, including bilingual site.js/explorer.js/dissolve.js chrome. Correction: workshop HTML was already zh-CN; the original item recorded this inverted. No English workshop edition was required.
DEF-11alignmentPer-repo README alignment with this sitedeferredExplicitly next-phase after the site ships; requires site approval and stability.
DEF-12explorerForce-directed graph canvas; asciinema/screencastsdeferredQuery console + radial view cover v1; no recording toolchain in the workspace. Post-launch work.
DEF-13namingnpm scope @madpolaris/truthsrc → @co-arising/truthsrcdeferredZero cost before first npm publish; must precede DEF-03 closing.
DEF-14orgRemaining monarch-* / saga-* repos → co-arising orgdeferredbank-wealth-demo and truthsrc have migrated; runtime repo migration still awaits an owner decision. Maintain current links in site.js and static HTML/clone examples separately; retain historical snapshot origins.
DEF-15deliveryPublic matched CLI package, clean1134 and paired source materialsblockedRuntime artifacts are public, but the matched tool tgz, frozen toolchain/third-party archive and complete paired bundles/overlays have no confirmed public delivery channel. Requires public byte-matched materials and a documented acquisition path.
DEF-16usabilityIndependent human newcomer acceptanceopenNo three independent readers have signed off. Automated browser checks and technical passes are not human usability acceptance; requires human acceptance records for the documented path.
DEF-17familiesFour Saga and two Play family observationsdeferredPlanned 24 observations: 12 generated + 6 compiled + 6 behavior. Bank acceptance cannot substitute; Play examples do not themselves consume these engines. Requires family-specific records.
DEF-18runtimeRetry/backoff/deadline engineering debtopenStill OPEN; finite-profile acceptance is not an exemption. Requires separately approved runtime work and evidence.
DEF-19assuranceTargeted Inspector race/fault-injection negatives and Node CI/typecheckopenIdentity-validation fixes entered the technical run, but their specific negative probes and extra Node CI/typecheck were not executed in that round. Requires separately scoped probe and CI receipts.
DEF-20distributionLegacy offline-bundle runtime-pin migrationdeferredHistorical offline distribution tooling still targets retired P23. The current explicit-supply workshop does not rewrite or re-sign that archive. Migrate separately when that distribution path is next used.
DEF-21behaviorVersioned function signatures, independent BDD cases, expression-call resolution and implementation bindingdeferredBC already has functions.yaml, independent cases and specialized generation; JS legacy has declaredFunction/fn:. The gap is the current strict compiler closure, including approved guard/binding/fold and pure-translation positions. Preserve nominal typing, deterministic replay and pinned implementations; no arbitrary host calls or effects. DEF-01 output and the fold RFC’s admission defects are separate. P0 design is recorded but not frozen; real implementation tests, replay and source tracing remain required.
DEF-22contractsExternal-contract references, translation/invocation, version resolution and concrete ArtifactType bindingsdeferredExisting contracts, ports and version checks are not absent. Jointly design references, observation-to-command translation and inbound/outbound API bindings with binding-profile and versioning-policy. Resolve the selected contract to actual ports, adapters and artifact instances; a category label is not an implementation. DEF-23 covers owned read-model consumption. P0 is recorded, not frozen; source/version/type resolution and actual bindings still need verification.
DEF-23contractsExternal contracts as truth-source inputs for internal read modelsdeferredEmail-security dashboard: external datasets, message-bus messages (including external domain events) and APIs feed declared ingestion, processing, projection and storage into owned read models. Complements DEF-22; do not fabricate local commands or events to force a read-side path. OpenAPI, AsyncAPI, CloudEvents and JSON Schema are role-specific candidates, not adopted versions or current support. Preserve replay inputs, deduplication and checkpoint semantics. P0 is recorded, not frozen; standards/subsets and an independently checked mock-backed example remain required.
DEF-24workshopBank wealth inbox: 13 artifact directories and EventStorming information coverage in 01–05deferredTarget all 01–13 artifact directories and their content, not empty folders. Independently audit 01–05 against Alberto Brandolini’s EventStorming information patterns; the Fab and batch-transactor examples are incomplete references, not acceptance baselines. The 13-part layout is a project convention, not 13 official EventStorming steps. Preserve reconstruction/provenance labels; do not invent workshop history. Completion requires approved content, explicit gap/not-applicable records and an evidence-backed information-pattern review; directory counts alone do not close this item. Local audit and candidate checklist.
DEF-25languageMultiple bounded contexts and explicit cross-context relationships in the recommended author/project entrydeferredThe current entry admits one context and requires an empty relationships array. Historical context metadata is not absent; the gap is current authoring, qualified references and admitted composition across contexts. Independent of DEF-21–DEF-23; no name flattening or implicit profile widening. Requires a separately frozen identity/relationship/composition contract and cross-context positive/negative tests.
BUSINESS-EXPRESSION DESIGN · 2026-11-15

P0 assessment and design documentation are recorded, not a frozen contract or implementation. The single design is BUSINESS-EXPRESSION-DESIGN.md in the truthsrc repository, linked from its PROJECT-OPEN-ITEMS.md; BC tracks S2-104. Local recording does not claim that this new document is already published.

Exact function/call schemas, durable replay-bundle association, external-standard versions/subsets, concrete ArtifactType realization and independent fixtures remain open. DEF-21/22/23 require their own compiler and behavior gates; DEF-25 is separate. DEF-09/24 content and DEF-18 runtime debt remain unchanged. No new syntax, runtime release or bank acceptance is claimed.

DEF-24 · LOCAL INBOX AUDIT · 2026-11-14
  • bank-wealth-demo/truth/bank-wealth/inbox/: 3 / 13 directories, 5 YAML notes — three role notes in 02, one context note in 05 and one implementation note in 06; missing 01, 03, 04 and 07–13. Its README maps thirteen coverage viewpoints to slices, sagas, pipelines, stories, use cases and six read models. This is not thirteen content-bearing inbox directories; missing notes do not imply missing business implementation or justify duplicating executable rules.
  • fab-simulator-demo/truth/inbox/: 12 / 13 directories, 119 YAML notes; missing 04. bank-batch-transactor-demo/truth/inbox/: 11 / 13 directories, 65 YAML notes; missing 04 and 10. Both READMEs declare reconstruction rather than a live workshop and explicitly skip 04. Fab’s README says 10 has no independent note, yet it contains the proposed OnEquipmentFaultReschedule note, awaiting adjudication; do not treat it as accepted policy.
  • Candidate 01–05 checklist: event chronology and pivotal points; commands, actors and external systems; policy triggers and read-model/decision inputs; branches, exceptions and time constraints; hot spots, questions, assumptions and unresolved decisions; aggregate, subdomain and context boundaries/relationships. Check relationships and meaning, not just note types; distinguish present, referenced elsewhere, missing and not applicable without inventing a subdomain split or workshop history.

Read-only local structure/content check, not a complete comparison with Brandolini’s primary material; method-source review remains pending. No demo truth, current business rules or runtime acceptance was changed.

DISCIPLINE

The ledger and the status page are updated in the same commit. A number that leaves SITE-FACTS must leave the pages; a promise that leaves the ledger must appear in a repo.