Skip to content

Doctrine

Baseline (phase 0): Q-Ledger (v0.1) — 2026-01-19 to 2026-02-06

Phase 0 baseline for Q-Ledger v0.1: what was observed, under what conditions, and what this initial baseline cannot prove.

CollectionDoctrine
TypeDoctrine
Layerq-layer
Version1.0
Levelinformatif
Published2026-02-11
Updated2026-02-26

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.

  1. 01Q-Ledger JSON
  2. 02Q-Ledger YAML
  3. 03Q-Metrics JSON
Observability#01

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.

Observability#02

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.

Observability#03

Q-Metrics JSON

/.well-known/q-metrics.json

Descriptive metrics surface for observing gaps, snapshots, and comparisons.

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 (1)

These surfaces extend the main block. They add context, discovery, routing, or observation depending on the topic.

Observability#04

Q-Metrics YAML

/.well-known/q-metrics.yml

YAML projection of Q-Metrics for instrumentation and structured reading.

Baseline (phase 0): Q-Ledger (v0.1) — 2026-01-19 to 2026-02-06

This page fixes the phase 0 baseline for Q-Ledger v0.1 over the observation window from 2026-01-19 to 2026-02-06. It documents what was observed, what was archived, and what this initial baseline does not prove.

Scope: observation, not attestation. The baseline describes edge-observed access and derived artifacts. It does not prove identity, authorship, intent, or compliance.


Why publish a baseline

In an interpreted web, publication alone is no longer enough. The operational question becomes: is the governance surface discovered, consulted, stable, and traceable over time? Publishing a baseline means freezing a point zero that can later be compared with subsequent phases of passive discoverability.


What the baseline shows

  • observed accesses to machine-first entrypoints during a bounded time window;
  • snapshot continuity when chaining and archive are available;
  • descriptive signals derived from Q-Ledger and, where available, Q-Metrics.

What it does not prove

  • effective ingestion into a model or downstream use in generation;
  • the actual identity behind a user agent;
  • legal compliance, authority, or accountability.

Baseline artifacts

  • /.well-known/q-ledger.json and /.well-known/q-ledger.yml
  • /.well-known/q-metrics.json and /.well-known/q-metrics.yml
  • archived snapshots and a baseline report suitable for later comparison

Next step: passive discoverability

The next phase is not more active extraction. It is to stabilize the machine-first entrypoints, publish them consistently, and observe what happens in a more neutral regime. The purpose is to measure discoverability, stability, and continuity over time against this baseline.

What this baseline is for

This baseline is meant to be preserved as a reference window. Its role is not to prove doctrinal correctness, but to create a stable observational state against which later discoverability signals can be compared.

What this baseline can and cannot show

The baseline can show access, sequence, and the existence of archived artefacts. It cannot show understanding, doctrinal alignment, or authority compliance by itself. That limitation is not a weakness of the archive. It is the condition that keeps the baseline epistemically clean.

Closing note

This frozen window becomes useful precisely because it remains modest in what it claims and explicit in what it cannot establish.

How this baseline should be interpreted

A baseline is a starting state, not a conclusion. It gives later observations something to compare against. Its value comes from making initial conditions explicit: what was observed, what was not observed, which systems were included, which signals were weak, and which uncertainties remained open.

Without a baseline, later improvement or degradation can be misread. A correction may appear successful simply because the query changed. A drift may appear new even though it was already present. A citation may look stable while the underlying interpretation remains unstable.

Maintenance implication

Baseline material should be kept separate from current authority. It documents a historical state. It may inform later analysis, but it should not be treated as the latest interpretation unless it has been refreshed, compared, and reconciled with current observations.

Reading rule

This doctrinal note on Baseline (phase 0): Q-Ledger (v0.1) — 2026-01-19 to 2026-02-06 should be read as a positioning surface within the interpretive governance corpus. It does not replace the canonical definitions or the operational frameworks. It explains why a distinction matters, where the doctrine draws a boundary, and what kind of error becomes more likely when that boundary is ignored.

The reader should separate three levels. First, the conceptual level: what this page names or refuses to name. Second, the procedural level: what a system, organization or evaluator would need to check before relying on a response. Third, the evidence level: what would make the interpretation reconstructable, contestable and corrigible. A doctrinal page is strongest when it keeps those three levels visible rather than collapsing them into a persuasive formulation.

Use in the corpus

Use this page as a bridge between definitions, frameworks and observations. It can guide a reading path, justify why a framework exists, or explain why a response should be bounded, refused or audited. It should not be treated as a runtime instruction, a guarantee of model behavior or a substitute for evidence. If a response based on this doctrine cannot show which source was used, which inference was allowed and which uncertainty remained unresolved, the doctrine remains a reading principle rather than an operational control.