Ontogony began with a philosophical question: how does a produced state acquire identity, authority, and persistence? The software system asks the operational version.
How can a machine-produced decision become authoritative without becoming opaque?
The answer is not one model or one dashboard. It is an explicit sequence of mechanics, execution, model access, semantic judgment, promotion, evidence, and verification.
Act I
The philosophical problem
A produced state is not authoritative merely because it exists. Its identity depends on where it came from, which transformation produced it, and what allows it to persist as the same state through change.
Act II
The operational problem
Enterprise agents intensify the problem. A model can produce a result, but production is not authority. The operational question is how source, context, execution, judgment, promotion, and evidence remain inspectable when a result becomes consequential.
Act III
The system answer
Ontogony separates mechanics, model access, semantic authority, governed execution, promotion, evidence, and verification into explicit contracts. The system category follows from that separation: a governed control plane and system-of-record for consequential decisions.
Operational translation
From philosophical question to contract boundary
- Identity
- Source intake, lineage, and temporal context.
- Production
- Governed execution and controlled model access.
- Authority
- Semantic judgment and explicit promotion.
- Persistence
- Dossier evidence, replay, and offline verification.