Define
Describe product knowledge in Markdown files in your repository.
Product Definition as Code · reference implementation
Keep product decisions close to the work that changes them.
ProductShape helps teams define product knowledge in versioned Markdown, connect delivery work to the accepted definition, and see when that definition changes.
Used in real projectsRaccord · DomusMind · several private projects. Also used for reverse-engineering product documentation in projects whose details are confidential.
A shared structure
One definition. Clear links to delivery.
A small, inspectable workflow keeps people in control at every decision point.
Validate
Check schemas, identifiers and relationships with deterministic rules.
Cite
Connect delivery documents to the exact accepted artifacts they use.
Change
Propose an update, review it, and detect stale citations after it changes.
The important boundary
Tools check structure. People decide meaning.
ProductShape can find broken references and changed definitions. It cannot decide whether an idea is true, whether a change is right, or whether implementation is complete.
Public dogfooding
See the ProductShape model, not a sales demo.
This repository defines itself with the same product model it asks teams to create. Browse real artifacts and their relationships in a generated, read-only snapshot.
Implementation
Built to stay understandable.
Explore the twelve arc42 views of the implementation, from package boundaries to publishing and quality evidence.
Engineering →Next step
Start with one product decision.
You do not need a complete model to begin. Start from the knowledge your next change depends on.