gnomonlearn
Docs/RFC-0005 Install Operator RDF identity proposal

RFC-0005 Install Operator RDF 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: owner decision pending. No Gnomon RDF has been published from the new organization, and nothing is deployed; an exact-IRI consumer of the local preview may still exist. Owner: spec semantics and RDF publication.

Source and projection

RFC-0000 §9.1 defines Install Operator as the human or CI identity that applies an install plan, with High trust. RFC-0005 §4a requires that principal for declaration, schema, and activation operations. The RFC-0005 domain projection instead emits https://gnomon.sh/domain/capability/install-operator with RDF class domain:Capability and domain:capabilityScope "admin". In the domain ontology, Capability denotes a permission or scope, not a principal role. The RFC-0005 projection review already marks this node as a source mismatch.

The ontology has no principal-role class. A repository search found the old IRI only in the RFC-0005 domain source, its generated Turtle, and its projection-review entry. No checked-in claim link or SPARQL query names it. This does not prove that no external preview consumer uses it.

Add domain:PrincipalRole as a subclass of domain:DomainEntity, defined as a named trust/authorization role that a principal may hold. Replace the RFC-0005 node subject with https://gnomon.sh/domain/principal-role/install-operator, type it domain:PrincipalRole, retain definedIn RFC-0000, FQN install-operator, and the current summary. Remove the capability-scope triple; RFC-0000’s High trust classification is about the role, not an admin permission grant. Do not alias the old capability IRI to the new role, since that would preserve the erroneous capability interpretation.

For the RFC-0005 domain graph, the semantic diff is five removed triples on the old subject and four added triples on the new subject. The ontology gains the new class declaration, subclass link, label, and description. No RFC prose, Lean normative fact, wire identifier, or deployed resource changes. The alternative is to retain the old subject and change only its class, but the /capability/ path would continue to misidentify the role.

Acceptance

  1. Confirm the identity choice. Edit the ontology and RFC-0005 protobuf projection source, regenerate Turtle, and refresh the affected semantic review fingerprint and verdict.
  2. Compare the exact old/new triple sets. Search spec, framework, site, and Graph consumers for either IRI; review any exact-IRI query before publication. Run ontology, projection drift, RDF link, and all 16 claim queries against the regenerated corpus.
  3. Verify that Install Operator remains a principal role in the authored RFC and Lean catalog, and that no grant is inferred from its High trust label or from the removed capabilityScope assertion.