Ouroboros

Ouroboros is the return of consequence into the next act of creation. A LichThe AssistantThe Assistant 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, ContextBriefing PackBriefing Pack, 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.

Follow the return through Creation, workflow evaluation, or discernment training, according to what the encounter has shown needs to change. This map introduces no autonomous coordinator or registered PatternWorkflowWorkflow. 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: tests and review]
    D -. declared evaluation .-> Q[Drift: candidate findings]
    Q --> V
    V --> P[Owned decision and effect]
    V -- failure or rejection --> O
    P --> O[Retain consequence]
    O --> E[Drift: result or workflow findings]
    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 Q,O,E,C,R,S evaluation
    class T,A,B training

Blue follows one piece of work. Red marks evaluation: first of the candidate before promotion where required, then of its observed consequences or the method that produced it. Each is a distinct evaluation subject with its own declared evidence. Tests and review keep their separate roles, and a favorable inferred judgment cannot erase a failed deterministic gate. DriftEvaluatorEvaluator has its own jurisdiction, but evaluation belongs both within SDLC and across its improvement cycle.

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 RunJob RecordJob Record spanning all three cycles. An eventual application must publish its exact PatternWorkflowWorkflow; live coordination across Composition-owned InvocationsJob RequestsJob Requests needs a named Suite.

Desire, judgment and inheritance

The Paperclip Maximizer names the desire to become more; the Synchronic Syncretizer names Evolution's judgment of what a successor should inherit. Their tension belongs within the existing offices. It does not create a universal Ouroboros coordinator or make every acquisition an improvement.

Make the return concrete through one candidate and a declared comparison. Select the relevant predecessor history and make its omissions visible. Gather verification, independent findings and affected-owner judgments, then give each obligation a reasoned disposition: retained, reconciled, replaced or rejected. Reconciliation sends a new combined candidate back to Creation. Replacement identifies the consumers and work that must transition. An unresolved contradiction returns a bounded question or a refusal; it does not quietly become consent. Once settled, the result can support a later Promotion Request, whose effects still require their receiving owners.

For example, a successor may remove an insecure legacy contract while preserving an unrelated private extension. The old contract's failing check is retained as a fact. Changing the declared contract requires the responsible owner's separate acceptance, consumer/work disposition and verification of the new candidate; an overall quality gain cannot erase the failure. Likewise, a blocked replacement is no reason to continue executing a revoked unsafe baseline.

This gives the language of emergence a testable foothold: later choices may inherit useful correction without losing the reasons, conflicts and consequences that made it useful. The philosophical question of life remains open; no loop diagram or adoption record resolves it.

Run an offline historical comparison

The comparison mechanism checks one caller-admitted boundary and proposal. Its evolution-comparison@1 packet pins base, candidate, policy and selected history through ArtifactRefs; each historical obligation names its owner and inherited contract. Every obligation needs a reasoned retain, reconcile, replace or reject disposition. Bind the proposal and each evidence summary to admission_digest(admission). The focused examples exercise replacement of an insecure v1 while retaining extension C, a changed combined candidate, missing evidence, conflicting results and exact replay. Their receipt claims are synthetic fixtures.

From a configured source checkout, feed one admitted JSON packet to the offline utility:

uv run python scripts/compare_evolution.py < comparison.json

It accepts at most 1 MiB and emits a bounded report. Exit 0 means comparison_complete or rejection_recorded; inspect the outcome, because a recorded rejection accepts no candidate. Exit 1 means blocked; exit 2 refuses malformed, duplicate-key, nonfinite or oversized input with a fixed diagnostic. No public PulseCommand Line (CLI)Command Line (CLI) command is added.

The utility evaluates attributed receipt summaries without reading the referenced bytes. It therefore proves no test result, issuer identity, independence, DriftEvaluatorEvaluator Outcome or promotion eligibility; a summary is a claim, not the receipt's authenticated contents. Old-baseline failures remain in the pinned history. Active summaries concern this exact candidate, and its failing checks still block a non-rejection disposition. The caller must retain the packet and its references: a deterministic digest supplies neither durable custody nor an adoption ledger. State of Work distinguishes this mechanism from the still-designed native lifecycle and target-owner effects.

Carry the distinction, not the entire conversation

First decide what the next attempt needs. A missing fact, a damaged handoff, and a skill that fails across unfamiliar tasks call for different returns:

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 prepares that bounded handoff by preserving purpose, accepted decisions and their reasons, the strongest surviving objections, evidence references, authority boundaries, unfinished obligations and the next discriminating probe. It points back to durable artifacts; it neither replaces them nor silently resolves a dispute. The shared workspace remains an attributable record of the undertaking, rather than an 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.

