Commit all in-flight work — ckb-module and ckb-reset skills, the .agents/modules/ scaffold, OPENSPEC docs, decision records D-0001 and D-0002, graph edges and workload summaries — so the reset that follows is fully recoverable. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
17 lines
773 B
Markdown
17 lines
773 B
Markdown
# KB-root specs
|
|
|
|
Cross-cutting capability specs — the ones that span several `src/` repos and that
|
|
no single repo owns. Managed by the `ckb-spec` skill.
|
|
|
|
* `specs/<capability>.md` — current truth. What the system, as a whole, does.
|
|
* `changes/<change-id>/` — a proposed delta, not yet true.
|
|
* `changes/archive/` — applied or rejected changes. Immutable; often worth a
|
|
matching decision record under `wiki/decisions/`.
|
|
|
|
Specs for how *one* repo implements a capability belong in that repo, at
|
|
`src/<repo>/openspec/`, where OpenSpec's own tooling manages them and they travel
|
|
with the code. Link the two with `implements:` / `implemented_by:` — both sides,
|
|
always.
|
|
|
|
Unlike `src/`, this directory **is** tracked in the KB's git history: it is
|
|
knowledge, not code.
|