Repository navigation
registry: GV-001 states the hosted build in its scope, re-pinned to ghost-visualizer 2ce5a96 - #38
Merged
Merged
Conversation
…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.
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
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:
CLARIFYtransition inclaims_history.yaml(entry75824d86…), not an edit in place.bf8d87bto2ce5a96. The README is byte-identical at both (git diff bf8d87b 2ce5a96 -- README.mdis empty), so the trigger stays quiet.scoperenders as escaped plain text ingenerate_claims_pages.py.Decisions in this diff that are yours
Merging this attests them. Change them before merging if you disagree.
last_reviewed(GV-001),last_owner_review(registry) and the homepagedateModifiedall move to 2026-10-24. The registry gate requireslast_owner_reviewto cover the newest claim review, andindex.htmlmust state it. That is the only change to the homepage.CLARIFYwith basisDECLARED_HUMAN_JUDGMENT,event_at2026-10-24 (your local date; the deploy is 2026-10-25 UTC). The reasoning is in the entry'sreason. If you read it asEXPANDinstead, the chain must be re-appended.Evidence
Run in a fresh full clone (322 commits) at
e2cec7b, venv fromrequirements.txt.main)python3 scripts/verification_manifest.pyclaims_history.py verify, edit made before the appendFAIL GV-001: commitment changed without a declared transition(the gate works)claims_history.py verify, after the appendverify_claims.pyGV-001 lines2ce5a962reachable from the default branch; reviewed 2026-10-24; support URL embeds the commit and resolves; README matches the bound ref; rendered in ledgerverify_attribution.pyGenerated 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/anddata/public-state.json,sitemap.xml,docs/graph/,distribution/traction/. Their diffs contain only GV-001's fields, the 2026-10-24 review date, the newclaims.yamldigest, and source pins.claims_history.yamlalso carries the aggregate transition count, 45 → 46, as in4cfda6d.Disclosures
distribution/traction/was regenerated with the offlinescripts/distribute.py run(no network;publish,snapshotandreplieswere not run). The four drafts (try-a,try-b,try-c,show-overlap) citeclaims.yaml, so their source pins and revisions changed. Post text is identical in all four. None was approved at its previous revision, andapprovals.jsonis untouched, so no approval was invalidated. Nothing was sent.docs/graph/repo-graph.jsonwas 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.verify_attribution.pyrejects 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
reproduce_cc001.pyandverify_clean_clone.py(both clone over the network; CI runs them),smoke_deployed.py, Lighthouse.scripts/publication_gate.pyexits 2 (BLOCKED) identically on cleanmainand on this branch: three blockers (title sources record, one film without a phone composition, no reader records). The title blocker is a self-inconsistency inpublication/readiness.json:verified_source_sha256lists four files and the gate compares two. Not touched here.verifyonmainhas 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.claude/design-system-2026-10-24branch has uncommittedindex.htmlchanges.