causal-continuity-engine 0.3.0__tar.gz → 0.4.0__tar.gz

{causal_continuity_engine-0.3.0 → causal_continuity_engine-0.4.0}/.github/CONTRIBUTING.md

@@ -53,7 +53,7 @@ do. `just setup` installs every direct and transitive tool from
 `requirements-dev.lock` in pip's all-or-nothing hash-checking mode, refuses
 source distributions, then installs `causal-continuity-engine` editable without dependency
 resolution or an isolated build environment. The reviewed direct inputs are
-`pytest` 9.1.1, `ruff` 0.16.7, `build` 1.6.1, `jsonschema` 4.26.0,
+`pytest` 9.1.1, `ruff` 0.16.10, `build` 1.6.1, `jsonschema` 4.26.0,
 `setuptools` 84.0.0, and `pip` 26.2.1. None is imported by the engine; jsonschema validates
 emitted receipt instances only in the test/release gate.
 

{causal_continuity_engine-0.3.0 → causal_continuity_engine-0.4.0}/.pre-commit-config.yaml

@@ -43,7 +43,7 @@ repos:
       - id: check-merge-conflict
 
   - repo: https://github.com/astral-sh/ruff-pre-commit
-    rev: e8f7d69b957a30acb2c875078d5fd012de24b64c  # v0.16.7
+    rev: f12be1ebaa5351c1fc76472de98db2c3446c8253  # v0.16.10
     hooks:
       # Lint only, matching `just lint` and CI. Formatting is advisory in this
       # project and deliberately not a gate: the tree was hand-formatted before

{causal_continuity_engine-0.3.0 → causal_continuity_engine-0.4.0}/CHANGELOG.md

@@ -9,6 +9,27 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 No unreleased changes.
 
+## 0.4.0 — 2026-10-17
+
+### Changed
+
+- **Breaking: processor compatibility advances to `cce-processor/1.11.0`;
+  extraction stays `cce-deterministic/1.5.0`.** Preserve older projected stores
+  and their SQLite sidecars after stopping writers. Re-ingest retained sources
+  into a separate new store/project and review its proposals before confirming
+  them. Older projections do not upgrade in place; erased source payloads
+  cannot be reconstructed by replay (ADR-114, ADR-134).
+
+### Fixed
+
+- **A GitHub author association is trusted only in GitHub's exact spelling.**
+  Text authority upper-cased the association before comparing it, so a payload
+  carrying `owner` or `Member` was read as maintainer intent and could raise an
+  ADR-133 notice, while command authorization compared exactly and refused the
+  same value. Both now accept only `OWNER`, `MEMBER` and `COLLABORATOR`; any
+  other spelling is untrusted content. GitHub itself sends only the upper-case
+  values, so webhook data is unaffected (ADR-134).
+
 ## 0.3.0 — 2026-10-16
 
 ### Added

{causal_continuity_engine-0.3.0 → causal_continuity_engine-0.4.0}/CITATION.cff

@@ -8,8 +8,8 @@ authors:
   - given-names: Thomas
     family-names: Albrecht
     alias: The Quantum Falcon
-version: 0.3.0
-date-released: 2026-10-16
+version: 0.4.0
+date-released: 2026-10-17
 license: Apache-2.0
 repository-code: https://github.com/thequantumfalcon/causal-continuity-engine
 url: https://github.com/thequantumfalcon/causal-continuity-engine

