Deployed/Independent findings. Owner-authorized publication.
Private by default · Owner authorizes first publication
Independent findings. Owner-authorized publication.
The review stays private until an authorized protocol representative chooses to publish. Authorization does not let the protocol rewrite findings, and published history does not silently disappear.
ARTIFACT · PUBLICATION_PREVIEW
visibility PRIVATE
state PUBLICATION_AUTH_PENDING
passport (not public)
extension (no verdict)
after publish: CURRENT | STALE | SUPERSEDED | WITHDRAWN | DISPUTED
new implementation never inherits old proof
What you get
Private draft surfaces
Intake, analysis, missing proof, interviews, and score previews stay private before first publish.
Publication authorization console
Preview public fields, extension verdict, Passport URL, score factors, and recorded limitations before deciding whether to publish.
Correction and dispute path
Submit new evidence for independent review. A finding is upheld, corrected, or visibly marked disputed with its reason and evidence version.
Versioned proof manifest
Bound to chain, address, implementation fingerprint, evidence roots, and policy versions.
Automatic stale path
Material live code or critical config change can move CURRENT to STALE without owner approval to hide it.
Permanent version states
Published history can become CURRENT, STALE, SUPERSEDED, or WITHDRAWN. Later states do not erase the earlier version where retention is legally permissible.
How it works
01
Private case
Nothing hits investor dashboard, API, passport, or extension.
02
Draft proof
Manifest and score draft prepared after human gates.
03
Protocol reviews
Sees exact public fields, warnings, limitations, and correction route.
04
Authorize or wait
Only a verified protocol representative can authorize first publication; findings remain independent.