Governance artifacts
Governance files brought into scope by this page
This page is anchored to published surfaces that declare identity, precedence, limits, and the corpus reading conditions. Their order below gives the recommended reading sequence.
Q-Ledger JSON
/.well-known/q-ledger.json
Machine-first journal of observations, baselines, and versioned gaps.
- Governs
- The description of gaps, drifts, snapshots, and comparisons.
- Bounds
- Confusion between observed signal, fidelity proof, and actual steering.
Does not guarantee: An observation surface documents an effect; it does not, on its own, guarantee representation.
Q-Ledger YAML
/.well-known/q-ledger.yml
YAML projection of the Q-Ledger journal for procedural reading or tooling.
- Governs
- The description of gaps, drifts, snapshots, and comparisons.
- Bounds
- Confusion between observed signal, fidelity proof, and actual steering.
Does not guarantee: An observation surface documents an effect; it does not, on its own, guarantee representation.
Q Ledger Latest
/.well-known/q-ledger-latest.json
Observation surface that exposes logs, metrics, snapshots, or measurement protocols.
- Governs
- The description of gaps, drifts, snapshots, and comparisons.
- Bounds
- Confusion between observed signal, fidelity proof, and actual steering.
Does not guarantee: An observation surface documents an effect; it does not, on its own, guarantee representation.
Complementary artifacts (3)
These surfaces extend the main block. They add context, discovery, routing, or observation depending on the topic.
Q-Metrics JSON
/.well-known/q-metrics.json
Descriptive metrics surface for observing gaps, snapshots, and comparisons.
Q-Metrics YAML
/.well-known/q-metrics.yml
YAML projection of Q-Metrics for instrumentation and structured reading.
Observatory map
/observations/observatory-map.json
Structured map of observation surfaces and monitored zones.
Evidence layer
Probative surfaces brought into scope by this page
This page does more than point to governance files. It is also anchored to surfaces that make observation, traceability, fidelity, and audit more reconstructible. Their order below makes the minimal evidence chain explicit.
- 01Canon and scopeDefinitions canon
- 02Response authorizationQ-Layer: response legitimacy
- 03Weak observationQ-Ledger
- 04AttestationQ-Attest protocol
Definitions canon
/canon.md
Opposable base for identity, scope, roles, and negations that must survive synthesis.
- Makes provable
- The reference corpus against which fidelity can be evaluated.
- Does not prove
- Neither that a system already consults it nor that an observed response stays faithful to it.
- Use when
- Before any observation, test, audit, or correction.
Q-Layer: response legitimacy
/response-legitimacy.md
Surface that explains when to answer, when to suspend, and when to switch to legitimate non-response.
- Makes provable
- The legitimacy regime to apply before treating an output as receivable.
- Does not prove
- Neither that a given response actually followed this regime nor that an agent applied it at runtime.
- Use when
- When a page deals with authority, non-response, execution, or restraint.
Q-Ledger
/.well-known/q-ledger.json
Public ledger of inferred sessions that makes some observed consultations and sequences visible.
- Makes provable
- That a behavior was observed as weak, dated, contextualized trace evidence.
- Does not prove
- Neither actor identity, system obedience, nor strong proof of activation.
- Use when
- When it is necessary to distinguish descriptive observation from strong attestation.
Q-Attest protocol
/.well-known/q-attest-protocol.md
Optional specification that cleanly separates inferred sessions from validated attestations.
- Makes provable
- The minimal frame required to elevate an observation toward a verifiable attestation.
- Does not prove
- Neither that an attestation endpoint exists nor that an attestation has already been received.
- Use when
- When a page deals with strong proof, operational validation, or separation between evidence levels.
Complementary probative surfaces (1)
These artifacts extend the main chain. They help qualify an audit, an evidence level, a citation, or a version trajectory.
AI changelog
/changelog-ai.md
Public log that makes AI surface changes more dateable and auditable.
Q-Ledger
Q-Ledger is a machine-first observation ledger derived from edge observations, designed to make governance artefacts detectable, traceable, and chainable over time.
Scope: observation, not attestation. Q-Ledger proves neither identity, nor intent, nor legal compliance. It documents that a surface was observed as published and, in some cases, consulted within a declared window.
Why Q-Ledger exists
In an interpreted web, systems reconstruct context from partial signals. Q-Ledger publishes a weak but structured memory of that detectability:
- which machine-first entry points exist;
- which snapshots were published;
- what continuity is visible;
- which ruptures become detectable.
Q-Ledger does not settle truth. It preserves the conditions of observation from which later discussions about continuity, drift, or correction can become less anecdotal.
What Q-Ledger can show
Q-Ledger can show:
- that a set of machine-first artefacts was publicly published during a given window;
- that certain endpoints or artefacts were observed as consulted;
- that successive snapshots exist with a chaining logic;
- that continuity or rupture becomes visible.
Its purpose is to make publication historically legible.
What Q-Ledger cannot prove
Q-Ledger does not prove:
- the identity of the actor behind the artefacts;
- the intent behind a consultation;
- editorial or legal compliance;
- the absolute completeness of observation;
- the fidelity of a synthesis produced from those surfaces.
That is why Q-Ledger must remain connected to Observation vs attestation: why Q-Ledger is deliberately weak.
Published artefacts
Primary entry points:
- JSON:
/.well-known/q-ledger.json - YAML:
/.well-known/q-ledger.yml - Latest:
/.well-known/q-ledger-latest.json
Context artefacts often read together with Q-Ledger:
/.well-known/q-metrics.json/.well-known/q-metrics.yml/observations/observatory-map.json
Chaining, continuity, and rupture
Q-Ledger relies on a logic of snapshots, hashes, and previous references. The interest is not cryptographic by itself. The interest is interpretive:
- make visible that a sequence of publications exists;
- make a rupture or lacuna easier to contest;
- prevent a silent correction or silent change from erasing all memory of what was previously published.
Continuity does not establish absolute truth. It makes a history more readable.
Relation to Q-Metrics and observations
Q-Ledger is not a dashboard. It is closer to a weak memory of observed conditions.
Q-Metrics then condenses some of those signals into comparable indicators. Observations serves as the descriptive hub that connects snapshots, windows, limits, and interpretations.
The proper chain is therefore:
published artefacts → weak observation → chaining → metric condensation → doctrinal reading
Why Q-Ledger matters in a machine-first device
Publishing governance files is not enough. It must still become possible to document their continuity, visibility, and publication stability.
In that logic, Q-Ledger helps make auditable the coupling between:
- machine-first architecture;
- governance files;
- identity and boundary surfaces;
- observation and measurement layers.
This is what connects Q-Ledger to Machine-first is not enough: why governance files change the reading regime and What each governance file actually does.
Limits and biases
- Observations depend on edge visibility, caches, and access conditions.
- Silence does not prove absence: an artefact may exist without being observed in the window.
- An observed consultation does not prove correct use of the surface.
- A published snapshot does not guarantee that every system will take it into account.
Q-Ledger therefore remains descriptive. Its strength comes precisely from the fact that it does not try to promise more than it can support.
Canonical definition linkage
For the canonical term definition, see Q-Ledger. This doctrine page explains the operational and machine-first surface, while the definition fixes the term inside the interpretive-governance lexicon.