Amanuensis

Reference

Calibrated review checklist

See the concern set used to test each subsystem and the provenance of those checks.

Branch  main Checked  adc4ce04aa57 As of  2026-08-29 04:56:43 No recorded stale entries

Derived: 2026-08-12 from onboarding session mspky4v5-2wuk50if at b8b566f

This file supersedes the generic territory catalog for the self-survey. A disposition is terminal only when it carries evidence or a tracked unresolved destination.

§Active concerns

active concerns
CodeCategorySource territoryCodebase-specific probe
SI-1scope identityT1Try to make project-key derivation conflate workspaces or escape the configured storage root; inspect the stored workspace_path response.
SI-2revision identityT1Trace evidence/artifact SHA fields through writes and reads; attempt reuse at another revision.
CC-1derived-state coherenceT2Enumerate every materialized page's DB/prose dependencies and compare them with the page plan and manifest.
TB-1temporal boundsT3Enumerate git and Python subprocess calls; locate timeout, cancellation, and failure propagation.
EP-1exceptional pathsT4Inject one renderer failure and inspect global status, retained pages, manifest writes, and publication behavior.
EP-2exceptional pathsT4Fail validation/SQL/filesystem steps inside mutating tools and compare pre/post dependent rows.
IF-1incremental/full parityT6Render incremental, force-full, and clean export from identical state and compare state, coverage, and bytes.
AT-1atomicityT7Inspect every multi-table mutation for one transaction covering the invariant it claims.
AT-2checkpoint atomicityT7Mutate DB under WAL, call commit_phase_gate, clone/restore the storage commit, and verify the mutation exists.
CR-1concurrencyT8Race writers, locks, SQLite WAL commits, and storage git commits; reconcile landed records and history.
RL-1resource lifecycleT9Inject success/error/timeout/cancel at DB, child-process, temporary-directory, and materializer-lock boundaries.
RL-2workflow lifecycleT9Abandon sessions, dispatches, questions, and locks; verify explicit recovery and authority behavior.
TR-1trust boundaryT10Fuzz MCP paths/enums/strings for storage escape, SQL/git injection, and depth-authority bypass.
TR-2installer trust boundaryT10Feed conflicting/commented/malformed configs and hostile paths; verify backup, preservation, and refusal behavior.
SC-1schema/tool/materializer seamT11Change a schema field and require tool queries plus Python projections to fail or update together.
SC-2source/package seamT11Compare root agent/materializer sources with package mirrors from a clean tree and require generated inventory parity.

§Non-applicable during onboarding

non applicable during onboarding
TerritoryDisqualifying condition
T5 aliasing and ownershipNo cross-request shared returned mutable object was established in the onboarding read. Request/response values cross MCP serialization; residual process-local state is covered by CR-1/RL-2. Reopen if a subsystem structural pass finds an alias.

§Discovered concerns

None promoted during onboarding. The Codex registration gap is a B-05 open question, not yet a correctness concern. The WAL/checkpoint observation is already captured by AT-2.