Expand description
WorkloadGate: the governance gate for workload.* actions.
Evaluation order (every step’s outcome is chained, ADR-022):
- The action must be one of
GOVERNED_ACTIONS; an unknownworkload.*action is refused and chained asworkload.refuse. - The
workloadcontext object must parse and validate. - The subject revocation list must be readable, a request that installs, places, loads, starts or migrates must name a package, signer key or artifact hash, and none of those may be revoked. Teardown (stop, unload, re-adoption) is never blocked by a revocation.
- Workloads carrying secrets need a
pinnednode (ADR-099 s8.3). - A
WorkloadPermitRulemust match; otherwise the default deny holds. This is enforced in code as well as by theWORKLOAD-DEFAULT-DENYrule, so a rule set that lost that rule still fails closed. - The governance engine evaluates the derived 5D effect vector with every rule except the default-deny category (effect ceiling and any other distributed rules still apply).
Structs§
- Workload
Gate - Governance gate for workload actions.
Constants§
- CHAIN_
SOURCE - Chain source used for workload governance events.
- DEFAULT_
THRESHOLD - Default effect-magnitude threshold for workload actions.
Functions§
- chain_
revocations - Chain every revocation and un-revocation
listtakes from now on, from any caller (the operator verb, a mesh notice, kernel code), asworkload.revoke/workload.unrevokeevents from sourceCHAIN_SOURCE. First call wins; returns whether this one did. - event_
kind_ for - Chain event kind for a governed action (
Nonefor unknown actions). - revoke_
and_ record - Revoke a subject and chain a
workload.revokeevent when newly added. - unrevoke_
and_ record - Lift a revocation and chain a
workload.unrevokeevent when one was removed. Same chain rules asrevoke_and_record.