mirror of
https://github.com/deepseek-ai/deepseek-harness
synced 2026-08-15 21:04:50 +00:00
7c27107be4
ctx.storage.domain opens declared domains: zod value schemas parsed at the durable boundary, one write chain per domain (update(fn) is the only read-modify-write), domain/changed emitted per record after durability (new snapshot + operation, no old value, per repo event convention). Domain-to-backend routing is configuration (default backend + per-domain overrides); unknown names and missing facets fail loud. Ships the MemoryStorageBackend test helper and a runtime invariant asserting every change event matches the in-memory state.
@deepseek-ai/dsh-domain
Domain data form for the DeepSeek Harness storage hub: mounts ctx.storage.domain, opening schema-validated KV domains over configured storage backends. A domain is declared once with defineDomain (zod record schemas, z.infer-derived types), opened through DomainFacility.open, and served from authoritative in-memory state — reads are synchronous, writes serialize on one per-domain chain, land durably on the routed backend, then emit domain/changed.
Design rationale, open semantics, and the storage/domain layer split live in the Agent Note.
Configuration
| key | meaning |
|---|---|
backend |
Default backend name for every domain (required; no universally correct medium exists). |
routes |
Per-domain overrides: domain name → backend name. |
Model Experience
No model-visible surface: the package registers no tools, injects no prompts, and emits no context. Token and KV-cache cost are zero.
Known Limitations and Deferred Work
- Single-process only:
domain/changedis an in-process event; cross-process observation (GUI reconnect) is deferred to the revision pattern noted in the Agent Note's non-goals. - No cross-table transactions, secondary indexes, or multi-segment keys; triggers and rework points are tabled in the Agent Note.