Architecture

Generated from the codebase by scripts/gen_architecture.ts — run npm run docs:arch. Every table below is read out of the source: if a surface is listed, code for it exists in src/ or packages/. Two sections are authored rather than derived — the diagram and Not built — and both say so where they appear, because a shape and an absence cannot be parsed out of code. LESSONS R6: eight prior submissions documented routes that were never built.

_Generated: 2026-09-28T08:34:23.602Z_

Protocol

scripts/e2e.ts and scripts/verify.ts §6 both assert the NEGOTIATED version at runtime and exit non-zero below that floor, so this row cannot drift from the wire.

The shape

_Authored, not derived — the tables below are the machine-checked copy._

flowchart LR
  physio["Sarah, physio<br/>web/clinician.html"] -- "POST /write<br/>HMAC over raw bytes" --> http
  subgraph proc["one process · npm start"]
    http["src/http.ts<br/>Streamable HTTP · OAuth resource"]
    server["src/server.ts<br/>10 MCP handlers"]
    store["packages/live-resources<br/>versioned records · hash chain<br/>audience partition"]
    env["src/envelope.ts<br/>AES-256-GCM · AAD binds the slot"]
    http --> server
    server --> store
    store --> env
  end
  store -- "notifications/resources/updated" --> server
  server -- "SSE, resumable by Last-Event-ID" --> echo["Ray, Echo Show<br/>web/echo.html · ui://unsay/echo"]
  echo -- "resources/read · re-read under current scope" --> http
  http -- "GET /verify · public chain replay" --> judge["a judge, no account"]
  store -. "care-internal:// refused<br/>-32002, never a 403" .-> echo

MCP surfaces actually registered

10 request handlers + 3 notification sender(s).

Declaring logging also makes the SDK serve logging/setLevel without a handler of our own, so it is a surface a host can call but is deliberately not listed above — this table only names methods with a sender or handler in the source. It is honoured, not merely served: src/server.ts passes the transport session id to sendLoggingMessage(), which is what the SDK filters the level against, and npm run e2e asserts a notice is suppressed at level emergency while notifications/resources/updated still arrives.

HTTP routes

6 routes + 3 static pages + 5 rendered documents, all in src/http.ts.

Plus a second read-only allowlist — the documents and receipts the landing page cites, so every link on it resolves against the server a judge is already running:

/README.md · /DEMO.md · /ARCHITECTURE.md · /FRICTION.md · /LICENSE · /docs/SPEC.md · /docs/proof/bench.txt · /docs/proof/bench.remote.txt · /docs/proof/verify.json · /docs/proof/bench.json · /docs/proof/live_run.jsonl · /docs/proof/probe_subscribe.json · /docs/proof/resume.json · /skill/SKILL.md · /icon.svg · /og.png · /docs/assets/readme-hero-animated.svg · /docs/assets/icon-animated.svg · /packages/live-resources/src/store.ts · /src/server.ts · /src/http.ts

Declared capabilities

resources: { subscribe: true, listChanged: true },
completions: {},
prompts: {},
// A second, cheap notification channel. Declaring it also makes the SDK
// serve logging/setLevel, so a host can turn the revision log down.
logging: {},
tools: {},

Modules

Extracted package

The generic half — versioned resources, revision notifications, the hash chain, and the audience/scope partition — lifted out of src/ so it can be depended on without Unsay. Consumed here by relative import; not published to npm.

Executable scripts

Runtime dependencies

Not built

The one authored section in this file — every table above is derived from the source, this list is written by hand in scripts/gen_architecture.ts because absence cannot be parsed out of code. Stated so this document cannot imply otherwise:

• No AWS deployment. npm start runs the server locally and nothing is hosted. The KMS provider in src/envelope.ts is SigV4-signed and shaped correctly but has never been executed against a live CMK — see FRICTION.md F-004, the payment-verification hold.
• No authorization server. Unsay is an OAuth 2.1 protected RESOURCE only: no /authorize, no /token, no refresh, no revocation, no JWKS. Tokens are HS256 under a shared secret, minted by mintToken() in the same file that verifies them.
• No durable storage. The store, the event store and the audit log are in memory; the audit log survives only if UNSAY_AUDIT_LOG names a file.
• The MCP Apps binding is shaped, not exercised. ui://unsay/echo is served and read over the protocol by npm run e2e, but no host we can reach implements the extension, so the _meta template binding on whats_changed has never been rendered by one — see FRICTION.md F-013.
• No ML model of any kind, by design — the reasoning model belongs to the host.
• No blockchain, token, or payment surface.

Rendered from ARCHITECTURE.md in the repository. Source as text: /ARCHITECTURE.md.