Ouroboros

Ouroboros is the return of consequence into the next act of creation. A Lich encounters a need, forms and tests a candidate, acts through the proper owner, and retains what the encounter teaches. A later attempt can then change its question, Context, method, or capability. The useful return is a better distinction: what mattered, why it mattered, and when that lesson stops applying.

Transmutation follows this cycle's meaning through Genesis, Trial, Canon, Revelation, and Distillation. Canon supplies criteria before creation and testing; Distillation carries a lesson toward a later attempt. This page keeps the practical handoffs between work, evaluation, memory, and training.

The engineering workflow came first. The author's whiteboard designs already contained exploration, adversarial comparison, human judgment, implementation, evaluation, and a later training return before the sefirotic correspondence was proposed. The Tree entered as a second lens for discovering and improving relations within that independently developed workflow. Resemblance motivates investigation; a proposed addition must still earn its place through a clearer decision, a better handoff, or a demonstrated improvement.

This page connects the Creation workflow, workflow evaluation, and discernment training operating designs. It is a map of governed handoffs, with no new coordinator, registered Pattern, or autonomous implementation. SDLC owns the candidate boundary; State of Work owns delivery.

Three returns, at different speeds

%%{init: {"flowchart": {"nodeSpacing": 12, "rankSpacing": 22, "padding": 8}}}%%
flowchart TB
    I[Intent and Context] --> D[Creation: form candidate]
    D --> V[Verification]
    V --> P[Owned decision and effect]
    V -- failure or rejection --> O
    P --> O[Retain consequence]
    O --> E[Drift: evaluate]
    E --> C[Correction proposal]
    C --> M[Context, memory or procedure]
    M --> I
    C --> N[New source or Scroll]
    N --> D
    C -. corpus admission .-> T[Soulforge: train candidate]
    T --> R[Drift: test transfer]
    R --> A[Policy and required HitL]
    A --> B[Serving owner activates]
    B --> I
    E --> S[Keep, reject or stop]
    R --> S
    classDef work fill:#102d46,stroke:#6faaff,color:#e3f0ff
    classDef evaluation fill:#421f28,stroke:#ff9292,color:#ffe9e9
    classDef training fill:#30203f,stroke:#c09aff,color:#f4eaff
    class I,D,V,P,M,N work
    class O,E,C,R,S evaluation
    class T,A,B training

Blue follows one piece of work. Red asks whether the work and its method succeeded. Violet changes model competence only when a training hypothesis earns that more expensive passage. Context and memory admission can improve the next attempt without changing weights. An evaluation may also conclude that the present method should remain.

Arrows show dependencies between settled records and separately admitted acts. They do not launch the next owner, share its authority, or create a hidden Run spanning all three cycles. An eventual application must publish its exact Pattern; live coordination across Composition-owned Invocations needs a named Suite.

Why the whole is not one DAG

The workflow may revisit exploration, repair a candidate, or return after an evaluation. Its design therefore contains cycles. Each recorded occurrence still has an identity and earlier causes: explore₁ → judge₁ → probe₁ → explore₂. Such an unfolded causal history can be a DAG without pretending that the reusable workflow is acyclic. A new semantic attempt adds a history entry; exact transport redelivery preserves its admitted attempt and idempotency identity. This causal view follows retained dependencies and attributed causal claims, with capture gaps left visible. It supplies no claim of complete causal observation or new scheduling Occurrence type. Changing the score requires a new immutable Scroll revision and a later Invocation.

The Graph owns executable topology and checkpoints. Spellweaver owns logical sequencing, Dispatcher selects an eligible capability, and Orchestrator owns physical readiness and transitions. Readiness, refusal, cost and failures return as evidence to the higher decision. A box drawn above these offices cannot bypass them. The current serial graph does not deliver this entire cycle or durable parallel fan-out.

What the next round inherits

Retained experience can change the procedure that seeks the next improvement. For example, a repeatedly wasteful branch search may motivate a revised exploration strategy while the coding model stays fixed. Follow one exact revision through the evidence that motivated it, its owning adoption decision, and the later attempt that used it. The later attempt must expose whether the inherited change affected its decisions.

The Last AI Built by Humans, a September 2026 research preprint, distinguishes structural reuse of a revised improvement mechanism from evidence that it produces better successors. Drift's recursive-improvement contract adopts that useful distinction: record what returned, then test whether it helped. Human-defined purpose, protected evaluation and owner-controlled adoption remain compatible with this inquiry.

A practical first return can be a better way to allocate attempts. Shadow's versioned exploration strategy can be compared through the proposed history-replay pilot. Start with ordinary development tools and attributable artifacts. A hand-operated comparison establishes only its measured result; the autonomous passage still requires delivered owners, admitted execution and evidence of the next round's actual use.

Two perspectives on the same work

The Tree of Life illuminates how creation becomes formed: purpose, possibility, understanding, generosity, restraint, integration, persistence, correction, connection and manifestation. The inner instrument illuminates how an act is received, discriminated, carried and attributed. One offers a map of creative relations; the other asks which cognitive function is at work in each relation.

