docs: reconcile stale deployed-vs-verifier status + fix dead link - #145
Closed
ai-hpc wants to merge 2 commits into
Closed
docs: reconcile stale deployed-vs-verifier status + fix dead link#145ai-hpc wants to merge 2 commits into
ai-hpc wants to merge 2 commits into
Conversation
…M_ROUTER link Doc-vs-code drift audit (docs only; no code change): - VALIDATOR.md Status table asserted a hard `FAIL` for "deployed vector vs independent verifier" and told operators to stay in non-writing preview "until the supported release converges." That verdict is stale and contradicts sibling docs: the 2026-07-28 redeploy converged production and cathedral-compute BUILD_STATUS.md reported AGREE (2026-08-07), while cathedral-compute EVIDENCE_LANE.md still says "not converged" — one question, three answers. Reconcile VALIDATOR.md to defer to a LIVE re-derivation (this status moves with each deploy) while keeping the safety caution: confirm the live vector reproduces against the pinned verifier before broadcasting. - MINER_VALIDATOR.md linked deploy/MECHANISM_ROUTER_CONTRACT.md, which does not exist in this repo (it lives in the cathedral monorepo). Point it at the in-repo deeper-contract doc, BOUNDARY.md. For wallscaler review; not self-merged. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…_supply_v1) VIOLET_EXTERNAL_SCORES.md's example said the require-policy default is "unpinned (accepts legacy, v3, and confidential_primary)". The actual default is validated_supply_v1 (scaffold/cli.py:59), which REJECTS a plain confidential_primary/v3 vector (validator_thin.py:3470-3494). Fix the comment. Doc-vs-code drift audit; docs only. For wallscaler review. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Contributor
|
Closing as superseded by PR #157 and PR #158. Current main now:
No code from this PR is being merged. |
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
2 participants
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.
Doc-vs-code drift audit of the compute lane surfaced two doc-accuracy issues in this repo (docs only, no code change).
D1 (HIGH) — contradictory
deployed vector vs verifierstatusThe same question has three different answers across the official docs:
VALIDATOR.md:33(this repo) → hardFAIL, plus an operator directive to stay in non-writing preview "until the supported release converges"cathedral-compute/docs/EVIDENCE_LANE.md:48→ "Not converged" (as of 2026-08-01)cathedral-compute/BUILD_STATUS.md:22→AGREE(2026-08-07) (the designated current-state doc; notes the 2026-07-28 redeploy converged production)The live SN39 surface is currently unreachable (Cloudflare 522), so the current truth can't be adjudicated here. This change removes the flat stale
FAIL/blocker verdict and makesVALIDATOR.mddefer to a live re-derivation (the status moves with each deploy), while keeping the safety caution (confirm the live vector reproduces against the pinned verifier before broadcasting; stay in preview until it does).D2 (MED) — dead reference
MINER_VALIDATOR.md:6linkeddeploy/MECHANISM_ROUTER_CONTRACT.md, which does not exist in this repo (it's in thecathedralmonorepo). Repointed to the in-repo deeper-contract doc,BOUNDARY.md.Docs only — no reward/attestation/weight code touched. Flagging for review since D1 changes operator-facing guidance; please confirm the live converged state before merge.
🤖 Generated with Claude Code