Extensions

In plain words: Plug-in areas overview

4 min read 15 glossary terms 25 connected pages

The short version written for the Snayu team

A map of the fifteen plug-in areas (Extension Domains) where LychD can grow, such as web fetching, workflows, evaluation, training, voice and vision, and how extension packages register into them.

Why read it: Start here before writing or reviewing any extension, to learn which area owns which job and what registering a package does and does not allow.

1An area on the map is a responsibility boundary, not a promise that code exists or works.
2Extension packages are selected explicitly and register via register(context); there is no scanning, hot-load or hot-unload.
3Changing extension code or selection needs a new body generation; no area can promote its own result or grant itself privileges.

Words on this page, decoded click one for its card

Where it sits in LychD

Plug-in Area Extension Domain

Fifteen named areas where new abilities can be plugged in: web, voice, vision, security and more.

It's like: Departments in a company. New hires join a department; the department's rules apply.

Click a dot to open that part's card.

Glossary page On the system map In the network

In this section 17 pages

Smith Code assimilation agent The planned agent (Smith) that turns an admitted outside pattern, protocol, defect or need into candidate code, tests and docs inside an isolated lab, with full source, license and authorship records. open → Spellweaver Workflow engine The workflow engine (Spellweaver) that validates immutable workflow versions (Scrolls), admits their execution, and keeps them intact through pauses, resumes and endings. Lists the current fixed workflows and how to configure the Chat workflow. open → Oculus Observability and evidence tracing The planned observability area (Oculus) for tracing a Run across state, approvals, tools, readiness and effects, while keeping records, observations, derivations and judgments clearly distinct. Today the read-only Run Inspector (Orb) covers part of this. open → Soulforge Model trainer overview The planned training area (Model Trainer, or Soulforge) that keeps an unbroken record from admitted data and base model through a training run to evaluated candidate weights, in four separate passages. open → Drift Evaluator overview The planned evaluation area (Evaluator, or Drift) that turns a declared goal into test cases and rubrics, runs trials against an exact version, and returns findings that keep uncertainty, without authority to act on them. open → Scout Web fetcher The web acquisition area (Web Fetcher, or Scout) that carries each search, fetch, extract, render or interaction attempt under its own grant and budget, and returns attributed external material, not truth. open → Tether Private network link (WireGuard) The planned private-reachability area (Tether) that would use WireGuard to open exact private network paths between hosts, without granting any application authority. open → Veil Public ingress proxy The planned edge proxy area (Veil), using Caddy by default, that would terminate TLS, clean up hostile request metadata and expose only declared routes to backends that still check authority themselves. open → Ward Security desk: identity and permissions The core authority (Security Desk, or Ward) for authenticating callers and authorizing each exact action, covering credentials, principals, ID badges (Sigils) and grants, and rechecking permission right before every effect. open → Prism Vision and media overview The vision and media area (Prism) that takes admitted images, documents and video through bounded operations, OCR, detection, generation, 3D and motion, always linking results back to the exact source. open → Echo Voice: speech in and out The speech area (Voice, or Echo) that follows an utterance from visible push-to-talk capture to transcription, an ordinary agent step, optional speech synthesis and observed delivery. open → Local speech qualification Local speech test probe The engineering probe for testing local speech: audio.cpp with Parakeet and Supertonic, or whisper.cpp for transcription, called over loopback with pinned models, explicit recording and no native LychD integration. open → Speech provider study Speech provider comparison A dated study comparing local and hosted speech-to-text and text-to-speech options for Slovak, Czech and English, with pinned versions, licenses and what still needs measuring. open → Shadow What-if simulator overview The planned area (What-if Simulator, or Shadow) for holding isolated candidate possibilities with exact parentage, assumptions and evidence, so a branch is never mistaken for the real world. open → Mirror Persona keeper and attribution The planned identity area (Persona Keeper, or Mirror) that records which exact persona version, caller, authority and contributors stand behind each act, and how agents are prepared with that identity. open → Toll Payments and service credits The planned optional economics area (Toll) for paying for remote work: quotes, reservations, authorization, a single-signature settlement gate, delivery, refunds and reconciliation, plus local MANA service credits. open → Legion Multi-machine work distribution The planned area (Legion) for spreading work across several machines owned by the same operator, where each node agent keeps final say over its own hardware and can refuse. open →

The original text Underlined words open their plain-English card.

Fifteen arts gather beneath one skin.

Search the web, judge an artifact, train a model candidate, carry a voice: different work needs different organs. The fifteen Extension DomainsPlug-in Areas below say where each responsibility belongs. They map jurisdictions; a name on the map promises neither an installed package nor delivered behavior.

The Federation of Fifteen

