Is the model ready?
Are references, obligations, criteria and hooks sufficiently defined for the declared scope?
One System.
Different ways to see it.
Intent, work and evidence share the same subjects.
A private contact is an entity in the model, something an agent works on, and a subject whose privacy needs evidence. Moving between views changes the question, not the System.
Keep in TouchIllustrative System
A System for the relationships you choose.
What should hold true.
A Thing can begin with its Genome alone: purpose, structure and contracts, before Parts or source exist.
A declared contract. Its purpose, policies and acceptance criteria give the work its context.
Intent is not implementation evidence.Choose a subject. Change the layer. It is still the same System.
Try the views.
Genome describes intended structure and contracts: purpose, requirements, journeys, policies and criteria. It can exist before any Part or source Artifact.
Proteome describes how work is realized and evaluated: roles, task packets, Realizations, hooks and checks.
Phenome defines what can be observed and records evidence, feedback and outcomes, with their time and context. Runtime evidence links through the authoritative Thing, source and realized output association.
Genome, Proteome and Phenome are views over the same System, not successive build stages or nested containers.
The pieces,
in plain language.
- System
- System is the context and governance wrapper for the work. It can contain one Thing that is the whole application, and its boundary does not have to match a repository.
- Purpose & Externals
- The change you want for people in a surrounding context, and the people, services and conditions your System interacts with.
- Thing
- A Thing is a subject the System defines, such as a whole application, a service or a document. A Thing can begin with its Genome alone, with zero Parts and no source Artifact.
- Parts
- Parts are optional reusable packages that may be partial or complete at any scale. A recipe composes pinned contributions explicitly; upgrades compare saved baselines so custom work is preserved or conflicts are shown.
- Source & realized Artifacts
- Source Artifact is authored code, configuration, assets and manifests, excluding dependencies, caches and generated output. Realized Artifact is one specific build output with its own identity, locator or digest, and its source and Genome lineage. Rebuilding identical source can produce distinct outputs.
- Evolution & Realization
- An Evolution describes intended change. A Realization is a scoped attempt by a contributor or agent. Several Realizations can explore the same Evolution.
- Evaluation & System commit
- An Evaluation records a check against an exact candidate. Promotion records an accepted System revision, its manifest, evidence and decision. A local Git commit alone does not authorize promotion.
Three questions.
Three separate answers.
Does the implementation conform?
What checks ran against this exact version, and what did they establish?
Does it help?
What observations show that the intended change is happening for the beneficiaries?
A passing implementation check does not establish usefulness or causal impact. Outcome claims remain hypotheses until the relevant observations support them.
Make the model
part of the handoff.
A Task Packet brings the relevant parts into an agent's workspace.
Bring your agent