Repository navigation
Allow future design notes to publish without formalization - #28
Merged
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.
Publishing currently fails because the generic-views proposal is a draft specification unit, which intentionally fails evidence validation. Add
{future-note} IDfor exploratory content outside the current specification and convert that proposal.Future notes reject
:lean:,:rust:,:tests:, draft status, and nested specification blocks. They retain identity, reference, and coverage checks, render without a formalization selector, and report correspondence as not applicable. Preparing or recording a correspondence review for a future note is an error. Draft specification units retain their existing evidence requirements.The change includes authoring guidance, parser/rendering/evidence regression tests, and renewed correspondence reviews for all 86 specification units. Most of the diff consists of immutable evidence bundles and records required by the repository's tooling freshness policy; historical evidence is preserved.
Validation passed locally (Cargo commands from
v2/):cargo fmt --all --checkcargo clippy --locked --workspace --all-targets -- -D warningscargo test --locked --workspace, includingevidence_is_complete_and_currentcargo test --locked --test evidence_validation -- --ignoredbash pages/build.shfrom the repository root (both books and root redirect)No Lean formalization was changed.