# v0.8.0-beta.21 Release Notes

## Immutable Final Observer Procedure

This document records the `0.8.0-beta.21` Consumer Authority Beta source
candidate. It makes no npm publication, tag, dist-tag movement, GitHub release,
original signed consumer artifact, promotion, Finish authority, or issue closure
claim.

`0.8.0-beta.20` is immutable staging evidence and is not reused as the current
package. Its live authority fetch reached `trusted/unconsumed`, but the observer
then invoked default Finish before the same consumer had completed its public
lifecycle. The intentional `workflow-state-uninitialized` block consumed
nothing and is not reusable closure evidence.

Beta21 changes no product fetch, authority, Finish, transport, or workflow
behavior. It binds the accepted immutable final-observer procedure record by
SHA-256 `1d370a4e4cdd55b20e27c016073246b78c373548c84c89c3499b3838e27980a7`;
the record is coordinator-governed and no local absolute path is a source of
truth.

The package-visible
[`consumer-authority-beta21-acceptance.json`](consumer-authority-beta21-acceptance.json)
record binds the ordered procedure to the existing release and observer
boundaries.

## Required Procedure

Use one exact Git-backed registry consumer CWD/HEAD and one isolated consumer
HOME/store. Before enrollment, live artifact work, or fetch, run public strict
bootstrap, the accepted plan/current loops, Gradle test/compileJava/clean,
README/profile/Java evidence reads, public implementation/review report ingress,
and plan status. A default Finish must then block only on
`trusted-authority-required`.

Only that ready, unchanged consumer may enroll and later process the one current
artifact through the existing transport and online-crypto procedure. Recheck
trusted/unconsumed status and explain with no readiness blocker, consume Finish
once, then check immediate replay rejection. After fetch, do not bootstrap,
reset/copy lifecycle state, change CWD/HEAD/source/profile, replace the isolated
HOME/store, or switch consumers. A prefetch failure requires abandoning and
recreating the consumer before any live fetch.

## Required Live Evidence

After protected integration and current-package installation, the sole hosted
residual is one natural current-version artifact observation under that frozen
procedure: online verification, authenticated fetch, one Finish consumption,
and immediate replay rejection in the same unchanged consumer. It does not
substitute local modeled evidence for live crypto or authority.