Skip to main content

AEROSIM-TS-129

Project task

Freeze immutable Release 1.0.0 candidate

One immutable candidate binds the exact application source revision, Harbor web and API digests, chart revision, GitOps template revision, and rendered GitOps revision.

AEROSIM-TS-129Canonical ID TASK-0129
Verified flow state
Done
Owner
AeroSim Releases
Component
Release management — immutable candidate evidence
Repository
corp-v1-aerosim/corp-v1-aerosim-documentation; corp-v1-aerosim/corp-v1-aerosim; corp-v1-aerosim/gondor-v1-tmpl-aerosim; corp-v1-aerosim/gondor-v1-aerosim

Delivery scope

Resolve every candidate reference through source-specific readback, cross-check that chart and GitOps inputs select the same application images and configuration, and publish one reviewable candidate manifest that fails closed on missing, mutable, or mismatched evidence.

Implementation contract

Implementation artifacts

  • corp-v1-aerosim/corp-v1-aerosim-documentation:ways-of-working/release-readiness.md
  • corp-v1-aerosim/corp-v1-aerosim-documentation:data/tasks/TASK-0129.yml

Inputs

  • Exact application source revision with successful validation and immutable publication evidence.
  • Harbor web and API repository names, immutable digests, and source-revision annotations.
  • Helm chart, project GitOps template, authoritative render, and rendered repository revisions.

Outputs

  • One immutable Release 1.0.0 candidate evidence manifest with exact revisions, digests, URLs, actor, and capture time.
  • A mismatch report that identifies the conflicting source and stops promotion.

Failure boundaries

  • Reject tag-only, branch-only, latest, missing, inaccessible, or mutable candidate identities.
  • Reject Harbor annotations, chart values, template values, or rendered manifests that do not resolve to the same application revision and digests.
  • Do not infer deployment, runtime health, or release completion from candidate freeze.

Excluded scope

  • Do not change application source, publish replacement images, merge GitOps, synchronize Argo CD, or deploy.

Verification steps

  • Read back the exact application commit, successful exact-head checks, Harbor manifests, image annotations, chart source, template source, authoritative render output, and rendered repository commit.
  • Recompute the evidence manifest twice from unchanged inputs and require byte-equivalent candidate identity.
  • Mutate each reference in focused tests and prove every mismatch fails closed.

Traceability

Requirements

Dependencies

None

UI/UX applicability

verification

Acceptance evidence

Verified delivery: immutable Release 1.0.0.0 candidate: application and chart source 94061818a414e70845f454d4c39792e5e846e033; chart 1.0.0+build.1 at sha256:f5e811912acda00c90ed671098439c88ebf5d85b0a832ec5676c58aa99d743da; Nebula sha256:77eaacfd6a68c2003b0ef763bf2840f99e48b33faeaed2cc3de424c3b0ec8535; Singularity sha256:b917a53c6e1bdcb823df17a8fb2812df822fefc82bf6aeec8dc2e755ae21d07f; template PR #14 and rendered PR #24. Release completion verified on product 1.0.0.0 at GitOps revision 5d3712d89dfbf7dacd993348e55f497d126c7bf9 with Argo Synced/Healthy, exact image digests, authenticated API/database access, and three-world configured-flight acceptance.

Current evidence boundary

No current implementation, acceptance, release, or deployment evidence is claimed for this planned Task. Any prior implementation may be used only as prototype and discovery evidence.