Repository navigation
docs: add Vision and Legacy Plan with reproduced audit and witness-grid preflight - #2
Merged
Merged
Conversation
…id preflight Adds docs/VISION-LEGACY-PLAN.md: thesis, epistemic contract, empirical ladder (v0 / v0.2 E2-MEASURED / v0.3 CENSUS-LIVE / v1.0), falsifiable legacy criteria with the current gap named for each, and a phased build plan with acceptance tests. Every claim carries an evidence tag resolved in Appendix A. Adds scripts/preflight-witness-grid.mjs, a read-only check that reproduces the finding cited in the plan: at bf8d87b the endpoint-witness builder returns non-integer atom counts on 1,552 of 10,201 integer marginal pairs at n=100. It is not reachable from the shipped UI and exits 1 until Phase 2. No source, copy, or README change. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This was referenced Oct 25, 2026
…Rs in the plan - Phase 1b table now names the two draft PRs (cc-framework#67, #1). - Section 6.1 gains the cc-framework coupling: its evidence cards pin the README digest, so any README edit there needs regenerated cards. - Phase 2 gains the Google Fonts request found while verifying the Pages build locally. - Appendix A: E23, E24. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Phase 1 is deployed and the cross-link PRs are no longer drafts blocked on it, so the column now says when its entries were true. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
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.
What
Adds
docs/VISION-LEGACY-PLAN.mdand one read-only preflight script. No source, copy, or README change.The plan covers: thesis (§1), epistemic contract (§2), empirical ladder v0 → v0.2 E2-MEASURED → v0.3 CENSUS-LIVE → v1.0 (§3), four falsifiable legacy criteria with the current gap named for each (§4), phased build plan with acceptance tests (§5), what the site and other repositories pin about this one (§6), and the decisions that are the owner's (§8).
Evidence
Audit facts re-run in a fresh checkout at
bf8d87b. Two did not reproduce as stated:AUDIT_REPORT.mdsays "no Remotion" and "6 tests". The Remotion claim is contradicted by the tree. The "6 tests" figure is not:npm testalso reports 6. Nothing in the plan depends on this.cubits11.github.ioorigin/main. It was removed in2949acdon 2026-10-17. This blocks the site cross-link PR as specified; see plan §6.3. That PR is held.New finding, reproducible with the script in this PR:
At
bf8d87bit exits 1:buildEndpointWitnessesForHarmfulOrreturns non-integer atom counts (e.g.7.000000000000001) on 1,552 of 10,201 integer marginal pairs at n=100. The only caller chain issampleReceipt.ts:4with marginals 0.9 and 0.9, where the product is exact, so no displayed number is wrong and the committed receipt is byte-stable (6b56c1e9…c83abefore and afternpm run generate:evidence). Any new input path would expose it. Fixing it is Phase 2 and precedes v0.2.Also named in the plan: the site's GV-001 has a
remote_content_changetrigger on this repository'sREADME.md, so README edits must ship paired with the site's re-review. Phase 1 therefore does not touch the README.For the owner
🤖 Generated with Claude Code