Architecture at a glance · Amanuensis

§Runtime boundary map

Projected from the recorded onboarding runtime boundary table; mechanisms and targets are preserved as surveyed.

6 recorded runtime boundariesRuntime → communication mechanism → recorded target

Host agent runtime

external

Communicates withMCP server

Mechanismstdio MCP

Recorded noteStarts the server with a workspace path. .mcp.json@b8b566f.

`amanuensis-memory`

Node/TypeScript

Communicates withhost, SQLite, git, Python

MechanismMCP stdio, native SQLite binding, subprocess

Recorded noteOwns validation and durable records. mcp-server/src/index.ts:main@b8b566f.

SQLite `memory.db`

SQL

Communicates withMCP server and materializer

MechanismWAL; one writer API, read-only materializer connection

Recorded noteSchema initializes and migrates on open. mcp-server/src/db.ts:openDatabase@b8b566f.

Git storage history

git subprocess

Communicates withstorage directory

Mechanismsynchronous child process

Recorded noteCommits DB/prose state at gates. mcp-server/src/storage-git.ts:commitStorage@b8b566f.

Python materializer

Python

Communicates withSQLite and prose storage

Mechanismchild process and filesystem

Recorded noteEmits docs and .manifest.json. materializer/amanuensis_materializer/core.py:Materializer.materialize@b8b566f.

Installer CLI

Node/TypeScript

Communicates withworkspace files

Mechanismfilesystem/config merge

Recorded noteWrites agents and VS Code MCP config. mcp-server/src/cli.ts:plan@b8b566f.

§Subsystem dependency graph

1 connected area2 subsystems · 1 dependenciesFollow any name to its subsystem report

Connected area 1 · hub

B-03 Knowledge tools and workflow API

2 subsystems · 1 connection

data-flowOutgoing · confirmed

ToB-04 Diff-aware materializer

Staleness flows from B-03's detect_changes into B-04's staleness_map projection via the entries table (seam SM-09). Because no writer inserts rows, the defect propagates from an inert internal metric (B03-2) into a published freshness claim in the primary reading surface (B04-1).

§Seam topology

1 connected area7 subsystems · 10 seamsFollow any name to its subsystem report

Connected area 1 · hub

B-01 Survey methodology and agent contracts

7 subsystems · 10 connections

SM-01Two-way seam

WithB-03 Knowledge tools and workflow API

MCP tool protocol and survey phase contract

SM-04Two-way seam

WithB-05 Packaging, installer, validation, and product docs

packaged agent and reference mirrors

SM-07Two-way seam

WithB-06 Report interface design and validation studies

reporting terminology and information-architecture contract

SM-10Two-way seam

WithB-05 Packaging, installer, validation, and product docs

activation contract (installation scope, skill destination, config markers)

Other connection in this area

B-02 MCP core, persistence, and lifecycleSM-02↔ServerContext and memory.dbB-03 Knowledge tools and workflow API

B-03 Knowledge tools and workflow APISM-03↔materialize_docs subprocess and storage/docs projectionB-04 Diff-aware materializer

B-05 Packaging, installer, validation, and product docsSM-05↔packaged Python materializer mirrorB-04 Diff-aware materializer

B-06 Report interface design and validation studiesSM-06↔report projection design/component contractB-04 Diff-aware materializer

B-07 Embedded research surveys and platform trialsSM-08↔research-backed report design constraintsB-06 Report interface design and validation studies

B-03 Knowledge tools and workflow APISM-09↔entries table (staleness columns: stale, stale_since, stale_reason)B-04 Diff-aware materializer

§Staleness map

Staleness distribution

B-0535

B-0313

B-089

B-049

B-028

B-018

B-062