Skip to content

Stage v0.2 reconciliation and approved JSON representation - #497

Draft
4444J99 wants to merge 6 commits into
wave/wa-publication-20261009from
wave/correction-serialized-admission-20261009-a
Draft

4444J99 wants to merge 6 commits into
wave/wa-publication-20261009from
wave/correction-serialized-admission-20261009-a

Conversation

@4444J99

@4444J99 4444J99 commented Oct 10, 2026 •

Copy link
Copy Markdown
Owner

2026-10-12 workload migration — current head 25affa7

The workload CI defect is repaired in 25affa78bcbf16e89667cbe3cbcfbc3a7fa05006, whose parent is afdd2ffe03bd840516947a9256ff9aea380335fb. PR #497 remains draft and dependent on #496 at unchanged head a9ab644a9577083fc130c9efa4ec249632a22dda. GES v0.2 remains Staged and unfinished.

The historical workload now reproduces from its explicitly preserved membership. A separate current inventory and independently pinned transition require exactly the five approved WA successor additions, preserve every old document byte and family/receipt association, and reject unrelated additions or changed inputs. The original full-directory check remains the default. Both historical and complete-current checks are required by the real-data tests and Toolkit workflow.

Workload measure Preserved baseline Current metadata
Recorded claims 61,936 61,941
Claim documents 654 655
Advisory families 4,651 4,651
Frozen workload receipt subjects 474 474
Records without a workload receipt 61,462 61,467
New review / reconciliation credit 0 / 0 0 / 0

Verified results at this head

Observed at 2026-10-12 19:40:26 UTC:

  • Toolkit push 38298921068: SUCCESS, Python 3.11 and 3.13.
  • Toolkit PR 38298926203: SUCCESS, Python 3.11 and 3.13. The inspected 3.11 log and 3.13 log each show 705 tests passed, both workload commands returning MATCH, and successful validation, compilation and generated-view parity.
  • Native focused workload verification: 51 tests passed on Python 3.14.8. The exact preserved and current CLI commands both returned MATCH; complete argument arrays, timestamps, exit codes and output are preserved in the execution record.
  • An independently authored metadata audit checked all 655 document hashes, all 61,941 claim IDs, every family/count field, all 474 frozen receipt subjects and the exact five successor pairs. The actual /root/accounting_review agent subsequently reviewed the complete output and exact software/evidence files. This supplies software and metadata review.
  • Current-head source-acquisition PR run 38298926193 is in progress at this observation. The same-head push acquisition run 38298920909 is cancelled. The successful acquisition run at the parent revision does not establish the new run's result.

Execution, publication and lease closeout

The native checkout matched the reviewed source fingerprints, and the final staged whitespace check, normal commit and normal push all exited 0. Remote branch readback matched 25affa78bcbf16e89667cbe3cbcfbc3a7fa05006; git status --porcelain was empty at 19:37:52 UTC.

The final controller release returned allowed: true for writer lease 83f0a3de801148e78c5d6f94a4df31b0, owner chatgpt-ges-workload-20261012-b970b9876653, actual PID 56261, surface chatgpt:workload-commit-tranche. Its response listed no remaining leases. The publication tranche began at 19:37:12.430544Z, retained a 600-second limit across retries, and finished after 40.555 seconds. The previous metadata tranche and its original deadline remain recorded; historical cumulative usage is UNKNOWN_NOT_RESET.

The evidence records the earlier driver's missing release receipt separately from successful child verification results. Publication guards also caught extra terminal newlines in review copies/new evidence; the independent reviewer confirmed the exact one-byte differences, and the native verification record was preserved. No check or hook was bypassed.

Remaining holds

The latest heavy acquisition attempt, at 19:20:03 UTC, was denied for swap-fraction; its pressure observation at 19:20:05.143058Z recorded 11,739,070,464 swap bytes on a 16 GiB host and vitals throttle. A later pressure observation returned by the final writer release was timestamped 19:36:09.252829Z and recorded 7,142,249,594 swap bytes with vitals shed. No heavy lease was acquired and no full native authenticated source replay was launched.

The broader historical ledger's 2,164 validated dispositions and conditional 2,174 / 59,767 unresolved expectation are separate from the 474 workload receipt subjects. No fresh broader reconciliation accounting or replacement envelope is claimed. Issuance still requires the original authorized actors or an authentic renewed grant covering current actors, with no identity substitution or backdating.

Remaining adapters/synthesis, retained-body authentication, complete public disposable pilot evidence, final publication clearance, human code/security review, owner acceptance and merged-main verification remain open. Private support remains unverified.

Full repair evidence: migration README, transition contract, and publication preparation.


Earlier staged implementation record

Scope

