RFC-0047 observability domain identity proposal
Versioned draft snapshot
RFCs, reference catalogs, and evidence reflect Spec 3b2e3e7a114fb826b1445d39a48756b8fff629cd. Counts and pending/status notes belong to that snapshot. Read the dated project update for later progress.
Source repositories are private during staging. Links marked “repository access required” need access to the linked repository.
This is a trace and gap record from the pinned draft specification. It does not establish proof or implementation conformance.
Status: source-bound review proposal. No public RDF class or IRI changed. Runtime type names should align with the pending cross-RFC ontology decision.
Classification findings
RFC-0047 §8.2’s errors { ... } is a nested operation syntax block, not a
top-level declaration kind. Its current /domain/declaration/errors IRI and
DeclarationKind class imply the wrong owner.
The thirteen gnomon.* nodes at /domain/declaration/ are runtime metric
names (eight) and trace event names (five). NamedDeclaration means a
specific source declaration instance; these names are emitted telemetry
contracts, not declarations authored in .gnm.
The 26 AuditLogEntry.* nodes are fields of a runtime audit record that
crosses storage and export boundaries. The ontology’s Field class is a
slot on a Gnomon source declaration. The record itself, CorrelationId,
Metric, and Span are runtime or telemetry shapes, not Gnomon language
types, so their four DataType class assignments are also misleading.
The three services.metrics.* and services.observability.* functions are
runtime methods, not the five Gnomon algebra Operation kinds defined by
the ontology. The existing RuntimeMethod class fits them.
Six invariant nodes link via invariantOf to the currently misclassified
runtime type IRIs. Three of these additionally carry the source conflicts
in RFC0047_OBSERVABILITY_CONTRACT_PROPOSAL.md: audit rollback after an
external sink failure, exactly-one audit under sink failure, and exported
spans under SDK sampling. Of the four invariant nodes without such links,
three have faithful class and source summaries. The stack-trace invariant
turns §8.3’s two SHOULD rules into unconditional requirements and needs its
modality corrected in prose, Lean, and RDF together.
Recommended map
| RDF set | Proposed class | Proposed IRI pattern |
|---|---|---|
nested errors block | SyntaxForm | /domain/syntax/operation/errors |
| eight metric names | new RuntimeMetric | /domain/metric/<name> |
| five span event names | new TraceEvent | /domain/trace-event/<name> |
| 26 audit record fields | new RuntimeRecordField | /domain/runtime-record-field/AuditLogEntry/<field> |
| three service APIs | existing RuntimeMethod | /domain/runtime-method/<fqn> |
AuditLogEntry, CorrelationId, Metric, Span | new runtime/telemetry type class | /domain/runtime-type/<name> |
| ten invariants | existing Invariant | retain IRI; relink six invariantOf targets |
The audit record should be owned by a versioned .proto schema because it
crosses process, storage, and export boundaries. The RDF node should point
to that proto message and its fields after the audit contract is chosen.
Acceptance
Update ontology definitions, RFC-0047 Lean/domain facts, generated Turtle, and SPARQL consumers together. Require each metric and event to have exactly one telemetry class, each audit field to resolve to the proto field it describes, each invariant target to exist with the intended class, and no runtime service API to appear in algebra-operation queries. Compare all 16 checked-in claim query result sets before and after the class correction. Nothing is deployed, so no RDF migration is needed for the first release.