View as
Switch to see what matters for your role
Anchored to
Provision text is sourced from the registries below. The displayed timestamp is the last successful fetch; a stale anchor is never silently re-stamped.
Anchor registry
UK legislation.gov.uk
Stale / uncheckedUK primary and secondary legislation. Atom data feed of new items, for automated ingestion.
https://www.legislation.gov.uk/new/data.feedEUR-Lex CELLAR (AI Act)
Stale / uncheckedEU legal corpus including the AI Act. CELLAR endpoint throttled in last sweep.
https://eur-lex.europa.eu/C2PA 2.4 specification
Stale / uncheckedContent Credentials specification for provenance and authenticity.
https://github.com/c2pa-org/specificationsRFC 9964 (PQC for IETF)
Stale / uncheckedPost-quantum cryptography for IETF protocols. ML-DSA-65 signature scheme.
https://www.rfc-editor.org/rfc/rfc9964NIST IR 8547 (PQC transition)
Stale / uncheckedNIST IR 8547, INITIAL PUBLIC DRAFT — transition to post-quantum cryptography standards. A draft, not final guidance; cited as a draft and never as a settled requirement.
https://csrc.nist.gov/pubs/ir/8547/ipdCrosswalk registry
Stale / uncheckedLocal meta-watcher for cross-referencing provisions across jurisdictions.
/crosswalkStaleness policy
A successful check is recorded within 24 hours. This does not by itself prove current reachability or reliability.
Anchor passed between 24-72 hours ago. Data may be stale.
No successful check is recorded in 72+ hours. This does not prove the source is unreachable; current freshness is unknown.
The threshold is conservative — a stale anchor is never silently re-stamped.
Why anchoring matters
The integrity of every measurement depends on the integrity of the source. Each audience cares about a different aspect of that integrity.
For Investors
Anchors are part of the evidence perimeter. The table exposes the last successful check and current clock-derived freshness. A stale timestamp is a due-diligence finding, not a clean bill of health.
- → 0 currently fresh within 24 hours
- → 0 degraded · 6 stale / unchecked
- → Source-specific terms shown below
For Regulators
The statute entries point to official UK and EU sources. Standards point to their publishing bodies or repositories. The Crosswalk registry is a local operator source, not an external primary source. Each row must be judged on its own URI, timestamp, and stated reuse terms.
- → UK: legislation.gov.uk (OGL v3.0)
- → EU: EUR-Lex CELLAR (EU reuse)
- → IETF & NIST: standard licences
For IP Counsel
Anchor freshness is a discovery question. If a witness is asked "what version of the EU AI Act did you test against", the answer is in the timestamp row. Stale anchors are not concealed — they are surfaced.
- → Timestamped at every fetch
- → 72-hour staleness policy
- → Degraded state visible
Licence register (for legal review)
This table records the stated reuse terms for each listed source. Open licences and reuse notices do not mean the material is uncopyrighted, and the self-hosted Crosswalk registry has no external-source licence. Verify the applicable terms before reuse.
| Source | Licence | Jurisdiction | Use |
|---|---|---|---|
| legislation.gov.uk | OGL v3.0 | UK | Primary & secondary legislation |
| EUR-Lex CELLAR | EU reuse | EU | EU AI Act, GDPR, directives |
| C2PA spec | CC BY 4.0 | Global | Provenance & authenticity spec |
| RFC 9964 | IETF Trust | Global | PQC for IETF protocols |
| NIST IR 8547 | NIST pub | US | PQC transition guidance |
| self-hosted | internal | — | Crosswalk registry |
