deadbyte-mcp 0.8.9 → 0.9.0

package/CONTEXT.md

@@ -0,0 +1,41 @@
+# DEADBYTE MCP Context
+
+This file defines the production vocabulary and invariants. It is context, not authority: observed machine state and signed evidence outrank prose.
+
+## Machine truth
+
+Machine truth is an observed, reproducible fact bound to exact bytes, policy, runtime identity, or signed evidence. A report is a claim until independently verified.
+
+## Core vocabulary
+
+- **Workspace root**: a bounded filesystem root exposed to a tool. Paths are relative; traversal and symlink escape are denied.
+- **Coding root**: a workspace root declared in the coding policy with explicit read/write/exec permissions and deny paths.
+- **Authority plane**: an independently revocable capability boundary. DEADBYTE uses process, coding, autonomous, and privileged-host planes.
+- **Standing grant**: explicit local authority that remains armed until explicit revocation. A grant never expands configured policy.
+- **Immutable release slot**: a content-addressed package tree copied from a verified manifest. Runtime state never belongs inside it.
+- **Generation bundle**: immutable controller configuration bound to a release slot plus external Bridge, Cloud, and Loop Supervisor identities.
+- **Active pointer**: the atomically replaceable record selecting one exact release and generation.
+- **Native Diff**: a preconditioned surgical mutation transaction with rollback and independently verifiable receipts.
+- **Semantic code**: bounded compiler/language-service navigation over an allowed coding root. Semantic edits still commit through coding-plane preconditions and receipts.
+- **Loop Supervisor**: the local out-of-band owner that can advance durable autonomous work and recover a parked/lost Bridge without arming privilege.
+- **Evidence**: immutable or append-only receipts, journals, manifests, and gate records used to verify a claim.
+
+## Engineering loop
+
+Inspect -> define acceptance -> reproduce -> make one surgical change -> verify -> adversarially test -> record evidence -> continue or stop.
+
+A failed tool call changes the hypothesis; it is not permission to retry blindly. Durable tasks and autonomous goals resume from authenticated state rather than conversational memory.
+
+## Context discipline
+
+Prefer progressive disclosure: symbol navigation, bounded search, paged observation, multi-file reads, and named resources. Do not dump whole repositories into prompts. Load only the skill, resource, source slice, or evidence needed for the current decision.
+
+## R35 successor anchor
+
+R35 / V0.9.0 is developed only as a successor to sealed R34 release `v0.8.11-6c01e5285e065220`, whose immutable package manifest is `6c01e5285e065220db07d7719f78bb6aa4fde88365419281b33be1b1d59dd3c5` with exactly 1560 listed package files. The mutable R34 development tree is never parent authority.
+
+The sealed R34 core MCP `tools/list` surface contains 73 tools with canonical schema surface SHA-256 `1fe5b624c0f95cf61261b9609aa98114adc18662d372c144773e6d7b30cfb9e5`. The public HTTP Bridge also exposes 73 tools but intentionally adapts only `autonomous_goal_run` for MCP multi-round tool result sampling by removing the downstream-only `planner_response` argument; its canonical public surface SHA-256 is `319be58b5972bc2a50f765cbe8e262ed0a3635b097ce80d40c6cae8cfc44f8f4`. Core and public compatibility are therefore separate evidence boundaries, not interchangeable hashes.
+
+## Final-baseline rule
+
+Do not call a build Final because source looks complete. Final requires exact-tree verification, tests/evals, platform gate evidence, reversible activation, public parity, rollback/restore proof, all intended authority state verified, and an independently verified signed closure.