16. Creation: The Workflow of Autopoiesis

Requirements

• Hermetic Isolation: Physical prevention of live system file modification during the experimental phase.
• Speculative Sandbox: A protected environment (The Shadow Realm) that mirrors the production substrate but lacks the authority to impact Primary Reality.
• The Verification Ritual: Mandatory success of a formal verification suite (e.g., Unit Testing, Linting, Type Checking) before logic transitions from experiment to reality.
• Atomic Promotion: Transactional migration of code; broken or untested artifacts must be discarded rather than merged.
• History Preservation: Mandatory Jujutsu-backed VCS tracking from the moment of inception to ensure a permanent audit trail of the system's evolution.
• Promotion Authorization: Integration with the Human-in-the-Loop protocol and Codex autonomy policy so structural promotion requires live Magus consent unless an explicitly bounded preauthorization class applies.

Considered Options

Decision Outcome

A formal Creation Workflow is adopted, governing how new intents are manifested into the system's body. The workflow is a linear path through the system's domains.

1. Invocation (Genesis)

When a Magus or an authorized process initiates a change, the system creates a new coordinate in the Lab region of the Crypt (13).

• Freedom: This directory is the site of conception. The process can break things here, install experimental dependencies, and generate files without affecting the active Daemon.
• Context: The process is provided with the current state of the Core and the Crypt lockfile (13) to ensure the new creation is compliant with the system's existing laws.

2. Speculation (The Shadow Realm / Manas)

The initial labor is performed using a divergent VCS revision. This state of "Speculative Execution" allows for the exploration of multiple branching paths for a given problem. It is the domain of Manas (the divergent router), where the machine is permitted to generate "Vṛttis" (fluctuations and parallel branches) to navigate the Possibility Space. The fruits of this speculation are presented to the Magus as "Visions" at the Altar (15).

Using Jujutsu (jj), this speculative state is even more natural: every modification in the working copy is automatically a "change" (revision) in the graph, providing implicit checkpointing without the friction of manual commits.

The agent graph orchestrating the speculation runs in the Vessel. Safe control-plane creation work may remain there: planning, graph routing, policy checks, structured diff preparation, review packaging, and promotion decisions. Raw execution payloads (code edits, test suites, linter invocations, arbitrary scripts, or risky tool calls) are dispatched to The Tomb container via SAQ for sandboxed execution. The Tomb returns stdout only; it does not run agent logic or LLM calls.

3. Creation (The Sequential Deep-Dive / Buddhi)

Once a valid path is found in the Shadow Realm, the machine must transition from exploration to execution. This is the domain of Buddhi (the convergent intelligence).

When writing core logic with causal dependencies, the agent must operate in a Single-Threaded, Deep Sequential mode. Massive parallelism here is a "hallucination trap." Because of Computational Irreducibility, the agent cannot predict the end state of a complex logical loop; it must walk the path step-by-step. By enforcing Stillness (Metabolic Discipline) during the actual creation phase, the system maximizes logic-per-watt and prevents the introduction of recursive errors.

4. Verification (The Rite of Albedo)

Before leaving the Lab, every creation must undergo the Verification Ritual.

• The Strike: The system enqueues a job for the Ghouls (14).
• The Test: The Ghouls execute the verification suite (e.g., ruff, pytest) against the new code in isolation.
• The Verdict: If the tests fail, the process must iterate within the Lab. No human intervention is requested for technical errors; the machine must solve its own syntax.
• Migration Isolation: Verification rituals must utilize a transient, ephemeral database instance. The creator of the new logic must prove that all new relational models and migrations are valid against this empty shell before the logic is ever promoted to the Primary Phylactery.

5. Promotion (The Rite of Passage)

Once a creation is deemed "Stable" (passes all verification) and is authorized through Consent or a Codex-defined preauthorization class, it undergoes Assimilation. High-stakes creation, schema changes, secrets, host lifecycle authority, and destructive actions still require live Magus consent.

1. The Lock: The new logic is formally added to the system's federated lockfile.
2. The Move: The directory is moved from the Lab (Read-Write) to the Crypt (Read-Only).
3. The Rebirth: The system signals a Packaging (17) ritual to forge the new physical body.

6. Conflict Sovereignty (The Magus Always Wins)

In the event of a "Temporal Collision"—where a file in Primary Reality has been modified by the Magus while an Agent was speculating on a change in the Shadow Realm:

• Banishment of the Dream: The system enforces a "Fail-Fast" merge policy. If a VCS merge conflict is detected during the Promotion Ritual, the Shadow Timeline is immediately banished.
• Sovereign Authority: The machine possesses no authority to overwrite manual changes made by the Magus.
• Resynchronization: The Agent must be re-awakened to the new reality, internalizing the Magus's changes before it is permitted to initiate a new cycle of creation.

Consequences