Skip to content

docs: add Vision and Legacy Plan with reproduced audit and witness-grid preflight - #2

Merged
Cubits11 merged 3 commits into
mainfrom
docs/vision-legacy-plan
Oct 25, 2026
Merged

Cubits11 merged 3 commits into
mainfrom
docs/vision-legacy-plan

Conversation

@Cubits11

Copy link
Copy Markdown
Owner

What

Adds docs/VISION-LEGACY-PLAN.md and 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:

  1. AUDIT_REPORT.md says "no Remotion" and "6 tests". The Remotion claim is contradicted by the tree. The "6 tests" figure is not: npm test also reports 6. Nothing in the plan depends on this.
  2. The site homepage blurb ("INSPECT SOURCE", old title) is not on cubits11.github.io origin/main. It was removed in 2949acd on 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:

node scripts/preflight-witness-grid.mjs

At bf8d87b it exits 1: buildEndpointWitnessesForHarmfulOr returns non-integer atom counts (e.g. 7.000000000000001) on 1,552 of 10,201 integer marginal pairs at n=100. The only caller chain is sampleReceipt.ts:4 with 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…c83a before and after npm 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_change trigger on this repository's README.md, so README edits must ship paired with the site's re-review. Phase 1 therefore does not touch the README.

For the owner

  • §2 binds future work once merged. Read it before merging.
  • §8 lists the decisions that are yours (licence holder name, site homepage design, E2 run, G2–G4 binding, Zenodo, repository settings, five readers).

🤖 Generated with Claude Code

…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>
…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>
Cubits11 added a commit that referenced this pull request Oct 25, 2026
…IT license) (#3)

Phase 1 of docs/VISION-LEGACY-PLAN.md (#2): Vite base /ghost-visualizer/, deploy workflow (checks on PR, deploy on push to main, actions pinned by SHA), MIT LICENSE. README untouched on purpose (plan section 6.1).

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>
@Cubits11
Cubits11 merged commit 46eeb0e into main Oct 25, 2026
1 check passed
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