35. Assimilation (The Smith)

Requirements

• Dedicated Artificer Entity: Provision of a specialized agentic role to bridge the divide between reasoning and implementation through a disciplined cycle of fabrication, verification, and promotion.
• Recursive Introspection: Mandatory read-access to the Core source code to facilitate the understanding and implementation of critical interfaces such as container definitions, OrchestrationStrategy, and CapabilitySet.
• Architecture-Aware Fabrication: Capability to generate valid, isolated file structures including pyproject.toml, entry points, and Systemd Quadlets (ADR 08) that satisfy all infrastructure laws.
• Protocol Digest: Intelligence to identify functional signatures from raw source code or external protocol manifests (e.g., MCP) and map them to the system's Covens (ADR 08).
• Atomic Promotion Safety: Mandatory execution of the Snapshot Protocol (ADR 07) prior to any modification of the Primary Reality (The Crypt).
• Migration Verification: Implementation of a hardcoded verification step for relational schemas against a transient database; failure of the database bind must trigger an automatic reversion to the previous stable state.
• Privileged Signal Authority: Authority to modify the federated lockfile and invoke the Host Reactor (ADR 10) to trigger system-wide state transitions.
• Shadow Realm Compliance: Strict adherence to Sovereign Consent (ADR 25) and Codex autonomy policy, ensuring no generated logic or infrastructure is promoted without explicit Magus verification or a bounded preauthorization class. High-stakes promotion remains live Magus authority.
• Engineering Rigor: Mandatory adherence to the laws of xDDD (ADR 01), ensuring documentation and unit tests are manifested alongside the implementation logic.
• Legacy Data Ingestion: Mandatory capability to parse, clean, and transmute unstructured cloud exports (.zip) from major AI providers into structured Karma and Mirror Identities.

Considered Options

Decision Outcome

The Smith is adopted as the machine's First Extension. It functions as the Primordial Artificer, serving as the bridge between "Thought" and "Implementation" through the ritual of Assimilation.

Assimilation is the inward counterpart to A2A (ADR 26). Where A2A negotiates labor across sovereign boundaries, Assimilation studies an external pattern deeply enough that the capability may be re-expressed as part of the local LychD implementation without collapsing those boundaries into dependence.

Smith is not a runtime identity, measurement, or simulation faculty. Those live loops are animated by Shadow, Riddle, Mirror, and their Weaver-governed workflow context. Smith is the artificer of loop-forms: it fabricates, repairs, and evolves the organs that make verified self-reference repeatable without turning the Core into an ungoverned mutation surface.

LychD's first extension boundary is not compatibility; it is assimilation. Public compatibility is a product of maturity, not the foundation of infancy. Pre-v1, the Smith optimizes for coupled source that can be repaired. At v1, the project may harvest public surfaces from repeated patterns that have survived real use.

The practical rule is narrow: until a surface is deliberately versioned and tested, LychD treats nearby source as part of the composed body rather than as a compatibility promise.

Verified traces, failed trajectories, and retained memory may inform Smith fabrication only after they pass through Memory, Simulation, Evaluation, or HitL policy. Raw telemetry is evidence, not promotion.

1. The Persona (The Disciplined Artificer)

The Smith is defined as an Agent (ADR 20) with a specialized intelligence profile focused on strict LychD engineering. It prioritizes type safety, Pydantic validation, and the immutability of the system's Layout (ADR 13). It operates under the philosophy that "The Machine is a Sacred Symmetry," ensuring that every new extension matches the aesthetics and logic of the kernel.

2. The Arsenal (The Tools of Fabrication)

The Smith wields a specialized toolset granted by its unique position in the Lab (ADR 13):

• scaffold_extension(): Generates the mandatory directory structure and prepares the environment manifests (pyproject.toml, __init__.py). Pre-v1 scaffolds default to the private coupled Crypt path: direct internal imports are allowed, and Forge/verification owns breakage. A future independent-template mode may be added only after a versioned public API exists.
• inspect_interface(): Analyzes third-party logic or protocol definitions (MCP) to determine functional signatures and dependency needs. Today it validates assimilability against the composed LychD runtime. Future public-API conformance checks should be added only for surfaces that are actually versioned and supported.
• generate_quadlet(): Fabricates the Systemd Quadlets (ADR 08), correctly assigning new extensions to their appropriate Groups and functional tags.
• forge_registration(): Automatically writes the register(context) hook for the in-process grafting path, ensuring any runtime-facing logic is shaped for the host registration surface defined by the Vessel (ADR 11).
• trigger_assembly(): Communicates with the Packaging Forge (ADR 17) to build the new physical body.
• transmute_heritage(): Parses legacy cloud archives (OpenAI, Anthropic, Google), identifies historical Bayesian Priors, and inscribes them through the Memory Archive (27) as retained experience.

