The chief of staff role can revoke a run with a reason (role.revoke) and write the organization file (organization.set), each under a broker grant. organization.set checks the grant before the writer runs and consumes it only after the writer returns, so a refused change leaves no action.allowed. migrations/3c-3d.sql takes the store from 3c to 3d; migrate-schema.mjs chains it after 3b to 3c. roles/chief-of-staff.json and the business vocabulary carry the new actions. The harness tools for them are row 132, which must land before 3d goes live. Candidate 255a960582f1018b8d400e8d193e8e95713a078930277652d59ef4153197d9f6, Researcher packet agents/researcher/work/queue-123/r2 (b959160f9), built oneaeb5ebf2plus row 49 r1. Filbert approved round 2 in 28578. Landing gate at3a4afdc03: 24 suites green, 0 failed. 14 package suites passed 1611 tests (bus 191, business 92, harness 84, tasks 97, webui 112). The 10 script suites passed (land-work 84, queue 156). Co-Authored-By: Claude Opus 5.5 <[email protected]>
6 lines
367 B
SQL
6 lines
367 B
SQL
-- Row 123 (#1617): a revoke needs a resolved decision or a reason (the chief of staff's role.end).
|
|
DROP TRIGGER role_revoke_needs_decision;
|
|
CREATE TRIGGER role_revoke_needs_decision BEFORE INSERT ON role_claims
|
|
WHEN NEW.op = 'revoke' AND NEW.decision IS NULL AND NEW.reason IS NULL
|
|
BEGIN SELECT RAISE(ABORT, 'revoke needs a resolved decision or a reason'); END;
|