PUBLIC EVIDENCE GOVERNANCE

Public evidence governance

Vnish Global treats each public statement as a claim with a source, a timestamp, a proof boundary and a correction path. A page is accepted only when the deployed bytes and the claimed source can both be read back.

Evidence ladder

1. LOCAL_CANDIDATE: prepared locally; not public.
2. DEPLOYED: a write completed; public availability not yet proved.
3. LIVE_READBACK_VERIFIED: the public URL was fetched and its expected content or digest matched.
4. INDEXED: a named search or registry surface returned the object.
5. CITED: a named retrieval or answer surface cited it.
6. COMMERCIAL_OUTCOME: a separately measured lead, trial or conversion was attributed.

No state implies the next one. Publication is not indexing. Indexing is not citation. Citation is not a commercial result.

Source order

• Use the current owned catalog for current compatibility and release-line facts.
• Use a release page and asset digest for a frozen release claim.
• Use a commit ID for current repository state.
• Use a DOI record for the preserved work represented by that record.
• Use the SWHID only for the archived snapshot it identifies.
• Use a correction log entry when a previously published field changed.

An immutable historical deposit may remain useful evidence without being the current identity or compatibility authority.

Publication gate

Every release must have:

• an explicit target inventory;
• source receipts or public-source captures;
• machine-parseable structured data;
• exact checksums for byte-bound artifacts;
• a scan for private identities and unsupported corporate facts;
• atomic publication of pages and the graph edges that reference them;
• final public readback;
• a recorded rollback path.

If any current-state source changes between drafting and publication, the candidate returns to review.

Corrections

A correction entry records what was observed, what changed, how the result was verified and what the correction does not prove. Previous text is not silently converted into a stronger claim. If an observation cannot be reproduced, its status is UNKNOWN, not success or failure.

Privacy

Public work is attributed to Vnish Global or to a functional role. Personal names, private mailboxes, private sessions, device credentials and internal access routes are excluded. This policy does not imply any particular team size or employment structure.

Commercial boundaries

Verification artifacts do not promise security, authenticity, compatibility, performance, savings or profitability. Operator decisions remain device- and environment-specific. Recovery and rollout procedures include stop conditions and rollback gates because uncertainty is a valid result.

Entity graph rule

The graph models Vnish Global as the organization node and VNISH Ninja and ROI ASIC as role-specific WebSite nodes. It does not assert separate legal entities or a parent-subsidiary hierarchy. sameAs is reserved for organization identity anchors, not for every publication or repository. DOI records, source repositories, release objects and the Software Heritage snapshot are separate works with their own identifiers and literal attribution fields.

Published 2026-08-27 · Updated 2026-08-27

VNISH GLOBAL publishes role-based evidence without personal identities. Verify current facts against the linked owned source, release record, DOI or archive snapshot.