Amanuensis

Evidence

System boundaries

Inspect shared objects and ordering assumptions where independently understandable subsystems meet.

Branch  main Checked  adc4ce04aa57 As of  2026-08-29 04:56:43 No recorded stale entries
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

SM-01

Kind
rpc
Parties
B-01 ↔ B-03
Assessment ready
✅

Shared object

MCP tool protocol and survey phase contract

Notes

Assessed at b8b566f: protocol/tool contract passed; generative truth remains evidence-gated.

SM-02

Kind
table
Parties
B-02 ↔ B-03
Assessment ready
✅

Shared object

ServerContext and memory.db

Notes

Assessed at b8b566f: context/schema contract mapped; B02-1 remains a visible recoverability defect.

SM-03

Kind
file
Parties
B-03 ↔ B-04
Assessment ready
✅

Shared object

materialize_docs subprocess and storage/docs projection

Notes

Assessed at b8b566f: storage/process/summary contract passed; timeout remains unresolved.

SM-04

Kind
file
Parties
B-05 ↔ B-01
Assessment ready
✅

Shared object

packaged agent and reference mirrors

Notes

Assessed at b8b566f: root agent sources are copied into the package mirror at prepack.

SM-05

Kind
file
Parties
B-05 ↔ B-04
Assessment ready
✅

Shared object

packaged Python materializer mirror

Notes

Assessed at b8b566f: root materializer source is copied and the published layout is smoke-tested.

SM-06

Kind
other
Parties
B-06 ↔ B-04
Assessment ready
✅

Shared object

report projection design/component contract

Notes

Assessed at e33bb5f under SC-3: refined coverage index, contextual identifier treatment, and prose-flow measures align; design validator and full materializer integration/red paths pass.

SM-07

Kind
other
Parties
B-06 ↔ B-01
Assessment ready
✅

Shared object

reporting terminology and information-architecture contract

Notes

Assessed at e33bb5f under SC-4: both sides agree on sparse coverage, contextual identifier definitions, intact status labels, and 120ch/190ch prose flow.

SM-08

Kind
other
Parties
B-07 ↔ B-06
Assessment ready
✅

Shared object

research-backed report design constraints

Notes

Assessed at e33bb5f under SC-5: B-06 preserves B-07's report-owned re-entry boundary, uses stricter visible copy where appropriate, and retains reader/browser/AT limitations rather than promoting evidence to an efficacy claim.

SM-09

Kind
table
Parties
B-03 ↔ B-04
Assessment ready
✅

Shared object

entries table (staleness columns: stale, stale_since, stale_reason)

Notes

Assessed during the 2026-08-27 refresh under concern VG-1. The seam is broken on both sides of the same absent writer: no code path inserts into entries, so B-03 publishes stale_entries=0 and an empty backlog, and B-04 publishes an affirmative freshness sentence. Findings B03-2 (inert staleness surface) and B04-1 (absence rendered as health) are the two halves. Schema authority sits with B-02, so a fix must decide whether entries is populated, whether staleness moves to a populated table such as file_ledger or subsystems, or whether the legacy surface is retired along with its public signals.

SM-10

Kind
config
Parties
B-01 ↔ B-05
Assessment ready
✅

Shared object

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

Notes

Assessed during the 2026-08-27 refresh. Verified in agreement at 5694080: scope defaults, $CODEX_HOME destinations, project-pin paths, the non-Codex --scope user rejection, and both contract markers match between setup.md and cli.ts. The agreement is currently maintained by hand; ADR-0021's A19 receipt is the closest thing to a check on it.