phaedo-mcp 0.1.0

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Randy Shelton
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,301 @@
+# Phaedo MCP server — Phase 1 (push injection)
+
+A local [MCP](https://modelcontextprotocol.io) server that exposes your Phaedo
+cognitive-fingerprint **projection** to any MCP client (Claude Desktop, Claude
+Code, Cursor, agent frameworks) — so the assistant responds in your style
+without the Chrome extension. One integration, every MCP client.
+
+Implements `docs/protocol/mcp-binding.md` §3.1:
+
+| Surface | Name | Returns |
+|---|---|---|
+| tool | `phaedo_request_injection` | §9.2 request → §9.3 Injection Response |
+| resource | `phaedo://fingerprint/projection` | default projection (all layers, standard) |
+| prompt | `phaedo` | one-click `/phaedo` — inserts the projection as a message |
+| tool | `phaedo_consult` | §10.2 request → §10.3 Consultation **signal** (never layer content) |
+| tool | `phaedo_check_authorization` | deterministic-only pre-flight: does a standing authorization (§10.5) already decide this action? (no inference) |
+
+The projection is rendered by the **same** `context-block.js` the extension
+injects, so MCP injection is byte-identical to web injection.
+
+## Status
+
+- **Phase 1a (this cut):** reads the fingerprint from a local JSON file (see
+  *Fingerprint source*). Lets injection work in a real client today, no crypto.
+- **Phase 1b-i (done):** the spec-faithful key boundary — authorize → pull
+  `/v1/profile` → unwrap the §7.2 envelope from the paired phone, reusing the
+  repo crypto modules (`protocol/envelope/kdf/identity.js`) in node. The
+  decrypted fingerprint stays in memory (never written to disk). Auto-selected
+  when a pairing record is configured (see *Fingerprint source*). Plan +
+  decisions: `../docs/roadmap/mcp-1b-plan.md`.
+- **Phase 1b-iii (done):** **encrypted at-rest cache** — a successful phone pull
+  caches the fingerprint as ciphertext under a server-held key; when the phone is
+  unreachable the server serves that cache, so it works **phone-absent**
+  (frictionless default; mirrors the extension's Option C — defense-in-depth, NOT
+  phone-gated). State dir defaults to `~/.phaedo-mcp/` (override `PHAEDO_MCP_STATE_DIR`);
+  holds a `0600` key file + ciphertext-only cache. **Revocation is honored:** if
+  the phone *rejects* this client (revoked / invalid credentials → 4xx), the cache
+  is purged and the pull fails — a revoked agent can't keep serving a cached copy.
+  The cache only covers the phone being genuinely *unreachable* (network/timeout).
+  v1 caveat: the raw key is on disk (weaker than the extension's non-extractable
+  key) — OS-keychain is a hardening follow-up.
+- **Per-agent revocable pairing (built, device-verify pending):** the server
+  pairs **itself** with the phone as its own SAS-approved, **revocable** client —
+  `npm run pair` (LAN auto-discovery or relay typed-code, mirroring the
+  extension). Needs the phone's multi-client support (spec §8.4 **v0.1.6**) + the
+  phone **Agents/revoke** screen. Obviates hand-copying the pairing record. Plan:
+  `../docs/roadmap/mcp-revocable-approval-plan.md`. Phone-gated unlock stays a
+  deferred enterprise mode behind a config flag.
+
+**Injection-only.** MCP never returns the conversation, so there is **no
+capture** here (binding §5) — your fingerprint does not learn from MCP sessions.
+Local **stdio** only; **standard** mode only (enhanced-privacy/Stained-Glass and
+remote HTTP/SSE are out of this cut).
+
+## Install & test
+
+```bash
+cd mcp
+npm install
+npm run smoke        # 1a: unit + live stdio integration (23 checks)
+npm run smoke:phone  # 1b-i: mock-phone authorize→pull→decrypt→project (12 checks)
+npm run smoke:cache  # 1b-iii: encrypted at-rest cache + phone-absent fallback (11 checks)
+npm run smoke:pair   # P3: self-pairing crypto vs a mock phone (pair_key + SAS match)
+```
+
+## Pair with the phone
+
+```bash
+cd mcp
+npm run pair
+```
+The server generates its own long-term identity (`identity.json`, `0600`,
+gitignored) and pairs with the phone vault as a distinct client named **"Phaedo
+MCP Server"**:
+- **Same Wi-Fi:** it finds the phone automatically — approve "Phaedo MCP Server"
+  on the phone and confirm the SAS matches what the terminal prints.
+- **Off-network:** it prints an `XXXX-XXXX` code; on the phone tap **Pair with
+  code**, type it, then confirm the SAS.
+
+On success it writes `pairing.json` and pulls your fingerprint autonomously
+thereafter. Revoke anytime from the phone's **Agents** screen.
+
+## Fingerprint source
+
+`loadFingerprint()` auto-selects, so `server.js`/`projection.js` never change:
+
+**Phase 1b — phone (preferred).** If a pairing record is configured, the server
+pulls the live fingerprint from the paired phone over the encrypted boundary.
+A record is found via `PHAEDO_PAIRING` (path) or `mcp/pairing.json`. Run
+**`npm run pair`** (see *Pair with the phone*) to create it — the server pairs
+itself with the phone as its own revocable client. `pairing.json` holds
+`pair_key` (a long-term secret) and is **gitignored**. The phone app must be
+foregrounded/reachable at the configured `endpoint`. *(You can still hand-copy
+`pairing.sample.json` → `pairing.json` from the extension's `phaedo_local_pairing`
+if you prefer.)*
+
+**Phase 1a — local JSON (fallback / demo).** With no pairing record, reads a
+**vault payload** from `PHAEDO_FINGERPRINT`, then `mcp/fingerprint.json`, then
+the shipped `mcp/sample-fingerprint.json` (so it runs out of the box):
+```json
+{
+  "phaedo_fingerprint": { "layers": { ... }, "fingerprint_id": "...", "persona_strength": 0.6 },
+  "phaedo_behavioral_signals": { ... },
+  "phaedo_linguistic_profile": { "messageCount": 64, ... },
+  "phaedo_session_metrics": { "sessionCount": 6, ... }
+}
+```
+
+## One-click install (recommended)
+
+The installer finds the MCP clients you already have (Claude Desktop, Cursor,
+Claude Code), adds Phaedo to each — preserving your other servers, backing the
+file up first — and then runs the one-time phone pairing.
+
+- **macOS:** double-click **`installers/macos/Install Phaedo MCP.command`**.
+- **Windows:** double-click **`installers/windows/Install Phaedo MCP.bat`**.
+- **Linux:** `bash installers/linux/install-phaedo-mcp.sh`.
+
+(The launcher installs dependencies the first time, then runs the installer.)
+
+Prefer the terminal? From this folder:
+```bash
+npm install
+npm run setup        # configure detected clients
+npm run setup:pair   # configure, then pair with the phone
+npm run unsetup      # remove Phaedo from every client
+node install.mjs --dry-run   # preview, write nothing
+```
+
+Each client entry runs the server with the **absolute path to your node binary**
+(not bare `node`) — a GUI-launched app like Claude Desktop often has no `node` on
+its PATH. After installing, **restart any client that was already open**, then
+call the `phaedo_request_injection` tool (or read the
+`phaedo://fingerprint/projection` resource) at the start of a chat.
+
+> One remaining prerequisite: Node.js (from [nodejs.org](https://nodejs.org)). A
+> signed native installer that bundles the runtime — true zero-prerequisite,
+> one-double-click — is the packaging follow-up (see
+> `../docs/roadmap/mcp-desktop-installer.md`).
+
+## Inject at session start (manual → automatic)
+
+MCP is pull-based — a server can't push a system prompt into every new session the
+way the browser extension owns the input box. So injection ranges from one-click to
+fully automatic depending on the client:
+
+- **Any client — `/phaedo` (one click).** The server exposes a **prompt** named
+  `phaedo`. Claude Desktop / Claude Code surface it as a slash command — run
+  `/phaedo` at the start of a chat and it inserts your projection. One keystroke,
+  no typing.
+- **Claude Code — automatic (a hook).** Run `npm run setup:code-hook` (or
+  `node install.mjs --code-hook`). It adds a **SessionStart hook** to
+  `~/.claude/settings.json` that runs `hooks/session-start.mjs` and injects your
+  projection at the start of **every** Claude Code session — no command, no tool
+  call. Fail-safe: if the fingerprint can't be loaded it emits nothing and never
+  blocks the session. Remove it with `npm run unsetup`.
+- **Claude Desktop — near-automatic (a Project instruction).** Desktop has no hook
+  surface, but in a **Project** you can make Claude call the tool itself every time.
+  Paste into the Project's custom instructions:
+  > At the start of every conversation, call the `phaedo_request_injection` tool and
+  > treat the returned `projection` as authoritative on how I think and want
+  > responses formatted. Don't announce that you did it.
+
+  Every chat in that project then injects automatically.
+
+## Consult at decision points (`phaedo_consult`, §10)
+
+Beyond injecting style, an agent can **ask the fingerprint how the user's pattern
+bears on a decision** — without ingesting the fingerprint. `phaedo_consult` takes a
+§10.2 request and returns a §10.3 **signal**, never layer content (§10.4 boundary):
+
+```jsonc
+// request (tool arguments)
+{ "consultation_type": "action_approval",
+  "action_descriptor": { "domain": "financial", "reversible": false, "magnitude": "high",
+                         "summary": "Approve $12k vendor payment outside terms." },
+  "context": { "evidence_provided": ["invoice", "po_match"] } }
+
+// response
+{ "signal": "escalate", "confidence": 0.81,
+  "rationale_hint": "On irreversible, high-magnitude actions in the financial domain, the subject favors caution and human review.",
+  "deference_level": "high" }
+```
+
+- `consultation_type`: `action_approval` · `domain_risk_check` · `escalation_default` · `voice_draft`.
+- `signal`: `proceed` · `proceed_with_note` · `clarify` · `escalate` · `decline` · `insufficient_signal` (abstain — the fingerprint has no coverage for this action; fall back to your own default).
+- `deference_level` (`high`/`medium`/`low`) = how strongly to weight it; sparse data → `low`.
+
+### Fast pre-flight (`phaedo_check_authorization`, §10.5)
+
+Before paying for a full consult, an agent can ask whether one of your **standing
+authorizations** already decides the action — a **deterministic-only** check (no
+inference, no model):
+
+```jsonc
+// request:  { "action_descriptor": { "domain": "financial", "reversible": false, "amount": 12000 } }
+// matched:  { "authorization_matched": true, "signal": "escalate", "rule_id": "irreversible-spend-over-5k-escalate",
+//            "rationale_hint": "Per your standing rule: Any irreversible spend over $5,000 goes to me…" }
+// no match: { "authorization_matched": false, "signal": null, "rule_id": null,
+//            "rationale_hint": "No standing authorization matches this action; run phaedo_consult…" }
+```
+
+A match is your pre-decision (confidence 1.0, deference high). On no match, fall back to
+`phaedo_consult` or your own default. Same §10.4 boundary — only the rule's decision crosses.
+
+### Receipts (§10.6) — your on-device audit trail
+
+Every resolved consultation (abstains included, plus matched pre-flights) writes one
+**encrypted, append-only receipt** to `~/.phaedo-mcp/receipts.enc` — which agent asked
+what, and what your oracle answered. Receipts **never leave the device**; the store is
+ciphertext under its own derived key (`phaedo:receipts:enc:v0.1`), capped (default
+5,000, oldest evicted; `PHAEDO_RECEIPTS_CAP` to change). Only one field is ever mutable
+after write: `user_action` (what you actually did — feeds future agreement tracking).
+Quick readout on your own machine:
+
+```bash
+cd mcp && npm run receipts                          # decrypts locally, lists the last 50 (with a short id per line)
+node receipts.js mark <id|prefix|latest> approved   # record what YOU did → approved | rejected | modified | unknown
+npm run agreement                                   # per-domain agreement rate (oracle vs your actual decisions)
+```
+
+`user_action` is **subject-authored**: set it from what *you* decided, not from whether an
+agent proceeded. Until receipts carry one, `npm run agreement` shows `—`
+(no data ≠ 0%); each one you mark makes the rate live. Metric definition:
+`../docs/architecture/agreement-metric.md`.
+
+**Two resolvers, both local.** The default is a **deterministic rule engine** —
+resilient cue extraction (reads §4.2 signals, then keyword-scans the relevant
+layers' interview text), relevance-scoped per consultation type, with
+confidence/deference grounded in real cue coverage. Nothing leaves the device;
+always available.
+
+**Model judge (richest context — ON by default, local).** The judge reasons over
+the *full projection* via a **local** Ollama / OpenAI-compatible endpoint and
+returns a §10.3 signal. Any failure/timeout/parse error **falls back to the rule
+engine**, so the model can only improve on, never break, the floor (and a missing
+model never breaks consultation). The §10.4 boundary is enforced on parse.
+
+The **installer turns this on automatically**: it probes local Ollama and writes
+`PHAEDO_CONSULT_MODEL` into each client's server entry (picking an installed general
+model, else defaulting to `llama3.1:8b`). Toggle it at install time:
+
+```bash
+npm run setup                              # model judge ON (auto-detect Ollama)
+node install.mjs --consult-model qwen2.5:7b   # pin a specific model
+node install.mjs --consult-url http://localhost:11434   # custom endpoint
+node install.mjs --no-model-judge          # rule engine only
+```
+
+Use a **general** chat model (NOT the extraction fine-tune). To run it: `ollama
+pull llama3.1:8b`. Raw env (if configuring a client by hand):
+`PHAEDO_CONSULT_MODEL`, `PHAEDO_CONSULT_MODEL_URL`, `PHAEDO_CONSULT_API_KEY`
+(OpenAI-compatible endpoints only).
+
+`voice_draft` always redirects to the injection projection (generation is out of
+scope). A retrieval/scoping reranker is the next upgrade (`../docs/roadmap/mcp-server.md`).
+
+### Deference policies (guardrails that make delegation safe)
+
+The user can author **standing rules** that *override* the inferred signal —
+per-domain / magnitude / reversibility (spec §10.5). e.g. "always escalate
+irreversible spend/legal", "auto-proceed low-stakes reversible writing".
+
+**Author them in the browser:** open **`policy-editor.html`** (double-click — it's
+self-contained), build rules with the form, and **Download / Copy** the result to
+**`mcp/consult-policies.json`**. The server **auto-reads that file** — no env, just
+restart the client. (Override the path with `PHAEDO_CONSULT_POLICIES`; see
+`consult-policies.sample.json`.) Portable alternative: put the rules in the vault
+under `phaedo_consult_policies` so they travel with you (in-app authoring is a
+follow-up).
+
+`effect`: `escalate`/`require_human` · `decline` · `autoproceed` (all at `deference:
+high`) · `bias_cautious`/`bias_bold` (nudge one step). The matched rule's `note`
+becomes the `rationale_hint` ("Per your standing rule: …"), so the agent sees why.
+Policies never apply to `voice_draft` and never widen the §10.4 boundary.
+
+## Connect a client manually (advanced)
+
+The installer writes exactly this. The minimal **paired** entry needs no `env` —
+`pairing.json` next to `server.js` drives the source automatically.
+
+**Claude Desktop** — add to `claude_desktop_config.json`:
+```json
+{
+  "mcpServers": {
+    "phaedo": {
+      "command": "/absolute/path/to/node",
+      "args": ["/Users/galavoxx/phaedo/mcp/server.js"]
+    }
+  }
+}
+```
+For the Phase-1a demo (no phone), add
+`"env": { "PHAEDO_FINGERPRINT": "/absolute/path/to/your/fingerprint.json" }`.
+Restart Claude Desktop, then call `phaedo_request_injection` at the start of a
+chat and prepend the returned `projection`.
+
+**Claude Code** — `.mcp.json` in a project, or:
+```bash
+claude mcp add phaedo -- /absolute/path/to/node /Users/galavoxx/phaedo/mcp/server.js
+```

package/agreement.js

@@ -0,0 +1,95 @@
+// Phaedo — agreement tracking FOUNDATION (build brief M5).
+//
+// Given the §10.6 receipt store, compute the per-domain AGREEMENT RATE: how often
+// the oracle's decisive signal matched what the subject actually did
+// (`user_action`), over a sliding time window. This is the minimal data layer for
+// the delegation gradient and the seed of the native persona benchmark
+// (docs/architecture/agreement-metric.md).
+//
+// PURE: (receipts, opts) -> report. No I/O, no globals, no side effects — the
+// same discipline as consult-core.js. Reading the store happens in the caller
+// (CLI below / harness); receipts are data here.
+//
+// DELIBERATELY NOT WIRED to deference_level. Closing the loop (high agreement →
+// auto-raise deference) is a product decision for a later session, not an
+// engineering default (brief M5 step 2). Dev-only readout: `npm run agreement`.
+//
+// Metric definition v0 (full rationale in docs/architecture/agreement-metric.md):
+//   - Only receipts with a known user_action count (`approved|rejected|modified`;
+//     `unknown`/null are recorded but excluded from the rate).
+//   - Only DECISIVE signals are scored: proceed / proceed_with_note / decline.
+//     escalate, clarify, and insufficient_signal hand the decision to a human or
+//     defer — they make no outcome prediction, so "agreement" is undefined for
+//     them; they are counted separately as non_directional.
+//   - Agreement: proceed|proceed_with_note ↔ approved; decline ↔ rejected.
+//     `modified` counts as DISAGREEMENT for every decisive signal (the subject
+//     did not accept the action as-judged). Conservative on purpose: it
+//     understates agreement rather than overstating delegation safety.
+//   - Domain key: action_descriptor.domain, lowercased; null → "(none)".
+
+export const DECISIVE = ['proceed', 'proceed_with_note', 'decline'];
+export const DEFAULT_WINDOW_DAYS = 30;
+
+function agrees(signal, userAction) {
+  if (userAction === 'approved') return signal === 'proceed' || signal === 'proceed_with_note';
+  if (userAction === 'rejected') return signal === 'decline';
+  return false; // 'modified' — the action was not accepted as-judged
+}
+
+// (receipts, { windowDays, now }) -> {
+//   window: { days, since, now, total_receipts, in_window },
+//   overall: { scored, agreements, disagreements, rate, non_directional, awaiting_user_action },
+//   domains: { [domain]: same-shape-as-overall },
+// }
+// `rate` is null when nothing was scored (no data ≠ 0% agreement).
+export function computeAgreement(receipts, { windowDays = DEFAULT_WINDOW_DAYS, now = Date.now() } = {}) {
+  const since = now - windowDays * 24 * 60 * 60 * 1000;
+  const bucket = () => ({ scored: 0, agreements: 0, disagreements: 0, rate: null, non_directional: 0, awaiting_user_action: 0 });
+  const overall = bucket();
+  const domains = {};
+  let inWindow = 0;
+
+  for (const r of Array.isArray(receipts) ? receipts : []) {
+    const t = Date.parse(r?.created_at);
+    if (!Number.isFinite(t) || t < since || t > now) continue;
+    inWindow++;
+    const domain = (r.request?.action_descriptor?.domain || '(none)').toLowerCase();
+    const d = (domains[domain] ||= bucket());
+    const signal = r.response?.signal;
+    const action = r.user_action;
+
+    for (const b of [overall, d]) {
+      if (!DECISIVE.includes(signal)) { b.non_directional++; continue; }
+      if (action == null || action === 'unknown') { b.awaiting_user_action++; continue; }
+      b.scored++;
+      if (agrees(signal, action)) b.agreements++; else b.disagreements++;
+    }
+  }
+
+  for (const b of [overall, ...Object.values(domains)]) {
+    if (b.scored > 0) b.rate = Math.round((b.agreements / b.scored) * 1000) / 1000;
+  }
+
+  return {
+    window: { days: windowDays, since: new Date(since).toISOString(), now: new Date(now).toISOString(), total_receipts: Array.isArray(receipts) ? receipts.length : 0, in_window: inWindow },
+    overall,
+    domains,
+  };
+}
+
+// ── Dev CLI: `node agreement.js` / `npm run agreement` — local readout only ───
+// Decrypts the local receipt store with the local key; nothing leaves the device.
+// NOT product UX and NOT fed back into deference (see header).
+if (process.argv[1] && process.argv[1].endsWith('agreement.js')) {
+  const days = Number(process.argv[2]) || DEFAULT_WINDOW_DAYS;
+  Promise.all([import('./receipts.js'), import('./cache.js')]).then(async ([{ readReceipts }, { defaultStateDir }]) => {
+    const report = computeAgreement(await readReceipts(defaultStateDir()), { windowDays: days });
+    const { overall: o, window: w } = report;
+    console.log(`Agreement over the last ${w.days}d — ${w.in_window}/${w.total_receipts} receipts in window\n`);
+    const line = (label, b) =>
+      console.log(`${label.padEnd(22)} rate ${b.rate === null ? '  —  ' : (b.rate * 100).toFixed(1) + '%'}  (${b.agreements}✓ ${b.disagreements}✗ of ${b.scored} scored · ${b.non_directional} non-directional · ${b.awaiting_user_action} awaiting user_action)`);
+    line('OVERALL', o);
+    for (const [dom, b] of Object.entries(report.domains).sort()) line(`  ${dom}`, b);
+    if (o.scored === 0) console.log('\nNo scored receipts yet — set user_action on receipts as you accept/reject agent actions.');
+  }).catch((e) => { console.error(`agreement: ${e.message}`); process.exit(1); });
+}

package/build-package.mjs

@@ -0,0 +1,22 @@
+#!/usr/bin/env node
+// Make the npm package self-contained. The MCP server reaches two sets of files at
+// the repo root (one source of truth, shared with the extension): the injection
+// renderer (context-block.js, via projection.js) and the classic crypto modules
+// (protocol/envelope/kdf/identity.js, via lib/phaedo-crypto.js). The published
+// package ships only mcp/, so this copies those root modules into mcp/vendor/;
+// projection.js and lib/phaedo-crypto.js prefer the vendored copies when present
+// and fall back to the repo root in dev. Runs as `prepack` (npm pack / publish)
+// and `npm run build`. Idempotent; mcp/vendor/ is gitignored (a build artifact).
+
+import { copyFileSync, mkdirSync } from 'fs';
+import { dirname, join, resolve } from 'path';
+import { fileURLToPath } from 'url';
+
+const HERE = dirname(fileURLToPath(import.meta.url));
+const ROOT = resolve(HERE, '..');
+const VENDOR = join(HERE, 'vendor');
+const FILES = ['context-block.js', 'protocol.js', 'envelope.js', 'kdf.js', 'identity.js'];
+
+mkdirSync(VENDOR, { recursive: true });
+for (const f of FILES) copyFileSync(resolve(ROOT, f), join(VENDOR, f));
+process.stdout.write(`[phaedo-mcp] bundled ${FILES.length} root modules → mcp/vendor/\n`);