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>
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>
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>
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>
Read-only skill: given a topic, resolve it to an anchor page via the
cascade, walk the graph edges (2 hops, ~8-page cap) — falling back to
link-following when no edges exist — order the pages pedagogically
(prerequisites first, then the topic, then what builds on it), and print
a numbered reading tour with per-page "what you'll find" notes.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Continue the ckb- namespace consolidation: rename the bootstrap skill
directory and its name: frontmatter from cascade-kb-init to ckb-init.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Rename four cascade-KB skills to a consistent ckb- namespace:
- export-okf -> ckb-export-okf
- export-starlight -> ckb-export-starlight
- project-summary -> ckb-project-summary
- sync-changes -> ckb-sync-changes
Update the name: frontmatter in each SKILL.md and all cross-references
in README.md, AGENTS.md, cascade-kb-init, and export-starlight. Historical
wiki/log.md entries are left unchanged as a record of past actions.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Add four skills for Tempo/KSeF timesheet and invoice workflows:
- check-my-timesheet: show/log the current user's Tempo time entries
- timesheet-checker: audit timesheet completion across all reporters
- invoice-checker: pull KSeF invoices, check contractors + MF white list
- invoice-prep: summarize Tempo hours per Jira project for invoicing
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
