setupEmbeddings constructs a client at boot and holds it on b.embeddings, but no production code reads that field yet, so a resolved models.embedding role currently produces a client whose only observable effect is a boot log line. The document already notes that no curator consumes a Sampler yet; it now says the same of the embeddings client, so the inert state is stated rather than implied. Both are prerequisites waiting on #437, not unwired defects.
4.8 KiB
Plugins and Extensions
Status: Approved foundation
Date: 2026-07-28
Tracking issue: #73
Plugin framework
The core plugin domain lives under internal/domain/plugin. It owns:
- plugin identity and metadata;
- discovery and registration contracts;
- lifecycle rules;
- capability registration;
- validation and compatibility rules.
The generic plugin contract remains metadata-only. Functionality is exposed through narrow typed capability contracts with an owning registry or manager.
Workflow plugins belong to the Workflow capability family. The Workflow domain
at internal/domain/workflow owns their typed registration, validation,
versioning, definition, and execution contracts. The generic plugin domain may
provide plugin identity, discovery, compatibility, and lifecycle mechanics, but
it MUST NOT define Workflow semantics or expose untyped Workflow hooks.
Plugin implementations
First-party plugins are self-contained vertical modules under
plugins/<plugin>.
A plugin:
- owns its implementation, settings, templates, assets, and tests;
- receives only explicitly supplied contracts and services;
- MUST NOT receive daemon internals, a service locator, or unrestricted application access;
- MUST NOT import arbitrary infrastructure or application composition code;
- MAY use approved domain and shared application contracts;
- MUST remain removable without changes to unrelated domains.
Plugins may be internally cohesive like small services. They do not become network services without a concrete security or operational reason.
Event sources and reactions
archie-core-7d5u.1 asked whether extensions should react to events
in-process through typed capability families (this document's model) or
out-of-process like a generic DispatchEvent dispatcher. Decided 2026-08-22
in docs/prds/event-sources-and-reactions.md: in-process typed families,
confirming this document's model rather than amending it. The forge webhook
receiver (internal/forge/webhook, see ARCHITECTURE.md's "Webhook intake"
section) and the EDA playbook engine's Module action position
(docs/prds/eda-playbook-engine.md, internal/domain/eda/module) are the
shipped instances of that decision -- each is a narrow typed contract with an
owning registry, not a generic event hook. The playbook engine's Channel and
Forge action positions are designed but not yet implemented (open
investigation archie-core-t2db.19); when they land they follow the same
model, not a new one.
Curator surprisal sampling
Decided 2026-08-05, wave 1 landed 2026-09-05 — the curator engine family (epic #435) selects which memories deserve agentic attention via surprisal-based sampling: score memories by how surprising they are and spend the sampled reasoner's agentic budget on the most surprising items.
The prerequisites are built: the embeddings capability
(#436, internal/domain/embedding contract +
internal/infrastructure/embedding implementation, config-driven via
models.embedding) and the wave-1 Sampler strategy seam
(internal/domain/sampling -- not internal/curator, see
docs/prds/curator-sampler-wave1.md for the settled design and tracking)
with four
cheap, embedding-free strategies (recency, random, all, staleness proxy).
No curator consumes a Sampler yet, and the embeddings client is likewise
deliberately inert: setupEmbeddings constructs it at boot and holds it on
b.embeddings, but no production code reads that field yet, so a resolved
models.embedding role currently produces a client whose only observable
effect is a boot log line. Both are prerequisites waiting on #437, not
unwired defects.
Still deferred: #437, the embedding-backed surprisal strategy, which depends on the above and on #407. Requirements for that deferred work, so it can be picked up without re-deriving the design:
- A
Samplerimplementation behind the same interface as the cheap strategies; selection deterministic given fixed inputs. - Algorithm: sample up to a candidate cap; build a k-NN graph over embedding vectors; row-normalize the adjacency with self-loops; power-iterate to the stationary distribution; surprisal = −log(stationary probability of the nearest point); select the highest-surprisal items.
- Degradation: content without an embedding is skipped; an embedding failure aborts sampling and falls back to free exploration — a sampling failure must never fail or crash a curator pass.
- Cost bound: the graph build is quadratic in the candidate cap; the cap must be a named constant with a documented bound.