open/repo-mailbox
1
0
Fork 0
Code Issues Pull requests Releases Activity

docs(board): keep the axis rationale, drop the private referents

Browse source 
The v0.9.0 comments explained the attention-vs-topic axis by pointing at the
operator's private cross-repo register by path, naming an internal incident
code, and quoting a measured count of the operator's own repo population.
This repo mirrors to a public remote, so operational metadata about a private
machine does not belong in it - the reasoning does, the referents do not.

Rewritten self-contained: the topic-axis contrast now stands on its own terms
without citing a file a public reader cannot see, the defect class is named
rather than coded, and the worktree rationale keeps WHY .git is tested with
-e (a worktree or submodule has .git as a FILE) while dropping the census
that motivated measuring it. Illustrative paths stay; they carry no fact.

Comments only, no behavior change: 136 + 28 selftest checks and 6/6 node
tests unchanged. No version bump, so the v0.9.0 tag and the catalog ref stay
where they are - and with them the pre-scrub text, which history and that tag
still carry. Un-publishing that is a history rewrite and the operator's call,
not a side effect of a comment edit.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01U6EixQo6hpoRCVtiAXdnFs
This commit is contained in:
Kjell Tore Guttormsen 2026-07-28 21:35:42 +02:00
commit f7ad4741a3
2 changed files with 15 additions and 15 deletions
Download patch file Download diff file Expand all files Collapse all files

22
scripts/board.sh
View file

@ -24,13 +24,14 @@
# blocked-on <repo-name> or - (only meaningful with status=blocked)
# next-cost <model>/<effort> from the global model rubric, e.g. opus/xhigh
#
# ATTENTION AXIS, NOT THE REGISTER AXIS. This status vocabulary is deliberately
# NOT the 7-token vocabulary in ~/.claude/coord/register.md. That one describes
# a TOPIC's status inside a repo (has this repo adopted OKF?); this one
# describes a REPO's own next step (does this need me?). `not-applicable` is
# meaningless here and `partial` carries register Regel 1 (eier + neste-steg),
# which does not transfer. Conflating the two axes is the AS#5 defect class
# register.md was written to close - keep them separate.
# ATTENTION AXIS, NOT A TOPIC AXIS. This status vocabulary is deliberately NOT
# the vocabulary a cross-repo TOPIC register uses. A topic register answers
# "what is this repo's status on subject X (has it adopted convention Y?)";
# this line answers "does this REPO's own next step need me?". Topic tokens do
# not transfer: `not-applicable` is meaningless about a repo's next step, and a
# topic-level `partial` carries an ownership-and-next-step rule that belongs to
# the register, not here. Conflating the two axes is a real defect class - the
# board reads only its own axis, so keep them separate.
#
# Usage: board.sh [--roots <dir>[,<dir>...]] [--plain]
# Env: CLAUDE_COORD_DIR overrides the mailbox root.
@ -66,10 +67,9 @@ trunc() { printf '%s' "$1" | LC_ALL=en_US.UTF-8 cut -c1-"$2"; }
# contributes its children, never itself.
#
# "Is a repo" tests .git with -e, not -d: a worktree or submodule has .git as a
# FILE. Measured 2026-07-26: STATE.md is tracked in 7 of 25 repos, so a plain
# `git worktree add ~/repos/feature-x` lands a depth-1 sibling that CARRIES a
# STATE.md - a -d test drops it silently. Kept identical in the rollup builder
# (catalog) on purpose: two readers, one name.
# FILE. A plain `git worktree add <root>/feature-x` lands a depth-1 sibling that
# can CARRY its own STATE.md - a -d test drops it silently. Kept identical in
# the rollup builder (catalog) on purpose: two readers, one name.
REPOS=""
# Split on comma via IFS + `set --` rather than an unquoted $(...) expansion:
# unquoted word-splitting would also split roots containing spaces. Arg parsing