stack/docs/tess/M4-003-OPERATOR-PLUGIN-SKETCH.md

TESS-M4-003 Operator Plugin Sketch

Memory/retrieval slice — TESS-MEM-001

Introduce a transport-neutral OperatorMemoryPlugin in packages/memory. The plugin receives a server-derived {tenantId, ownerId, sessionId} scope and delegates to a registered MemoryAdapter; callers cannot select an adapter or namespace. Its operations are capture, search, recent, stats, and startupContext. Results carry provenance and namespace metadata. Capture/redaction occurs before adapter persistence; startup context is bounded and ordered so project/flat-file truth can take precedence over retrieved material.

Registration remains replaceable-adapter based: registerOperatorMemoryAdapter(kind, factory) and createOperatorMemoryPlugin(config) resolve a configured adapter. Identity and namespace are configuration/scope data; no interaction-agent name is embedded in keys or defaults.

Remaining plugin foundations — TESS-PLG-001

• packages/agent: capability descriptors for runtime bootstrap, durable inbox/state hooks, and read-only fleet diagnostics. Each capability advertises supported operations and fails closed when absent.
• packages/mosaic: a catalog/registration surface for GitOps, fleet diagnostics, runtime bootstrap, Discord, and MCP/skill discovery. Catalog entries describe authority, input schema, and safe/read-only status; they do not invoke provider transports directly.
• Gateway/channel adapters consume these contracts through server-derived actor/tenant context and durable session state, preserving the replaceable-adapter boundary.

First implementation boundary

The first PR slice should add the operator-memory plugin contract, config-driven factory registration, scope isolation, provenance-bearing retrieval, and tests for namespace isolation plus a differently named configured instance. Durable inbox/outbox remains owned by the existing DurableSessionCoordinator; this plugin only supplies bounded context/capture at lifecycle boundaries.