docs: record the open question about non-conformant knowledge bases

The adapter that adoption generates is schema-correct and inert: it is created
with empty topics on purpose, so `context` on such a repository returns an
empty bundle. That is the honest answer at apply time, but it leaves the
repository without routing indefinitely, which is the whole point of a KDB --
so whether the adapter should stay or the legacy file should be rebuilt into
one canonical index is a real open question, not a settled one.

Recorded as research rather than as a runbook change: no decision was taken and
no behaviour changed. The note argues against rebuilding, and identifies why
the adapter cannot yet grow into a replacement -- runbook 11.1 offers
`Topic.data.x-selector` as the way to index sections of a legacy source, and
build_context assembles bundles from document ids and never reads it. Until
that exists a topic can only reference a whole legacy file, so incremental
migration has nowhere to start.

Also names the question that precedes both options: whether the legacy file is
a knowledge base in a foreign format or domain data that was called kdb, which
adoption currently cannot distinguish and does not ask.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Alexander Baranov
2026-08-24 23:26:50 +03:00
co-authored by Claude Opus 5
parent c483d94f36
commit 693211cee9
2 changed files with 79 additions and 0 deletions
+8
View File
@@ -54,6 +54,7 @@ spec:
documents:
- adoption-runbook
- stewardship-specification
- legacy-kdb-treatment
data:
loadPolicy: runbook-first
phases:
@@ -192,6 +193,13 @@ spec:
mediaType: text/markdown
authority: manual
status: draft
- id: legacy-kdb-treatment
title: Legacy knowledge base treatment options
role: explanation
path: docs/research/legacy-knowledge-base-treatment.md
mediaType: text/markdown
authority: manual
status: draft
- id: repoctl-human-guide
title: repoctl CLI reference for humans
role: explanation