Refresh UCF context after v1.1 merge - #5
Merged
Merged
Conversation
raelovejoy
marked this pull request as ready for review
September 25, 2026 22:50
raelovejoy
deleted the
context-refresh-after-pr2-pr4-2026-09-24-0811
branch
September 25, 2026 22:50
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.
Why this context refresh is needed
Merged PR #2 placed the proposed v1.1 reconciliation, claims register, evidence rules, worked example, and change record on
main.Merged PR #4 was authored while PR #2 was still open. Because #4 merged afterward, it restored routing that describes those files as draft-only and says PR #2 remains unmerged.
Proposed edits
START-HERE.mdto describe v1.1 as a proposal now present on the public default branch while retaining its AI-assisted, author-review-pending, non-release, and non-validation boundaries.docs/claims.mdanddocs/evidence.mdto the short orientation and review-source metadata.PROJECT-CONTEXT.mdso its source map points to the canonical default-branch files rather than merged PR Reconcile UCF with the living paper; add scoped definitions and a worked example #2.The README link is present and working, so README is unchanged. Project purpose, visibility, ecosystem role, and typed relationships are unchanged; no Wiki or organization-registry update is proposed.