Files
repoctl/kdb/kdb.yaml
Alexander BaranovandClaude Opus 5 693211cee9 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>
2026-08-24 23:26:50 +03:00

210 lines
6.7 KiB
YAML

apiVersion: stewardship.corsus.ru/v1alpha1
kind: KnowledgeBase
metadata:
name: repository-stewardship-kdb
title: Repository Stewardship knowledge index
spec:
repository: repo:repository-stewardship
defaultLanguage: ru
topics:
- id: repository-bootstrap
title: Bootstrap a new repository
summary: Choose a repository type and create the minimal Stewardship layer without inventing domain content
intents:
- repository.initialize
- repository.bootstrap
keywords:
- init
- template
- ssh
- contract
priority: 90
documents:
- stewardship-specification
- stewardship-guide
data:
loadPolicy: headings-only
readHints:
- document: stewardship-specification
headings:
- 1. Цели и границы
- 3. Каноническое обнаружение
- 5. RepositoryContract
- 6. ContentRoot
- 17. Agent entrypoints и adapters
- 18. Bootstrap, adoption и template update
- document: stewardship-guide
headings:
- 4. Минимальная структура репозитория
- 5. Четыре типа репозиториев
- 17. Bootstrap нового и adoption существующего репозитория
- id: repository-adoption
title: Adopt an existing repository
summary: Assess, plan and apply a metadata overlay while preserving existing authoritative content
intents:
- repository.adopt
- repository.standardize
- repository.normalize
keywords:
- assess
- overlay
- legacy
- migration
priority: 100
documents:
- adoption-runbook
- stewardship-specification
- legacy-kdb-treatment
data:
loadPolicy: runbook-first
phases:
- assess
- plan
- review
- apply
- verify
readHints:
- document: adoption-runbook
headings:
- 3. Safety invariants
- 6. Phase 1 — preflight
- 7. Phase 2 — assessment
- 10. Phase 4 — adoption plan
- 11. Compatibility rules
- 11.5. Normalization recipe documents-to-content-root
- 12. Phase 5 — apply
- 13. Phase 6 — verify
- id: stewardship-model
title: Understand or evolve the model
summary: Definitions, invariants, schemas and the reasoning behind Repository Stewardship
intents:
- repository.model.explain
- repository.model.change
- repository.standard.design
keywords:
- contract
- intent
- capability
- requirement
- binding
- kdb
priority: 80
documents:
- stewardship-specification
- stewardship-guide
- architecture-options
data:
loadPolicy: specification-first
authorityOrder:
- stewardship-specification
- stewardship-guide
- architecture-options
- id: tooling-implementation
title: Implement repoctl or an adapter
summary: Implementation boundary, commands, validation rules and harness-neutral adapter design
intents:
- repository.tooling.implement
- repository.tooling.test
- repository.tooling.use
- repository.adapter.create
- repository.handoff
keywords:
- repoctl
- parser
- schema
- validator
- skill
- mcp
priority: 85
documents:
- stewardship-specification
- adoption-runbook
- stewardship-guide
- repoctl-human-guide
data:
loadPolicy: selected-sections
readHints:
- document: stewardship-specification
headings:
- 19. Команды MVP
- 20. Validation rules MVP
- 21. Security invariants
- 22. Versioning и расширения
- 23. Порядок реализации
- 24. Acceptance criteria MVP
- document: stewardship-guide
headings:
- 14. Интерфейсы для агентов и людей
- 15. Простая первая версия
- 16. Предлагаемая внутренняя структура repoctl
- document: repoctl-human-guide
headings:
- Команды по порядку знакомства
- Коды возврата
- Устранение неполадок
- id: architecture-research
title: Revisit architecture choices
summary: Earlier alternatives, trade-offs and external design lineage
intents:
- repository.architecture.research
- repository.architecture.compare
keywords:
- architecture
- alternatives
- backstage
- gitops
- mcp
priority: 50
documents:
- architecture-options
- stewardship-specification
data:
loadPolicy: research-on-demand
readHints:
- document: stewardship-specification
headings:
- 28. Design lineage
documents:
- id: stewardship-specification
title: Repository Stewardship Protocol
role: reference
path: docs/specification.md
mediaType: text/markdown
authority: local-canonical
status: draft
- id: stewardship-guide
title: Repository Stewardship human guide
role: explanation
path: docs/guide.md
mediaType: text/markdown
authority: local-canonical
status: draft
- id: adoption-runbook
title: Repository Adoption Runbook
role: runbook
path: docs/adoption-runbook.md
mediaType: text/markdown
authority: local-canonical
status: draft
- id: architecture-options
title: Infrastructure operations architecture options
role: explanation
path: docs/research/infrastructure-operations-architecture-options.md
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
path: docs/repoctl.md
mediaType: text/markdown
authority: local-canonical
status: draft