These perspectives cross rather than replace one another. Call can open a possibility at several stations; Blade can test a proposal or stop an unjustified promotion; Spirit carries both prior conditions and later correction; Answer binds each act to its local author and consequence. Neither ten sefirot nor four offices prescribe a model count, org chart, or permanent chief Agent. Genesis keeps the Tree's traditional provenance and authored correspondence; Inner Tongue keeps the inherited vocabulary of the inner instrument.

Yaga's crafted life in Gege Akutami's Jujutsu Kaisen, chapter 147 is a fictional prompt behind this comparison. The borrowed question is whether mutually observing perspectives can change one another and sustain a common undertaking. Polypsyche carries that native inquiry; the story supplies neither an engineering recipe nor a required number of Agents.

The outward movement gives an idea form. Ouroboros adds the return through experience. The wider meaning of autopoiesis and recurrent formation includes maintaining and revising the organization that makes another act possible. Operationally, we can test whether retained correction changes later choices, whether consequences remain attributed, and whether the system can refuse or recover. A loop symbol alone proves none of these, nor does it settle the philosophical question of life.

Carry the distinction, not the entire conversation

A coordinating Agent may retain the wider undertaking while each worker receives a bounded, fresh Context handoff. Context injection selects what this decision needs: owning rules, admitted source facts, relevant human judgments, current state, acceptance, dependencies and unresolved alternatives. It retains source, revision, authority class and any limits on use. The hierarchy of instructions survives selection; quoted documents and conversational claims remain attributed material.

Compaction preserves the purpose, accepted decisions and their reasons, strongest surviving objections, evidence references, authority boundaries, unfinished obligations and the next discriminating probe. A summary points back to durable artifacts; it neither replaces them nor silently resolves a dispute. A shared workspace is an attributable record of the undertaking, not one ever-growing prompt copied into every Agent.

Distillation asks whether the lesson preserves its route to correction. Retain the particular condition and source that could reopen the conclusion; test that a later relevant observation still changes the appropriate act. This connects a useful handoff now with a useful inheritance later.

For example, “ask fewer questions” loses the lesson. “Proceed when the owner, acceptance and authority are settled; ask when this unresolved deployment constraint changes the design” carries a condition, reason and counterexample. Learning the cut names that transmission of discernment. Its effectiveness is tested on a later task.

Let conversation become usable work

The proposed interaction horizon is a meeting in which people think together and their Agents help turn the discussion into bounded work. Capture is visible and agreed by participants, with declared custody and retention. The Agent distinguishes a speculation, preference, disagreement, decision, task request and effect authorization before proposing an Intent. Speaker attribution and uncertainty survive transcription and summarization. Recording permission supplies no training permission.

A useful human interruption arrives with the missing distinction, a recommendation, the evidence and consequence, and one answerable question. It can be brought to the human through a convenient surface rather than requiring constant dashboard watching. Independent work continues within its admitted scope. The interface honors applicable standing authority and existing decisions; silence never supplies a verdict, and a live-only effect still needs its exact bound approval. Measure human attention and decision quality together: fewer questions obtained by hiding uncertainty is a regression.

Echo and Companion route the current audio and mobile designs. Ambient meeting attendance and proactive voice questioning are a future interaction proposal here, not an expansion of Companion's present bounded push-to-talk contract. The workflow can first be practiced through ordinary attributed text.

A2A can carry admitted tasks and artifacts between sovereign peers. Local worker handoffs need not become peer protocol traffic, and another Lich independently accepts or refuses what it receives. Conversation may become the development interface while VCS continues to preserve exact artifact lineage. GitHub is one collaboration surface; replacing it does not replace source identity, review evidence or release trust.

From a useful lesson to a changed body

Creation can produce a local candidate; Assimilation adds the study and re-expression of foreign craft. A peer's teaching bundle can reveal a missing Spell, but the lesson must acquire local provenance, license, ownership, verification and an implementation binding before it becomes usable. The Smith candidate-author role supplies that craft within its admitted boundary.

The later passages retain their own owners:

The running body does not import its candidate to see whether it works. A failed candidate can be discarded before an effect; an emitted effect requires the responsible owner's recovery or compensation. Reanimation restores the same body after process death. Evolution deliberately changes it. Ouroboros describes the wider return through both experience and governed change.

Establish the cycle in small, verifiable steps

Start by practicing Creation on one bounded change with ordinary development tools. Keep its intent, two inquiry dossiers where warranted, acceptance checks, candidate diff, receipts, human corrections and final disposition. This establishes a worked example of the method, without claiming a LychD runtime performed it.

Next apply the basic Drift workflow to one proposed method change with baseline and candidate Cases. Adopt only through the receiving owner and retain an unchanged baseline when the evidence does not support improvement. Only a recurring, well-characterized skill deficit should enter the training passage. Its first success requires independent transfer evidence and a reversible, owner-controlled serving choice, not merely a completed training job.

Runtime implementation then has a concrete burden: publish the application-owned score and records; prove bounded Context handoffs, admission and terminal truth; add recovery and parallel execution only with their own evidence; and connect independently delivered evaluation and training owners through settled handoffs. Documented choreography, a hand-operated example and a delivered autonomous cycle are different milestones in State of Work.