The workflow
From product knowledge to delivery, step by step.
ProductShape gives product knowledge stable structure and links it to the documents that implement it. Your existing repository and review process stay in control.
Start where you are
Initialize a new product or add ProductShape to an existing repository. For a brownfield system, recover candidate knowledge from evidence; the tool structures the work but does not scan code and invent a model.
Write a proposed definition
Describe an actor, rule, journey, requirement or term in the change's proposed state. The initial baseline follows the same governed Product Change process as later updates.
Check structure
Run validation to check schema, IDs, relationships and lifecycle rules. Structural validity is a useful signal, not proof that the definition is semantically complete.
Review and accept
People decide whether a change is accurate. Apply materializes it on a working branch; a reviewed merge accepts the new baseline.
Cite and verify
Consumer documents cite accepted artifacts by stable ID and content digest. Verification makes changed or broken references visible for review.
A Product Change records product intent. The implementation may ship in the same or a later pull request. A merge does not claim the change was implemented, tested, or released.
Archify diagrams
From product knowledge to two publications
These are conceptual explanations. Links to sources show where to check canonical processes and artifacts; shape and color do not encode facts by themselves.
Canonical product sources → · Canonical architecture documentation →