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.
20 / Evidence observatory
Do not trust the dashboard. Open its sources.
The Observatory assembles bounded live evidence from PactVerity's public health, receipt-activity and independent market-route endpoints. Every tile states what it does—and does not—prove.
Live evidence feeds3Accepted external runs0Claim challengesPublic
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.
| Claim | Status | Primary evidence | Boundary |
|---|---|---|---|
| Proof Engine | Operational | Run it · Health JSON | First-party deterministic software; not an independent audit. |
| Receipt API | Public beta | Specification and examples | Caller-supplied observations; no custody or settlement. |
| External integrations | 0 verified | Independent-results register | Applications and proposals are not integrations. |
| Independent audit | Pending | Security status | Internal 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.
Safe disclosureRequired
Security-sensitive findings
Do not post exploit details, secrets or private data. Use the documented security route for responsible disclosure.