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.

Waveframe Ledger v0.8.0

Waveframe Ledger v0.8.0 Release Notes

Untrusted policy-translation boundary

Waveframe Ledger v0.8.0 introduces a strict authoring boundary for untrusted policy
translation proposals. An external model or deterministic form may propose bounded
controls, but every control is independently confirmed by a human before it can become
authority. Ledger validates exact source provenance, trusted capability confinement,
human decisions, chronology, and deterministic lowering. It does not call or bundle an
AI/model provider and does not claim arbitrary English policy comprehension.

One source clause may produce multiple independently confirmed controls. A partially
covered clause preserves exact residual unsupported spans and requires explicit human
acknowledgement. Only the confirmed controls become executable; residual meaning stays
visible as public provenance and never becomes implicit runtime behavior.

Additive native v3 publication

The new policy_translation_commitment.v1, authority_bundle.v3, and
publication_receipt.v3 artifacts are additive. They bind confirmed controls,
acknowledged residual meaning, Constraint IR, source and approval identities, and the
complete publication chain without changing existing v1/v2 artifacts. The runtime
payload remains compiled_authority_contract.v2.

Provider/model attribution, prompts, requests, responses, retries, failures,
explanations, and token usage remain private authoring evidence. They are independently
deletable and are not required to validate, load, or enforce the published v3 authority.

Guard compatibility

Ledger 0.8.0 restores its optional guard extra with the exact release-tested
dependency:

waveframe-guard==0.17.0

Guard 0.17.0 declares governance-ledger>=0.7.0,<0.9.0. It verifies native v3 bundles
and their mandatory matching receipts before enforcing the unchanged v2 compiled
runtime payload. Existing v1/v2 loading, verification, caching, runtime-fact, and
enforcement behavior remains compatible.

Install the release pair with normal dependency resolution:

pip install "governance-ledger[guard]==0.8.0"

Availability

Local authoring, publication, registry resolution, verification, and Guard enforcement
are available in this release. Hosted Cloud authoring and native v3 serving are not yet
available. This release does not modify or deploy Cloud or Guard.

This pull request prepares the release only. It does not merge the branch, create a tag
or GitHub release, upload to PyPI, publish a package, or deploy a service.

Waveframe Ledger v0.7.0 — Deterministic Domain-Pack Compiler

Waveframe Ledger v0.7.0

Waveframe Ledger v0.7.0 introduces the deterministic domain-pack compiler boundary for policy interpretation and publication. Selected immutable domain packs replace a global, mutable policy lexicon, keeping vocabulary, grammar, validation, runtime facts, and lowering scoped to one exact pack identity and version.

Deterministic repository policy compilation

The first and only built-in pack is repository-changes / 1.0.0. It supports repository acting-role requirements plus exact-path and path-prefix allow/deny rules. Unmatched nonempty clauses remain pending until a human explicitly chooses an enforced, informational, or unsupported disposition.

Interpretation and enforcement use no AI model, probabilistic classifier, embeddings, external inference service, or heuristic language model. Runtime-fact schemas define the exact proposal facts required by a constraint, and missing or incompatible facts fail closed rather than weakening policy meaning.

Constraint and publication artifacts

Waveframe-owned constraint_ir.v1 is the canonical typed enforcement representation. The new publication chain binds:

• constraint_ir.v1
• runtime_fact_schema.v1
• domain_pack.v1
• policy_mapping_decision.v1, where applicable
• semantic_commit_bundle.v1
• compiled_authority_contract.v2
• authority_bundle.v2
• publication_receipt.v2

Advanced Boolean conditions, approval and evidence obligations, separation of duties, and exceptions remain unavailable in the repository lowering and fail closed until an exact trusted lowering supports them.

Compatibility

The v0.6 customer-policy APIs retain their supported and rejected behavior and exact canonical hashes. Published v1 artifacts remain readable, and their historical schema meanings are unchanged. Finance interpretation remains available only through the v0.6 compatibility APIs; no finance domain pack is included.

Install

Base installation, without Guard:

pip install governance-ledger

Install the tested optional Guard integration:

pip install "governance-ledger[guard]"

PyPI is the distribution source for the wheel and source distribution; this GitHub release has no attached package assets.

Links

• Waveframe Ledger 0.7.0 on PyPI
• Release PR #10
• Deterministic Domain-Pack Policy Compiler documentation

