An engagement MUST be in force only when the commit that holds it was accepted by the signers of the fleet (with the approval its controlled path asks for), the file is the one committed, and the instant is within its window (from and not after the end); an engagement that is unsigned, modified, refused or blocked, or whose window is not open, MUST be not in force, with every reason said.
Enforced (check): .github: cd commons/pentest && bun run verify — suite/authorization.test.ts
An action (one technique on one asset) MUST be allowed only when the engagement is in force, the technique is one the engagement grants and no technique that is never granted, and the asset is in its scope; a technique that is never granted or is no technique MUST be refused whatever else is true; and passive, which sends nothing to a target, MUST be allowed without an engagement in force, and the answer MUST say so. Every answer MUST say why in a sentence.
Enforced (check): .github: cd commons/pentest && bun run verify — suite/authorization.test.ts
The scope MUST be the assets of the include question less those of the exclude question, each read from a column named asset of its answer; it MUST be a problem where a question is refused or has no such column, where an asset is not one the estate has, and where the scope is empty.
Enforced (check): .github: cd commons/pentest && bun run verify — suite/authorization.test.ts