Mapping
Builds a view of the territory and its relationships.
RUNTIME · RESIDENT OBSERVATION
A daemon to
know its territory.
In GenOS, a resident daemon observes a project territory across missions. It maintains traceable knowledge and sends useful signals to the orchestrator.
IMPLEMENTED ARCHETYPE · EXPERIMENTAL MATURITY
DAEMONObserves and learns
→ORCHESTRATORChooses the mission
→WORKERActs under control
ANIMATED FLOWS · LOCAL SIMULATIONSee each cycle
See each cycle
in motion.
Choose a component to follow its role, limits, and handoffs. This animation explains the flows; it does not run the GenOS runtime.
Resident archetype
1 territory · observation onlyResidentDaemon
Follows a project territory over time. Its knowledge stays attached to the repository and HEAD it observed.
01
CONTEXT
Territory
Repository, scope, and HEAD are registered.
02
SIGNAL
Event
A commit, test, or orchestrator entry draws its attention.
03
ORGANELLES
Observation
Cartography, interoception, and search gather clues.
04
VERIFIABLE
Finding
A claim receives evidence, scope, and limitations.
05
DECISION
Handoff
A brief goes to the orchestrator, which chooses what happens next.
Organelles are its internal functions. Phenotypes shift its attention in response to measured pressures.
8 ORGANELLES · INTERNAL FUNCTIONS
cartographyinteroceptionsearchfindingsverificationstigmergyhandoffreconciliation
10 PHENOTYPES · ATTENTION MODULATION
securitycontractdependencydocumentationhistorianchaperonemetaboliccross-reporepairdeep research
01 · THE ARCHETYPE
One resident,
one territory.
ResidentDaemon is the only GenOS resident-daemon archetype. It follows an identified territory—such as a repository at a specific Git HEAD—so its findings remain attached to their context.
Residency grants no additional authority: the daemon observes and reports. A finding is neither sufficient evidence nor an instruction to act; the orchestrator chooses what happens next, and a worker can intervene with the required checks.
FILE WRITES · PROHIBITEDGIT PUSH · PROHIBITEDMERGE · PROHIBITED
02 · INTERNAL ORGANS
Eight organelles,
one logical process.
These are functions of ResidentDaemon, not eight separately launched agents or processes.
↗
Interoception
Tracks activity, health, and pressure signals.
Natural search
Explores clues and knowledge relevant to the territory.
Findings
Produces bounded findings with scope and limitations.
Verification
Checks freshness, scope, and observed evidence.
Stigmergy
Leaves markers to guide future attention.
Handoff
Sends a contextualized brief to the orchestrator.
Reconciliation
Finds stale states and resources that need cleanup.
03 · ECOLOGICAL SPECIALIZATIONS
Ten phenotypes
shape attention.
Phenotypes activate in response to measured pressures in the territory. They shape attention, memory, and briefs without changing the daemon's identity.
securitySecurity signals and threat signatures.
contractDrift between producers and consumers.
dependencyDependency changes and compatibility.
documentationGaps between code, tests, and documentation.
historianRepeated failures, regressions, and historical context.
chaperoneNew structures and signs of incomplete integration.
metabolicResource pressure and operational anomalies.
cross_repoShared contract drift across territories.
repairRepair opportunities to pass on for controlled handling.
deep_researchKnowledge gaps and stale information.
Adaptive activationCurrent thresholds are heuristics. The benefits and costs of each family remain to be measured separately.
04 · RELATED COMPONENTS
Components
near the daemon.
They are part of the ecosystem but do not add more resident archetypes.
ScoutCells
Read-only scouting cells with limited duration and budget. They are not resident daemons.
SentinelDaemonKeeper
Observes process availability. It does not produce domain findings or decide on its own to restart a process.
WorkspaceGitDaemon
An older model kept for compatibility. Its autofix is deprecated; repairs go through an episode, a worker, and checks.
SCOPE AND LIMITS
An experimental observation system.
The runtime, territories, findings, handoffs, reconciliation, and evaluation are implemented. Overall maturity remains EXPERIMENTAL: available live results are too limited to establish a general benefit. Knowledge can also become stale when the territory's HEAD changes.
The resident host polls the indexed durable event cursor every 500 ms. On restart it returns to BOOTSTRAPPING while retaining health, revision count, and the last event cursor. Production events are reported as emitted only after the cheap update and journal write both succeed.
Read the daemon reference catalog ↗