From 90b44a48df4fd14b7070c164e871fec7504a6a53 Mon Sep 17 00:00:00 2001 From: jochen Date: Wed, 30 Sep 2026 18:09:54 +0200 Subject: [PATCH] Issue 006 resolved: the record is read where it is written, and the console lists it Design 35 implemented with what shipped and the live check; 006 closes on ADR 0025's own test, run through the console. --- 03-DESIGN/01-to-be/35-reading-the-record.md | 16 +++++++++++++++- .../00-report.md | 19 ++++++++++++++++--- 2 files changed, 31 insertions(+), 4 deletions(-) diff --git a/03-DESIGN/01-to-be/35-reading-the-record.md b/03-DESIGN/01-to-be/35-reading-the-record.md index 40d8416..0eff58f 100644 --- a/03-DESIGN/01-to-be/35-reading-the-record.md +++ b/03-DESIGN/01-to-be/35-reading-the-record.md @@ -1,6 +1,6 @@ --- layer: to-be -status: in-progress +status: implemented code: [mesh-catalog modules/records] updated: 2026-09-30 decisions: @@ -71,6 +71,20 @@ harmless. The mesh session of design 15, when it exists, calls this rather than | a sync against an unreachable origin leaves the checkout standing and says why | silence and success never look alike | | live: through the console, `records_search` for a phrase that appears only in a design document here returns it | issue 006's closing check | +## What shipped, 2026-09-30 + +mesh-catalog PR 183, then PR 185. Verified on the live mesh the same evening: `records` assigned to the +control node with `{"repository": …}` as its setting, its checkout at the repository's `main` with 478 +documents, its five tools listed by the console beside every other tool, and — ADR 0025's check — +`records_search` for a phrase from this document's title returned it from where it is written, with +the commit. The first live search missed: the phrase chosen from ADR 0025 straddled a line break under +emphasis, and the reader matched single lines. PR 185 matches a line together with the next and +ignores emphasis marks, which the module's test now covers; until it rolls, a phrase that wraps is one +to shorten. + +The reader's `consumes` names the forge module's event rather than the `git` seat, because the seat +declares none; a merge into the repository was seen and pulled within seconds. + ## What this does not settle - Ranking or meaning. A search that understands a question is the session's job, not the reader's. diff --git a/04-ISSUES/006-hq-is-not-indexed-into-the-knowledge-base/00-report.md b/04-ISSUES/006-hq-is-not-indexed-into-the-knowledge-base/00-report.md index 08eba24..a8812d3 100644 --- a/04-ISSUES/006-hq-is-not-indexed-into-the-knowledge-base/00-report.md +++ b/04-ISSUES/006-hq-is-not-indexed-into-the-knowledge-base/00-report.md @@ -1,9 +1,9 @@ --- -status: located +status: resolved opened: 2026-08-23 located-in: [mesh-catalog modules/records, mesh-catalog modules/mesh-console] -fixed-by: -amended-design: 02-DECISIONS/0025-the-design-record-is-read-not-copied.md +fixed-by: ADR 0153; mesh-catalog PR 183 (records), PR 185 (a phrase that wraps) +amended-design: 03-DESIGN/01-to-be/35-reading-the-record.md --- # 006 — This repository is not indexed into the knowledge base, and the claim that it is holds up a decision @@ -193,3 +193,16 @@ forge and answering `records_search`, `records_read`, `records_list`, `records_s [35 — Reading the record](../../03-DESIGN/01-to-be/35-reading-the-record.md). The module's test runs 0025's check against a repository it makes; this record closes when the same check passes through the console on the live mesh, and says so below. + +## Resolved, 2026-09-30 + +The check ADR 0025 names passed on the live mesh: through the console on a workstation, +`records_search` for a phrase that appears in one design document here returned that document and the +commit it was read at, from a checkout the mesh keeps and nobody copied. What this record asked on +2026-08-23 — *does the searcher find it without already suspecting it exists?* — is answered by where +the tool sits: in the same list as the forge's and the mesh's own, described as the thing to search +before forming a hypothesis. Reachable became surfacing when the surface became a list. + +Open beside it, and not this record's: the mesh has no symptom-indexed memory at all since the +cut-over ([as-is 07](../../03-DESIGN/00-as-is/07-knowledge.md) says so), and the lessons of these +days are in this repository by hand.