Interpretive governance observability

Interpretive governance observability

This page exposes the observability layer of interpretive governance. It publishes descriptive metrics derived from observation ledgers so that discoverability, continuity, and certain drift signals become legible, comparable, and contestable.

These metrics do not constitute authorization, compliance, or certification. They describe an observed state inside a weak-proof regime.

Why this layer exists

Publishing governance artifacts is not enough. One must still know whether those surfaces are actually:

• discovered by systems;
• consulted before other content;
• maintained with continuity over time;
• coherent with the declared machine-first path.

Observability therefore exists to make the access behavior around governance surfaces readable, without pretending to turn observation into strong proof.

Canonical machine entrypoints

• Metrics (JSON): /.well-known/q-metrics.json
• Metrics (YAML): /.well-known/q-metrics.yml
• Ledger (JSON): /.well-known/q-ledger.json
• Ledger (YAML): /.well-known/q-ledger.yml
• Descriptive protocol: /.well-known/q-attest-protocol.md

Minimum indicator families

1. Entrypoint compliance

Measures the proportion of reconstructed sessions or observations that begin with the expected governance entrypoints before the rest of the corpus.

2. Constraint touch rate

Measures the proportion of sequences in which at least one policy, exclusion, or constraint surface is consulted before synthesis or content reading.

3. Escape rate

Measures the proportion of sequences that leave the expected path and access content directly without passing through machine-first surfaces or declared constraints.

4. Sequence fidelity

Measures the coherence between the expected path and observed sequences, as well as continuity between published snapshots.

How these signals should be read

A rise in entrypoint compliance suggests stronger discoverability of governance surfaces. A higher escape rate may signal path drift, insufficient internal routing, unintended redirects, or indexing instability. A lower sequence fidelity signals a continuity problem or an incomplete archive.

These indicators should always be read comparatively and longitudinally. A single value says little without a baseline, a time window, and a publication context.

What this layer must not claim

• It does not prove identity.
• It does not prove intent.
• It does not prove legal compliance.
• It does not replace a cryptographic attestation layer when such a layer is required.

Observability describes access behavior. By itself, it does not create authority.

Minimum publication discipline

To remain useful, this layer assumes:

• continuity of snapshots;
• readable archival chaining;
• an explicit time window;
• a strict distinction between observation, attestation, and decision.

Without those bounds, the metric layer becomes decorative or over-read.

Doctrinal articulation

This page should be read together with:

• Q-Ledger for the logging layer;
• public benchmarks, observation ledgers, and snapshots for comparative publication;
• applied observability and probative surfaces for the limited evidentiary role of these surfaces.

Reading rule

This doctrinal note on Interpretive governance observability 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.