Skip to content

CK-08R3A: bound evidence lifecycle queries by session - #417

Merged
douglasmonsky merged 5 commits into
mainfrom
feature/ck08r3a-lifecycle-final-acceptance-a152c75
Aug 5, 2026
Merged

CK-08R3A: bound evidence lifecycle queries by session#417
douglasmonsky merged 5 commits into
mainfrom
feature/ck08r3a-lifecycle-final-acceptance-a152c75

Conversation

@douglasmonsky

Copy link
Copy Markdown
Owner

What changed

  • Reapplied the authority-selected CK-08R3A lifecycle cohort across EvidenceService, publication preparation/writer, lifecycle/domain persistence, analytical DDL/schema, and focused fixture/test support.
  • Persisted session-scoped lifecycle access and preserved exact seven-part provenance/order, cursor pagination, LIMIT+1-before-decode, rejection-only cutover, and query-only boundaries.
  • Added synthetic first/deep forward/backward and foreign-history boundedness coverage while preserving rate-card, base/tail, publication, privacy, and package contracts.

Validation

  • Focused/authority/scope/publication/lifecycle tests: 139 passed.
  • just vp, just v (1,403 tests plus invariant lane), and just vc passed; sdist/wheel release checks passed.
  • Synthetic physical evidence: 2,000/10,000 activities returned 7 and decoded 8; foreign lifecycle 0/1,000/5,000 rows held first/deep forward/backward callbacks at 24/27/26/30 with marker-free plans.
  • GitNexus impact/detect_changes, identity, diff, private/secret checks passed.
  • Reused final-cohort reviewer: P0/P1/P2/P3 = 0/0/0/0; total findings 0; acceptable.

Synthetic/query-only evidence only; no live operation or real Codex data.

Squash merge after focused authority review, exact cross-SQLite preflight, and green Console/Python 3.10/3.14 hosted CI. This authority remains permitted_not_accepted; it does not accept R3A or authorize CK-07/live/downstream operation.
@douglasmonsky
douglasmonsky marked this pull request as ready for review August 5, 2026 03:32
@douglasmonsky
douglasmonsky merged commit 38537f6 into main Aug 5, 2026
3 checks passed
douglasmonsky added a commit that referenced this pull request Aug 6, 2026
## What changed

This authority-only PR binds the exact CK-QG1 maintainability baseline transition caused by the already-accepted writer provenance implementation on exact main `479cc58a887ab49e1bf6fae90ed87cd1cf389fd5`.

- predecessor baseline: `c490d954a5e9d09c61f884d51e3b9d3196af5615887f409c36f8469d1b2b6cf9`
- successor baseline: `fda777e28db7a0696f29b55c9d694f99d987413b206d8e323f217b4fa6a73ad5`
- exact transition: `publication/writer.py:PublicationWriter._validate_turn_provenance`, score `35`, count `1`
- accepted source: writer SHA `13da341fc2a3c50d8d7de7fd6a6fc2b0aca0dbc832a9b56597cd96ab67d17488`, introduced by accepted PR #417 commit `38537f6cee42ad4ba2fb6e45354e410053c7a7cd`

The machine-readable authority artifact includes byte-serializable predecessor/successor documents, exact metadata/tool/normalization identity, C/B/B thresholds, fail-closed new/worsened/improvement behavior, no text exemptions, privacy and spike invariants, and explicit negative mutations. It records current active package ceilings of 1,000,000/2,000,000 bytes while preserving CK-08R0’s historical 383,000/820,000 ratchet and the accepted package-budget supersession authority.

## Scope

Only authority JSON/schema, roadmap links and readiness wording, the repository scope helper, and focused authority/documentation/scope tests are included. No production source, maintainability checker, baseline file, candidate support bytes, or retained PR #392 witness is changed. CK-QG1 implementation acceptance is not granted.

## Validation

- held candidate’s actual `maintainability_failures` entry point: predecessor mismatch, exact successor match, byte mismatch, improvement without rebaseline, exact shrink, new finding, worsened finding, text exemption, and production-scope mutation matrix all passed as recorded
- `git diff --check`
- focused Ruff
- focused authority/documentation/scope tests: 35 passed
- full `tests/kernel`: 506 passed, 1 skipped
- `just vp`: passed
- `just v`: 1,406 passed, 1 skipped; performance invariants passed; Pyright and release safety passed
- `just vc`: package build and distribution release checks passed
- exactly one bounded independent reviewer; final correction review reported no material findings

## Handoff and acceptance boundary

After this PR is squash-merged and fresh exact-main identities are verified, coordinator may instruct the existing CK-QG1 worker to resume in a new latest-exact-main worktree and reuse PR #392. The held candidate remains read-only until then. No new authority task, implementation acceptance, CK-08RG/CK-09 dispatch, or live operation is authorized by this PR.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant