# v0.8.0-rc.1 Release Notes

## First Release Candidate For The 0.8.0 Line

This advances the Consumer Authority acceptance record to `0.8.0-rc.1`. It
carries the same tree as `0.8.0-beta.34` and changes no Persona Harness
authority, Fetch, Finish, artifact transport, workflow runtime, registry
channel, tag, release, observer, or fixture behavior.

It exists to open the release-candidate cycle that
[`p3-integrity-roadmap.md`](../p3-integrity-roadmap.md) requires before Stable,
GA, or an npm `latest` move:

> Stable, GA, and npm `latest` require a separate actual RC release cycle, exact
> tag/version/main ancestry, registry readback, and the Level 2 trusted external
> attestation boundary.

`0.8.0-beta.34` is terminal, non-reusable staging-channel evidence. It was
accepted as Consumer Authority Beta on `staging` only, under a GO decision that
carried conditions, so it establishes no release-candidate or `latest` claim.
Every earlier terminal record described in its notes remains as stated there.

## What this candidate does not decide

- **It is not a `latest` move and does not authorize one.** `latest` stays at
  `0.7.0`.
- **It does not close the P3 hold.** Of the four gates above, the Level 2
  trusted external attestation boundary was demonstrated end to end during the
  beta audit, and exact tag ancestry and registry readback are performed by
  `publish.yml`. The RC cycle itself is what this candidate opens, not
  completes.
- **It does not resolve the open lifetime question.** Whether a workspace takes
  exactly one external-attested finish is unspecified rather than decided, and
  the beta GO made deciding it a condition of promotion past `staging`.

## Scope

A release-candidate procedure record. Not a Stable claim, not a GA claim, and
not a claim about generated application quality.

## Verification

Publish through `.github/workflows/publish.yml` with `dist_tag: next` and
`approval_scope: next-promotion-approved`. The run performs the canonical pack,
the publisher preflight, the provenance publish, and the registry readback in
sequence.