Ledger 0.9.0

governance-ledger 0.9.0

Release date: 2026-09-15. Published on GitHub and PyPI; public Ledger
base-install verification passed. Public Guard-extra acceptance remains pending.

Ledger 0.9.0 adds explicit catalog 3 for create/modify authority with isolated
action grants, roles, and fresh approval. Catalog 1 remains the default; catalog 2
retains its opt-in development behavior and immutable approved meaning.

Guard 0.19 integration reports missing Guard and unsupported raw legacy replay
through distinct Ledger errors and actionable CLI diagnostics. Explicit injected
evaluators remain supported. Native publication, mediated repository writes, and
saved logical replay use the supported Guard SDK/store boundary.

Dependencies remain ordinary version ranges:

• cricore-contract-compiler>=0.5.0,<0.6.0
• Optional [guard]: waveframe-guard>=0.19.0,<0.20.0

Public governance-ledger[guard]==0.9.0 acceptance remains pending until
installation is actually verified after Guard 0.19.0 publication. Combined acceptance uses authenticated candidate
inputs and does not establish public Guard-extra availability or runtime activation.

Integrated source and build provenance

PR, in integration order	Merge commit
#18	6d522262072d9bfd67347d49fbe9276b7b00e23b
#20	2afc23686e2b74d485cd91532518dd82b2aa15df
#22	606dca0fb56a2ed34d06cc289b39bedafa49604e
#24	55dfff45f2d0aaaae0ba65332e774c51814b1879
#26	bd82c11dc0c4d4003063c7f2ce0f2e87f12f7bf1

Tag v0.9.0 targets bd82c11dc0c4d4003063c7f2ce0f2e87f12f7bf1.
Its entire tree is identical to reviewed candidate/build source
a34c11d81b85963794cf28b4adad091fac15e130:
e8dcd316014c5152382b9bb118b997dfc354e591. Merge commits preserve all
reviewed heads as ancestors; stacked PRs were retargeted to main in order and
their branches retained.

The attached distributions are the original selected Ubuntu / Python 3.14 build,
with original Ledger evidence
and selected package-set manifest.
Manifest SHA-256: 9639a315e88223d2a6241850ff2685ebd61eea1ded01115418686f2b2c8fa504.
Their bytes were preserved; integration CI builds are validation artifacts.

Selected distribution	SHA-256
governance_ledger-0.9.0-py3-none-any.whl	6b7913e4ba4e2b11d1007bb3006dea81cde08ebc06980a7bab89113938779bd4
governance_ledger-0.9.0.tar.gz	8ceb328437c794a3306d22ca82e99787f3bf4ff0d0281b4e245d7d0b29c42c2c

Validation

• Strict Twine checks pass for both selected distributions. Metadata/ranges match;
  297 packaged runtime/support files match the reviewed Git source blobs exactly.
• Final integrated general CI
  and four-cell source, installed, and combined producer rerun
  pass while testing the tag target, including Windows/Linux and Python 3.10/3.14.
• The exact selected Ledger wheel with public PyPI Compiler 0.5.0 passes in a
  fresh environment outside the checkout on Windows / Python 3.14.4: 674 passed,
  47 expected skips; all 70 catalog-3 release cases executed. Expected skips
  are 44 opt-in development cases and 3 absent-Guard entries.
• Public API/CLI, release/development fixture probes, installed module/resource
  bytes, historical Ledger 0.7/0.8 behavior and immutable v2/v3 identities,
  old-Compiler resolver rejection, and pip check pass.
• The earlier pre-upload public-only verifier preflight correctly returned PyPI
  404 for Ledger 0.9.0. That failed attempt remains preserved; the subsequent
  successful public-base verification is recorded in the closeout below.

The initial integrated acceptance run
is retained as failed: after Compiler publication, pip selected public Compiler
0.5.0 in the Guard upgrade step, whose existing provenance assertion requires the
retained candidate archive. All source/installed/combined test suites passed, but
the complete producer correctly failed that provenance assertion.