{causal_continuity_engine-0.3.0 → causal_continuity_engine-0.4.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: causal-continuity-engine
-Version: 0.3.0
+Version: 0.4.0
 Summary: Causal Continuity Engine - continuity, causal invalidation, and proof for long-running coding agents
 Author: Thomas Albrecht
 License-Expression: Apache-2.0
@@ -27,7 +27,7 @@ License-File: LICENSE.txt
 License-File: NOTICE
 Provides-Extra: dev
 Requires-Dist: pytest==9.1.1; extra == "dev"
-Requires-Dist: ruff==0.16.7; extra == "dev"
+Requires-Dist: ruff==0.16.10; extra == "dev"
 Requires-Dist: build==1.6.1; extra == "dev"
 Requires-Dist: jsonschema==4.26.0; extra == "dev"
 Requires-Dist: pip==26.2.1; extra == "dev"
@@ -145,9 +145,11 @@ than the official SDK, which would pull in more than twenty packages.
 
 ## Quickstart
 
-The installation commands below install the package PyPI currently serves; to
-run this exact checkout, including its authority and v2 packet examples, use
-the editable installation that follows.
+Install either the published package (the next blocks) or this checkout (the
+editable installation further down), not both: one virtual environment is
+enough. The published package runs this quickstart when this checkout is the
+release PyPI serves; for `main` between releases, or your own changes, use the
+editable installation.
 
 Python 3.11 or newer is required; the engine has no third-party runtime
 dependencies. Choose the block for your platform and run it in a new working
@@ -174,15 +176,15 @@ with `.\.venv\Scripts\python.exe -m pip install causal-continuity-engine`
 and invoke the environment's `cce-engine.exe` by its absolute path in the
 commands below. After activation, `cce-engine --help` checks the installation.
 
-**Upgrading an existing project:** this release uses processor 1.10.0 and
-extractor 1.5.0; projections written by 0.2.0's processor 1.9.0 or earlier
+**Upgrading an existing project:** this release uses processor 1.11.0 and
+extractor 1.5.0; projections written by 0.3.0's processor 1.10.0 or earlier
 processors are refused. There is no in-place projection or authority upgrade. Stop writers,
 preserve the complete old project state (including its database and any SQLite
 sidecars), and re-ingest retained sources into a separate new project/store.
 Review and explicitly confirm the new proposals there; old prose is not approval.
 Do not remove markers or sidecars to bypass refusal. Payloads already removed
 by retention cannot be reconstructed from their digests. New users can simply
-start a fresh project. See [the upgrade notes for this release](CHANGELOG.md#030--2026-10-16);
+start a fresh project. See [the upgrade notes for this release](CHANGELOG.md#040--2026-10-17);
 the [0.1.6 notes](CHANGELOG.md#016--2026-09-20) remain historical.
 
 To run this exact checkout instead of the published package, or to work on the
@@ -198,13 +200,20 @@ python -m pip install -e .
 ```
 
 On Windows, use the PowerShell environment-creation and activation commands
-above, then `python -m pip install -e .` from the checkout.
+above, then `python -m pip install -e .` from the checkout. Keep that
+environment active and `cd` back to your new working directory before the steps
+below, so `cce-demo` and its secrets are not created inside the checkout.
 
 The editable install is enough for the engine but not for the test suite,
 which fails at collection without the hash-locked development tools. Install
 them with `python -m pip install -r requirements-dev.lock` (or `just setup`),
-then run `python -m pytest tests -q`. The full suite can take around fifteen
-minutes.
+then run `python -m pytest tests` from the checkout. The project configuration
+already adds `-q`; adding another hides the closing pass/skip summary. The full
+suite can take around fifteen minutes. A few tests skip when the environment
+lacks what they exercise; `-rs` lists each skip with its reason. To see the
+completion gates described below exercised, run
+`python -m pytest tests/test_instrument_validation.py`: it plants each defect a
+gate exists to catch and checks that the named gate catches it.
 
 Global flags come **before** the subcommand: `cce-engine --dir <path> <subcommand>`.
 
@@ -406,6 +415,8 @@ Response: cli-markdown | max bytes: 131072
 The full human view renders each schema field or declares it as metadata kept
 in canonical JSON. Use `resume --format json` for those complete canonical
 field values, including signatures, digests and the state-basis object.
+Recent context lists retrieved nodes by their text; an event node has none, so
+it appears by its id alone (`-  (evt_...)`).
 
 The named verification gap is expected on a fresh project: proof is required
 by default, but CCE cannot safely invent a project-specific verifier
@@ -722,10 +733,17 @@ Published v1 schemas remain historical contracts; v1 proofs are not current
 completion evidence. The v2 schema URLs are bound to the `v0.2.0` release tag,
 and the release workflow verifies that each serves the checked-out bytes.
 
+`verify_proof.py` is a single file. Installing the published package places a
+copy under the environment's `share/causal-continuity-engine/audit/verifiers/`;
+with an editable install, use the checkout's `verifiers/verify_proof.py`. From
+the project directory:
+
 ```bash
 # The complete configured verifier set must already be pinned in project policy.
 cce-engine --dir . --json verify > proof.json
-python verifiers/verify_proof.py proof.json
+VERIFY_PROOF="$VIRTUAL_ENV/share/causal-continuity-engine/audit/verifiers/verify_proof.py"
+# editable install: VERIFY_PROOF=/absolute/path/to/this/local/checkout/verifiers/verify_proof.py
+python "$VERIFY_PROOF" proof.json
 ```
 
 ```text
@@ -733,6 +751,8 @@ UNVERIFIED means nothing was established, not that nothing is wrong.
 An hmac-sha256 envelope needs --hmac-key-hex; a lamport envelope needs --fingerprint
 from a source other than the envelope itself.
 UNVERIFIED C1:P C2:S C3:S C4:P C5:S  proof.json
+
+1 UNVERIFIED
 ```
 
 **That verdict is the honest one, and it is the point.** `hmac-sha256` is not
@@ -740,10 +760,15 @@ a third-party-verifiable scheme at all. Without the secret, an untouched
 envelope and a resealed forgery are indistinguishable, so the verifier reports
 `UNVERIFIED` — not `VALID` — and exits 2. A verifier that returned `VALID`
 there would be telling a stranger that a body a forger rewrote and resealed is
-sound. Supply the key and the same envelope verifies:
+sound. Supply the key and the same envelope verifies. For `hmac-sha256` the key
+is the project's local signing key, `.cce/secrets/signing.key`, given as hex.
+Anyone holding it can also seal a forgery, so this is the operator's own check,
+not a stranger's. The command below puts the key on the command line; run it
+only on a machine you control:
 
 ```bash
-python verifiers/verify_proof.py proof.json --hmac-key-hex <hex>
+python "$VERIFY_PROOF" proof.json \
+  --hmac-key-hex "$(python -c "import pathlib; print(pathlib.Path('.cce/secrets/signing.key').read_bytes().hex())")"
 # VALID      C1:P C2:P C3:P C4:P C5:S  proof.json
 ```
 
@@ -753,7 +778,7 @@ Reaching `VALID` as a stranger requires the fingerprint from somewhere other
 than the artifact:
 
 ```bash
-python verifiers/verify_proof.py proof.json --fingerprint sha256:...
+python "$VERIFY_PROOF" proof.json --fingerprint sha256:...
 ```
 
 The verifier's input boundary is deliberately finite. One invocation accepts
@@ -778,8 +803,9 @@ and `INVALID` dominates — a batch containing both an `INVALID` and an
 Check that the reference implementation still agrees with the corpus:
 
 ```bash
+# from the checkout
 python vectors/generate.py --check
-# reference agrees with every committed vector
+# reference agrees with all 50 committed vectors
 ```
 
 ## What this does not do

{causal_continuity_engine-0.3.0 → causal_continuity_engine-0.4.0}/README.md

@@ -110,9 +110,11 @@ than the official SDK, which would pull in more than twenty packages.
 
 ## Quickstart
 
-The installation commands below install the package PyPI currently serves; to
-run this exact checkout, including its authority and v2 packet examples, use
-the editable installation that follows.
+Install either the published package (the next blocks) or this checkout (the
+editable installation further down), not both: one virtual environment is
+enough. The published package runs this quickstart when this checkout is the
+release PyPI serves; for `main` between releases, or your own changes, use the
+editable installation.
 
 Python 3.11 or newer is required; the engine has no third-party runtime
 dependencies. Choose the block for your platform and run it in a new working
@@ -139,15 +141,15 @@ with `.\.venv\Scripts\python.exe -m pip install causal-continuity-engine`
 and invoke the environment's `cce-engine.exe` by its absolute path in the
 commands below. After activation, `cce-engine --help` checks the installation.
 
-**Upgrading an existing project:** this release uses processor 1.10.0 and
-extractor 1.5.0; projections written by 0.2.0's processor 1.9.0 or earlier
+**Upgrading an existing project:** this release uses processor 1.11.0 and
+extractor 1.5.0; projections written by 0.3.0's processor 1.10.0 or earlier
 processors are refused. There is no in-place projection or authority upgrade. Stop writers,
 preserve the complete old project state (including its database and any SQLite
 sidecars), and re-ingest retained sources into a separate new project/store.
 Review and explicitly confirm the new proposals there; old prose is not approval.
 Do not remove markers or sidecars to bypass refusal. Payloads already removed
 by retention cannot be reconstructed from their digests. New users can simply
-start a fresh project. See [the upgrade notes for this release](CHANGELOG.md#030--2026-10-16);
+start a fresh project. See [the upgrade notes for this release](CHANGELOG.md#040--2026-10-17);
 the [0.1.6 notes](CHANGELOG.md#016--2026-09-20) remain historical.
 
 To run this exact checkout instead of the published package, or to work on the
@@ -163,13 +165,20 @@ python -m pip install -e .
 ```
 
 On Windows, use the PowerShell environment-creation and activation commands
-above, then `python -m pip install -e .` from the checkout.
+above, then `python -m pip install -e .` from the checkout. Keep that
+environment active and `cd` back to your new working directory before the steps
+below, so `cce-demo` and its secrets are not created inside the checkout.
 
 The editable install is enough for the engine but not for the test suite,
 which fails at collection without the hash-locked development tools. Install
 them with `python -m pip install -r requirements-dev.lock` (or `just setup`),
-then run `python -m pytest tests -q`. The full suite can take around fifteen
-minutes.
+then run `python -m pytest tests` from the checkout. The project configuration
+already adds `-q`; adding another hides the closing pass/skip summary. The full
+suite can take around fifteen minutes. A few tests skip when the environment
+lacks what they exercise; `-rs` lists each skip with its reason. To see the
+completion gates described below exercised, run
+`python -m pytest tests/test_instrument_validation.py`: it plants each defect a
+gate exists to catch and checks that the named gate catches it.
 
 Global flags come **before** the subcommand: `cce-engine --dir <path> <subcommand>`.
 
@@ -371,6 +380,8 @@ Response: cli-markdown | max bytes: 131072
 The full human view renders each schema field or declares it as metadata kept
 in canonical JSON. Use `resume --format json` for those complete canonical
 field values, including signatures, digests and the state-basis object.
+Recent context lists retrieved nodes by their text; an event node has none, so
+it appears by its id alone (`-  (evt_...)`).
 
 The named verification gap is expected on a fresh project: proof is required
 by default, but CCE cannot safely invent a project-specific verifier
@@ -687,10 +698,17 @@ Published v1 schemas remain historical contracts; v1 proofs are not current
 completion evidence. The v2 schema URLs are bound to the `v0.2.0` release tag,
 and the release workflow verifies that each serves the checked-out bytes.
 
+`verify_proof.py` is a single file. Installing the published package places a
+copy under the environment's `share/causal-continuity-engine/audit/verifiers/`;
+with an editable install, use the checkout's `verifiers/verify_proof.py`. From
+the project directory:
+
 ```bash
 # The complete configured verifier set must already be pinned in project policy.
 cce-engine --dir . --json verify > proof.json
-python verifiers/verify_proof.py proof.json
+VERIFY_PROOF="$VIRTUAL_ENV/share/causal-continuity-engine/audit/verifiers/verify_proof.py"
+# editable install: VERIFY_PROOF=/absolute/path/to/this/local/checkout/verifiers/verify_proof.py
+python "$VERIFY_PROOF" proof.json
 ```
 
 ```text
@@ -698,6 +716,8 @@ UNVERIFIED means nothing was established, not that nothing is wrong.
 An hmac-sha256 envelope needs --hmac-key-hex; a lamport envelope needs --fingerprint
 from a source other than the envelope itself.
 UNVERIFIED C1:P C2:S C3:S C4:P C5:S  proof.json
+
+1 UNVERIFIED
 ```
 
 **That verdict is the honest one, and it is the point.** `hmac-sha256` is not
@@ -705,10 +725,15 @@ a third-party-verifiable scheme at all. Without the secret, an untouched
 envelope and a resealed forgery are indistinguishable, so the verifier reports
 `UNVERIFIED` — not `VALID` — and exits 2. A verifier that returned `VALID`
 there would be telling a stranger that a body a forger rewrote and resealed is
-sound. Supply the key and the same envelope verifies:
+sound. Supply the key and the same envelope verifies. For `hmac-sha256` the key
+is the project's local signing key, `.cce/secrets/signing.key`, given as hex.
+Anyone holding it can also seal a forgery, so this is the operator's own check,
+not a stranger's. The command below puts the key on the command line; run it
+only on a machine you control:
 
 ```bash
-python verifiers/verify_proof.py proof.json --hmac-key-hex <hex>
+python "$VERIFY_PROOF" proof.json \
+  --hmac-key-hex "$(python -c "import pathlib; print(pathlib.Path('.cce/secrets/signing.key').read_bytes().hex())")"
 # VALID      C1:P C2:P C3:P C4:P C5:S  proof.json
 ```
 
@@ -718,7 +743,7 @@ Reaching `VALID` as a stranger requires the fingerprint from somewhere other
 than the artifact:
 
 ```bash
-python verifiers/verify_proof.py proof.json --fingerprint sha256:...
+python "$VERIFY_PROOF" proof.json --fingerprint sha256:...
 ```
 
 The verifier's input boundary is deliberately finite. One invocation accepts
@@ -743,8 +768,9 @@ and `INVALID` dominates — a batch containing both an `INVALID` and an
 Check that the reference implementation still agrees with the corpus:
 
 ```bash
+# from the checkout
 python vectors/generate.py --check
-# reference agrees with every committed vector
+# reference agrees with all 50 committed vectors
 ```
 
 ## What this does not do

{causal_continuity_engine-0.3.0 → causal_continuity_engine-0.4.0}/causal_continuity_engine/__init__.py

@@ -7,7 +7,7 @@ authenticated runtime records are not replay-derived (ADR-001). Storage is
 SQLite implementing the PostgreSQL-first relational adjacency design (ADR-011).
 """
 
-__version__ = "0.3.0"
+__version__ = "0.4.0"
 
 SCHEMA_VERSIONS = {
     "anchor": "cce.anchor.v1",

{causal_continuity_engine-0.3.0 → causal_continuity_engine-0.4.0}/causal_continuity_engine/engine.py

@@ -104,7 +104,7 @@ from .store import (
 )
 from .verifiers import VerifierRunner, VerifierSpec, record_verification
 
-PROCESSOR_VERSION = "cce-processor/1.10.0"
+PROCESSOR_VERSION = "cce-processor/1.11.0"
 _AUTHORITY_SCHEMA = "cce.authority-decision.v1"
 _AUTHORITY_SOURCE = "cce:authority-decision:v1"
 _AUTHORITY_EXTRACTOR = "cce.authority-decision"

{causal_continuity_engine-0.3.0 → causal_continuity_engine-0.4.0}/causal_continuity_engine/github.py

@@ -65,10 +65,12 @@ def text_authority(author_association: str | None) -> str:
     """Source authority for text authored by a GitHub account.
 
     An issue or comment body is evidence about intent, never policy — and
-    whose intent it is decides how much weight it carries.
+    whose intent it is decides how much weight it carries. GitHub sends the
+    association in upper case; any other spelling is not a GitHub value and
+    stays untrusted, exactly as command authorization compares it (ADR-134).
     """
     if (isinstance(author_association, str)
-            and author_association.upper() in TRUSTED_ASSOCIATIONS):
+            and author_association in TRUSTED_ASSOCIATIONS):
         return "human_intent"
     return "untrusted_content"
 

{causal_continuity_engine-0.3.0 → causal_continuity_engine-0.4.0}/causal_continuity_engine.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: causal-continuity-engine
-Version: 0.3.0
+Version: 0.4.0
 Summary: Causal Continuity Engine - continuity, causal invalidation, and proof for long-running coding agents
 Author: Thomas Albrecht
 License-Expression: Apache-2.0
@@ -27,7 +27,7 @@ License-File: LICENSE.txt
 License-File: NOTICE
 Provides-Extra: dev
 Requires-Dist: pytest==9.1.1; extra == "dev"
-Requires-Dist: ruff==0.16.7; extra == "dev"
+Requires-Dist: ruff==0.16.10; extra == "dev"
 Requires-Dist: build==1.6.1; extra == "dev"
 Requires-Dist: jsonschema==4.26.0; extra == "dev"
 Requires-Dist: pip==26.2.1; extra == "dev"
@@ -145,9 +145,11 @@ than the official SDK, which would pull in more than twenty packages.
 
 ## Quickstart
 
-The installation commands below install the package PyPI currently serves; to
-run this exact checkout, including its authority and v2 packet examples, use
-the editable installation that follows.
+Install either the published package (the next blocks) or this checkout (the
+editable installation further down), not both: one virtual environment is
+enough. The published package runs this quickstart when this checkout is the
+release PyPI serves; for `main` between releases, or your own changes, use the
+editable installation.
 
 Python 3.11 or newer is required; the engine has no third-party runtime
 dependencies. Choose the block for your platform and run it in a new working
@@ -174,15 +176,15 @@ with `.\.venv\Scripts\python.exe -m pip install causal-continuity-engine`
 and invoke the environment's `cce-engine.exe` by its absolute path in the
 commands below. After activation, `cce-engine --help` checks the installation.
 
-**Upgrading an existing project:** this release uses processor 1.10.0 and
-extractor 1.5.0; projections written by 0.2.0's processor 1.9.0 or earlier
+**Upgrading an existing project:** this release uses processor 1.11.0 and
+extractor 1.5.0; projections written by 0.3.0's processor 1.10.0 or earlier
 processors are refused. There is no in-place projection or authority upgrade. Stop writers,
 preserve the complete old project state (including its database and any SQLite
 sidecars), and re-ingest retained sources into a separate new project/store.
 Review and explicitly confirm the new proposals there; old prose is not approval.
 Do not remove markers or sidecars to bypass refusal. Payloads already removed
 by retention cannot be reconstructed from their digests. New users can simply
-start a fresh project. See [the upgrade notes for this release](CHANGELOG.md#030--2026-10-16);
+start a fresh project. See [the upgrade notes for this release](CHANGELOG.md#040--2026-10-17);
 the [0.1.6 notes](CHANGELOG.md#016--2026-09-20) remain historical.
 
 To run this exact checkout instead of the published package, or to work on the
@@ -198,13 +200,20 @@ python -m pip install -e .
 ```
 
 On Windows, use the PowerShell environment-creation and activation commands
-above, then `python -m pip install -e .` from the checkout.
+above, then `python -m pip install -e .` from the checkout. Keep that
+environment active and `cd` back to your new working directory before the steps
+below, so `cce-demo` and its secrets are not created inside the checkout.
 
 The editable install is enough for the engine but not for the test suite,
 which fails at collection without the hash-locked development tools. Install
 them with `python -m pip install -r requirements-dev.lock` (or `just setup`),
-then run `python -m pytest tests -q`. The full suite can take around fifteen
-minutes.
+then run `python -m pytest tests` from the checkout. The project configuration
+already adds `-q`; adding another hides the closing pass/skip summary. The full
+suite can take around fifteen minutes. A few tests skip when the environment
+lacks what they exercise; `-rs` lists each skip with its reason. To see the
+completion gates described below exercised, run
+`python -m pytest tests/test_instrument_validation.py`: it plants each defect a
+gate exists to catch and checks that the named gate catches it.
 
 Global flags come **before** the subcommand: `cce-engine --dir <path> <subcommand>`.
 
@@ -406,6 +415,8 @@ Response: cli-markdown | max bytes: 131072
 The full human view renders each schema field or declares it as metadata kept
 in canonical JSON. Use `resume --format json` for those complete canonical
 field values, including signatures, digests and the state-basis object.
+Recent context lists retrieved nodes by their text; an event node has none, so
+it appears by its id alone (`-  (evt_...)`).
 
 The named verification gap is expected on a fresh project: proof is required
 by default, but CCE cannot safely invent a project-specific verifier
@@ -722,10 +733,17 @@ Published v1 schemas remain historical contracts; v1 proofs are not current
 completion evidence. The v2 schema URLs are bound to the `v0.2.0` release tag,
 and the release workflow verifies that each serves the checked-out bytes.
 
+`verify_proof.py` is a single file. Installing the published package places a
+copy under the environment's `share/causal-continuity-engine/audit/verifiers/`;
+with an editable install, use the checkout's `verifiers/verify_proof.py`. From
+the project directory:
+
 ```bash
 # The complete configured verifier set must already be pinned in project policy.
 cce-engine --dir . --json verify > proof.json
-python verifiers/verify_proof.py proof.json
+VERIFY_PROOF="$VIRTUAL_ENV/share/causal-continuity-engine/audit/verifiers/verify_proof.py"
+# editable install: VERIFY_PROOF=/absolute/path/to/this/local/checkout/verifiers/verify_proof.py
+python "$VERIFY_PROOF" proof.json
 ```
 
 ```text
@@ -733,6 +751,8 @@ UNVERIFIED means nothing was established, not that nothing is wrong.
 An hmac-sha256 envelope needs --hmac-key-hex; a lamport envelope needs --fingerprint
 from a source other than the envelope itself.
 UNVERIFIED C1:P C2:S C3:S C4:P C5:S  proof.json
+
+1 UNVERIFIED
 ```
 
 **That verdict is the honest one, and it is the point.** `hmac-sha256` is not
@@ -740,10 +760,15 @@ a third-party-verifiable scheme at all. Without the secret, an untouched
 envelope and a resealed forgery are indistinguishable, so the verifier reports
 `UNVERIFIED` — not `VALID` — and exits 2. A verifier that returned `VALID`
 there would be telling a stranger that a body a forger rewrote and resealed is
-sound. Supply the key and the same envelope verifies:
+sound. Supply the key and the same envelope verifies. For `hmac-sha256` the key
+is the project's local signing key, `.cce/secrets/signing.key`, given as hex.
+Anyone holding it can also seal a forgery, so this is the operator's own check,
+not a stranger's. The command below puts the key on the command line; run it
+only on a machine you control:
 
 ```bash
-python verifiers/verify_proof.py proof.json --hmac-key-hex <hex>
+python "$VERIFY_PROOF" proof.json \
+  --hmac-key-hex "$(python -c "import pathlib; print(pathlib.Path('.cce/secrets/signing.key').read_bytes().hex())")"
 # VALID      C1:P C2:P C3:P C4:P C5:S  proof.json
 ```
 
@@ -753,7 +778,7 @@ Reaching `VALID` as a stranger requires the fingerprint from somewhere other
 than the artifact:
 
 ```bash
-python verifiers/verify_proof.py proof.json --fingerprint sha256:...
+python "$VERIFY_PROOF" proof.json --fingerprint sha256:...
 ```
 
 The verifier's input boundary is deliberately finite. One invocation accepts
@@ -778,8 +803,9 @@ and `INVALID` dominates — a batch containing both an `INVALID` and an
 Check that the reference implementation still agrees with the corpus:
 
 ```bash
+# from the checkout
 python vectors/generate.py --check
-# reference agrees with every committed vector
+# reference agrees with all 50 committed vectors
 ```
 
 ## What this does not do

{causal_continuity_engine-0.3.0 → causal_continuity_engine-0.4.0}/causal_continuity_engine.egg-info/SOURCES.txt

@@ -140,6 +140,7 @@ tests/test_content_marks.py
 tests/test_contradiction_notice.py
 tests/test_distribution_environment.py
 tests/test_engine_e2e.py
+tests/test_exact_author_association.py
 tests/test_extraction_negated_cue.py
 tests/test_github_redaction.py
 tests/test_identity_compatibility.py

{causal_continuity_engine-0.3.0 → causal_continuity_engine-0.4.0}/causal_continuity_engine.egg-info/requires.txt

@@ -1,7 +1,7 @@
 
 [dev]
 pytest==9.1.1
-ruff==0.16.7
+ruff==0.16.10
 build==1.6.1
 jsonschema==4.26.0
 pip==26.2.1

{causal_continuity_engine-0.3.0 → causal_continuity_engine-0.4.0}/docs/RELEASE.md

@@ -43,9 +43,9 @@ which maintainer signed.
 
 ## Prepare the tree
 
-Processor 1.10.0 and extractor 1.5.0 are not an in-place projection upgrade.
+Processor 1.11.0 and extractor 1.5.0 are not an in-place projection upgrade.
 Stop writers and preserve each complete older database with its SQLite
-sidecars, including processor 1.9.0 stores. Re-ingest retained sources into a
+sidecars, including processor 1.10.0 stores. Re-ingest retained sources into a
 distinct current store/project (ADR-114, ADR-126). Review the
 new source-event-bound proposals and explicitly confirm the intended statements
 and global or confirmed-task scopes through the local authority producer.
@@ -87,7 +87,7 @@ omits `date-released`.
    and its negative fixtures; the test gate fails otherwise.
 2. Regenerate `docs/CAPABILITIES.md` only with
    `python -m causal_continuity_engine.capabilities --write`.
-3. Run `python .github/scripts/check_release_metadata.py --release v0.3.0`,
+3. Run `python .github/scripts/check_release_metadata.py --release v0.4.0`,
    then `just setup` and `just release` from a clean checkout.
    Release-mode metadata checking refuses while the heading is undated.
 4. Drive the MCP server by hand from the built wheel with a real client, and

{causal_continuity_engine-0.3.0 → causal_continuity_engine-0.4.0}/docs/REQUIREMENTS_COVERAGE.md

@@ -1,7 +1,7 @@
 # Requirement Coverage — CCE reference implementation
 
-This matrix describes version 0.3.0. It is a narrative status record, not a
-claim that artifact or platform gates have run. Processor 1.10.0 refuses older
+This matrix describes version 0.4.0. It is a narrative status record, not a
+claim that artifact or platform gates have run. Processor 1.11.0 refuses older
 projections: preserve those stores, re-ingest retained inputs into a distinct
 current store/project, then review and explicitly confirm new proposals.
 Payloads already removed by retention cannot be reconstructed (ADR-114, ADR-126).
@@ -57,7 +57,7 @@ Status legend:
 | AD-003 | implemented | scope/criticality/confidence/authority/valid-time on every node |
 | AD-004 | implemented | current prose proposals use `cce.proposal-id.v1`, binding tenant/project, canonical source event, source identity/field, proposed kind and exact retained text; confirmation has a distinct canonical-decision identity. Older normalized statement identities retain compatibility checks but are not current proposal authority (ADR-126; `test_authority_extraction.py`, `test_authority_producer.py`). |
 | AD-005 | implemented | status resolution is versioned but cannot grant prose authority. Owner-local `record_authority_decision` and `authority --request FILE` provide closed confirm/revoke/replace_scope/confirm_invalidation/reject_invalidation operations with canonical operand checks; HTTP/MCP expose no confirmation producer (ADR-126). |
-| AD-006 | implemented | source typing and injection quarantine precede extraction. All prose, including OWNER and human-decision prose, proposes rather than mandates; explicit local confirmation is required (`test_authority_extraction.py`, `test_authority_consumers.py`; ADR-126). |
+| AD-006 | implemented | source typing and injection quarantine precede extraction. All prose, including OWNER and human-decision prose, proposes rather than mandates; explicit local confirmation is required (`test_authority_extraction.py`, `test_authority_consumers.py`; ADR-126). A GitHub association types text as maintainer intent only in GitHub's exact spelling, as command authorization compares it (`test_exact_author_association.py`; ADR-134). |
 | AD-007 | implemented | calibration by source authority + abstention gate |
 | AD-008 | partial | assumes/depends_on edges supported; automatic linking only where extraction sees both ends |
 

{causal_continuity_engine-0.3.0 → causal_continuity_engine-0.4.0}/docs/adr/ADR-INDEX.md

@@ -3634,3 +3634,57 @@ not make it. A trusted author's stray "not" raises a notice that blocks
 completion of touched tasks until rejected, which is the human gate working.
 The packet summary shows the target and recommended action, not the sentence;
 `invalidations --explain` and MCP `list_invalidations` show the reason.
+
+## ADR-134 — A GitHub author association is trusted only in GitHub's exact spelling
+
+**Status.** Accepted for the local next-version candidate, 2026-10-16;
+not published.
+
+**Context.** `text_authority` upper-cased `author_association` before
+comparing it with OWNER, MEMBER and COLLABORATOR, and a test pinned that
+`owner` counted as maintainer intent. Command authorization (GHI-005)
+compared the same field exactly, so one payload could be trusted for its prose
+and refused for its command. A reproduction run of the ADR-133 notice showed
+the effect: a comment whose association was `owner` raised a
+`contradictory_evidence` notice, while `OWNER ` with a trailing space did not.
+GitHub sends only upper-case association values, so the lenient path served
+no webhook input; it only widened what a hand-made or replayed payload could
+claim.
+
+**Decision.** `text_authority` returns `human_intent` only when the
+association is a string exactly equal to OWNER, MEMBER or COLLABORATOR; every
+other value, including other spellings of those three, is
+`untrusted_content`. Text authority and command authorization now compare the
+same set the same way. Untrusted text is still extracted, screened and
+proposed as before; it cannot mandate, cannot raise an ADR-133 notice and
+cannot run a command.
+
+**Alternatives.** Documenting the case-insensitive comparison would keep two
+answers to one question in the engine. Normalizing at ingestion would rewrite
+a retained source field. Refusing the whole event for a non-GitHub spelling
+would turn a typing decision into a rejection of evidence that untrusted
+typing already contains.
+
+**Compatibility.** Replay re-normalizes each retained payload, so a retained
+event whose association differs from GitHub's spelling now types differently.
+The processor identity advances from `cce-processor/1.10.0` to
+`cce-processor/1.11.0`; `cce-deterministic` stays 1.5.0 because extraction is
+unchanged. Stores projected by 1.10.0 or earlier are refused under ADR-114:
+preserve them with their SQLite sidecars and re-ingest retained sources into a
+distinct new store/project, then review and confirm its proposals. Webhook
+data from GitHub projects identically.
+
+**Verification.** The three GitHub spellings type issue, comment, pull-request
+and review text as `human_intent`; ten other spellings, among them `owner`,
+`Member` and `OWNER ` with a trailing space, type all four as
+`untrusted_content`, and non-text values are untrusted without raising. Text
+trust and command authorization agree on every tested value. `owner`,
+`Member` and `OWNER ` comments raise no ADR-133 notice while the upper-case
+associations still raise one. The processor identity is pinned. The deciding
+tests fail against processor 1.10.0.
+
+**Limit.** This decides how a value is compared, not whether it is true.
+Anyone who can submit a payload chooses its association: HTTP ingestion
+trusts it only after webhook signature verification, and CLI ingestion is
+owner-local. Exact comparison removes a spelling GitHub never sends; it does
+not authenticate the author.