Bind source admission and draft promotion to reviewed federation candidates - #7
Merged
Merged
Conversation
The per-kind evidence commit added two .gitattributes lines after the manifest hash was computed, so validate-hashes.sh and verify:ci failed at HEAD. Recomputed the hash and regenerated docs/MANIFEST.yaml. Co-Authored-By: Claude Fable 5.1 <[email protected]>
…ration evidence Move the CI checkout of snapsynapse/obligation-first from a848817d to af66a287, the reviewed validator that the September 9 correction tranche was validated against locally. Migrate the superseded 0.2.3 R1 preparation receipt out of the ignored handoff queue into tracked evidence with an explicit supersession note, and hash-pin it. Co-Authored-By: Claude Fable 5.1 <[email protected]>
Adds a dated, report-only receipt for the open owner item on whether any docket event after D. Colo. ECF 24 or any final Colorado Attorney General rulemaking is publicly retrievable. Anonymous CourtListener docket and docket-entries endpoints returned 401; the search endpoint identified the docket (id 73171074) with an index timestamp predating ECF 24; RECAP storage probes for entries 25 through 40 all returned 404 while 24 and 1 returned 200 as controls. One Perplexity query is recorded as unverified leads only. No instrument, obligation, admission, or legacy record changed. Manifest gains the receipt entry and its refreshed hash. Co-Authored-By: Claude Fable 5.1 <[email protected]>
…ngelog Add a "Shipped locally 2026-09-09" entry to the roadmap covering the frozen legacy-unreviewed inventory and admission receipts, Ajv-backed generated-record schema enforcement, the source-owned EveryAILaw anchor mapping that consumes finding F15, per-kind evidence boundaries for the Obligation-First projection, the Doctronic agreement and outcome distinction, the Colorado SB 24-205 ECF 24 recovery with explicit unknown operative and enforcement status, and the separation of the published 0.2.2 identity from the unpublished 0.2.3 source candidate. Update the F14 fixture paragraph so F15 curated mappings are delivered by the reviewed mapping receipt while predecessor-history source review stays pending. Add a matching Unreleased section to the changelog. Package, server, and release-note versions are unchanged, and push, CI on main, release, and publication remain separate held work. Refresh the manifest hashes and regenerated docs copies. Co-Authored-By: Claude Fable 5.1 <[email protected]>
…w receipt Adds the enrolled-copy PDFs and pdftotext -layout snapshots for Utah SB 149 (2024), SB 226 (2025), SB 332 (2025) and HB 320 (2026) under data/admission/sources, re-retrieved from le.utah.gov with recorded HTTP metadata and confirmed byte-identical to the first download. Records the source-consistency review of the four overdue statute records in ops/evidence/utah-statute-source-review-2026-09-09.json with per-record findings and locators for a human editor. No record, obligation or mapping file was edited and no last_verified, status or effective field was changed. MANIFEST.yaml gains the receipt entry and docs/MANIFEST.yaml is the regenerated copy. Co-Authored-By: Claude Fable 5.1 <[email protected]>
…orts, and Obligation-First The September 8 admission audit left one recommended control open: generic draft, remap, and issued negative fixtures across every export surface and derived count. Auditing that gap showed the native schema, cross-reference validator, and admission receipt each rejected a different slice of it, and that a PubLedge original draft promoted to a published-like status with a reviewed receipt could still build, pack, and project because admission only enforced issuance evidence for source: authority-issued. Source admission now refuses any metadata change that leaves a publedge-original-draft record at a status other than proposed or carrying issuance_event or enacted, mirroring the rule validate.js and the native schema already stated. The native instrument schema and the generated record.schema.json now both refuse issuance fields on an original draft, and the generated schema also carries the original-draft-must-stay-proposed rule it previously lacked. Obligation-First issuance determinations exclude original drafts explicitly rather than relying on the status filter alone. The docs/api/v1 aggregate projections (containers, upcoming, recently_changed) move into scripts/lib/api-projection.js so tests can exercise them with in-memory mutations, and each item now carries the record's source and editorial_status so a draft or demonstration record keeps its labelling wherever a status appears. Demonstration-remap and authority-issued semantics are unchanged. Tests add in-memory negative fixtures for all three mutation classes on the native validator, the admission receipt path, the generated record.json path, the aggregate exports and status counts, and the Obligation-First determination count. Each new guard was knocked out in turn to confirm its test fails.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The correction branch binds native records, public projections and promotion decisions to source-admission evidence, preserves original drafts, and retains Colorado/Utah source observations without inventing issuance or commencement. It now pins OF 7f032fc5482b34359770bc50ca6fa94c6606e6fb and validates PR/push/manual owner comparison bases before canonical CI.
Validation: npm run verify:ci passed against main 3a07bba, including schema/admission tests, deterministic builds, package smoke and generated-tree parity. Copied negative fixtures and installed package tests retain snapshot-admission checks without inheriting a commit SHA from a Git history they do not contain. Hash manifests and their generated mirror were refreshed.
Draft only. Main merge and automatic Pages deployment, 0.2.3 publication, tags, Registry updates and paid calls remain held. Human decisions remain on the ten Utah statute discrepancies and the additive aggregate source/editorial_status fields. Draft JIA, ElizaChat, Doctronic, Legion and Colorado later-event evidence retain their stated review/unknown boundaries. No last_verified renewal or broad ingestion is authorized.
Owner preparation record: ops/CANDIDATE-INTEGRATION-2026-09-11.md. EveryAILaw owns the private exact candidate tuple and integration check; production federation still checks sibling mains.
Session 8 republishes this exact candidate with the final shared-checker pin. Local canonical CI passes. The updated GitHub checks must pass at this PR head before coordinated merge. Named history branch:
codex/session8-checker-pin-2026-09-11.Final hosted CI at
7a405b938fd414ebd23585b76a877f1d30a7ce74: both build and a11y pass in run 34661901641.