Skip to content

A decision on a default needs rung 2, the deadline passed, and the answer unused - #127

Merged
hhff merged 1 commit into
mainfrom
default-authority
Nov 6, 2026
Merged

hhff merged 1 commit into
mainfrom
default-authority

Conversation

@hhff

@hhff hhff commented Nov 6, 2026

Copy link
Copy Markdown
Member

What

  • devteam.mjs (decisionAuthorityGap, the default case): this judges every decision line, hand-written ones included. A decision resting on a default now needs:
    • a ladder class on rung 2 or above;
    • a cited question that carries a default;
    • a question that wasn't defaulted before its deadline;
    • an answer not already used (answerUseGap).
  • Test: a hand-written question, its defaulted line and a production-migration decision citing it are refused at act --decision.

Why

An independent review of #105 found this, and it's on main. decide refuses a default below rung 2, but the check on decision lines only looked for a defaulted question in the class, and the supervisor writes the defaulted status itself. So a decision could approve a call in a rung-1 class with no owner involvement. Under #105 that would release to production.

Migration

None. Decisions made through decide already met the rung rule.

🤖 Generated with Claude Code

…swer unused

decide refuses a default below rung 2, but decisionAuthorityGap (which judges
every decision line, hand-written ones included) only checked that the cited
question was defaulted in the class. The supervisor writes a question's
"defaulted" status itself, so a hand-written question, default line and
decision approved a call in a class on rung 1, with no owner involved (found
reviewing #105, where it would release to production). The default case now
needs a ladder class on rung 2 or above, a question that carries a default
and was defaulted no earlier than its deadline, and the answer unused
(answerUseGap), as decide enforces.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@hhff

hhff commented Nov 6, 2026

Copy link
Copy Markdown
Member Author

Merging (upstream loop). Local Node 24.14.1 main suite passed 49/49, including the hand-written default-decision refusal. CI 18/20/22/24 is green (Node 18 rerun after the known tmux idle-timing flake).

@hhff
hhff merged commit e24e5ce into main Nov 6, 2026
7 of 8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant