T1-domain-param KILLED | harness: raise_decision offers domain as technical or delivery only, optional, and says where a raise goes
T2-domain-enum KILLED | harness: raise_decision offers domain as technical or delivery only, optional, and says where a raise goes
T3-domain-desc KILLED | harness: raise_decision offers domain as technical or delivery only, optional, and says where a raise goes
T4-raise-desc KILLED | harness: raise_decision offers domain as technical or delivery only, optional, and says where a raise goes
S1-sr-bash KILLED | business: both definitions load, with a contract file, and are exactly the approved lists; security-reviewer has no write or shell tool and classifies only the verdict as its own
S2-sr-send KILLED | business: both definitions load, with a contract file, and are exactly the approved lists; security-reviewer has no write or shell tool and classifies only the verdict as its own | bus: security-reviewer answers a review with its verdict alone; it holds no message.send
S3-sr-messaging KILLED | business: both definitions load, with a contract file, and are exactly the approved lists; neither role can be an arbiter: its messaging lists refuse the business file
G1-mg-within KILLED | business: both definitions load, with a contract file, and are exactly the approved lists; merge-gate's only grant is git.merge.protected cross-role, and it has no write tool | bus: merge-gate has no message.send, and without a domain its raise goes to the delivery arbiter; merge-gate's technical raise is cross-role, goes to the cto, and only merge-gate can use the approval; the cto must be able to message merge-gate, or the technical raise is refused
G2-mg-extra-cross KILLED | business: both definitions load, with a contract file, and are exactly the approved lists; merge-gate's only grant is git.merge.protected cross-role, and it has no write tool
G3-mg-edit KILLED | business: both definitions load, with a contract file, and are exactly the approved lists; merge-gate's only grant is git.merge.protected cross-role, and it has no write tool
G4-mg-no-cto KILLED | business: both definitions load, with a contract file, and are exactly the approved lists | bus: merge-gate's technical raise is cross-role, goes to the cto, and only merge-gate can use the approval
G5-mg-messaging KILLED | business: both definitions load, with a contract file, and are exactly the approved lists; neither role can be an arbiter: its messaging lists refuse the business file | bus: the cto must be able to message merge-gate, or the technical raise is refused
G6-mg-send KILLED | business: both definitions load, with a contract file, and are exactly the approved lists; merge-gate's only grant is git.merge.protected cross-role, and it has no write tool | bus: merge-gate has no message.send, and without a domain its raise goes to the delivery arbiter
H1-header KILLED | business: both definitions load, with a contract file, and are exactly the approved lists
P1-proactive-gone KILLED | business: every role contract carries the proactive line in its Authority section
P2-proactive-outside KILLED | business: every role contract carries the proactive line in its Authority section
R1-routing-gone KILLED | business: pm and chief-of-staff say where a raise goes under REQ-DEC-2
R2-hard-wait KILLED | business: pm and chief-of-staff say where a raise goes under REQ-DEC-2
R3-old-text KILLED | business: pm and chief-of-staff say where a raise goes under REQ-DEC-2
restored True
rc=0
2026-10-18T13:05:08Z