amanuensis

Unresolved

Leads

Open observations that are not yet findings.

Branch  main Checked  ec5824bceb9c As of  2026-10-07 22:54:09 Stale: 0 with a survey obligation, 65 exempt, of 655 scoped files

Observations from every survey pass that are not yet findings: patterns, anomalies, connections, tensions, and candidate concerns recorded when a reader noticed something the phase structure did not ask for. Closed leads are on Resolved leads and questions.

§Tension

1 open lead.

  • The live store carries 37 inherited obligations: 23 have terminal outcomes and 14 have none. Historical acceptance receipts measured a 22-record carry at their own revision, and do not discharge later undecided records. This source refresh leaves those decisions open and makes no fully-surveyed claim; the current overview publishes live counts alongside 10 open findings and 6 open questions. @ Inherited findings and historical receipt subjects · recorded 2026-10-07 22:55 UTC

§Anomaly

2 open leads.

  • During self-refresh, the MCP binding correctly named this repository, but rendering treated the historical workspace_path record as the operational checkout and published the old survey-depth HEAD 7384acbbb559. Commit ec5824b passes the bound checkout through --workspace to rendering, read-back and promotion. Regressions passed for a tool invoked from cwd=/ and a real relocated-store projection with provenance preserved. This repair follows published beta.3; that released package is unchanged. @ B-03/B-04/B-09 materializer publication boundary · recorded 2026-10-07 22:55 UTC
  • Measured over this store at 2388433 by extracting each evidence row's file at its own ref_sha and counting lines: 13 of the 35 rows carrying a line_range point past the end of the file they name — ev13 git.ts:detect_changes 1319-1384 of 465, ev14 carried.ts:record_carried_outcome 3512-3639 of 735, ev17 xrefs.ts:resolvesInWorkspace 581-588 of 107, ev18 dashboard.ts:get_dashboard 141-148 of 85, ev19 artifacts.ts:resolveArtifactPath 689-712 of 177, ev20 dashboard.ts:get_dashboard 102-121 of 85, ev21 findings.ts:verify_finding_fix 1792-1798 of 486, ev22 stale.ts:clear_staleness 1107-1120 of 135, ev23 findings.ts:update_finding_status 1696-1700 of 486, ev24 phase-2-structural.md 238-302 of 254, ev25 onboarding.md 213-250 of 205, ev27 refresh.md 345-357 of 141, ev31 diagrams.py:subsystem_dependency_view 1022-1048 of 307. Every named symbol does exist in its file and the behaviour each row was cited for holds where the symbol actually is, so these are displaced coordinates rather than invented observations — the mechanism is recorded as finding B03-R5. The same displacement appears in the root_cause prose of B03-R1, B03-R2, B03-R3 and B03-R4, which are the four findings re-found from carried obligations; the ranges they quote are the archived store's, not this repository's. @ .amanuensis/memory.db:evidence · recorded 2026-09-18 02:14 UTC

§Connection

