Tianyi Cui
cc24e79cd2
The agent-scope-contexts RFC (implemented) records the decision tree: the dsh-scope primitive over cordis extend/Context.filter/no-op fibers, two-level flat scope with shadowing, restriction/grant semantics, the scoped-dispatch rule with fused helpers, the setup window, and the alternatives (explicit scope params, isolate, event-filtering-only, vendored support) with why each lost. CONTEXT.md pins the glossary. architecture.md gains the Agent Scope section, the dsh-scope spine row, the scoped turn-flow line, and an extension-table row (ceiling 1640→1790: the two-layer registration model is a new architectural axis; additions are condensed to pointers). READMEs of every touched package re-state their scoped facts; the stale structured-runtime README section is replaced by the scoped-registration description.
2.2 KiB
2.2 KiB
Context glossary
Domain vocabulary for the DeepSeek Harness SDK — one canonical term per concept. Terms link with [[name]]; implementation detail stays in the package READMEs and RFCs.
agent-scope
- scope — the unit of per-agent registration: a contribution (tool, prompt section, variable, restriction, listener) is either global (visible to every agent) or scoped (owned by exactly one scope-key). Two levels, flat: nothing inherits down to subagents; subtree behavior is expressed with lineage data, never structure.
- scope key — the opaque identity a scope is keyed by, compared by object identity. The harness convention: a live agent is the key of its own scope.
- agent context (
agent.ctx) — the agent's scoped context; registrations through it are scope-visible AND scope-lifetime (one fact drives both), and listeners on it hear only that agent's dispatches. - scope carrier — the
thisArga scope-filtered dispatch carries (built byscopeTarget); its filter admits untagged listeners plus the subject's own. A subject-less carrier (no key) admits untagged listeners only. - scoped dispatch — the rule: an event about one agent's activity dispatches with that agent's carrier. Events about a registry itself (a tool was added) are registry-subject and stay unfiltered.
- shadowing — most-specific-wins name resolution: a scoped tool/section/variable replaces its same-named global twin for that scope alone. The per-agent persona and per-agent tool-variant mechanism.
- restriction / grant — a restriction (
tools.restrict) masks the GLOBAL tool surface for one scope (compose by intersection); a scoped registration is an explicit grant that bypasses restrictions. A restricted-away tool is absent from the prompt AND refuses execution, indistinguishably from a nonexistent one. - setup window — the creation slot where a creator composes an agent's scoped world (
CreateAgentOptions.setup): after the scope exists and the agent is registered, beforeagent/session-startand the first prompt assembly. Setup registers; it never drives the agent. - lineage — parent/child facts carried as data (
parentSession,subagentDepth); never affects visibility.