gnomonlearn
Docs/RFC-0052 catalog identity proposal

RFC-0052 catalog 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: proposed, awaiting owner decision. Owner: Module Platform and RDF ontology maintainers. No facts changed.

The domain review found eight class mismatches. The consumer inventory finds three incoming source links and no shared definitions for these eight identities.

Concrete correction

IdentitiesCurrent classProposed classProperty change
template-visibility.private, protected, publicCapabilityTemplateVisibilityRemove capabilityScope.
ApplicationModule, BootstrapModule, LayeredModule, PlatformModule, InstallRankDataTypeCatalogConceptRetain descriptive properties.

Define TemplateVisibility as a DomainEntity representing a template access modifier, distinct from a grantable permission. Define CatalogConcept as a DomainEntity representing a named catalog classification or explanatory term, without asserting a Gnomon language type declaration. Add both classes to the JSON-LD context and ontology changelog.

Retain all eight current IRIs, fqn values, provenance, and incoming claim references. The existing /capability/ and /type/ path segments are historical identifiers; their spelling does not establish the ontology class. A later IRI cleanup would require its own explicit source and consumer change.

Remove capabilityScope from the three visibility nodes because its ontology domain would otherwise infer Capability after the explicit class correction. No new visibilityScope property is needed: the current core scope value is not an authored rule delimiting where public/private/protected apply.

This class correction does not authorize core.* to invoke protected db.graph templates. The namespace exception and the protected node’s access-summary conflict require a separate normative visibility decision. Likewise, typing BootstrapModule as a catalog concept does not resolve the install cycle.

Acceptance after approval

  1. Change the ontology and authored protobuf facts; regenerate Turtle rather than editing generated files.
  2. Verify all eight IRIs survive and the three incoming claim links still resolve. Check the inferred graph contains neither Capability on the three visibility values nor DataType on the five catalog concepts.
  3. Refresh source-bound reviews only for the corrected class/property facts; retain protected-summary and bootstrap-contract findings until resolved.
  4. Run ontology/projection drift, JSON-LD, query, and artifact-fed consumer gates. Inspect class-selection query differences explicitly.

The five aspect-summary findings and physical schema naming remain outside this bounded correction.