Pharometric · Governance

Adopted 12 July 2026

The rules we publish under

Governance

An index that contracts settle against must answer one question before its first release: what stops its own operator — or anyone else — from quietly bending it later? These rules are that answer. They were adopted and recorded before the first index release, because stating them afterward would not count.

1 · DATA LICENSE

Published releases are CC BY 4.0

Every public index release is licensed under Creative Commons Attribution 4.0 with a mandatory attribution string carrying the release identifier. Anyone may republish, analyze, or build on the public data — provided the source and release travel with it. A separately sold full-resolution feed contains additional data; it does not restrict, and is not restricted by, the public tier.

2 · OPEN FORMAT

The schema is open; the calibration is not

The Pharometric record and release schema is published under CC BY 4.0, and the reference client under Apache-2.0, so any counterparty can read, validate, and verify a Pharometric artifact without buying anything from us. The reference client ships with stub calibration only. The live calibrated feed, the accumulated release history, and settlement authority are the closed core — the open layer lets anyone speak the format; it does not let anyone impersonate the instrument.

3 · CONFORMANCE & THE NAME

The spec is forkable. The name is not.

A record is Pharometric-conformant when it validates against the published schema and preserves its attribution and release linkage when republished. Anyone may fork the specification or the reference client under their licenses — but a fork is not "Pharometric," and may not present itself as conformant to this instrument. The name identifies exactly one thing: releases signed by this pipeline, under these rules. Trademark protection for the name precedes the first release.

4 · SIGNATURES

Every release is signed; history is never re-signed

Releases are content-addressed and signed (Ed25519, minisign-verifiable offline in one command; signing keys custodied in AWS KMS). The public key, its fingerprint, and every retired key are published permanently at a stable URL beginning with the first release. Retired keys are never removed and old releases are never re-signed — re-signing history is restating history, and restating history is the one thing this instrument exists to make impossible.

5 · METHODOLOGY CHANGE CONTROL

Versioned, announced, run in parallel — and never restated

Methodology carries a semantic version. Every release pins the methodology version it was computed under, and a contract settles against that pinned version — so methodology can improve without breaking anything that settled before. Material changes are announced in advance and run in parallel with the prior method for one quarter before becoming primary. Errors are corrected in the next release with a public erratum; a published release is never edited. Methodology authority sits with a defined seat (currently the founder); the first contract naming Pharometric as calculation agent triggers the addition of an independent review step to that seat.

6 · CAPTURE RESISTANCE

The rules above change only in public

Conformance rules, licenses, and the commitments on this page change only with published advance notice — never retroactively, never quietly. Funding sources material to the index's operation are disclosed. No party — including any customer, funder, or the operator — receives the ability to alter a published number. As counterparties adopt the index, governance formalizes further on named triggers rather than on promises; this page is the floor, and floors only move up.

The working demonstration of these rules already exists: our first publication was a pre-registered test that failed, published with the same prominence a success would have received.