docs: publish the tenant verification contract — claim, artifact, trust assumption#9258
Merged
loopover-orb[bot] merged 1 commit intoJul 27, 2026
Merged
Conversation
…st assumption (#9186) Adds "What you can verify" as a sibling to verify-this-review: for every claim LoopOver makes, the artifact that proves it, the endpoint or CLI that checks it, who can run it, and the trust assumption behind it. States the boundaries as plainly as the guarantees: the ledger is tamper-evident rather than tamper-proof until external anchoring ships, live gate execution is not attested by standing design, ground-truth honesty is closed by no artifact including attestation, digests commit to inputs and never to non-deterministic model outputs, and the hosted-tenant column is weaker than the self-host one.
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
loopover-ui | b6d8e59 | Commit Preview URL Branch Preview URL |
Jul 27 2026, 10:48 AM |
Bundle ReportChanges will increase total bundle size by 25.61kB (0.34%) ⬆️. This is within the configured threshold ✅ Detailed changes
Affected Assets, Files, and Routes:view changes for bundle: loopover-uiAssets Changed:
|
loopover-orb
Bot
added
the
gittensor:bug
Contributor
|
Tip ✅ LoopOver review result - approve/merge recommendedReview updated: 2026-07-27 10:51:25 UTC
Review summary Nits — 7 non-blocking
Decision drivers
Context & advisory signals — never blocks the verdict
Linked issue satisfactionAddressed Review context
Contributor next steps
Signal definitions
🧪 Chat with LoopOverAsk LoopOver a question about this PR directly in a comment — grounded only in the same cached, public-safe facts shown above, never a new claim.
Full command reference: https://loopover.ai/docs/loopover-commands 🧪 Experimental — new and may change. Visual preview
Click any thumbnail to open the full-size screenshot. Before = production · After = this PR's preview deploy. Scroll preview
A short scroll-through clip (desktop) — click either thumbnail to open the full animation. Evidence for scroll-linked behavior a single screenshot can't show. 🟩 Safe / merged · 🟦 Advisory · 🟨 Held for review · 🟥 Blocked / closed 💰 Earn for open-source contributions like this. Gittensor lets GitHub contributors earn for the work they already do — register to start earning →. Checked by LoopOver, a quiet PR intelligence layer for OSS maintainers.
|
![loopover-orb[bot]](https://avatars.githubusercontent.com/in/4139483?s=60&v=4){kind=small}
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
1 participant
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.
Summary
Publishes the verification matrix decided on #9186 as a tenant-facing docs page,
/docs/what-you-can-verify— a sibling toverify-this-review(which stays the how-to walkthrough; this is the what-can-I-check contract).Five rows, each stating claim → artifact → endpoint/CLI → who can run it → trust assumption: gate-decision integrity (hash-chained ledger), decision-record authenticity (digest + published record), published accuracy numbers (corpus export + replay), attested execution (envelope + offline verifier CLI), and what the record's digests do and do not commit to.
The boundaries are stated as plainly as the guarantees:
buildLedgerAnchorPayloadexists but is called from nowhere)promptDigest+modelIdscan still yield different completionsCloses #9186. The decision record resolving all four numbered requirements is on the issue.
Test plan
npx vitest run src/components/site/docs-nav.test.tsx— 4/4 passing (the bidirectional nav drift guard: everycontent/docs/*.mdxhas a nav entry, no entry points at an unpublished page)npm run docs:drift-check— cleannpm run ui:lint— 0 errorsnpm run ui:build— builds cleanGET /v1/public/decision-ledger/verifyreturns HTTP 200 unauthenticated with exactly the documented shape ({ok, checked, nextAfterSeq, tipSeq, tipHash, totalCount})api.loopover.ai(matchesDEFAULT_API_ORIGIN)