Terms01
Define before measurement
Record the facility, reporting period, metric, threshold, units, exclusions and evidence requirements before evaluating an outcome.
29 / Data centre assurance
Infrastructure claims need evidence a reviewer can replay.
PactVerity has published a pilot-ready receipt profile for data-centre commissioning, power delivery, availability, efficiency, resilience, incidents and covenant reporting. The profile makes evidence provenance and missing data visible before a deterministic result is produced.
Profile statusPublic specificationLive integrations0 verifiedAssurance boundaryEvidence processing
01 / Investor question
What was promised, what was observed and who supplied the evidence?
A useful infrastructure receipt keeps those questions separate. It records the applicable threshold, the observed value, the measurement period, source type, source reference, signer and individual rule result.
Evidence02
Preserve provenance
Label operator-reported, meter-derived, monitoring-platform and independent-engineer evidence so different trust levels are not blended together.
Receipt03
Replay the decision
Bind the normalised inputs, checks and outcome to a stable digest that another system can recompute and challenge.
02 / Evidence profile
Eight evidence groups cover the operating story without inventing certainty.
Every group is optional unless the parties make it part of the review terms. Missing, stale or malformed evidence must remain visible rather than silently becoming a pass.
| Evidence group | Minimum receipt content |
|---|---|
| Commissioning | Milestone identifier, planned and actual dates, test procedure, sign-off reference and responsible evidence issuer. |
| Power | Contracted capacity, delivered megawatts, meter identifier, measurement window, curtailment and outage evidence. |
| Availability | Uptime basis points, downtime minutes, maintenance exclusions, SLA threshold and monitoring-source reference. |
| Efficiency | PUE value, reporting period, energy inputs, calculation method, meter coverage and methodology version. |
| Sustainability | Energy-source evidence, renewable-certificate reference, water-use measure and geographic reporting boundary. |
| Resilience | Backup-power, cooling and network test outcomes with test dates, evidence digests and unresolved exceptions. |
| Security and incidents | Incident class, impact window, evidence source, remediation state and disclosure boundary without exposing sensitive exploit detail. |
| Covenant reporting | Named covenant, threshold, observed value, reporting date, document digest and deterministic pass or fail result. |
03 / Responsibility
The receipt identifies responsibility instead of hiding it.
Operator
Operator
Supplies identified source records and signs the evidence package; self-reported evidence remains labelled as such.
Independent engineer
Independent engineer
Can attest commissioning or technical observations using a separate key and documented scope.
Lender or investor
Lender or investor
Defines review thresholds and inspects the same portable receipt without relying on a changing dashboard.
PactVerity engine
PactVerity engine
Normalises supplied values, applies explicit rules and creates a deterministic receipt; it does not certify the truth of the source data.
04 / Machine-readable artefacts
The public schema can be reviewed before a pilot starts.
The schema defines facility identity, reporting periods, evidence provenance, explicit checks, receipt status, limitations and signatures. The example shows a fictional evaluation record and is not an operating claim.
JSON Schemav0.1
Validate a proposed receipt
Use the draft schema to align evidence fields and review requirements before connecting any data source.
ExampleFictional
Inspect a bounded record
The example contains synthetic values, explicit source labels and a limitation statement. It demonstrates format only.
05 / Pilot gate
A real pilot requires real evidence owners.
A verified integration will be counted only after the data source, participant, scope, sample receipt and reproduction steps are public enough to check, with sensitive information appropriately redacted.
- Name the facility or a defensible anonymised test environment and the evidence owner.
- Choose two or three measurable claims rather than attempting a complete technical audit.
- Document each source system, export method, timestamp basis and signer.
- Publish at least one reproducible sample receipt and one known limitation.
- Do not describe an application, meeting, proposal or first-party demonstration as an integration.
PVTY is not a data-centre bond or investor claim.
Holding PVTY provides no equity, debt, revenue share, redemption right, yield, data-centre ownership or repayment guarantee. Any future token staking utility would require deployed, reviewed protocol rules and real network use.
Propose an evidence pilotBuild with evidence