Q-Ledger
Q-Ledger is a machine-first publication ledger derived from edge observations, designed to make governance artifacts detectable, traceable, and chainable over time.
Scope: observation, not attestation. Q-Ledger does not prove identity, authorship, intent, or compliance.
Why Q-Ledger exists
In an interpreted web, probabilistic systems reconstruct context from partial signals. Q-Ledger publishes weak but structured evidence: this is what was observed as requested, and this is how the published surface evolved over time.
What Q-Ledger can show
- that machine-first entrypoints were observed as consulted over a defined period;
- that snapshots were published on specific dates with visible continuity;
- that silent modifications become harder to hide thanks to chaining and archive.
What it cannot prove
- the identity of the person or organization behind the artifacts;
- authority, intent, or legal compliance;
- completeness of the observation; a log is never total truth.
Entrypoints
- JSON:
/.well-known/q-ledger.json - YAML:
/.well-known/q-ledger.yml
Chaining and continuity
Q-Ledger uses snapshot hashes and previous snapshot hashes to make continuity visible. If the published chain no longer matches the archived chain, continuity is broken and the gap itself becomes detectable.
Archive surface
Snapshot history is archived separately in immutable repositories. The point is not to turn the archive into proof of identity. The point is to make publication continuity auditable.
Governance role
Q-Ledger matters because it creates an archival memory for machine-first discoverability. It does not decide truth, but it preserves the observational conditions under which later claims about continuity or drift can be discussed.
Why continuity matters
Q-Ledger is most valuable when later observations can still be related back to a stable baseline and archive logic. Continuity is what allows discoverability to become historically legible rather than purely anecdotal.