Release/deployment is blocked pending an owner-approved application identity and manifest. This document defines gates; it does not authorize publication.
Commit, push, tag, release, signing, deployment, and QDN publication each require explicit owner authorization. Read-only validation does not grant live write authority.
-
Establish branch, HEAD, origin relation, and complete working-tree state.
-
Preserve and review all owner changes.
-
Confirm package version and select the exact APP service, registered publisher name, identifier, entry point, permissions, license, and source repository metadata.
-
Add and validate an owner-approved
qortium-app.jsonbefore release. -
Verify current Home/Core contracts and intended runtime environment.
-
Run:
npm ci npm run test npm run build npm run lint npm run format:check git diff --check -
Inspect
dist/, relative asset paths, and absence of secrets/source maps or unintended files. -
Record source commit and artifact SHA-256 in the release handoff.
Use an owner-approved Qortium Home/QDN publication flow for the exact identity and artifact. Record the transaction/resource reference. Validate the deployed resource in embedded Home: startup, routes, selected account, read/write authority, search, taxonomy, media, comments/reactions, refresh, and readback.
Automated tests, local preview, and build output do not prove deployed behavior. Do not mark complete until required owner/live validation passes.