gnomonlearn
Docs/RFC-0040 manifest domain identity

RFC-0040 manifest domain identity

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 domain review, 2026-10-04. Owner: Module Platform, Language/Compiler, and Spec. No Gnomon system is deployed, so no stored-data migration is required.

The ontology defines DeclarationKind as a top-level Gnomon declaration form. RFC-0040 instead projects 13 declaration/* nodes for a graph-module YAML document and its nested object kinds or manifest members. RFC-0008 defines a keyword-driven .gnm language with a module declaration and a closed list of language declaration kinds. The graph-module compiler parses YAML from .gnm files; the source-format and filename decision is recorded in DSL_COMPILER_BOUNDARY_PROPOSAL.md. Until that decision is made, treating the graph document’s Module kind as the RFC-0008 module declaration would conflate two authoring languages.

The 12 nested forms are classifier, data_source, hook, predicate, provider, re-export, resource, resource_type, statement, template-call, token, and transform. They are objects map kinds or manifest members rather than top-level source declarations. The transform manifest entry also shares its IRI with RFC-0008’s data transform, despite RFC-0040 §8 explicitly distinguishing them. Its separate identity and RFC-0044 changes are in RFC0044_TRANSFORM_PROPOSAL.md.

The five token-scope RDF nodes use FQNs scope.root, scope.core, scope.app, scope.admin, and scope.webhook, while RFC-0040 §5.1.1 spells their values without scope.. The same IRIs are used for RFC-0048 session scopes, which describe the requester side of the authorization relation. Their source and consumer distinction is in DOMAIN_IDENTITY_GAPS.md.

Two invariant details need correction. hook-install-context-only has enforcedBy "runtime", although RFC-0040 §7 runs hooks in an install transaction with install context. transforms-build-time-only points at the shared runtime declaration/transform IRI, so its target becomes wrong when the manifest entry is separated.

Five more field/type projections expose contract drift:

NodeAuthored source and mismatch
Hooks.postInstall§7 places the hook inside the install transaction; RDF says it runs after install completes. Define completion relative to commit.
Module.category§3.2 permits the runtime to use category for ordering and diagnostics; RDF says it is used, which overstates the rule.
Module.namespace§2 gives module identity as (namespace, version), while §3 and RDF say namespace alone is unique within a runtime. Decide whether multiple versions may coexist.
Provider.optional§5.2 lists this boolean without defining its effect. RDF says it relaxes token binding, although the authored waiver belongs to Token.optional.
SemVer§3 uses an exact module version; §4.1 uses an import range. RDF calls the type a range string for both.

The Module.category, hook enforcement phase, and SemVer summary errors are now corrected in the source projection and regenerated Turtle. The Hooks.postInstall, Module.namespace, and Provider.optional contract questions remain open alongside the identity changes.

Introduce GraphDocumentKind, ModuleObjectKind, and ModuleManifestMemberKind under DomainEntity. Type the graph Module document with GraphDocumentKind; type the objects discriminants with ModuleObjectKind; type classifier, hook, provider, re-export, token, and the build-time transform entry with ModuleManifestMemberKind as appropriate. A form appearing both as an object kind and a manifest member may carry both classes if the authored grammar supports both positions. Preserve Field for the typed slots and Invariant for the normative rules. Give the build-time transform a manifest-specific IRI. Assign token scope identities separately from requester session scope identities once the authorization relation is specified.

The exact source-format choice, document API version, and transform split must propagate together through prose, Lean, protobuf projections, generated Turtle, source fixtures, compiler consumers, and the pinned site. Do not publish mutually contradictory RDF classes or FQNs for one IRI.

Acceptance

  1. RFC-0008 language declarations, graph document kinds, module object kinds, manifest members, and runtime transform declarations have distinct identities and class definitions.
  2. Token scope names and requester session scope names resolve through one explicit authorization rule; no shared IRI carries opposite meanings.
  3. Hook invariant enforcement phase is install time. The build-time transform invariant references the build-time transform identity.
  4. Define module version coexistence, Provider.optional, hook timing, and exact version versus range values in narrative, Lean, RDF, and fixtures.
  5. Check Lean/reference drift, all 16 claim queries, domain IRI/class/FQN identity, parser fixtures for both source languages, graph-module compile tests, and the published dependency closure before normative release.