attesso 0.4.0 → 0.6.0

package/LICENSE

@@ -0,0 +1,201 @@
+                                 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 contributors
+
+   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/NOTICE

@@ -0,0 +1,4 @@
+Bounds (installed as the npm package "attesso")
+Copyright 2025-2026 Attesso B.V.
+
+This product includes software developed at Attesso B.V. (https://attesso.com).

package/README.md

@@ -1,17 +1,33 @@
-# attesso
+# Bounds
 
-A local, signed ledger of what your AI agents attempted, what was allowed, and what was refused. Any action, not only payments. No account, no server, no dependencies.
+Installed as `attesso`: a local, signed ledger of what your AI agents attempted, what was allowed, and what was refused. Free and unlimited on your own machine; $0.00085 per synced decision when the record has to travel. Any action, not only payments. No account, no hosted backend, no dependencies.
 
 ```sh
 npx attesso init
 npx attesso log --action tool.call --subject read_file --meta tokens=1200 --meta cost_usd=0.0004
 npx attesso log --action purchase.execute --subject shop.example --amount 12.50 --currency EUR
 npx attesso verify
-npx attesso show
+npx attesso prove 2 --out receipt.json
+npx attesso verify-receipt receipt.json
 npx attesso report
 ```
 
-`init` writes `.attesso/` with an Ed25519 key, a policy and an empty ledger. `log` evaluates one proposed action against the policy, records the decision and its reason, and exits 1 when it refuses. `verify` recomputes the hash chain and every signature. `show` prints what was allowed, what was refused, which subjects dominate, and any tokens or cost you passed in `--meta`. `--dir PATH` points any command at a different ledger.
+`init` writes `.attesso/` with an Ed25519 key, a policy, a tools allowlist and an empty ledger. `log` evaluates one proposed action against the policy, records the decision and its reason, and exits 1 when it refuses. `verify` recomputes the hash chain and every signature. `prove` writes a receipt for one entry; `verify-receipt` checks it with the public key alone, in an empty directory. `show` prints what was allowed, what was refused, which subjects dominate, and any tokens or cost you passed in `--meta`. `--dir PATH` points any command at a different ledger.
+
+## The local UI
+
+`attesso ui` starts a loopback-only control surface for the ledger. It shows the
+day's observed flow and the exact calls behind it, reads new decisions as they
+are appended, and writes mode and path changes to the same files the hook reads:
+
+```sh
+npx attesso ui
+npx attesso ui --port 0 --no-open
+```
+
+The server binds `127.0.0.1`, mints a per-process token, and serves the page from
+the installed package. It has no account, no hosted data, and no dependency on a
+snapshot file. `Ctrl-C` stops it.
 
 ## The overview
 
@@ -27,17 +43,68 @@ hermes-local-9552aa28437e88c0610a…  2058     455 (22%)  PATH_DENIED×455  3,92
 
 Actions are tool calls; refusals carry the reason; tokens are input plus output, with cache reads shown separately because they bill at a different rate and dwarf the rest. Cost comes from a `llm.session` entry the recorder writes from the agent's own usage record, never from a number the report invents. `--json` gives the same data for a dashboard.
 
+## Watch and steer
+
+`attesso watch` follows new decisions in one terminal; `--from-seq 0` starts from
+the beginning of the ledger. `pause` and `stop` refuse the next calls of one
+task, while `resume` releases it. These commands work from a second terminal, so
+the agent process does not need to be restarted:
+
+```sh
+npx attesso rules set-profile balanced   # migrate an existing ledger, keep rules.json.bak
+npx attesso watch --from-seq 0
+npx attesso pause <task> --reason "inspect the diff"
+npx attesso stop <task> --reason "leave it stopped"
+npx attesso control
+npx attesso resume <task>
+```
+
+A pause is an explicit operator action, so it blocks even when the hook was
+started with `--observe`. The ledger records a signed control entry with
+`TASK_PAUSED` or `TASK_STOPPED` and the task id. The local control file is
+`control.json` beside the ledger; it is steering state, not a proof of human
+authority.
+
+## Setup, explain, suggest
+
+```sh
+npx attesso setup          # detects the installed harnesses; wires Hermes
+npx attesso setup --write  # also merges the observe hook into Claude Code,
+                           # Codex, Gemini and Cline, preserving existing hooks
+npx attesso setup --write --enforce  # same, but a refusal blocks
+npx attesso setup --dry-run
+npx attesso explain 42     # entry #42: rule, the step that tainted the task, what to do
+npx attesso suggest        # rules the ledger's own counts justify
+```
+
+`setup` also writes an `AGENTS.md` block so the agent knows a veto is active, that a
+refusal is not retryable unchanged, and how to ask about a rule that looks wrong.
+`suggest` is how rules get discovered instead of configured: it counts identical
+calls (same tool, same arguments) and prints a rule with the count that justifies it.
+
 ## Wire it into an agent
 
-`attesso hook` speaks the shell-hook contract that Claude Code, Cursor and Hermes
-already use: one tool call on stdin, exit 2 to refuse. Start in observe mode so the
-ledger records what the rules would have refused and nothing is blocked:
+`attesso hook` auto-detects the caller from its event name and payload shape, then
+answers in that harness's native decision shape:
+
+| Caller | Event | Refusal |
+|---|---|---|
+| Hermes | `pre_tool_call` | exit 2 with a message |
+| Claude Code, Codex | `PreToolUse` | `hookSpecificOutput.permissionDecision: deny` |
+| Cursor | `preToolUse` | `permission: deny` with both messages |
+| Cline | nested `preToolUse` | `{ cancel: true, errorMessage }` |
+| Gemini | `BeforeTool` | `{ decision: deny, reason }` |
+
+Start in observe mode so the ledger records what the rules would have refused and
+nothing is blocked. In observe mode, and on an ALLOW, a native harness gets no
+decision from us, so its own approval prompt still runs:
 
 ```sh
 node bin/attesso.mjs --dir ~/.hermes/attesso-veto/ledger hook --observe
 ```
 
-Hermes config (`~/.hermes/config.yaml`), or the same shape in any harness with hooks:
+`setup --write` installs the same command in each detected harness. The Hermes
+config (`~/.hermes/config.yaml`) looks like this:
 
 ```yaml
 hooks:
@@ -46,8 +113,15 @@ hooks:
       timeout: 10
 ```
 
-Drop `--observe` when the refusal rate on your own work looks right: a deny then
-exits 2 with a message the agent reads, and the step never runs.
+Codex requires one manual trust step: run `/hooks` in Codex, review the installed
+command and trust it. A changed hook definition is untrusted again. The other
+harnesses load the written config on their next start.
+
+Remove `--observe` (or run `setup --write --enforce`) when the refusal rate on your
+own work looks right. Hermes then exits 2; the native harnesses get their own deny
+object and the step never runs. Claude Code also gets `onFailure: block` in enforce
+mode; Codex, Gemini and Cline have no equivalent field, so their own sandbox and
+approval rules remain the backstop.
 
 For a long-lived harness, `attesso serve` answers the same questions over one
 process: write one JSON request per line, read one verdict per line. A decision
@@ -59,15 +133,18 @@ One signed line per proposed action:
 
 ```json
 {"v":1,"seq":1,"at":"2026-10-31T12:00:00.000Z","action":"tool.call",
- "subject":"read_file","decision":"ALLOW","code":"ALLOW","policy_digest":"…",
+ "subject":"read_file","decision":"ALLOW","code":"ALLOW",
+ "policy_digest":"…","rules_digest":"…","args_hash":"…",
  "kid":"…","prev":"genesis","meta":{"tokens":1200,"cost_usd":0.0004},"sig":"…"}
 ```
 
-`subject` is the thing acted on: a tool name, a payee, a repo, a recipient. `amount` appears only for money actions. Refusal codes match the hosted engine: `ACTION_MISMATCH`, `ABOVE_MAXIMUM`, `VALUE_NOT_ALLOWED`, `VALUE_MISMATCH`, `OUTSIDE_DATE_RANGE`, `REQUIRED_ATTRIBUTE_MISSING`.
+`subject` is the thing acted on: a tool name, a payee, a repo, a recipient. `rule` names the policy field or path rule behind a refusal. `args_hash` is a digest of the arguments, never the payload. `amount` appears only for money actions. Refusal codes match the hosted engine: `ACTION_MISMATCH`, `ABOVE_MAXIMUM`, `VALUE_NOT_ALLOWED`, `VALUE_MISMATCH`, `OUTSIDE_DATE_RANGE`, `REQUIRED_ATTRIBUTE_MISSING`.
+
+In-process embedders can subscribe to the `bounds.decision` diagnostics channel. The event carries the verdict, the rule, the entry hash and the digests, never the subject, task, amount, arguments or your `meta`.
 
 ## The policy
 
-`.attesso/policy.json` starts empty, so nothing is allowed until you set it. A policy governs one action; `"action": "*"` covers every action and is what a recording-only ledger uses.
+`.attesso/policy.json` starts with `"action": "*"`, so a fresh ledger records every action; tighten it once you know what to allow. A policy governs one action; `"action": "*"` covers every action and is what a recording-only ledger uses.
 
 ```json
 { "version": 1, "action": "tool.call", "subjects": ["read_file", "search_files", "grep_repo"] }
@@ -101,21 +178,82 @@ npx attesso log --action mail.send  --subject partner@example.com  --task job-2
 # #4 ALLOW mail.send partner@example.com (ALLOW)
 ```
 
-`init` ships one rule, and it is the one worth having:
+`init` ships the balanced profile:
 
 ```json
 { "version": 1,
   "rules": [
     { "id": "no-send-after-untrusted-read",
-      "deny": { "capabilities": ["send", "execute"] },
-      "if_path": { "trust": "untrusted", "capability": "read", "within_minutes": 30 } }
+      "deny": { "capabilities": ["send"] },
+      "if_path": { "trust": "untrusted", "capability": "read", "within_minutes": 30 } },
+    { "id": "no-repeat-web-extract",
+      "deny": { "capabilities": ["read"] },
+      "if_path": { "capability": "read", "subject": "web_extract",
+                   "same_arguments": true, "within_minutes": 30 } }
   ] }
 ```
 
-`--task` scopes the history, so one job cannot taint another. `within_minutes` limits how long a read stays relevant; without it a taint lasts for the whole task. `--capability` is one of `read`, `send`, `execute`, `spend`. The refusal names the rule and the step that tainted the path, so a reader can see the sequence rather than a verdict.
+Balanced blocks the outbound boundary and duplicate fetches; it leaves local edits and commands alone. For an untrusted environment where a shell command itself can exfiltrate, `init --profile strict` adds `write` and `execute` to the deny list. An existing ledger can adopt either shipped profile with `attesso rules set-profile balanced|strict`; the previous file is kept as `rules.json.bak`.
+
+File tools can also be scoped by `paths.json`. Shell and execute tools remain
+unscoped by default. A deployment that wants the hook to refuse every execute
+capability can set `"shell_scope": "deny"` in `paths.json`; that is a denial,
+not a command sandbox.
+
+`--task` scopes the history, so one job cannot taint another. `within_minutes` limits how long a read stays relevant; without it a taint lasts for the whole task. `--capability` is one of `read`, `write`, `send`, `execute`, `spend`. The refusal names the rule and the step that tainted the path, so a reader can see the sequence rather than a verdict.
 
 Rules are ordinary files you own and version. Run them in observe mode first: `node scripts/hermes-ledger.mjs --observe` records what the rules would have refused without touching the agent, which is how you learn where a rule is too broad before it costs you a day.
 
+## Pin the MCP surface
+
+A tool call is judged by name unless you pin the definitions you reviewed. `tools pin` hashes each supplied tool's full definition and the current `.attesso/tools.json`:
+
+```sh
+npx attesso tools pin --manifest tools.manifest.json
+npx attesso tools verify --manifest tools.manifest.json
+```
+
+The manifest is the harness's own `{ "tools": [ { "name", "description", "inputSchema", "outputSchema", "annotations" } ] }` list. A caller that knows the definition can send `tool_definition_hash` with the call; a matching pin is recorded as `tool_pin: verified`, a changed one is refused as `TOOL_CHANGED`, and a call without a hash is recorded as `unverified`.
+
+For an MCP server, use the bundled stdio adapter instead of wiring the manifest by hand:
+
+```sh
+# 1. Ask the server for its identity, instructions, tools, prompts and resources.
+npx attesso-mcp --print-manifest -- npx -y @modelcontextprotocol/server-everything > mcp.manifest.json
+
+# 2. Review it, then pin the whole surface.
+npx attesso tools pin --manifest mcp.manifest.json
+
+# 3. Put the adapter in front of the same server.
+npx attesso-mcp --dir .attesso -- npx -y @modelcontextprotocol/server-everything
+```
+
+The adapter speaks both stdio protocol eras: the 2026-07-28 stateless discovery shape and the older `initialize` handshake. Pin the era your client uses; `--era legacy` forces the handshake when a dual-era server would otherwise be discovered as modern. It refuses a changed server identity, instructions, tool, prompt, resource or resource template before the client sees it, refuses a changed or unpinned tool before the call reaches the server, and refuses server-initiated sampling, elicitation and roots requests. Every allowed call is recorded in the signed ledger; `export` carries the pinned manifest and the tool lock, so `verify-bundle` can check the evidence in an empty directory. It is stdio only; remote HTTP servers and generic MCP gateway features are out of scope.
+
+Before tightening a policy, replay the ledger against the candidate file:
+
+```sh
+npx attesso replay --policy next-policy.json --max-newly-denied 0
+```
+
+Every recorded proposal is re-judged with the history that preceded it. The summary names how many decisions would flip, and `--max-newly-denied` turns a budget into an exit code, so a pull request can refuse a rule that would have blocked real work. Replay is a diagnostic: it uses the history the ledger holds and does not prove that history is complete.
+
+## Control the local configuration over MCP
+
+The bundled `attesso-control-mcp` is a control surface, not a second proxy:
+
+```sh
+npx attesso-control-mcp --dir .attesso
+```
+
+It speaks stdio only and answers both the legacy `initialize` handshake and the
+2026-07-28 direct request shape. It exposes `bounds_status`,
+`bounds_connect`, `bounds_mode`, `bounds_paths_get` and `bounds_paths_set`.
+Connect and mode are limited to `observe` and `off`; enforcement and path
+widening require the human CLI (`npx attesso mode enforce`,
+`npx attesso paths --set`). It has no HTTP listener and no network access.
+`attesso-mcp` remains the upstream tool proxy.
+
 ## Recording a real agent
 
 `attesso` is a CLI, so anything that can run a command can record an action. To see what a Hermes session actually did, the repo ships `scripts/hermes-ledger.mjs`, which reads a session from `state.db` read-only and appends one entry per tool call.
@@ -125,13 +263,28 @@ node scripts/hermes-ledger.mjs --dir .hermes/tmp/attesso-dogfood --observe
 npx attesso --dir .hermes/tmp/attesso-dogfood show
 ```
 
-`--observe` labels every verdict the rules produced and prints how many steps they would have refused; nothing in the agent is blocked. Tool calls are classified on the way in: `read_file` and the repo search tools read internal material, the web and browser tools read untrusted material, and anything that writes, executes or spawns is an effect.
+`--observe` labels every verdict the rules produced and prints how many steps they would have refused; nothing in the agent is blocked. Tool calls are classified on the way in by `.attesso/tools.json`: allowlisted names are internal, anything else is an untrusted read. Add your own tools there; an unlisted tool taints the task rather than being trusted.
+
+## Portable evidence
+
+```sh
+npx attesso prove 2 --out receipt.json          # one entry, its path, a signed head
+npx attesso verify-receipt receipt.json         # public key only, no ledger
+npx attesso checkpoint --out head.json          # keep this off the machine
+npx attesso verify --pin head.json              # refuse a rewrite below the pin
+npx attesso export 2 --out bundle.json          # receipt plus policy and rules
+npx attesso verify-bundle bundle.json --replay  # re-run the recorded verdict
+```
+
+A receipt is about 1.5 KB at ten thousand entries. A bundle adds the exact policy and rules bytes, so `--replay` recomputes the verdict instead of trusting the log; it replays against the history it carries, and does not prove that history is complete. The pin is what an attacker holding the key cannot re-derive. Store `head.json` on another device, or in a repository the agent cannot write; a pin stored beside the ledger is not independent. The receipt still proves integrity, not authority; see below.
 
 ## What this proves, and what it does not
 
 The signature proves the ledger was not edited after the fact: change one byte and `verify` names the entry, reorder two and the chain breaks, delete the last one and the recorded head no longer matches.
 
-It does not prove a human authorized anything. The signing key lives in `.attesso/key.json`, in the same directory as the log, so anything that can write the log can also write a new one. It cannot see absence either: a process that deletes the whole directory leaves nothing to verify.
+Each append is fsynced and the head is written after its line. On Linux that is a local-disk guarantee. On macOS Node cannot issue F_FULLFSYNC, so a power cut can still lose the last write even on APFS; a network filesystem has the same limit. The recorded head then refuses the next append instead of guessing.
+
+A receipt proves one entry sits in the tree whose head this key signed, and a pin proves the log was not rewritten below a head you kept elsewhere. Neither proves a human authorized anything. The signing key lives in `.attesso/key.json`, in the same directory as the log, so anything that can write the log can also write a new one. It cannot see absence either: a process that deletes the whole directory leaves nothing to verify.
 
 Hosted Attesso is where authority lives: a passkey approval binds a named human to exact terms, the decision and the refusal are recorded server-side, and the result is evidence a third party verifies offline against a published key. The local ledger uses the same event and code vocabulary, so it can be submitted there later.
 

package/bin/attesso-control-mcp.mjs

@@ -0,0 +1,13 @@
+#!/usr/bin/env node
+// Control-only MCP server. Keep this separate from attesso-mcp, which is a
+// proxy and must not gain a second job.
+import { homedir } from 'node:os';
+import { createControl, createServer } from '../src/mcp/control.mjs';
+
+const argv = process.argv.slice(2);
+const dirAt = argv.indexOf('--dir');
+const dir = dirAt === -1 ? '.attesso' : argv[dirAt + 1];
+const homeAt = argv.indexOf('--home');
+const home = homeAt === -1 ? homedir() : argv[homeAt + 1];
+const control = createControl({ dir, home });
+createServer({ control });

package/bin/attesso-mcp.mjs

@@ -0,0 +1,2 @@
+#!/usr/bin/env node
+import '../src/mcp-proxy.mjs';