Whether an engagement is in force and whether one action is allowed. An engagement is in force 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 now is inside its window. An action is one technique on one asset: allowed when the engagement is in force, the technique is one it grants (and is no technique that is never granted), and the asset is in its scope. A passive action sends nothing to a target, so it is allowed without an engagement in force, and is said so.
Everything is decided from what is given: the signature verdict (made by change-control from Git), the instant and the scope (made by asking the estate). Nothing is read or run here.
type Signature = {
/** `accepted`: signed by a signer of the fleet, with the approval its path needs. `refused` or `bl…(429 characters)
typeSignature= {
/** `accepted`: signed by a signer of the fleet, with the approval its path needs. `refused` or `blocked`: it was judged and not accepted. `unsigned`: no commit holds the file. `modified`: the file is not the one committed. */readonlystate:"accepted"|"refused"|"blocked"|"unsigned"|"modified";
readonlysigner?:string;
readonlyapprovedBy?:string;
readonlyreasons:readonlystring[];
};
What change-control found of the commit that holds the engagement.
type Signature = {
/** `accepted`: signed by a signer of the fleet, with the approval its path needs. `refused` or `bl…(429 characters)
typeSignature= {
/** `accepted`: signed by a signer of the fleet, with the approval its path needs. `refused` or `blocked`: it was judged and not accepted. `unsigned`: no commit holds the file. `modified`: the file is not the one committed. */readonlystate:"accepted"|"refused"|"blocked"|"unsigned"|"modified";
readonlysigner?:string;
readonlyapprovedBy?:string;
readonlyreasons:readonlystring[];
};
What change-control found of the commit that holds the engagement.