Seven features from the 2026-10-31 agent-knowledge research, no schema change (kb_schema_version stays 1.5): - F1 session-start hook: session_start.py --hook, start_hook.py, opt-in via session.start_hook in ckb.yaml (D-0011) - F2 kept answers in outputs/answers/, lint check 16 (D-0013) - F3 ingest check-in before writing; batch mode skips it - F5 open threads in workload notes, collected at session start (D-0012) - F6 dedup_inbox.py: duplicates reported before ingest - F19 lint check 15 for secrets and <private> spans, --secrets before every sync commit, redaction in saved conversations (D-0013) - F20 context budget: lint_report.py --budget, budget in ckb.yaml Smoke test covers every new script. Docs updated in EN and PL. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
60 lines
2.7 KiB
Markdown
60 lines
2.7 KiB
Markdown
---
|
|
type: decision
|
|
tldr: The "what is in flight" view is built from `### Open threads` checkboxes in each person's own workload notes, collected by session_start.py, instead of a shared rewritten-in-place status page; threads close where they were opened and are never deleted.
|
|
status: accepted
|
|
decided_on: 2026-11-02
|
|
decided_by: Michał Kopeć
|
|
affects: AGENTS.md, .agents/skills/ckb-lint/scripts/session_start.py, docs/MANUAL.md
|
|
confidence: 0.75
|
|
quality: 0.8
|
|
last_updated: 2026-11-02
|
|
freshness_window_days: 365
|
|
retention: high
|
|
---
|
|
|
|
# D-0012 — Open threads in workload notes, not a shared status file
|
|
|
|
**Status:** Accepted · **Decided:** 2026-11-02 · **Deciders:** Michał Kopeć
|
|
|
|
## Context
|
|
|
|
Feature F5 of the 2026-10-31 research report asked for working memory: a
|
|
short "now" page split from stable facts (Cline's Memory Bank, Manus's
|
|
`todo.md`), plus open threads collected at session start. The implementation
|
|
plan left the location of the "now" page to this record.
|
|
|
|
Two constraints decide it. Workload notes are one file per person per day
|
|
precisely so a shared repo never conflicts there (D-0004); one page that
|
|
everyone rewrites would conflict on every busy day. And a page under
|
|
`wiki/` would need a Rule B log entry for every rewrite, turning the log
|
|
into a status feed.
|
|
|
|
## Decision
|
|
|
|
1. **No status file.** Unfinished work goes in the author's own workload
|
|
note, under a `### Open threads` heading, as `- [ ] item` lines (Rule D).
|
|
2. **Closed where opened.** A thread is closed by ticking it in the note
|
|
that opened it (`- [x]`), or `- [x] dropped: <why>`. Nothing is deleted,
|
|
so the notes stay a record.
|
|
3. **`session_start.py` collects them.** Every unticked item under an "Open
|
|
threads" heading, in any top-level workload note, oldest first. The brief
|
|
shows the count and the five oldest, and marks any older than 30 days. The
|
|
line is printed only when a thread is open. The agent mentions the count
|
|
and picks a thread up only when asked.
|
|
4. **Stable facts stay where they are**: `wiki/overview.md` and `ABOUT.md`.
|
|
|
|
## Alternatives considered
|
|
|
|
- **`wiki/now.md`, rewritten in place** was rejected: merge conflicts in
|
|
shared repos, and a log entry per rewrite.
|
|
- **`workload/now.md`** was rejected: it avoids the log, not the conflicts.
|
|
- **One status file per person** was rejected: it is another file to keep
|
|
in step with the workload note that already records the session.
|
|
|
|
## Consequences
|
|
|
|
- The current-state view costs no new file and no new write rule.
|
|
- Closing someone else's thread means editing their note. That is a one-line
|
|
change in a file they rarely touch the same day.
|
|
- A thread nobody closes stays visible and gets marked stale. Pruning it is
|
|
a person's call.
|