The complete producer rerun uses the existing workflow from a separate validation
branch at 1e0d32b2a339ffa8953a3072a0a0fc8ba5c933f2, checks out and verifies the exact integrated commit, and passes
the authenticated per-cell Compiler wheel explicitly to the Guard upgrade command.
The same required producer, test suites, provenance assertions, resolver checks,
56 execution probes, and failure propagation all execute. No tracked file in the
tested source tree changes, and the original failed result is not overwritten.
This candidate-input orchestration remains outside the release tag and packages.

Every rerun cell reports source and installed base suites at 674 passed / 47
expected skips (default) and 718 passed / 3 expected skips (development), and
combined suites at 678 passed / 44 expected skips (default) and 722 passed / 0
skips (development). All 70 release cases execute in every suite; the development
suites execute all 44 opt-in cases. Each cell passes all 56 real catalog-3
execution probes and the Guard-entry upgrade/provenance/execution checks.

Attached release-evidence.zip retains commands, logs, JUnit, pip reports,
source/package validation, integration CI artifacts and publication provenance.
verify-public.py downloads both actual public PyPI distributions, checks their
hashes, and installs Ledger by version from public PyPI in a new external
environment, then reruns the base acceptance. It has no candidate fallback.
MANUAL-UPLOAD.md and upload.ps1 provide the exact-file interactive upload and
verification commands. No PyPI credentials were requested or used in this release session.

Status and historical records

The authorized execution handoff
supersedes earlier candidate coordination restrictions for this Ledger release.
Candidate documentation and earlier failed acceptance records remain unchanged as
historical evidence, preserving the reviewed tree and the selected archive bytes.
Only Ledger was integrated/released. Public Guard-extra acceptance remains pending
verification after its separately coordinated publication.

Public PyPI publication and base-verification closeout — 2026-09-15

Shawn completed the manual PyPI upload. The original successful Windows / Python
3.14.4 verifier run reports public-pypi-base: passed, completed at
2026-09-15T23:31:05.632998+00:00. Ledger 0.9.0 and Compiler 0.5.0 were installed by version
from public PyPI in a fresh environment outside the checkout; the retained pip
report records actual files.pythonhosted.org origins.

• 674 passed / 47 expected skips; all 70 release cases passed. The skips are
  44 explicit development opt-ins, two missing-Guard import cases and one
  collection skip. The existing skip validation passed; retained JUnit agrees.
• Both public Ledger distribution hashes match the original selected wheel/sdist
  and existing GitHub assets. Coordination independently downloaded and rehashed
  both public files
  and confirmed neither was yanked.
• Actual installed bytes, public API/CLI, release/development resources and
  fixtures, Ledger 0.7/0.8 history, Compiler 0.4 resolver rejection and pip check
  passed in that original run. The rejection command's exit code 1 is expected.
• Public governance-ledger[guard]==0.9.0 acceptance remains pending and was not
  exercised. It must pass after Guard 0.19.0 publication; publication alone does
  not complete this gate. The extra range remains >=0.19.0,<0.20.0.

Additive durable evidence

• Complete original verification directory
  (11,819 files, including verification.json, pip reports, JUnit,
  all 27 command logs, downloaded distributions, support files and environments).
• Per-file SHA-256 manifest; the identical manifest
  is also SHA256SUMS inside the ZIP, with paths relative to its root.
• Archive and manifest SHA-256 checksums.
• Archive SHA-256: 527c4fa148ad15a4d061ec5eb26eacf15d7b6d2a66466a0836e9b030e1b38f52.

Original directory: C:\Users\swrig\AppData\Local\Temp\ledger-090-verification-s1lqver2. The closeout inspected existing evidence and
verified every archived file against the original bytes; it did not rerun the
verifier or rebuild packages. The source/tag, selected distributions, all earlier
release assets and failed-attempt evidence are preserved unchanged. Earlier
manual-upload instructions and candidate records remain historical evidence.

Compiler and Ledger public prerequisites are satisfied. Guard proceeds under
the existing separate package-release authorization; this closeout does not block
it. Cloud release, deployment and activation remain separate. Issue #23 stays
open while public Guard-extra acceptance is pending.