Certificate Wording & Disclaimer
TrackForge certificate wording must describe the current methodology accurately: AAA-D ratings, deterministic leakage state, UK/US direct scope, methodology hashing, Merkle proofs, and OpenTimestamps proof state.
Standard Rating Disclaimer
The following wording is the baseline for current production rating certificates:
This certificate records a TrackForge rating event for the subject identified above. The rating was produced under the stated methodology version, taxonomy version, workflow version, and jurisdictional scope, using the evidence snapshot and rating inputs identified by the hashes shown on this certificate.
TrackForge certifies process fidelity: that the stated methodology was applied to the stated evidence snapshot at the stated time, and that the resulting rating event is reproducible from those inputs. TrackForge does not certify absolute legal ownership, authorship, entitlement to royalties, or the absence of future corrections, transfers, disputes, or contradictory evidence.
The current direct certification scope is United Kingdom and United States registration, repertoire, and revenue pathways unless this certificate states otherwise. The certificate does not directly certify non-UK/US society registration state.
The rating, methodology hash, evidence packet hash, Merkle root, and OpenTimestamps proof state are provided for independent verification. Pending anchoring status should be read as pending, not confirmed.
Scope-Specific Statement
Every certificate should include an explicit scope line:
Jurisdictional scope: UK, US
If a future methodology version expands direct society coverage, the certificate must name that scope and pin the workflow version that performed it.
Proof-State Statement
The certificate must distinguish:
| State | Certificate wording |
|---|---|
pending | Submitted or awaiting confirmation; not yet confirmed on-chain. |
confirmed | OpenTimestamps proof has confirmed blockchain attestation. |
failed | Anchoring attempt failed; certificate must not imply blockchain confirmation. |
not_submitted | No external timestamp was submitted. |
local_only | Local witness only; not a confirmed public blockchain anchor. |
Legacy Medal Language
Historical certificates and compatibility exports may contain Gold/Silver/Bronze/Declared fields. Current certificate wording must label those fields as legacy if they are shown.
Acceptable compatibility wording:
Legacy completeness tier: Bronze. This field is retained for historical compatibility and is not the current certificate-facing rating scale.
Unacceptable wording:
Bronze-rated certificate under the current methodology.
Verification Page Statement
The public verification page should show:
- Rating value and rating scale.
- Methodology version and methodology hash.
- Taxonomy version and workflow version.
- Jurisdictional scope.
- Snapshot run ID and snapshot time.
- Evidence hash, leakage-vector hash, and Merkle root where available.
- OpenTimestamps proof status.
- Legacy medal fields only when clearly labelled as legacy diagnostics.
Do Not Rewrite Historical Certificates
Historical certificates should not be rewritten. They should remain attached to their original methodology and wording. If a catalogue is re-rated under the current methodology, TrackForge should issue a new methodology-versioned rating event that supersedes the historical certificate for current reliance purposes.