ckb/docs/decisions/README.md
Michał Kopeć 000e633cdb Template 1.16.0: session title asked at start, routines in ckb.yaml
- 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>
2026-10-21 21:47:36 +02:00

1.6 KiB

Template design decisions

Decision records about the template itself — why the Cascade KB is shaped the way it is. They use the same type: decision format as wiki/decisions/, but they live here, in the template layer, because:

  • wiki/decisions/ is content: a KB's own decisions about its own subject. ckb-reset may wipe it, and a fresh ckb-init starts it empty.
  • Skills, modules and docs cite these records. A template must not depend on pages the content layer is allowed to delete.

ckb-upgrade carries this folder along with the rest of the template layer. ckb-decide never writes here — it is not a place for a KB's project decisions.

# Decision
D-0001 Optional capabilities ship as file-based modules under .agents/modules/, installed on request
D-0002 The software module: gitignored src/ clones, two OpenSpec spec levels, hybrid vendoring
D-0003 Python stays the only scripting runtime; portable interpreter resolution, per-OS install guidance, a native fallback for the session-start check, degraded paths per skill
D-0004 The git identity is the session's author; one workload file per person per day; **Author:** on log entries and saved conversations
D-0005 A new session asks for its title first and waits; routines are time-since-last actions in ckb.yaml, run after the user's request, with last_run committed