Name	Work it owns
Oculus	Evidence and observability: follow bounded observations, derivations, correlations and explicit gaps back to their sources.
Tether	Private reachability: open exact private paths.
Veil	Hostile ingress: terminate TLS and protocols, canonicalize metadata and admit declared routes.
Ward	IAM and authority: resolve principals and recheck current permission over an exact object or effect.
Spellweaver	Workflow: validate SpellStep contracts and ScrollWorkflow Version/PatternWorkflow lifecycle, admit castings and preserve continuity and logical time.
Scout	Web acquisition: bound search, fetch, extraction, rendering and interaction.
Smith	Assimilation: re-express admitted material as attributable candidate code.
Soulforge	Training: bind admitted corpus, base digest, objective, Recipe, Training RunJob Record, evaluation and candidate-weight lineage.
Drift	Evaluation: test exact subjects against declared goals through versioned trials and calibrated findings that retain uncertainty.
Toll	Economics: distinguish quote, authorization, settlement, delivery, refund and reconciliation.
Prism	Visual and spatial grounding: bind observations, transformations, reconstructions and generated forms to exact sources and derivatives, keeping them distinct.
Echo	Speech lifecycle: carry capture, transcription, synthesis and delivery with origin, consent and outcome intact.
Shadow	Possibility lineage: hold isolated candidate worlds with exact parentage, evidence and terminal disposition.
Mirror	Identity: preserve Persona lineage, hydration provenance and attribution.
Legion	Distributed embodiment: fence delegation across operator-owned bodies while each retains authority over its iron.

Consider a source acquired for a candidate change. ScoutWeb Fetcher can obtain the source, but acquisition cannot establish its truth or authorize a wider use. Smith can prepare the candidate, ShadowWhat-if Simulator can hold an isolated alternative, and DriftEvaluator can evaluate it. The responsible owner must still judge whether it may become an effect; none of those contributors can promote its own conclusion or grant privilege.

The same division holds at the system's edges. A private path or admitted route leaves application authority with the service behind it. Oculus observes records without replacing their owners, and MirrorPersona Keeper attributes identity without authorizing the caller. Cooperation joins the offices through these contracts.

Domain, package, and provider

Term	Place in the body
Extension DomainPlug-in Area	One of the fifteen stable user-facing jurisdictions through which the LichAssistant may grow
extension package	Explicitly selected built-in or private CryptData Folder code admitted through `register(context)` and shaped stores
Registrant	Core or one selected extension package performing registration under a host-assigned `registrant_id`
Contribution	A typed addition admitted by one explicit receiving Core office or Extension DomainPlug-in Area while that owner keeps authority
Provider	A concrete engine or service supplying mechanism behind a typed contract

A package can register contributions with several Core offices or Domains. Conversely, one Domain can receive several packages or Providers. These are different relationships, so Activation must name a concrete package or declared instance rather than an abstract Domain. Compositions and Products use and package the resulting contracts while keeping their own responsibilities.

How an organ enters

For a first contribution, follow Extension authoring through the existing Phoenix registration shim, typed RuneService Config File, Quadlet contributor, and configuration test.

The coupled pre-v1 Extension Protocol admits explicitly selected built-in and private CryptData Folder packages through register(context); it neither scans the environment nor discovers arbitrary entry points. Built-ins evolve atomically with Core, while private packages accept refactor breakage. A versioned independent extension-package API and conformance suite remain future work, so an external protocol is the present boundary where process or lifecycle coupling is unacceptable.

After assembly, that selection stays fixed for the VesselEngine Room process. There is no hot-load, hot-replace, or hot-unload. Changing code, package selection, dependencies, or contribution contracts requires a new body generation under Evolution. Compatible PhylacteryMemory Vault records and explicit Reanimation provide continuity into it; volatile extension objects do not migrate. The boot boundary is enforced, while automated Evolution remains Designed.

ADR 05 owns admission and compatibility. State of Work records the five-store surface, its v1 capability attribution, and the remaining lifecycle limits. Selection grants shaped registration—not route, secret, workflow, migration, workload, effect, or automatic activation authority.

How an organ earns permanence

Authorship, tests, and evaluation produce a candidate and evidence for the target owner's promotion decision. Smith, ShadowWhat-if Simulator, and DriftEvaluator cannot promote their own conclusions. Required HitLApproval Step or eligible policy supplies authorization; packaging, migration, activation, and verification remain separately owned effects. Follow the Assimilation passage to prepare that handoff with its failures and uncertainty still attributed.

Automated Smith and Forge promotion is Designed, not delivered. State of Work owns delivery; the Assimilation Covenant owns the fuller passage from bounded candidate work to an accepted organ.