governance: reconcile decisions, ruleset state, and release readiness - #15
Merged
davehallmon merged 3 commits intoAug 30, 2026
Merged
Conversation
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
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.
Summary
Commit 1 — Governance Reconciliation (f4f9fd5)
project/control/decisions.json(continuity-state treatment, transaction-boundary expression, shared finding envelope, Dust & Ash profile mechanism, transaction/audit placement, author-memory scope, vertical-slice scope, export authority, two-host evidence timing).1.0.0to1.1.0and adds milestoneREL-01 — Public Release Readinesswith three deliverables.REL-01-01,REL-01-02,REL-01-03to the task ledger (licensing, provenance, attribution).21815133(Protect Main) as independently verified, and adds runGOV-REC-01.PROGRESS.md,STATUS.md,ROADMAP.mdfrom canonical control data.Commit 2 — Reconciliation Correction (865198c)
docs/source-analysis/lensetek.mdtoREL-01-02evidence.result_commitandresult_referencetof4f9fd5..., and repairs the history entry.REL-B01linked toREL-01-02(Lensetek borrowing blocked; clean-room CP1A may proceed).validate(): history SHA checks, blocked-task ↔ blocker linkage, blocker task_id existence, ruleset field types, decision ID uniqueness.Commit 3 — Test Hardening (this commit)
requires_approvalsvalues.Verification
Current state
python3 scripts/generate_operational_views.py(clean)python3 scripts/generate_operational_views.py --check(clean)python3 -m unittest discover -s tests -p "test_*.py"(14/14 OK)git diff --check: cleand221fafd34d97be35a67b52cf77ef97bf08cbf4amatches remotemainChanged paths (this commit)
scripts/generate_operational_views.pytests/test_operational_views.pyCumulative changed paths across PR #15
project/control/decisions.jsonproject/control/roadmap.jsonproject/control/tasks.jsonproject/control/snapshot.jsonscripts/generate_operational_views.pytests/test_operational_views.pyPROGRESS.mdSTATUS.mdROADMAP.mdScope
Governance reconciliation, correction, and test hardening only. No schemas, skills, templates, profile files, or implementation code changed. CP1A implementation has not begun.
Test names (14)
test_control_data_validatestest_commit_shorthand_validatestest_every_blocked_task_has_blockertest_ruleset_fields_have_expected_typestest_committed_views_are_currenttest_every_root_view_declares_it_is_generatedtest_null_commit_rejected_before_generated_view_acceptedtest_malformed_history_sha_rejectedtest_blocked_task_without_blocker_rejectedtest_blocker_without_existing_task_rejectedtest_duplicate_decision_ids_rejectedtest_ruleset_requires_approvals_boolean_rejectedtest_ruleset_requires_approvals_negative_rejectedtest_ruleset_non_boolean_field_rejected