"@context":
  - https://chris-page-gov.github.io/okf-explorer/profile/bundle-wiki/v1/context.jsonld
  - https://chris-page-gov.github.io/okf-explorer/profile/bundle-wiki/v1/semantic-context.jsonld
"@id": https://chris-page-gov.github.io/okf-explorer/docs/postmortems/heritage-foundry-2026/evidence.html
"@type": https://schema.org/Report
type: Report
title: "Heritage Foundry postmortem evidence"
description: "Evidence inventory, retention boundary, hashes and release qualifications."
generated:
  by: process:heritage-foundry-postmortem-builder
  at: "2026-08-04T13:16:54Z"
assertion_status: normalized
assertion_scope: real-world
tags:
  - postmortem
  - evidence
  - provenance

Heritage Foundry Postmortem Evidence

Collection Result

The ignored private evidence plane contains structured PR/run metadata, six gzipped Actions logs, Git/reflog snapshots, all six release assets and three deployment archives captured before their one-day retention expired. The public evidence register publishes source URLs, byte counts, hashes and treatment decisions without publishing raw logs or local paths.

The current rollout is a separate normalized input. It records PR #70, the external candidate and Pages deployment, R1, terminal assurance and R2. Its generated current-publication register and the appended public records in the evidence register apply that fail-closed contract. All six milestones are verified from exact public identities, timestamps, claims and URLs; no success state is inferred from local implementation.

The separate R1/terminal/R2 attempt register reconstructs all nine closure runs from their public workflow logs. It records the failed step, bounded correction, control commit and retained artifact digest where present. All nine records explicitly prove that neither candidate nor Site bytes changed during closure.

Preserved Deployment Archives

GitHub downloads the Pages artifact as an exact artifact.tar. The private copy is stored with lossless gzip compression. The last column proves that decompression reproduces the original downloaded tar bytes.

GitHub Evidence Quality

• All six relevant workflow runs were successful attempt 1 runs with no rerun.
• PRs #67–#69 had no comments, reviews or review decision. Their required CI check was green.
• Each feature commit tree exactly matches its squash-merge tree, so CI tested the exact tree later deployed.
• The three Pages logs bind app, corpus, Site-tree and uploaded-artifact hashes.
• The terminal release contains six uniquely named receipt assets with reported SHA-256 digests.
• The independent R1 is immutable and retains five exact candidate assets; R2 is immutable and its GitHub Releases attestation binds all ten promotion assets.
• The final terminal artifact is independently hashed as sha256:2f9e5544a06bd143ab4f069c6cf65a4edf6f1c54a9fd88c0a7bfc74322f1447c.

Release Qualification

The historical 3 August release is content-addressed and frozen by project policy, but it is not platform-enforced immutable. GitHub reports isImmutable: false, the tag is a lightweight commit tag, and neither the tag nor assets are protected from a privileged maintainer.

The replacement policy is now implemented in release-policy.json, its validator and the external promotion workflow template. It requires an annotated tag, GitHub artifact attestation, immutable releases, draft-first asset attachment and a deterministic archive retained as a release asset.

The normalized current-publication evidence records exact verified R1, terminal and R2 identities, claims and public evidence URLs.

Publication Boundary

Public trace pages exclude hidden instructions, private reasoning, tool payloads, credentials and raw logs. Raw evidence remains ignored because it contains local paths and high-volume operational detail. Every public file is link-linted and scanned for forbidden local/token patterns.