Michał Kopeć
0c06cb64ab
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>
23 lines
1.2 KiB
Markdown
23 lines
1.2 KiB
Markdown
## MODULE: software
|
|
|
|
This KB documents software being built here. Source repos live in `src/<repo>/`
|
|
as **gitignored plain clones**, each with its own remote and history.
|
|
|
|
- `src/` is **evidence, not a cascade layer.** `ckb-retrieve` may open and cite
|
|
code to verify a claim; it never answers "what is entity X", and `ckb-ingest`
|
|
never treats code as inbox material.
|
|
- **Never `git add` under `src/`.** Those are separate repos. `ckb-sync-changes`
|
|
reports each one's dirty/ahead state separately and commits none of them.
|
|
- Every repo has a `type: repository` page in `wiki/entities/` — the durable
|
|
record, since the clone may be absent from a fresh checkout.
|
|
- Specs live at two levels: `openspec/` at the KB root (cross-cutting, owned by
|
|
`ckb-spec`) and `src/<repo>/openspec/` (per-repo, owned by OpenSpec itself).
|
|
They link via `implements:` / `implemented_by:`.
|
|
|
|
| User intent | Skill |
|
|
|---|---|
|
|
| Map or refresh a `src/` repo into wiki entities | `ckb-code-map` |
|
|
| Write, sync, or bridge specs (either level) | `ckb-spec` |
|
|
|
|
Module-contributed page types: `repository`, `component`, `spec`. Additional
|
|
optional frontmatter: `repo`, `commit`, `spec_id`, `implements`, `implemented_by`.
|