20 / Evidence observatory

Do not trust the dashboard. Open its sources.

The Observatory assembles bounded live evidence from PactVerity's public health, receipt activity, builder intake, token supply and independent market endpoints. Every tile states what it does—and does not—prove.

Live evidence feeds5Accepted external runs0Claim challengesPublic
Evidence rule:Operational software is not adoption. Self-tests are not audits. Token finality is not liquidity. The Observatory preserves those distinctions.

01 / Live sources

Current system evidence, with failure states visible.

The browser requests each public source directly. A missing response is displayed as unavailable rather than replaced by a promotional estimate.

Loading live evidence sources…

02 / Claim registry

Every material claim gets a source and a challenge path.

The register separates working product facts from pending external evidence.

PactVerity public claim register
ClaimStatusPrimary evidenceBoundary
Proof EngineOperationalRun it · Health JSONFirst-party deterministic software; not an independent audit.
Receipt APIPublic betaSpecification and examplesCaller-supplied observations; no custody or settlement.
PVTY marketLive, shallow poolRoute, depth and valuation JSONPool activity is not adoption, revenue or unique-investor evidence.
Builder interestApplications receivedAggregate programme JSONApplications are not selections, integrations or partnerships.
External integrations0 verifiedIndependent-results registerApplications and proposals are not integrations.
Independent auditPendingSecurity statusInternal tests do not create audit assurance.

03 / Challenge

Found a discrepancy? Make it reproducible.

A valid challenge names the exact claim, source, environment, timestamp, steps and complete public output. Never publish credentials or private vulnerability details.

Public processOpen

Challenge a project claim

Open a structured GitHub report. A challenge is not treated as resolved until the evidence or wording is corrected publicly.

Open claim challenge

Safe disclosureRequired

Security-sensitive findings

Do not post exploit details, secrets or private data. Use the documented security route for responsible disclosure.

Read security policy