FPF Reference

    G.12:Ext.QDTelemetry — illumination / archive telemetry panel

    Preface node heading:g-12-ext-qdtelemetry-illumination-archive-telemetry-panel:82078

    What this page is

    This is generated FPF reference text from the specification preface or supporting sections. It helps interpret FPF; it is not FPF Reference product documentation.

    Methodology

    Use it to understand how the specification wants to be read, then return to a route, pattern, or work packet for active work. Cite generated IDs only when the wording changes the task decision.

    Content

    PatternScopeId: G.12:Ext.QDTelemetry GPatternExtensionId: QDTelemetry GPatternExtensionKind: MethodSpecific GoverningPatternId: C.18 (QD / NQD‑CAL semantics; descriptor/distance/insertion policy) Uses: {C.18, G.5, G.11} ⊑/⊑⁺: ∅

    RequiredPins/EditionPins/PolicyPins (minimum):

    • DescriptorMapRef.edition
    • DistanceDefRef.edition
    • CharacteristicSpaceSpecRef.edition? (iff the descriptor or characteristic space is editioned as a published surface; required for view reproducibility)
    • InsertionPolicyRef
    • EmitterPolicyRef?
    • ArchiveSnapshotRef? (id/pin for the published archive snapshot, if any)
    • PathSliceId[] (scope for refresh; slice‑keyed)

    RSCRTriggerKindIds (delta): ∅ (base trigger set already includes RSCRTriggerKindId.TelemetryDelta; add only genuinely additional kinds here)

    Notes (wiring‑only):

    • Illumination/coverage signals are treated as telemetry. Any promotion of telemetry into selection dominance is governed elsewhere (typically CAL policy; pinned through G.Core).
    • If descriptor characteristics are surfaced as published identifiers (not just local UI text), they MUST follow the Tech/Plain twin-label discipline (UTS Name Cards); otherwise they remain non-normative view annotations.

    Last Updated: 2026-06-08 — upstream FPF commit 093d30e8 (github.com/ailev/FPF)