Dependent implementation tranche based on #496 at a9ab644. The PR targets
wave/wa-publication-20261009 so #496 retains its declared scope and unchanged
head. After its governed acceptance, retarget this tranche to main; do not replay
#495, which is already an ancestor. This PR is Staged, not Verified or release-ready.

  • Add five consumed successor claims, exact scoped owner authority, independently
    reviewed semantic dispositions and full metadata digest/carryforward-subject audit.
    Preserve historical claims and receipts; replacement envelopes remain unissued.
  • Implement a fail-closed structured-occurrence adapter and paired recovery inputs.
  • Implement the explicitly owner-approved JSON representation amendment, including
    v2 schema and unchanged independent rights, human and distribution gates.
  • Record actual public-pilot execution/rollback and a precise remaining matrix.
    Pilot main is restored and rule Disabled; private support is not established.

Earlier observed verification

100 focused tests pass: structured reconciliation 15, JSON representation 8,
publication use 31, completion milestones 21, structured reference review 25.
V2 JSON Schema validation plus 14 synthetic documents pass. Pinned WA source spans
and actual GHQR decoded expression comparison pass. git diff --check passes.
Independent agent code review found three issues; regression tests and fixes were
subsequently rechecked. Agent review does not replace required human review.

Holds

Heavy host admission denied full suite/corpus replay and prescribed governance
checks. No current full reconciliation accounting or accepted control is claimed.
Remaining evidence adapters, six-source extraction, retained-body authentication,
full pilot matrix, final release-file inventory/rights, human code/security review,
owner acceptance, main checks/CI and distribution/tagging all remain open.

The durable evidence and exact results are in
evidence/v02-finish-20261010/README.md; the approved implementation plan is
.codex/plans/2026-10-10-finish-ges-v02.md.

Summary by Sourcery

Advance GES v0.2 with fail-closed reconciliation and approved JSON representation support while documenting public pilot evidence and retaining all release readiness gates.

New Features:

  • Add fail-closed structured-occurrence reconciliation with digest-bound evidence, authority, and independent review inputs.
  • Support owner-approved version 2 JSON string representation validation while preserving existing rights, audit, human acceptance, and distribution gates.
  • Record an observed public native pilot with rollback and restoration evidence.

Bug Fixes:

  • Prevent incomplete, stale, duplicated, unauthorized, or non-independent reconciliation evidence from being treated as certification.
  • Correct publication-use handling so JSON escaping can be compared by decoded expression without bypassing rights decisions.

Enhancements:

  • Extend recovery reporting and publication accounting to expose structured reconciliation and representation comparison status.
  • Add five reviewed successor claims with provenance, metadata digest, and carryforward audits while preserving historical records.

Documentation:

  • Document the v0.2 implementation plan, structured reconciliation receipt contract, JSON representation amendment, pilot status, and remaining acceptance work.

Tests:

  • Add focused adversarial coverage for structured reconciliation, JSON representation validation, authority boundaries, evidence integrity, and legacy compatibility.

Chores:

  • Record staged continuation evidence and explicitly retain unresolved release, human review, CI, distribution, and full-replay holds.

@coderabbitai

coderabbitai Bot commented Oct 10, 2026 •

Copy link
Copy Markdown

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

  • Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@sourcery-ai

sourcery-ai Bot commented Oct 10, 2026

Copy link
Copy Markdown

Reviewer's Guide

This staged PR adds evidence-bound successor-claim reconciliation, a fail-closed structured-occurrence adapter, and an opt-in v2 JSON representation validator with preserved rights gates, while recording a partially completed public pilot and explicitly retaining all full-replay, release, human-review, and acceptance holds.

Sequence diagram for fail-closed structured-occurrence reconciliation

sequenceDiagram
    participant CLI as Recovery CLI
    participant Adapter as Structured adapter
    participant Sources as Pinned source artifacts
    participant Claims as Claim receipts
    participant Policy as Review policy and evidence
    participant Accounting as Recovery accounting
    CLI->>Adapter: reconciliation_accounting()
    Adapter->>Sources: Re-extract and hash complete structured set
    Sources-->>Adapter: Pinned occurrences and source snapshots
    Adapter->>Claims: Validate associations and claim dispositions
    Claims-->>Adapter: Validated claim IDs and input digests
    Adapter->>Policy: Validate authority, reviewers, chronology, and evidence
    Policy-->>Adapter: Complete occurrence receipts or failure
    Adapter->>Accounting: Return completed denominator and unresolved status
    Accounting-->>CLI: Structured reconciliation result
Loading

Sequence diagram for v2 JSON string representation validation