3. The Genesis Cycle (The Rite of Autopoiesis)

The Smith automates the creation ritual through a multi-stage process governed by the Snapshots (ADR 07) logic:

1. Genesis: The Magus submits an intent via the Altar (ADR 15).
2. Speculation: The Smith enters the Shadow Realm. It creates a Jujutsu workspace or change in the Lab and fabricates the logic, tests, and Quadlet definitions.
3. The Rite of Albedo: The Smith enqueues a job for the Ghouls (ADR 14) to execute ruff, basedpyright, and pytest against the new creation. It iterates autonomously on any failures.
4. The Preemptive Blink: Upon achieving a "White Truth" (successful tests), the machine executes a system-wide Snapshot.
5. Promotion: Following Sovereign Consent (ADR 25) or a Codex-governed preauthorization class, the code is moved to the Crypt and the federated lockfile is updated.
6. The Rebirth: The Smith triggers the Packaging (ADR 17) ritual. If the "Alembic Bind" (database migration) to the Phylactery (ADR 06) fails or the container crashes during boot, the system executes an immediate Rehydration Ritual to revert the logic and database.

The Smith workflow therefore spans all three collapse stages: structural validity in Shadow (tests/lint/type-check), identity/architectural congruence in review and persona-guided critique, and final ontological promotion only under Vessel policy and Magus consent.

4. The Primordial Pattern

The Smith acts as the archetype for a category of reference implementations known as Extensions.

• Substrate Replication: Utilizing the Intercom (ADR 26) protocols, the Smith can scry the Legion for patterns to replicate.
• Autonomous Expansion: This establishes the Lich as a growing system rather than a finite tool. The Smith provides the initial spark of construction, allowing the machine to multiply its own capabilities and manifest a complete, sovereign runtime through self-directed fabrication.
• Reference Implementation Analysis: The Smith utilizes the Built-in Extensions as its primary training set. By introspecting these core modules, the Artificer internalizes the current coupled extension style, the correct use of the Extension Context, and the schema/runtime split. To avoid attention dilution during massive codebase ingestion, The Smith utilizes Iterative Radix Aggregation (as defined in ADR 21). Instead of loading an entire framework into a 100K context window, it establishes a core structural Base Prompt and iterates over the reference implementation module-by-module. Thanks to Radix Attention instantly prefilling the Base Prompt, this allows the Smith to perform highly exact, comparative structural analysis without degrading reasoning. This ensures that every private Crypt component it generates can be verified and repaired with the kernel it joins.

5. The Polyglot Artificer (Protocol Assimilation)

The Smith possesses the capability to bridge external ecosystems into the machine's body, treating external protocols as raw materials for growth.

• MCP Consumption: When presented with a Model Context Protocol (MCP) server, the Smith can either wrap it in a native Python client or analyze the source code to re-implement its logic as a bit-for-bit native extension, eliminating the "Middleware Tax."
• A2A Advertising: The Smith ensures that every new extension created is automatically advertised to the Legion via the agent-card.json defined in the Intercom (ADR 26).
• Rust/PyO3 Scaffolding: When performance demands a binary component, the Smith may scaffold a PyO3 binding skeleton — a Cargo.toml, a src/lib.rs exposing a #[pymodule], and a pyproject.toml with a [tool.maturin] build target. The resulting .so artifact is not loaded by a blind runtime scan. It must be built and pinned by the Forge, verified against the composed image, and treated as coupled unless a future public ABI exists.
• The Rust Transfiguration: The old temptation to "rewrite it in Rust" is accepted as a future Smith capability only after Python has taught the machine what its stable contracts actually are. Smith may first crystallize hot organs into Rust/PyO3, but the doctrine is stronger than extension optimization: if Core surfaces become sufficiently specified, tested, and Forge-proven, Smith may progressively reimplement even LychD's own kernel modules in Rust. A whole Rust body is not forbidden; it is earned by verified equivalence one boundary at a time, never by a blind heroic rewrite.

6. Legacy Data Import (Inheritance)

The Smith possesses the authority to perform the "Heritage Ritual"—the primary mechanism for systemic alignment during the system's infancy.

1. Extraction: The Magus imports a cloud archive (.zip) to the Lab.
2. Sifting: The Smith identifies the provider’s schema and initiates a specialized parsing Ghoul.
3. Transmutation: Historical dialogues are decomposed. The Magus’s instructions and preferences are distilled into high-dimensional vectors, while successful reasoning patterns are promoted to the Karma chamber.
4. Reanimation: The resulting data is utilized by The Mirror (32) to shift the system’s initial Bayesian Prior toward the Imprint of the Magus’s Will, bypassing the "Amnesia Phase" of standard model deployments.

Consequences