gnomonlearn
Docs/RFC-0039 template domain identity

RFC-0039 template 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 RDF class review, 2026-10-04. Owner: Template Runtime and Spec. No Gnomon system is deployed; no data migration is required.

RFC-0039 defines a top-level template declaration, nested object-body forms, a template document schema, an expression language, and runtime interfaces. The inherited RDF projection uses the same ontology classes for these distinct kinds of things. In particular, the ontology says DeclarationKind is a top-level Gnomon declaration, Operation is a kind in the Gnomon operation algebra, Field is a slot on a declaration, and DataType is a type in the Gnomon language type model.

The source-bound review identifies these class mismatches:

Projected nodesCurrent classIntended identity
nested-template-call, resource-template, statement-templateDeclarationKindObject-body syntax forms inside a template.
Eight $ expression forms and four builtin functionsOperationExpression forms and callable functions, separate from the Gnomon operation algebra.
Five TemplateExecutionResult.* slotsFieldRuntime result fields. The authored result also has rootResourceName, which lacks a domain node.
Expression, Template, TemplateContext, TemplateExecutionResult, VisibilityDataTypeExpression value/schema, template document, runtime context/result, and template access enum, respectively. These are not types in the Gnomon language type model.

The template declaration, its authoring fields, object-body fields, and template.compose effect otherwise have the intended identities. The object body fields can retain Field because they are typed slots within a template declaration; their parent syntax forms need distinct identities.

The Template.metadata.version node originally lacked RFC provenance; that omission is corrected in source protobuf and generated Turtle. Three invariant projections need source reconciliation: the canonical expression owner points at the retired checkout; exports.root omits the permitted value form; and unconditional transaction rollback conflicts with continueOnError. The associated decisions and acceptance criteria are in RFC0039_EXPRESSION_SOURCE_GAP.md, RFC0039_ROOT_VALUE_FORM_PROPOSAL.md, and RFC0039_EXECUTION_OUTCOME_PROPOSAL.md.

Proposed correction

Define explicit ontology subclasses for template document/schema, runtime context/result and its slots, expression forms, and builtin functions. Reuse the existing SyntaxForm class for the three object-body forms. Give each new kind an IRI that reflects its identity. Keep template as the top-level DeclarationKind and template.compose as an EffectKind. Add the missing result slot when the result contract is settled. Update Lean, protobuf projection, Turtle, and consumers together so no IRI has contradictory classes.

Acceptance

  1. Authoring declarations, body syntax, expression forms, runtime objects, and Gnomon type-model types have distinct ontology classes.
  2. The RFC, Lean catalog, source projection, and generated Turtle agree on every changed node and the complete result shape.
  3. Run class/IRI collision checks, claim queries, projection drift, Lean compilation, and template runtime tests before normative publication.