Session audit: give the office CTO a board row, or exempt it? nf-4gyf ← Beads

closed priority 2 task unassigned

Twinned from https://github.com/cfsh/ninefold/issues/650 by tools/beads/import_github.py's reconcile pass.

From session:session-audit (#635, PR #638). The question was in that PR's body; @aedanpope approved without answering, so it is filed here to outlive the merge.

./tools/office/audit_sessions.py reports nf-office-ef — the office CTO agent, running in ~/nf/nf-office — as UNREGISTERED drift on every run, because no row on board #398 resolves to that workspace. It is a true statement and a permanent one.

A. Add a row for it to #398 *(recommended — this is what ships)* The board already carries rows for non-dev roles (playtest, ninefold-art, ninefold-release, ninefold-reviewer), so the CTO not having one is arguably the actual drift. One line, and the audit goes quiet on its own.

B. Exempt the office clone in the tool A path- or name-based carve-out. ⚠️ This is the option I would push back on: hardcoding "do not report this one" is the drift-tolerance the tool exists to remove, and the next unregistered thing gets the same treatment. The tool does have one exemption already — cron-spawned sessions — but that one is *measured from the process tree* and covers workspaces that cannot carry a row (each review runs in a per-invocation worktree). The office clone is not that: it is stable, long-lived, and perfectly nameable.

C. Leave it reporting Accept one standing drift item. Honest, but a report that always shows the same finding trains readers to skim past the section — which costs the findings that matter.

Default ships if unanswered — nothing is blocked on this. Today that means C by inaction; A needs only a board edit and no code change, and I would do it in a follow-up if you say the word.

Dependencies

None.

Comments

No comments.

Add a comment