Ontogenesis is the resident controller that follows a project between missions: it selects a task, starts a bounded run, examines evidence, and coordinates integration or resumption.
04 · Identity & Development
Ontogenesis
in GenOS.
Ontogenesis is the resident controller that follows a project between missions: it selects a task, starts a bounded run, examines evidence, and coordinates integration or resumption.
INPUTPROCESSINGRESULT WITH CONTEXT
DEFINITION AND SCIENCE
What it means
in GenOS.
The concept borrows from organismal development to describe continuity across software missions. A project controller is a stateful workflow, not a living or self-developing organism.
Ontogeny links successive developmental stages of one organism. GenOS borrows continuity across missions while implementing a governed project state machine.
Plan → Execute → Verify → Integrate and reassess
Model the controller as a finite-state process over {plan, execute, verify, integrate, wait}; transition δ(state,event) is allowed only when the relevant permission, evidence, and budget guards pass.
ANIMATED DIAGRAM · INTERACTIVE MODEL
01 / 03Explore the mechanism: Ontogenesis
A qualitative teaching model of this concept. It does not run GenOS or validate its implementation.
01Select eligible missionINPUT
02Execute and verifyMECHANISM
03Integrate or resumeCONDITIONAL OUTCOME
Current transition · Step 1Select eligible mission
The modeled transition may proceed. Change the assumption and move through the stages to inspect the decision path.
PROCESS AND USE
How it works
at a glance.
Plan
Choose an eligible backlog task based on dependencies, priorities, budgets, and its persisted kind (implement, verify, explore, decide, or repair).
Execute
Delegate a bounded mission to the GenOS runtime and preserve its state.
Verify
Examine the evidence; without enough evidence, return the mission to planning.
Integrate and reassess
Integrate an accepted result, link failures to the topology used, and choose what to do next or wait for an event.
RUNTIME IMPLEMENTATION
What is connected,
and how far.
This page describes project-level continuity through software states and resource constraints. It is distinct from cell-level HOX lineage differentiation in the Rust biology path. Project Ontogenesis remains partial: when no explicit completion contract is supplied, the mission gate can fall back to a generic outcome check. Task acceptance text is not independently verified by that gate. The loop and persistence mechanisms exist, but transparent recovery for every scenario is not guaranteed.
The project loop connects selection, bounded execution, checks, Git integration and targeted crash reconciliation. Explicit philosophical contracts require source-bound audit replay before verification; automatically added concepts remain advisory. General process recovery and acceptance semantics still require explicit contracts.
Failure modes have not yet been separately cataloged for this entry; follow the source and evidence links before relying on the mechanism.
PRIMARY RESEARCH · MECHANISM LEVEL
The mechanism
behind the analogy.
Distributed snapshots: determining global states of distributed systems
K. Mani Chandy and Leslie Lamport · ACM Transactions on Computer Systems 3(1), 63–75
Describes a snapshot algorithm under explicit assumptions; it does not prove a GenOS snapshot covers external effects.
Open publication ↗Primary research describes the cited mechanism; specific technologies may instead cite their original technical documentation. These sources provide context and do not validate the GenOS implementation.
HOW IT COMPARES TO OTHER AGENTS
The difference is
continuity.
Many assistants answer a request or execute a task. Ontogenesis adds a durable loop that resumes the project between missions and keeps decision steps visible.
One request, one response
Conversation-centered interaction. The person usually guides the next step and carries work forward from one session to the next.
FOCUS · ANSWER THE CURRENT TURNOne goal, one run
Can use tools and produce a deliverable within a defined scope. Persistence, verification, and integration depend on the product and its configuration.
FOCUS · COMPLETE A MISSIONOne project, multiple missions
A resident controller selects eligible tasks, starts bounded missions, examines evidence, then integrates, waits, or replans.
FOCUS · MAINTAIN PROJECT CONTINUITYAn architectural comparison, not a ranking. These are general categories: capabilities vary across agents, models, and configurations. GenOS does not claim to be better at every task; its distinctive focus is project lifecycle management with explicit evidence and authority limits.
EVIDENCE AND LIMITS
The controller is not a living organism
This page describes project-level continuity through software states and resource constraints. It is distinct from cell-level HOX lineage differentiation in the Rust biology path. Project Ontogenesis remains partial: when no explicit completion contract is supplied, the mission gate can fall back to a generic outcome check. Task acceptance text is not independently verified by that gate. The loop and persistence mechanisms exist, but transparent recovery for every scenario is not guaranteed.