sequenceDiagram
    participant Register as V2 publication register
    participant Publication as publication_accounting()
    participant Parser as decoded_json_expression()
    participant Output as Digest-bound JSON output
    participant Gates as Rights and distribution gates
    Register->>Publication: Submit JSON_STRING use and representation metadata
    Publication->>Output: Validate raw output digest and byte spans
    Publication->>Parser: Resolve JSON pointer and token bounds
    Parser->>Output: Parse complete UTF-8 JSON and reject ambiguity
    Output-->>Parser: Selected string token
    Parser-->>Publication: Decoded expression and decoded digest
    Publication->>Publication: Compare decoded expression with exact source span
    Publication->>Gates: Preserve independent rights and acceptance checks
    Gates-->>Publication: Rights decision remains separate from equality
    Publication-->>Register: V2 accounting with raw and decoded outcomes
Loading

State diagram for staged public pilot and release readiness

stateDiagram-v2
    [*] --> Staged
    Staged --> PilotObserved: Public pilot execution and rollback recorded
    PilotObserved --> MainRestored: Main restored and rule Disabled
    MainRestored --> HoldsRemain: Missing pilot cases, full replay, and human gates
    HoldsRemain --> ReleaseReady: Future acceptance, merged-main checks, rights, and distribution approval
    ReleaseReady --> [*]
Loading

File-Level Changes

Change Details Files
Adds an additive, evidence-bound v0.2 reconciliation checkpoint without replacing historical claims, receipts, or release candidates.
  • Adds five successor claim records with scoped authority, semantic review, digest audits, and carryforward verification.
  • Preserves historical inputs and explicitly withholds replacement envelopes and validated accounting closure.
  • Documents staged status, custody, execution boundaries, blocked full replay, and remaining acceptance work.
.codex/plans/2026-10-10-finish-ges-v02.md
evidence/source-reviews/wa-application-security-correction-01-claims.json
evidence/v02-finish-20261010/README.md
evidence/v02-finish-20261010/approval-requests.md
evidence/v02-finish-20261010/claim-migration-audit.json
evidence/v02-finish-20261010/claim-reconciliation-policy.json
evidence/v02-finish-20261010/owner-authorization.json
evidence/v02-finish-20261010/pull-request-body.md
Implements fail-closed structured-occurrence reconciliation from pinned source artifacts and paired, independently authorized evidence.
  • Extracts complete GHQR and Well-Architected occurrence sets and verifies pins, hashes, spans, denominator, and source identity.
  • Requires validated claim associations, exact subjects, complete evidence, independent reviewers, chronology, and stable inputs before counting.
  • Adds recovery CLI pairing and preserves unknown/incomplete status when evidence is absent or partial.
ges/ledger.py
ges/structured_reconciliation.py
ges/recovery.py
docs/structured-reconciliation-receipts.md
docs/remaining-work.md
tests/test_structured_reconciliation.py
Introduces an owner-approved opt-in v2 JSON string representation contract while retaining raw-byte and independent rights gates.
  • Adds strict JSON pointer/token validation with UTF-8 byte offsets, duplicate-key rejection, complete-document parsing, and decoded-expression hashing.
  • Adds versioned register, authority, receipt, attestation, accounting, and schema handling while leaving v1 behavior unchanged.
  • Separates raw and decoded equality results; JSON encoding differences do not bypass rights, attribution, audit, human, or distribution decisions.
  • Adds adversarial tests for escaping, Unicode, arrays, malformed documents, stale spans, wrong occurrences, substantive changes, and authority reuse.
ges/json_representation.py
ges/publication_use.py
schemas/publication-use.v2.json
docs/publication-json-representation-amendment-v2-proposed.md
docs/publication-use-register.md
tests/test_json_representation.py
Records an observed public native pilot and makes the remaining release and governance boundaries explicit.
  • Captures approved rule activation, partial positive/negative behavior, rollback, restoration, and reapplication against exact revisions.
  • Records that main and the pilot rule were restored to baseline, while cancelled/skipped, deletion/force/bypass, private support, and other acceptance items remain open.
  • Documents focused verification results and clearly distinguishes them from blocked full replay, merged-main checks, human review, owner acceptance, and release authorization.
docs/remaining-work.md
evidence/v02-finish-20261010/README.md
evidence/v02-finish-20261010/pilot-ruleset-active.json
evidence/v02-finish-20261010/pilot-ruleset-preimage.json
evidence/v02-finish-20261010/public-pilot-observations-01.json
evidence/v02-finish-20261010/public-pilot-observations-02.json
evidence/v02-finish-20261010/public-pilot-plan.json
evidence/v02-finish-20261010/publication-rights-decision-proposed.json

Possibly linked issues


Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

4444J99 added a commit that referenced this pull request Oct 12, 2026
Retain PR #497's independently published migration implementation and identical current inventory. Preserve the initial approved PR #503 payload in the first-parent history while integrating 25affa7.

Narrow the delta to the independently reviewed A3 reference stability guard, two regression tests covering four observed failure cases, and supporting review/verification evidence. Both full workload states and all 707 tests pass locally; source and receipt acceptance remain pending.
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