A delivery profile is a versioned acceptance contract for one workflow and environment. It should name:
- supported input and output formats and versions;
- permitted changes and preservation rules;
- structural validators and rule-pack versions;
- required renderers or desktop applications and their versions;
- required fonts and environment fingerprint;
- layout, density, hierarchy, accessibility, and per-page/sheet/slide thresholds;
- accepted fidelity-loss severities;
- evidence freshness and unsupported conditions;
- whether an authorized human must record creative acceptance.
The local bounded XLSX mutation profile currently proves structural validity, preservation and intended change. It reports delivery readiness as not_checked because it does not run Excel or render the result.
Don't require deliveryReady in a managed policy until the profile implements every check it needs. A policy that requires missing evidence blocks the artifact.