Fit, not a feature contest
Where does this fit
in your existing workflow?
Keep tools that help your team discover, describe and operate a domain. Consider a truth source when you also need a reviewable connection from declared behavior to generated implementation and back. That is a particular job, not a replacement for every modeling or data platform.
Start with the job you need done
These are complementary starting points, not an exhaustive vendor capability audit. No absence of a feature or integration is inferred from a tool’s category.
| Your job | A place to start | How a truth source could fit | Boundary to check |
|---|---|---|---|
| Discover a shared business language | EventStorming / Domain Storytelling | Keep the discussion and examples. Capture decisions as reviewable drafts, then make accepted rules and relationships explicit. | A workshop method is not replaced by a file format; promotion from a draft remains a human decision. |
| Collaborate on a model | Qlerify and other modeling canvases | Use the canvas for conversation; review how each exported field maps to declarations before treating an import as authoritative. | Roundtrip canvas integration is not shipped here. DEF-02 tracks the deferred integration; no product-wide coverage score is claimed. |
| Publish an architecture catalog | EventCatalog | A catalog can help people browse domains, services and events. A truth-source workflow adds its own declared-behavior generation and source-anchor checks. | Complementary roles do not imply an automatic catalog exporter or synchronization contract. |
| Explore bounded contexts and context maps | ContextMapper | Use strategic modeling to discuss boundaries. This project connects its supported declarations to a graph and CQRS/ES implementation. | A CML projection is a direction, not a delivered adapter or a claim about ContextMapper’s limits. |
| Implement an event-sourced application | prooph / Event Engine | Choose runtime and language for the application. Here, the demonstrated generation target is Scala CQRS/ES; Saga and Monarch have separate coordination responsibilities. | The knowledge layer does not make runtime ports interchangeable. There is no PHP target demonstrated here. |
| Connect enterprise data and actions | Palantir Ontology and semantic platforms | Both semantic models and truth-source models can express relationships and behavior. This project emphasizes author files, generated source and inspectable provenance. | Evaluate platform integration and governance on their own requirements. This is not a compatibility, feature-parity or vendor-exit assessment. |
Existing standards, explicit implementation status
The standards already exist. A sensible mapping onto one is not the same as an implemented, tested exporter. The current interfaces below are distinct from proposed derivatives.
SQLite knowledge graph
A local graph representation supports real queries. The Explorer reads the shipped bank snapshot F-03; it is not a live view of your repository.
MCP access
The toolchain provides read-oriented tools over stdio JSON-RPC F-16. This is a query interface, not an export to every standard listed below.
Proposed derivatives · not shipped integrations
| Job | Standard or format | Proposed mapping | Status here |
|---|---|---|---|
| Acceptance examples | Gherkin | Scenarios and declared behavior → Given / When / Then features | Designed, not built DEF-01. Expected behavior still requires independent review. |
| Event contracts | AsyncAPI | Events and payload schemas → messages, channels and operations | Proposed projection; not a current export. |
| Event envelopes | CloudEvents | Event metadata → an interoperable envelope | Proposed mapping; no conformance claim. |
| HTTP contracts | OpenAPI | Commands and queries → operations and schemas | Proposed projection; no current exporter claimed here. |
| Architecture views | C4 / Structurizr DSL | Explicit architecture declarations → system and container views | Proposed projection; domain relations alone do not specify deployment topology. |
| Service catalog | Backstage catalog | Contexts and declared dependencies → catalog entities | Proposed projection; not a synchronization integration. |
| DDD modeling | ContextMapper CML | Bounded contexts and context maps → CML declarations | Proposed projection; not a roundtrip adapter. |
Start from an available interface. For a new projection, agree on identity, semantics, information loss and ownership before building an exporter. A derivative should not become a competing editable source by accident.
Check the license at each boundary
truthsrc toolchain
The recorded toolchain license is MIT F-19. Review the license and notices for the version you adopt.
Engines and bank example
saga-core, monarch-core and monarch-persistence F-18, plus bank-wealth-demo F-20. Runtime dependencies retain their own obligations.
This site
Site content is CC BY 4.0; site code is MIT. Keep the applicable attribution and notices when reusing them.
For an application you distribute, review generated content, included scaffolding and runtime dependencies together; a permissive generator license is not a blanket waiver of their terms.