Waveframe Ledger v0.6.0 — Plain Policy to Published Authority

Customers can now supply short company-policy text and receive deterministic, provenance-complete published authority without manually authoring policy JSON or rule JSON. ## What's new - A deliberately narrow, deterministic policy grammar supports required acting roles, exact and prefix repository target rules, existing approval thresholds, and separation-of-duties constraints. - Bounded clarification keeps ambiguity visible and requires explicit human resolution and approval before publication. Interpretations with no enforceable rules fail closed. - Exact source bytes remain bound through statements, rule mappings, resolutions, approval, semantic commit, compiled contract, authority bundle, and publication receipt. - Source-policy revisions and published-authority versions remain independent identities linked explicitly through publishes_as. - The base package is Guard-free. Runtime admissibility remains available through the optional, tested Waveframe Guard 0.15.0 integration. - Existing authority_bundle.v1 artifacts remain readable and are honestly classified as provenance-incomplete when historical lineage is unavailable. ## Install bash pip install governance-ledger==0.6.0 Optional Guard integration: bash pip install "governance-ledger[guard]==0.6.0" ## Scope This release is not general natural-language policy interpretation. Similar-looking or unsupported prose is never silently promoted into enforceable rules; unsafe ambiguity remains blocked until a bounded human choice is supplied. ## Distribution verification PyPI is the canonical package distribution source; no binary assets are attached to this GitHub release. - Wheel SHA-256: ad670fdcb0e4877d1f26a6a7cc4405bab90d8e25fe3eb160c7c7acbee25a5bc9 - Sdist SHA-256: b3366e9875090bc3c2f83fdc2daf31001db8e76a76f64b28691b98e9c3cbce5e - Normalized 101-member sdist manifest SHA-256: fc771de53b309f4301d93c974c98467c7f4a4bc87cef2948d9250b6099b37338 - Independent raw sdists differed only in gzip, tar-member, and PAX mtime fields. See governance-ledger 0.6.0 on PyPI and release PR #7.

Waveframe Ledger v0.5.0 — Published Authority

Highlights

Waveframe Ledger now publishes a complete, immutable Published Authority rather than only a compiled contract.

Publication is now a single deterministic transaction that emits:

• Published authority contract
• Publication manifest
• Authority bundle (authority_bundle.v1)
• Publication receipt (publication_receipt.v1)
• Snapshot
• Deployed review
• Registry update

Published authorities now have stable identity, deterministic hashes, lifecycle state, and explicit versioned authority references.

New

• Authority Registry
• Versioned authority resolution
• governance-ledger resolve
• Bundle-backed registry entries
• Duplicate identity protection
• Publication receipts
• Canonical Published Authority specification

Registry Improvements

Registry entries now include:

• authority reference
• contract hash
• bundle hash
• bundle location
• publication identity
• lifecycle state

Duplicate publication identity with different immutable content is now rejected.

Resolution

Authorities are now resolved using explicit references such as:

finance-policy@0.1.0

Mutable aliases such as:

finance-policy@latest

are intentionally rejected.

Verification

202 tests passed

Governance Ledger v0.4.0

Semantic Governance Compilation & Replay Infrastructure

Governance Ledger v0.4.0 introduces the first stable public release of the semantic governance compilation architecture.

This release expands Ledger from a semantic extraction and lifecycle toolkit into a deterministic governance infrastructure layer capable of:

• semantic reconciliation
• governance chronology replay
• compiled authority contracts
• execution admissibility projections
• lifecycle enforcement projections
• semantic authority diffing
• governance event modeling
• replay continuity analysis
• execution context semantics
• identity and approval semantics
• deterministic governance projections

Highlights

Semantic Reconciliation

Introduced operator-governed semantic reconciliation with:

• ambiguity classification
• interpretation authority workflows
• deterministic reconciliation artifacts
• semantic commit readiness
• governance confidence posture modeling

Compiled Authority Contracts

Added deterministic compilation boundaries:

• semantic_commit_bundle.v1
• compiled_authority_contract.v1
• execution projection generation
• Guard-compatible enforcement projections

Governance Replay & Event Architecture

Introduced append-only governance event semantics and chronology replay:

• deterministic replay state reconstruction
• replay diffing
• continuity transition events
• projection invalidation events
• lineage and replay semantics

Execution & Lifecycle Projections

Added:

