Skip to content

registry: GV-001 states the hosted build in its scope, re-pinned to ghost-visualizer 2ce5a96 - #38

Merged
Cubits11 merged 6 commits into
mainfrom
claude/gv-001-hosted-re-review
Oct 25, 2026
Merged

Cubits11 merged 6 commits into
mainfrom
claude/gv-001-hosted-re-review

Conversation

@Cubits11

@Cubits11 Cubits11 commented Oct 25, 2026 •

Copy link
Copy Markdown
Owner

What

Re-reviews GV-001 only, after Ghost Visualizer's first GitHub Pages deploy (ghost-visualizer#3, merged as 2ce5a96, deploy run 40156629247).

GV-001's scope said "there is no hosted deployment, so the site links source, not a live demo". The first half stopped being true on 2026-10-24 (03:01 UTC on 2026-10-25). The scope now reads:

The repository at the bound commit. Runs locally. A GitHub Pages build of the repository is served at https://cubits11.github.io/ghost-visualizer/; it deploys from the default branch, so it can run ahead of the bound commit, and this claim covers only the bound commit.

  • Changed through a declared CLARIFY transition in claims_history.yaml (entry 75824d86…), not an edit in place.
  • Proposition, falsifier, forbidden rescues and non-claims are unchanged. The claim still rests on a local run from the bound revision.
  • Support commit and README trigger move from bf8d87b to 2ce5a96. The README is byte-identical at both (git diff bf8d87b 2ce5a96 -- README.md is empty), so the trigger stays quiet.
  • Manual trigger reworded from "hosted deployment added" (now fired) to "the hosted build is removed, moves, or stops serving the bound revision's Evidence Mode".
  • No hyperlink to the hosted build is added on any page. scope renders as escaped plain text in generate_claims_pages.py.

Decisions in this diff that are yours

Merging this attests them. Change them before merging if you disagree.

  1. Review dates. last_reviewed (GV-001), last_owner_review (registry) and the homepage dateModified all move to 2026-10-24. The registry gate requires last_owner_review to cover the newest claim review, and index.html must state it. That is the only change to the homepage.
  2. Transition declaration. CLARIFY with basis DECLARED_HUMAN_JUDGMENT, event_at 2026-10-24 (your local date; the deploy is 2026-10-25 UTC). The reasoning is in the entry's reason. If you read it as EXPAND instead, the chain must be re-appended.
  3. Left unchanged on purpose, and in tension with the new scope:
    • Forbidden rescue "do not recast a local-only source project as a hosted interactive demo" still reads as if the project were local-only. It still has a use (do not rescue a failed local run by pointing at the hosted build), but the wording is stale.
    • Non-claim 2 says the site "links source rather than exhibiting its media as a flagship". That stays true while no page links the hosted build. It will need a decision when a homepage entry is added.
    • Both are commitment fields, so changing them is a second declared transition. Not done here.

Evidence

Run in a fresh full clone (322 commits) at e2cec7b, venv from requirements.txt.

Check Before (clean main) After (this branch)
python3 scripts/verification_manifest.py exit 0, 90 unique checks exit 0, 90 unique checks
claims_history.py verify, edit made before the append n/a FAIL GV-001: commitment changed without a declared transition (the gate works)
claims_history.py verify, after the append ok ok: 53 entries, 22 live commitments equal the chain tip; prior 52 entries are an exact prefix
verify_claims.py GV-001 lines ok bound commit 2ce5a962 reachable from the default branch; reviewed 2026-10-24; support URL embeds the commit and resolves; README matches the bound ref; rendered in ledger
verify_attribution.py 56 bound commits 62 bound commits, all Cubits11, no machine trailers

Generated surfaces regenerated and re-checked with their own --check: claim pages (22 + index + JSON feed), ledger/, observatory/, records/conformance/, docs/RESEARCH_INDEX.md, films/data/facts.json, films/flagship/source-map.json, status/ and data/public-state.json, sitemap.xml, docs/graph/, distribution/traction/. Their diffs contain only GV-001's fields, the 2026-10-24 review date, the new claims.yaml digest, and source pins.

claims_history.yaml also carries the aggregate transition count, 45 → 46, as in 4cfda6d.

Disclosures

  • Distribution drafts. distribution/traction/ was regenerated with the offline scripts/distribute.py run (no network; publish, snapshot and replies were not run). The four drafts (try-a, try-b, try-c, show-overlap) cite claims.yaml, so their source pins and revisions changed. Post text is identical in all four. None was approved at its previous revision, and approvals.json is untouched, so no approval was invalidated. Nothing was sent.
  • Repo graph noise. docs/graph/repo-graph.json was regenerated from a fresh clone, so its branch-topology nodes reflect that clone's remote branches (52 → 37 nodes, different "behind" counts). The drift gate strips branch nodes and D2/D3/D4 findings, so this is not checked, but about 500 lines of that file are branch noise rather than GV-001.
  • Commit attribution. Commits are authored as you and carry no machine trailer, because verify_attribution.py rejects them. For the same reason this description has no "generated with" footer: a squash merge could copy it into the commit log.

Not run, and known state

  • Not run locally: reproduce_cc001.py and verify_clean_clone.py (both clone over the network; CI runs them), smoke_deployed.py, Lighthouse.
  • scripts/publication_gate.py exits 2 (BLOCKED) identically on clean main and on this branch: three blockers (title sources record, one film without a phone composition, no reader records). The title blocker is a self-inconsistency in publication/readiness.json: verified_source_sha256 lists four files and the gate compares two. Not touched here.
  • verify on main has been red since 2026-10-17 21:51 UTC (four runs, the latest the 2026-10-19 scheduled run). I read only the latest: its claim-registry and reproduce jobs passed, the Pages deploy was skipped, and "Deployed site smoke" failed. Not caused by this change.
  • No homepage entry is added. That is a design decision, and your local claude/design-system-2026-10-24 branch has uncommitted index.html changes.

…host-visualizer 2ce5a96

Ghost Visualizer's first GitHub Pages deploy went live on 2026-10-24 from
2ce5a96. The scope said there was no hosted deployment and that the site links
source, not a live demo; the first half stopped being true. The scope now says
a Pages build is served at the live URL, that it deploys from the default
branch and can run ahead of the bound commit, and that the claim covers only the
bound commit. It changes through a declared CLARIFY transition in
claims_history.yaml. Proposition, falsifier, forbidden rescues and non-claims
are unchanged. The support commit and the README trigger move to 2ce5a96; the
README is byte-identical to the one at bf8d87b. last_reviewed and
last_owner_review move to 2026-10-24. Generated surfaces follow.
…GV-001 re-review

Offline `scripts/distribute.py run` after the registry change. The four drafts
(try-a, try-b, try-c, show-overlap) cite claims.yaml and claims_history.yaml, so
their source pins move to 8fc919c and their revisions change. Post text is
identical in all four. None of them is approved at its previous revision, so no
approval is invalidated, and approvals.json is untouched. Nothing was sent.
…-10-24

verify_claims.py requires index.html to state last_owner_review. The registry
date moved with the GV-001 re-review; this is the only change to the page.
…rrection

Offline distribute.py run. Draft revisions are unchanged; only event source pins
and the manifest digest move. Nothing was sent.
@Cubits11
Cubits11 marked this pull request as ready for review October 25, 2026 03:40
@Cubits11
Cubits11 merged commit 9f617d1 into main Oct 25, 2026
6 checks 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