Smith

Purpose is the hammer.

Pattern is the anvil.

Consent is the seal.

What is worthy becomes organ.

Smith is the Assimilation Extension Domain. Its reference candidate-author Agent turns an admitted external pattern, protocol, defect, or need into attributable candidate code, schemas, migrations, tests, documentation, and packaging inputs within a bounded Lab coordinate. That work can be examined; it has not entered the body. A candidate is not an organ.

Maturity: Designed. No candidate-author Agent or end-to-end Assimilation path is delivered. ADR 35 owns the architecture and full protocol; State of Work owns delivery.

The hammer has no crown

Admission comes first. Scout may acquire exact material, but the custody owner must validate and admit its bytes before Smith can use them; another source/custody route may supply the same settled handoff. The Assimilation Dossier carries its source identity and revision, acquisition path, license and notice duties, local base, transformations, Smith/model/tool/human authorship, unresolved gaps, and maintenance lineage. Material without established identity, provenance, or license may inform study but cannot request promotion.

The candidate-author Agent may read admitted source and relevant Core code, then write only to permitted Lab paths. It can submit typed requests, but receives no ambient access to the active checkout, dependency locks, secrets, migrations, package publication, or host lifecycle.

The declared harness records deterministic facts such as lint, type, build, or test results; Drift owns calibrated quality and comparative claims. The required HitL or eligible policy decision supplies promotion consent. Forge constructs package or image artifacts from reviewed inputs, while Codex, migration, and lifecycle owners perform their own effects. A passing check supports only its declared predicate; ADR 35 keeps the exhaustive authority matrix.

Protocol stages, not a second coordinator

exact intent and admitted source
→ Dossier and isolated Lab candidate
→ deterministic receipts and Drift findings
→ promotion request
→ required HitL/policy and target-owner decisions
→ owned packaging and live effects
→ reassembly and observation

The path is compact, but its records are not disposable. Source revision, license, transformations, candidate parentage, tools and providers, human edits, checks, failures, and the final decision remain attributable.

Smith is not a Composition, Suite, or second workflow coordinator. It defines the candidate-author role; an exact application Pattern must select a registered AgentSpec satisfying it. Spellweaver may admit and execute that Pattern's pinned Scroll; each verification, consent, packaging, migration, and activation owner later acts from a settled typed request. No exact application Pattern or Suite for end-to-end Assimilation is defined yet, so the reference protocol remains non-executable.

Each arrow above is a governance dependency between separately owned, already-settled records. It is not one hidden Run that waits for, retries, cancels, recovers, or jointly settles every owner. A future application Pattern may own one bounded candidate-author job; a separately named Suite is required if one reusable promise must actively coordinate multiple Composition Invocations.

Repair and evolution

The Creation workflow gives candidate authors a repeatable method from intent and evidence through construction, verification and documented disposition. The wider Ouroboros map returns consequences to evaluation and separately admitted correction, including teaching, training and later body generations.

A candidate-author Agent may prepare a pinned update or propose a bounded correction in Shadow. Each revision retains parentage and repeats every invalidated check; the author cannot certify its repair or widen its budget.

If a required migration rehearsal still fails when that budget expires, the attempt records explicit non-completion, preserves the Dossier, candidate, and failure receipts, and leaves the running body unchanged. Any later attempt receives a new candidate identity and re-enters the affected gates. No autonomous loop may join authorship, judgment, consent, packaging, migration, or activation into a self-certified result.