announce_title replaces ask_title; no question, no waiting. D-0006 reverses
point 1 of D-0005.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
- Rule E opens a new session with the title question (conversations.ask_title);
save_conversation.py --set-title stores it, saved transcripts and workload use it
- New ckb-routine skill + routines.py: time-since-last actions in ckb.yaml,
checked at session start, run after the user's request, last_run committed
- Docs EN/PL, D-0005, smoke test coverage for both scripts
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
- ckb-init no longer copies tests/.
- ckb-upgrade drops tests/ from the template layer and offers once to
delete a leftover copy from an older template.
- Directory contract, READMEs, manuals and changelogs (en/pl) say so.
- Smoke test itself unchanged.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
- Rule E resolves git user.name/user.email once per session; OS user as
stated fallback.
- Rule D: one workload file per person per day,
YYYY-MM-DD_<author>_summary.md with type: session frontmatter; older
files read as before.
- Rule B log format gains an optional, lint-neutral **Author:** line;
wiki/log.md header and ckb-upgrade example updated.
- save_conversation.py records an author row (--author override); smoke
fixture passes a fixed author.
- ckb-project-summary and ckb-module cite the new workload name.
- D-0004 records the decision; manual, READMEs and changelogs in English
and Polish.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
- ckb.yaml: conversations.autosave (default false). On, Rule E saves every
session at its end without asking; ckb-add-conversation toggles it on
request.
- Per-machine half: autosave_hook.py --check/--install/--remove manages a
Claude Code Stop hook in gitignored .claude/settings.local.json. Rule E
runs --check at session start when autosave is on and asks before
changing machine configuration; toggling the switch asks the same.
- save_conversation.py --from-hook reads transcript_path from hook stdin.
- ckb-init writes the block, ckb-upgrade leaves it alone.
- Manual, READMEs and changelog in English and Polish; Polish changelog
also gains the missing 1.11.1 and 1.12.0 rows.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
- New skill ckb-add-conversation: on request, copies the session's Claude
Code transcript (JSONL) into raw/saved-conversations/<date>/ with a
readable Markdown rendering and an index.md; answers "did we discuss X"
from those files. Saved conversations stay outside retrieval and ingest.
- AGENTS.md: directory contract, cascade note, routing row, disambiguation,
Rule E session-end ask (save only on a yes).
- ckb-retrieve, ckb-ingest, ckb-reset (tier 3), ckb-init know the folder.
- Docs, both READMEs, CHANGELOG, VERSION; smoke test renders a fixture
transcript against a golden file.
- .gitignore: ideas/ local scratch folder for template ideas.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Remove the 1.11.1 session summary and refresh scaffold dates. Wiki content
was already empty: 0 pages, 0 decision records, 0 graph edges.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Four deterministic-script defects plus a contract gap, all reported by a
downstream KB running 1.11.0. None of them crashed; each produced confident,
wrong output, which is why they went unnoticed.
retrieve_candidates.py:
- load_pages() walked rglob unsorted, so tests/expected/retrieve.json encoded
one machine's directory order and the smoke test failed on a clean clone.
- cited_by used setdefault, crediting a shared source to whichever page was
walked first and dropping the source from the results entirely, so the other
citing pages reported corroborated_by: []. Now every citing page is credited.
lint_report.py:
- check 12 reported a cited directory as "does not exist", because is_file()
is false for a directory. Citing a subtree is now explicitly legal and
carries no fingerprint; same fix in lint_quick.sh and lint_quick.ps1.
- check 8 keyed log entries on timestamp + file with the action type dropped,
so a Rule B POINTER was indistinguishable from a duplicate of the entry it
points at. POINTER is now exempt; genuine duplicates still fire.
- check 13 required a backticked path, so "— Chat conversation, Name, date"
counted as unattributed although AGENTS.md lists it as a first-class source.
Attribution and verifiability are now separate questions.
AGENTS.md documents both resolved contract gaps: directory citations, and the
two legal attribution shapes. The fixture KB gained coverage for all three lint
defects — each finding fires under the old script and is silent under the new.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Remove the two workload summaries and refresh scaffold dates after the
1.11.0 template work. Wiki content was already empty.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
- D-0003: <python> interpreter resolution, per-OS install guide, lint_quick.sh/.ps1
session-start fallback, manual lint checklist, no-script retrieval path,
exporters declare Python a hard requirement
- Lint check 13 pairs each Crux quote block with the attribution under it, so a
multi-source Crux no longer cross-fails; fixture KB gains a second source
- Session summaries for 2026-09-29 and 2026-10-01
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
- Skills: descriptions cut to routing-hint length (1925w -> 840w), Trigger
phrases removed, Purpose collapsed, Edge cases moved to references/.
- Rule B names the decisions-log exception; "Sync the wiki" trigger dropped;
reserved sections "Four" -> "Three"; directory contract adds ckb.yaml,
docs/, tests/.
- MANUAL/CHANGELOG/OPENSPEC (EN+PL) moved to docs/; template ADRs D-0001 and
D-0002 restored from 0c06cb6 into docs/decisions/; referrers repointed.
- ckb-retrieve: rank fusion moved into scripts/retrieve_candidates.py;
Purpose states the one write it owns (query-gaps).
- tests/: fixture KB, golden JSON, smoke.sh.
- Scaffold: overview.md describes content not schema; graph/index.md names
base skills only; query-gaps.md loses its self-rotting freshness window.
- README/MANUAL/OPENSPEC/CHANGELOG ghost-writer pass in both languages.
- VERSION 1.9.0 -> 1.10.0.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
The template repo now keeps three branches with fixed meanings — main is
stable, test is the release candidate, experimental is development — and
ckb-init/ckb-upgrade can source from any of them instead of only main.
Selection is per-invocation, in words the user already uses ("initialize
from the test branch", "check experimental for updates", "switch back to
stable"), and sticky: the resolved repo and branch are written to a
template: block in ckb.yaml. Without persistence, a KB bootstrapped from
experimental would be silently pulled back to main by its next upgrade.
A missing file or missing block both mean main, so every KB predating
this convention behaves exactly as before.
One consequence needed explicit handling. A KB tracking test or
experimental can sit on a VERSION main has not released yet, so comparing
it against main finds nothing newer — which the version check would have
reported as "up to date". That is true and misleading. ckb-upgrade now
reports it as "ahead", and treats a move back to main as a downgrade:
explicitly confirmed, with the specific losses named, and blocked
outright where kb_schema_version would drop below what local pages are
already written against.
ckb-module is told not to clobber the template: block — a module install
that silently reset a KB's channel would change what its next upgrade
pulls, which is not a module's business.
Documented in both READMEs, both MANUALs and both CHANGELOGs. VERSION
1.8.0 -> 1.9.0; kb_schema_version stays 1.5, since this is tooling rather
than a content contract.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Clears the 3 wiki/log.md entries recording the schema 1.4 -> 1.5 migration.
That was the entirety of Tier 1 content: no entity pages, project scopes,
decision records or graph edges existed to remove.
Only wiki/log.md changed. The other scaffold files already matched what
ckb-init produces at schema 1.5, and edges.json/overview.md keep their
existing last_updated dates because those dates are accurate — bumping them
would assert changes that did not happen.
Rule B would normally require a wiki/log.md entry for a change inside wiki/,
but writing "emptied the log" into the log it just emptied defeats the
reset. The record is in workload/2026-09-22_summary.md instead, and the
migration itself remains documented in CHANGELOG.md and in commits 474630e
and 2c4d57a.
Tier 2 (workload summaries), the template layer, schema 1.5 and template
version 1.8.0 are all preserved. Lint: 0 findings.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Records the cancelled reset (inventory run, nothing deleted) and the
fast-forward merge of graft-ideas into main pushed to both remotes.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Two version numbers exist in this project and are easy to confuse:
kb_schema_version (the content contract, in wiki/index.md) and VERSION
(the tooling layer). Until now neither had a written history, and the
page schema was documented in four places at three levels of detail.
CHANGELOG.md / CHANGELOG.pl.md consolidate both: the current schema in
full (frontmatter for all pages and for decisions, the three reserved
body sections, the closed edge vocabulary with a "since" column, the
reserved scaffold), then the schema history 1.1-1.5 and the template
history 1.0.0-1.8.0.
The history is reconstructed from git rather than from memory, so it
records what actually happened rather than a tidied version of it:
- There was never a schema 1.0; versioning began at 1.1 on 2026-07-13.
- Template 1.4.0 and 1.5.0 were never published — VERSION jumped from
1.3.0 to 1.6.0 on 2026-09-01.
- Connector-backed libs shipped as tooling in 1.1.0, but the schema only
recorded them at 1.2 nine days later. The schema column shows what was
in effect after each release, with a footnote on the lag.
Registered with ckb-init (copied verbatim into a new KB) and ckb-upgrade
(taken wholesale from upstream rather than merged, since upstream is
authoritative about its own history). Cross-linked from both READMEs and
both MANUALs.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Graft keeps a derived, disposable code graph in sync with a content hash
rather than a calendar, and keeps a protected block on every regenerated
node. This KB is the opposite kind of store — durable, curated, built from
material that cannot be regenerated — but several of Graft's mechanisms
port cleanly, and two of them close real gaps here.
Schema 1.5 is additive: every 1.4 page remains valid.
1. `## Crux` — verbatim source excerpts alongside the synthesis. A summary
can drift silently; a quote either still matches its source or it does
not. Lets `ckb-retrieve` ground an answer without a round-trip to the
archive, and makes drift mechanically detectable.
2. `## Notes` — human-authored and protected everywhere. Closes a real
gap: `ckb-index-external` regenerates connector pages wholesale, so an
annotation written there was previously destroyed on the next refresh.
3. `source_fingerprint`/`source_checked` — a digest of the material a page
was built from. Freshness by date says a page has aged; a fingerprint
says whether its evidence moved. Most valuable for connector-backed
libs, where documents change with no notice.
4. `lint_report.py --quick` — a deterministic one-line session-start
signal, wired into Rule E next to the existing `git status` check.
5. In-degree as a rank-fusion signal in `ckb-retrieve`, weighted below 1.0:
centrality is a prior, not evidence.
6. Blast radius — a new `ckb-ingest` step walking the graph backwards from
touched entities to find what the incoming material contradicts, before
writing anything. Ingest was additive-first, which is how a wiki
accumulates two pages that quietly disagree.
7. Edge vocabulary in `wiki/graph/index.md` rewritten as a question per
verb, and completed: `part_of` was written by `ckb-code-map` but never
declared. Added `produces`, `configures`, `validates`, `implements`.
Lint gains checks 12 (fingerprint drift), 13 (crux verbatimness) and 14
(the protected-Notes rule), verified against a synthetic fixture covering
stale digests, missing sources, fabricated quotes and paraphrased evidence.
Not adopted: the gitignored regenerable store, the MCP server and CLI
daemon, tree-sitter parsing, statusline hooks, telemetry.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Empty the KB back to the shape ckb-init creates: remove decision records
D-0001 and D-0002, the single graph edge, all five workload summaries and
the generated outputs/okf/ tree, then restore the empty scaffold with
kb_schema_version held at 1.4.
The decisions status-vocabulary table is preserved verbatim, since
ckb-decide and ckb-lint both validate against it. Lint reports 0 findings.
Restore point for the pre-reset content: tag pre-reset-2026-09-20 (0c06cb6).
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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>
Graph edge endpoints use project-root-absolute paths per Rule C
(`/wiki/entities/foo.md`), while the `known` page set is keyed on paths
relative to `wiki/`. check_graph compared them directly, so every
conformant edge was reported as pointing at a missing page. Add the
`/wiki/`-stripped form to the candidate set, matching the normalisation
the decision-record check already performs.
Bump VERSION 1.6.0 -> 1.6.1.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Decision log (VERSION 1.6.0, kb_schema_version 1.4):
- wiki/decisions/ scaffold — numbered NNNN-slug.md records, own index
(with status vocabulary) and log
- type: decision adds status/decided_on/decided_by/affects/review_on;
supersedes/superseded_by carry history and must be set on both sides
- New ckb-decide skill: records decisions and answers what/why/who/when,
what superseded what, and what is still open. Decision pages are
append-only — a changed mind is a new superseding decision
- Graph gains decided_by and affects edge types
- ckb-ingest routes decisions found in raw material to this format;
ckb-retrieve gains the decisions index as a cascade step
Scriptified the mechanical skills:
- ckb-export-okf/scripts/export_okf.py does the whole OKF transform
(frontmatter remap, link rewriting, index/log regeneration, conformance
validation); --check validates without writing
- ckb-lint/scripts/lint_report.py does the read-only detection half
(conformance, freshness, confidence, retention, decisions, orphans,
graph, index/log, source.yaml); judgment calls stay with the model
Also: removed the duplicate personal quiz skill, fixed stale cbk-quiz
doc paths, gitignored __pycache__.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
ckb-index-external now goes beyond one page per document: it also
extracts people, organizations, projects, decisions, systems, and
processes each document discusses into thin, pointer-style entity
pages within the connector's own index (evidence back to source
documents, deferring to a full wiki/entities/ page where one already
exists), so the index supports "what do we know about X" lookups, not
just "what documents exist here".
New ckb-retrieve skill formalizes the retrieval half of the query
workflow: before grounding an answer in a page's tldr, follow it back
to its underlying source (a wiki page's Sources citations, or a
connector page's resource: pointer) rather than trusting the
compressed index entry as settled.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
The last skill clarification (check the shared index store on every
run; fetch if it exists; a write-access user's run creates it there
the first time it's empty) hadn't been reflected in the user-facing
docs, which only described the steady-state case. Also documents the
optional index.ref field, mentioned in the skill schema but missing
from all four docs' examples.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Spell out explicitly, per run: check whether the shared index store
already has a published index; if so, fetch it regardless of access
level; a write-access user always continues to rebuild and publish
back to that same store, and this is precisely what creates it there
the first time the store is empty. A read-only user never rebuilds or
publishes anything, whether or not the store already had content.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
source.yaml gains an optional index: block declaring where an
already-built index lives (a git repo or a shared resource), so a
user can fetch it instead of scanning the live connector from
scratch. Whether a given user may actually rebuild/publish an index
is now a local, per-user, gitignored source.local.yaml (access:
write|read) that defaults to read-only, letting a team designate one
or two admins per external source instead of everyone redundantly
re-indexing it. ckb-lint's checks against a connector's generated
index now respect the same read/write gate.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
libs/<name>/ now supports a second population mode alongside git-copy
clones: a user-authored source.yaml declares a live external source
(SharePoint, Google Drive, a plain URL, or another connector), and the
new ckb-index-external skill builds a self-contained generated index
for it (index.md/entities/graph/log.md), scoped entirely to that
connector and never blended into the main wiki/.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>