SOF Diagnostic Protocol

This paper defines the versioned reporting layer of the Sectorized Observable Framework (SOF). It asks what a capability-sound compiled report represents about its source when sectorization, observable extraction, analogue mapping, compiler profile, and assembly profile remain explicit choices rather than hidden defaults. The SOF Report Specification (SOFRS) v2.1 separates capability-aware compilation from report assembly. An admitted adapter supplies a Capability Manifest and validated Typed SOF IR; a Compiler Report Profile selects normative compiler items; and a distinct Assembly Profile renders one bound CompilerOutput without adding, deleting, duplicating, or altering its normative items. Report Relativity therefore identifies a family indexed by source snapshot, adapter, profiles, and version closure rather than one canonical report attached to a source system. Strict SOF reports and diagnostic analogues are mutually exclusive record kinds. Missing capabilities remain omitted or explicitly unavailable; they are not converted to zero findings, infinity, failed bridges, or nearby carriers. Claim status, claim target, certificate class, source-map status, and evidence status remain independently typed. Assembly Faithfulness preserves every normative compiler item exactly once, while the Adapter Adequacy Boundary keeps protocol conformance distinct from source fidelity and scientific adequacy. Version 2.1 adds an explicit report non-intervention boundary and an explicit semantic migration from frozen SOFRS v2.0 reports. Nine migrated v2.1 reports preserve their v2.0 normative projections while adding the fixed object-transition boundary. Their validation receipts bind the source v2.0 receipt, migration implementation, v2.1 contracts, validator, and boundary helper. The v2.1 contract also admits native generation when the producer and a nonempty input closure are digest-bound. Report compilation, assembly, serialization, and validation operate on report artifacts; they do not define, select, authorize, or execute a source-state transition. A conforming receipt establishes local protocol and artifact-closure validation only. It does not establish implementation purity, adapter adequacy, report alignment, causal attribution, action correctness, outcome, or effect. The source-addressed evidence preserves nine frozen version-1 reports as diagnostic analogues, records four bounded strict-reconstruction assessments with status yes, and replaces 118 legacy cutoff sentinels with typed states. These are finite Migration/Assembly Certificates and protocol controls; they do not recompute or promote the underlying domain claims. Source repository: https://github.com/dooven-prime/rime-lite Paper XII of the Representation-Induced Mechanics and Evolution (RIME) program. Independent researcher; no institutional affiliation.