@operatorstack/boatstack-software-delivery binds repository-selected policy
to trusted software-delivery operations.
softwareDelivery combines explicit lifecycle membership, priorities, work,
targets, entries, and the humanIdentity role with canonical domain facets,
evidence, operators, transitions, and producer declarations. It is a pure
composition helper: it adds no hidden lifecycle steps and grants no authority.
trustedTransition, trustedSoftwareDeliveryTransitions, and related helpers
bind operation IDs through the trusted registry. Repositories may strengthen
authority but cannot replace minimum capability, effect, verification, or
recovery semantics.
workPackageAdmit and workPackageApprove are optional plan-neutral trusted
steps. workPackage({ work }) validates a generic accepted-work declaration.
planningPackage({ work, planOutput }) adds one optional specialization:
planningPackagePromote binds the selected required output to canonical plan
bytes. The plan-output ID is a trusted compiled promotion parameter; plan
has no magic meaning.
humanIdentity selects a named project role. trustedDelegation("autonomy")
requests a trusted delegation mechanism. Entry requires.authorities controls
activation separately. inbox declares the trusted planning-input resolver;
none of these helpers approves a run.
Trusted producer helpers read the default branch, managed workspace identity, admitted work-package manifest, current revision, gate evidence, publication body, visual evidence, and recovery transaction through runtime-owned boundaries.
See Product Delivery for lifecycle semantics and the generated module page for exact signatures.