---
status: open
opened: 2026-08-23
located-in: [hal, hal-hq]
fixed-by:
amended-design:
---

# 006 — This repository is not indexed into the knowledge base, and the claim that it is holds up a decision

## Symptom

[`README.md`](../../README.md) states, as the answer to the objection against creating this
repository:

> These documents are still indexed into the knowledge base, so `recall_search` returns them
> beside everything else. One source, many surfaces — which was always the actual requirement.

Searching the knowledge base for this repository's content returns nothing.

## Evidence

Verified 2026-08-23, two searches against the mesh's operational memory:

| Query | Result |
|---|---|
| The full title of a decision record in this repository | No results |
| A distinctive phrase from the decision ledger | No results |

No entry, no partial match, no stale copy. The indexing does not exist and appears never to
have existed.

## Why this is an issue and not a task

The claim is **load-bearing**. Decision 27 separates HQ into its own repository, and the
objection it answers was that a fourth knowledge system repeats the mistake the mesh's
knowledge consolidation was created to fix. The recorded answer is *"indexing, not location"* —
that the split is safe **because** these documents remain searchable alongside everything else.

Without the indexing, the objection stands unanswered and this repository is precisely the
fourth knowledge system it was argued not to be. Either the indexing is built, or decision 27's
reasoning is amended to something that is true.

It is also, exactly, the failure this repository names in its own rules: a document stating a
rule about the mesh must say how the rule is checked. This one stated a mechanism and nobody
checked it — including in the same commit that wrote the rule.

## Open questions

- Where would the indexing run? The operational memory is written through a mesh capability;
  is this a periodic sync of a repository into it, or a search surface that reads the
  repository directly?
- Which store — the flat symptom-indexed memory, the structured archive, or both? They have
  different lifecycles ([`02-DESIGN/00-as-is/07-knowledge.md`](../../02-DESIGN/00-as-is/07-knowledge.md)),
  and this content is governed rather than incidental.
- Public repository, private mesh: the sync direction must not become a path for mesh-specific
  content to arrive **into** these documents.