Verify a signed PhaseFolio export.
Every signed export — case-study PDF, IC dossier, MCP-served payload — carries a content hash and an embedded version triplet (engine, methodology, dataset). Paste the hash below to confirm the document was produced by PhaseFolio at a specific point in time, against a specific methodology version, and has not been altered since.
Paste a content hash
Hashes are 64-character SHA-256 digests, printed in the footer of every signed export. Direct URL form: app.phasefolio.com/verify/<hash>.
What verification proves
- Authenticity. The document was issued by PhaseFolio and signed at the timestamp shown. Modification of any byte in the export changes the hash and breaks verification.
- Methodology pin. The methodology version actually consumed by the engine is embedded in the signature payload. A reader can navigate to the corresponding section in /methodology to see exactly how the numbers were computed.
- Engine pin. The rNPV engine version is embedded too. If a future engine release changes numeric outputs for the same inputs (a major bump), the already-issued signature still resolves to the engine that produced it — signatures remain valid indefinitely.
- Dataset pin. For exports that consume reference datasets (PoS benchmarks, sponsor profiles, the JHTV cohort), the dataset snapshot version is recorded so the cited numbers can be re-derived.
For programmatic consumers
Verification is also available as a JSON endpoint at GET /api/v1/verify/<hash>. AI agents and downstream systems consuming PhaseFolio output should verify provenance before relying on it. The MCP tool verify_export exposes the same surface to agentic clients.