• runtime consequence projections
• admissibility requirement projections
• lifecycle enforcement projections
• replay continuity projections
• execution context semantics

Public Core / Workspace Separation

v0.4.0 formalizes the separation between:

• the public governance core infrastructure layer
• and the private operational governance workspace layer

The public Ledger repository now focuses on:

• canonical schemas
• semantic tooling
• deterministic governance compilation
• replay infrastructure
• lifecycle semantics
• execution projections
• interoperability surfaces

Stability

• 198 passing tests
• deterministic replay guarantees
• schema-versioned governance artifacts
• normalized semantic compiler boundaries
• public CLI surface stabilized for v0.4.0

This release establishes the foundational governance substrate for the broader Waveframe governance ecosystem.

Governance-Ledger v0.3.0

Governance-Ledger v0.3.0 adds the canonical semantic derivation layer and promotes semantic governance artifacts to first-class Ledger outputs.

Added

• governance_ledger/semantics/ as the canonical semantic derivation layer.
• governance_impact_preview.v1 for deterministic governance summaries, enforcement behavior, consequences, lifecycle implications, and example governed outcomes.
• authority_diff_impact.v1 for semantic impact of authority changes, including operational, escalation, lifecycle continuity, and replay continuity implications.
• governance_review_packet.v1 for review-ready packets that bind authority, previews, optional diffs, optional evidence, review context, immutable inputs, and non-goals.
• authority_bundle.v1 as the publishable governance object binding authority contracts, publication manifests, semantic artifacts, optional review packets, lineage, provenance, schema compatibility, and immutable inputs.
• CLI commands: preview, diff-impact, review-packet, and authority-bundle.
• Canonical JSON schemas for all new semantic artifacts.
• SEMANTICS.md documenting semantic governance compilation boundaries, artifacts, guarantees, and CLI examples.

Changed

• README now describes Ledger as governance compiler and semantic derivation infrastructure.
• Documentation now explicitly distinguishes Ledger-owned governance meaning from Cloud-owned governance operations and Guard-owned admissibility.
• Package version bumped to 0.3.0.

Verification

• Full test suite passes with 125 tests.

Governance-Ledger v0.2.0

This release introduces the first major evolution of Governance-Ledger into governance compilation and semantic validation infrastructure.

Highlights:

• Deterministic governance statement normalization
• Governance compilation reports
• Semantic governance diagnostics and publication gating
• Canonical governance provenance and lineage verification
• Deterministic replay tooling for authority and execution verification
• Governance coverage analysis and normalization traceability
• Canonical governance schemas and artifact lineage propagation
• Compiler-style diagnostic domains and severity semantics
• Publication integrity and replay validation workflows

New capabilities:

• Governance normalization corpus testing
• Structured diagnostics (G1xx–G8xx)
• Lineage verification diagnostics
• Replay CLI tooling
• Governance compilation reports with deterministic hashing
• Source-to-authority provenance propagation

Operational improvements:

• Explicit package interoperability with released ecosystem dependencies
• Removed local integration path assumptions and transitional compatibility scaffolding
• Stabilized standalone package behavior and replay verification flows
• Improved schema discipline and canonical artifact handling

This release continues the transition from policy extraction utilities toward deterministic governance compilation and semantic validation infrastructure.

Governance-Ledger v0.1.1

First operational Governance-Ledger release.

Governance-Ledger operationalizes human governance text into deterministic, reviewable governance artifacts compatible with CRI-CORE runtime enforcement systems.

This release introduces:

• deterministic governance constraint extraction
• governance review lifecycle workflows
• validation and ambiguity gating
• canonical CRI-CORE compiler integration
• immutable runtime contract publication
• governance manifests and registry indexing
• deployment provenance tracking
• deterministic governance snapshots
• rollback lineage and governance diffing
• CLI-driven governance workflows
• GitHub Actions governance validation workflow

Governance-Ledger functions as the governance control plane within the broader Waveframe governance stack:

• Governance-Ledger → governance operationalization
• CRI-CORE Contract Compiler → canonical runtime contract semantics
• Waveframe Guard → runtime SDK integration
• Proposal Normalizer → canonical proposal assembly
• CRI-CORE → deterministic admissibility enforcement

This release validates the full end-to-end deterministic governance pipeline:

policy text → governance review → compiled contract → runtime enforcement → allow/block execution.