4 open leads.

  • Re-examination of the design-lane backlog distinguishes historical receipt subjects from live refresh state. Acceptance and dogfood receipts name a00d6f2; depth receipt names d206ad7 and the archived lane storage path. Acceptance witnesses 652 ledger paths, 357 examined of 496 obligations, 50 attached dispositions, 22 carried records and zero mapped subsystems. Survey progress's numeric end matches those historical counts. Plan marks P10/P11/P9 done and reviews complete, without advancing subsystem statuses. Recorder changes add reported deltas, UTC transition handling, seeded-vs-seam concern separation and batch-label support. Gate changes validate recorder outputs, progress census/final coverage, carry-audit producer output and store-scoped P17 denominators with historical and false-identity controls. Final review leaves mistaken carried-outcome correction deferred; Pecia pc-f6ec and pc-6425 retain that gap and regeneration/store-subject debt. Historical receipts remain historical evidence, not a current a521e28 acceptance claim. @ B-09: design/survey-depth/{spec.md,claims.md,plan.json,plan.md,survey-progress.json,acceptance-receipt.json,reviews/slice-S4/dispositions.md,reviews/final/dispositions.md}; design/reader-lenses/{dogfood-receipt.json,rebuild-depth-receipt.json}; dev/{record-survey-depth.mjs,record-rebuild-depth.mjs,test-survey-depth.mjs,test-rebuild-depth.mjs,test-survey-depth-acceptance.mjs,test-carry-receipt.mjs,test-pecia-carry-audit.mjs,amanuensis-defects-to-pecia.mjs,pecia-dogfood.md} · recorded 2026-10-07 22:46 UTC
  • Delivery re-examination records beta.3 package/runtime version alignment, explicit workspace handshake in product docs and generated tool inventory, and a new CI stdio regression. Release metadata names immutable db474db tag, npm checksum b17634c76f687468434c25aab7bbf30b3182b34e, publish run 37692059909 and four-platform smoke run 37693422887; prior integration receipt remains historical. Lockfile changes only release version and proxy-addr 2.0.8. README adds describe_locus/get_attention/get_history and refresh guidance. No repository-wide green CI claim is introduced. @ B-05: README.md; HISTORY.md; INSTALLATION.md; ROADMAP.md; dev/roadmap.json; mcp-server/package.json; mcp-server/package-lock.json; mcp-server/DEVELOPMENT.md; .github/workflows/test.yml · recorded 2026-10-07 22:44 UTC
  • Re-examination of the materializer delta: a declined vocabulary status now requires a declination whose ref_sha resolves in the bound workspace; unreachable rows remain history and render not-recorded. The corresponding test compares an all-zero nonexistent revision and real HEAD in both directions. Existing B04-R1 marker expectations and B04-R2 unresolved length-dependent link failure are not addressed by this delta and remain open. @ B-04: materializer/amanuensis_materializer/renderers.py:_vocabulary_state; materializer/test-unmeasured-coverage.py · recorded 2026-10-07 22:43 UTC
  • Re-examination at a521e28: the skill probes deferred tools and verifies get_project_info(workspace) against the chat root. Runtime context now starts project=null for Codex app-server parents and filesystem-root launch; tool discovery remains reachable, state tools refuse unbound calls, nested handshake paths normalize to the Git root, and an existing binding cannot switch roots. project.ts rejects filesystem root and accepts store relocation only with verified logical repository identity. This supersedes the B-03 structural artifact's statement that ctx.project is frozen at startup: it is selected once at startup or the first handshake, then immutable. Existing subsystem statuses remain unchanged; no new full survey is claimed. @ B-01, B-02, B-03: .claude/skills/amanuensis/SKILL.md; mcp-server/src/index.ts; mcp-server/src/codex-host.ts; mcp-server/src/project.ts; mcp-server/src/tools/project.ts · recorded 2026-10-07 22:42 UTC

§Pattern

3 open leads.

  • Changed delivery tests add status-checked Pecia setup, carry-role/anchor/filter/identifier ingress controls, duplicate-owned deletion reconciliation, app-server parent recognition, verified repository-copy read-back with foreign/tampered-store refusal, and ten public stdio handshake groups. These changes match their runtime deltas. Test source examination is not execution evidence for all suites; beta.3 package and workspace execution results are separately recorded in dev/release-notes-v0.2.0-beta.3.md. @ B-05: dev/test-amanuensis-pecia-defects.mjs; mcp-server/test-carried-findings.mjs; mcp-server/test-scope-reconciliation.mjs; mcp-server/test-codex-parent-workspace.mjs; mcp-server/test-workspace-binding.mjs; mcp-server/test-codex-app-workspace.mjs · recorded 2026-10-07 22:44 UTC
  • Re-examination of carried.ts changes since c073404: archived anchors are mandatory for nonempty carry sources; evidence roles and outcome filters use bounded vocabularies; store/subsystem identifier lengths and legacy compact-page fields are bounded. git.ts now deduplicates absent scope gaps by path while preserving per-owner ledger staleness. The structural account of transactional writes remains applicable; these narrow ingress and duplicate-ownership failure modes rather than resolving the five existing B-03 findings. @ B-03: mcp-server/src/tools/carried.ts; mcp-server/src/tools/git.ts · recorded 2026-10-07 22:42 UTC
  • Three guards in this subsystem share one shape: read the declaration out of the source that already exists, then assert the live state against it, rather than maintaining a second list. requireSchemaObjects parses schema.sql's own CREATE statements; helpers.ts re-exports the obligation split from the generated vocabulary module instead of restating it; the concern checklist was moved out of a gate's literal into a contract for the same reason. REQUIRED_VIEWS is the one place the pattern is not applied — two view names maintained by hand — and it is the one that predates the others. @ mcp-server/src/db.ts:requireSchemaObjects@c0734040022f0e1f1b9d8c480259f6142a875fca · recorded 2026-09-15 04:29 UTC