Generated from who-iris/processes/iris-cdn-sign-publish.bpmn by gen-processes-viz.ts — do not edit here. All processes · who-iris processes

Sign and publish an IRIS CDN release

Process_IrisCdnSignPublish · strict (defaulted) · 8 step(s)

Turn a candidate payload into a signed release on Cloudflare: each changed library item gets a detached JWS over its own manifest, and the BagIt bag (RFC 8493) whose tagmanifest pins every item manifest and signature is signed once with a detached JWS (RFC 7515 Appendix F, ES256 per RFC 7518), the key published as a verificationMethod of a did:web DID document whose publicKeyJwk carries an x5c chain to the WHO signing key. Nothing unchanged is re-uploaded or re-signed; an empty diff ends the process with no commit.

BPMN diagram: Sign and publish an IRIS CDN release

How it connects

Lanes — who acts

lanerolewhat it does here
Build pipelinebuild-pipelineDeterministic scripts in scripts/iris-cdn/, entry point run.ts. Same input, same bytes.
Release signerrelease-signerHolds the P-256 private key (GitHub environment secret IRIS_CDN_SIGNING_JWK). Signs each changed item manifest and the release tag manifest.
VerifierverifierAnyone. Resolves the key from the did:web DID document, never from the package, and checks its x5c chain up to WHO’s signing key. Cannot reach it: the verdict is unknown, not verified.

Steps

2 of 8 step(s) carry no documentation — activity-documented lists them.

steplaneskill / sub-processwhat it does
Write the BagIt tag files (sorted, no dates)
Task_BuildBag
Build pipelineiris-cdn-signingscripts/iris-cdn/bag.ts tagFiles: manifest-sha256.txt sorted by path, bag-info.txt with Payload-Oxum and no Bagging-Date.
Diff against the published manifest
Task_Diff
Build pipelineiris-cdn-signing—
Store new objects (never overwrite)
Task_Upload
Release signeriris-cdn-exporterContent-addressed: an object whose SHA-256 is already stored is skipped. Published objects are never deleted by a nightly run.
Sign each changed item manifest (ES256)
Task_SignItems
Release signeriris-cdn-signingA signature on each library item: items/<handle>/manifest-sha256.txt lists the item record and its files; its detached JWS sits beside it. Only items whose manifest bytes changed are signed: ES256 is randomised, so re-signing an unchanged item would be churn. The item manifests and their signatures join the payload, so the tag files are refreshed to cover them before the release is signed.
Sign the release tag manifest (ES256)
Task_Sign
Release signeriris-cdn-signingscripts/iris-cdn/signing.ts signDetached. kid is a did:web DID URL listed under assertionMethod.
Commit tag files and signature, last
Task_PublishTags
Release signeriris-cdn-signingOne commit to the Cloudflare git repository, after every payload object is in place, so a reader never sees a manifest naming bytes that are not there yet.
Resolve did:web; verify JWS and digests
Task_Verify
Verifieriris-cdn-signingscripts/iris-cdn/run.ts checkRelease: every tag file against tagmanifest-sha256.txt, then scripts/iris-cdn/signing.ts verifyDetached against the DID document fetched from its did:web URL.
Revert to the previous release
Task_Revert
Verifieriris-cdn-signing—

Decisions

2 of 2 decision(s) carry no documentation — gateway-documented lists them.

decisionwhat decides itbranches
Anything changed?
GW_Empty
—no → Unchanged: no commit
yes → Store new objects (never overwrite)
Verified?
GW_Verified
—yes → Release published and verified
no / unknown → Revert to the previous release

folio-assistant — code under the Apache License 2.0, documentation under CC BY 3.0. Generated schema and API references are rebuilt from source on every push to main.

deployed dev