What must remain true?
Use a file-based truth tree to name aggregates, commands, events and invariants. People can review the business rules before discussing implementation details.
co-arising · shared knowledge, accountable change
How do we keep a business decision connected to the code that implements it? Write the concepts, rules and behavior in a readable truth source. Generate the supported implementation, keep integration explicit, and trace changes back to their declarations.
Co-arising community
Discuss domain modeling, truth sources and event-sourced systems. Bring a question, share an experiment, or help shape the tools through practical feedback.
Join the Discord communityThe smallest useful loop is truth tree → compiled products → generated code → source anchors. Each part answers a different question; no single green gate proves the business decision right.
Use a file-based truth tree to name aggregates, commands, events and invariants. People can review the business rules before discussing implementation details.
Query declared relationships in a local SQLite knowledge graph. Explore the bank snapshot; the graph can only show dependencies that have been modeled.
Supported guards, event bindings and state folds become code alongside CQRS/ES structure. Generation does not invent missing business policy.
Technical bindings and a separate handwritten zone connect the generated project to external effects and host services. Their responsibilities and tests stay explicit.
Source anchors connect knowledge to generated code at the precision supplied. Verification checks freshness and bytes; it is not proof that every line is correct.
People and agents can query, propose and test. Humans approve the intended behavior. Technical passes, independent experience and delivery remain separate on the status ledger.
Use Node ≥ 22.13 in a new exercise directory. Acquiring the source checkout needs a network; the Counter generation loop needs no JVM or database service. The full walkthrough — including the bank example and the MCP integration — is on the hands-on guide.
export TRUTHSRC_WORKSPACE="$PWD"
git clone https://github.com/co-arising/metarch-truthsrc.git
export TRUTHSRC_CLI="$TRUTHSRC_WORKSPACE/metarch-truthsrc/bin/truthsrc.js"
node "$TRUTHSRC_CLI" init counter-lab --format human
cd counter-lab
node "$TRUTHSRC_CLI" generate-project --project truthsrc.project.json --out generated --plan --format human
node "$TRUTHSRC_CLI" generate-project --project truthsrc.project.json --out generated --format human
node "$TRUTHSRC_CLI" query-project --project truthsrc.project.json --out generated --knowledge SetCount --format human
node "$TRUTHSRC_CLI" verify-project --project truthsrc.project.json --out generated --format human
Start with DDD consistency boundaries and a small relationship exercise on real bank data.
ReadFollow a command through guards, event bindings and a state fold, then read the broader language.
BuildSee knowledge, technical bindings, generated code, handwritten integration and tests in one lifecycle.
EvaluateFollow payment, TA rejection, independent refund and bounded installments through their declarations.
InvestigateBrowse real nodes and edges, follow a scenario link, or query the shipped SQLite snapshot.
AdoptCompare jobs rather than slogans; distinguish current interfaces from proposed standards projections.
Chinese-language editorials on AI coding and co-arising’s engineering direction. These are perspectives, not verification of shipped capabilities; dated evidence stays on the status ledger.
A look at the shift from vibe coding toward agentic engineering: specifications, feedback loops and deterministic guardrails.
Exploring compact domain declarations, bounded agent work and model–code traceability as engineering directions, not a delivered-workflow claim.
The tree, code and anchor counts below retain their 2026-11-11 capture in SITE-FACTS; they are not new service-run counts. The engines are now published on Maven Central F-23. npm publication, hosting and BDD derivatives remain on the ledger.
On 2026-11-12, bank030-relocated-20261112-02 passed and rechecked source / anchors / code / service F-24, including real database/HTTP and automated browser observations F-26. This is candidate-specific technical acceptance, not independent experience (DEF-07), public matched-material delivery (DEF-15) or human usability acceptance (DEF-16). The old service02 failure remains historical (DEF-06). Read the acceptance scope and prerequisites.
Make the evidence boundary visible. These pages have no build step or npm dependencies; claims link to dated evidence and open items. A summary of privately reviewed reports is not a public reproduction package. Read why.