Skip to content

Allow future design notes to publish without formalization - #28

Merged
nikomatsakis merged 1 commit into
mainfrom
codex/future-notes
Nov 1, 2026
Merged

nikomatsakis merged 1 commit into
mainfrom
codex/future-notes

Conversation

@nikomatsakis

Copy link
Copy Markdown
Member

Publishing currently fails because the generic-views proposal is a draft specification unit, which intentionally fails evidence validation. Add {future-note} ID for 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 --check
  • cargo clippy --locked --workspace --all-targets -- -D warnings
  • cargo test --locked --workspace, including evidence_is_complete_and_current
  • cargo test --locked --test evidence_validation -- --ignored
  • bash pages/build.sh from the repository root (both books and root redirect)

No Lean formalization was changed.

@nikomatsakis
nikomatsakis merged commit 7de66ab into main Nov 1, 2026
3 checks passed
@nikomatsakis
nikomatsakis deleted the codex/future-notes branch November 1, 2026 20:34
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