What the next round inherits

The next improvement may come from changing how attempts are organized while leaving the coding model fixed. A repeatedly wasteful branch search, for example, can motivate a revised exploration strategy. Follow that exact revision from its motivating evidence through its owning adoption decision to the later attempt that used it. That 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. ShadowWhat-if SimulatorWhat-if Simulator'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.

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 ScrollWorkflow VersionWorkflow Version revision and a later InvocationJob RequestJob Request.

The Graph owns executable topology and checkpoints. SpellweaverWorkflow EngineWorkflow Engine 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.

Let conversation become usable work

One proposed setting for this work is a meeting where people think together and their Agents help turn discussion into bounded tasks. Capture is visible and agreed by participants, with declared custody and retention. Before proposing ana IntentRequestRequest, the Agent distinguishes speculation, preference, disagreement, decision, task request and effect authorization. Speaker attribution and uncertainty survive transcription and summarization. Permission to record supplies no permission to train.

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 LichThe AssistantThe Assistant 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.

One undertaking, several conversation surfaces

A joined workbench can keep an Atlas Project and its concerns beside the Bridge conversation, with exact RunsJob RecordsJob Records opening their evidence in OrbRun InspectorRun Inspector. AtlasProject BoardProject Board keeps the undertaking and captured judgments; BridgeChatChat keeps the conversation and its admitted RunJob Record references. The RunJob Record ledger owns RunJob Record identity and status. A reference links them without silently injecting the brief into ContextBriefing PackBriefing Pack or authorizing work. Supply an exact, explicitly admitted snapshot when a task needs that context. An Evolution comparison remains its own owner's result, not a persuasive chat message promoted into a verdict.

Begin with one operator-admitted issue snapshot, an existing Project and an explicitly selected session. A later GitHub or Discord adapter maps source identity and observations to those native records; it does not introduce a second backlog or development authority. Transport redelivery, issue identity, accepted intent and RunJob Record identity are different keys. GitHub's webhook guidance retains the same delivery identifier on redelivery. Changed bytes under an admitted observation identity refuse; an accepted issue edit creates a new native revision and cannot rewrite an already admitted RunJob Record or its judged basis.

Provider authentication establishes where a delivery came from, not the sender's LychD authority. The receiver checks local policy for the requested work separately, then checks again before later admission or effects. Never forward external prose under the bootstrap operator's ambient privileges. Replies have their own effect boundary: an external reply binds result, destination, payload and delivery identity under its credential-bearing effect owner. A lost send response remains unknown until reconciled; it cannot justify rerunning cognition or blindly posting again. A worker-job publication receipt is not proof of an external comment.

Several PCs can be clients of one resident authority through a collaboration surface. Physical workers under one sovereign plane follow Multinode; independent sovereign peers follow A2A. Neither follows merely from using two PCs. Remote AltarControl PanelControl Panel identity, automatic source-to-session replay and native development lifecycle ownership retain their own delivery gates; the current local operator surface does not supply a remote authorization protocol. Development bootstrap keeps the B7 ownership transfer separate from a connector or a desktop timer.

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 SpellStepStep, 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:

Candidate verification happens outside the running body; that body does not import its candidate to see whether it works. Before an effect, a failed candidate can be discarded. After an effect has been emitted, recovery or compensation belongs to the responsible owner. ReanimationCrash RecoveryCrash Recovery restores the same body after process death, whereas Evolution deliberately changes it. Ouroboros follows the wider return through experience and governed change.

Two perspectives on the same work

Creation draws exploration, adversarial comparison, human judgment, implementation, evaluation, and a later training return into one undertaking. Each changes what the others can receive. The Tree reveals where their relations need a clearer decision, a better handoff, or a correction before the whole can hold together.

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; Blademind officemind office can test a proposal or stop an unjustified promotion; Spiritmind office 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 sources and creative relations; Inner Tongue keeps the inherited vocabulary of the inner instrument.

Polypsyche carries the inquiry into mutually observing perspectives: how can they change one another and sustain a common undertaking? The Tree's relations within relations give specialization a way to preserve participation in that whole.

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.

Establish the cycle in small, verifiable steps

Development bootstrap gives the concrete operator campaign, staged delegation gates, review-capacity policy and first implementation queue for this passage.

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 DriftEvaluatorEvaluator 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.

These practiced handoffs give runtime implementation a concrete burden. Publish the application-owned score and records, then prove bounded ContextBriefing PackBriefing Pack handoffs, admission and terminal truth. Recovery and parallel execution each need their own evidence. Evaluation and training owners must be independently delivered and connected through settled handoffs. State of Work keeps documented choreography, a hand-operated example and a delivered autonomous cycle as different milestones.