The design record is read where it is written, never copied to be found
Decides the question 006 narrowed to. An agent reads this repository directly and the search consults it, so these documents surface beside ordinary results instead of only when somebody already suspects they exist. A scheduled sync into the mesh's memory was the option that works with what exists today, and lost on the ground this repository can least afford: it makes a second copy, and the copy that is searched quietly stops matching the copy that is edited. A design record that has silently diverged from the reasoning it claims to carry is worse than one that cannot be found — the first misleads, the second merely fails. Amends what 0019 promised rather than satisfying it: these documents will not be indexed, they will be read. The commitment that survives is the one that mattered — that a searcher finds them without already suspecting they exist. Gated on an agent that does not exist yet, so 006 stays open on the build with a decided shape. What closes it is a check that fails today by design: search the mesh's memory for a phrase that appears only in a design document here, and require it back.
This commit is contained in:
@@ -3,7 +3,7 @@ status: located
|
||||
opened: 2026-08-23
|
||||
located-in: [hal, hq]
|
||||
fixed-by:
|
||||
amended-design:
|
||||
amended-design: 02-DECISIONS/0025-the-design-record-is-read-not-copied.md
|
||||
---
|
||||
|
||||
# 006 — This repository is not indexed into the knowledge base, and the claim that it is holds up a decision
|
||||
@@ -136,3 +136,22 @@ about how the knowledge system works, not a defect to be fixed quietly.
|
||||
|
||||
**Marking it resolved while the indexing does not exist would be the failure this repository was
|
||||
created to name**, one folder away from where it names it.
|
||||
|
||||
## The direction is decided
|
||||
|
||||
*2026-08-31.* **The agent reads this repository; nothing is copied.** Recorded as
|
||||
[ADR 0025](../../02-DECISIONS/0025-the-design-record-is-read-not-copied.md), which also amends
|
||||
what [ADR 0019](../../02-DECISIONS/0019-how-this-repository-works.md) promised: these documents
|
||||
will not be *indexed*, they will be *read*, and the search consults the agent so its answers
|
||||
appear beside ordinary results.
|
||||
|
||||
A sync was the option that works with what exists today, and it was rejected on the one ground
|
||||
this repository can least afford: it makes a second copy, and *the copy that is searched quietly
|
||||
stops matching the copy that is edited*.
|
||||
|
||||
**So the open question above is answered, and this report stays open on the build.** What closes
|
||||
it is the check ADR 0025 names — search the mesh's memory for a phrase that appears only in a
|
||||
design document here, and get it back. That check fails today by design.
|
||||
|
||||
**What stands until then** is the signpost, and the honest description of it: reachable, not
|
||||
surfacing.
|
||||
|
||||
Reference in New Issue
Block a user