RFC-0043 operation 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 RDF IRI or ontology class changed. The cross-RFC module-object class choice remains with the owner.
Identity findings
RFC-0043 §1 distinguishes a language-level procedure from the compiled
runtime operation module-manifest object. Section 8 makes workflow a
nested optional member of that operation. The RDF projection gives both
runtime forms DeclarationKind IRIs, a class whose ontology definition is a
top-level Gnomon declaration form. Only procedure is a top-level language
declaration here. The nine EffectKind nodes have the intended class.
The 31 projected Field nodes are slots on the manifest operation and its
nested authorization, effect, guard, idempotency, and workflow records. The
ontology defines Field as a slot on a source declaration. These need an
explicit manifest-object field class and owner-qualified IRIs. Bare names
like key, when, and policy are otherwise ambiguous across records.
Five projected DataType nodes (ConflictPolicy, Guard, IdempotencyKey,
Transport, WorkflowTransition) describe runtime enum/record/value shapes,
not Gnomon source-language types. A runtime-value or manifest-schema type
class should own them. The ten invariant nodes link through the operation,
workflow, or field identities above and must be relinked when those targets
are corrected. Two also preserve the source-semantic conflicts documented
in RFC0043_EXECUTION_CONTRACT_PROPOSAL.md: unconditional invocation audit
and query prohibition of all mutating effects while adapters can mutate.
Recommended mapping and acceptance
| RDF set | Proposed class | IRI pattern |
|---|---|---|
operation, workflow | module object kind and nested manifest form | /domain/module-object/operation, /domain/module-object/operation/workflow |
| 31 operation slots | manifest object field | /domain/module-object-field/operation/<owner>/<field> |
| five runtime shapes | runtime/manifest schema type | /domain/runtime-type/operation/<name> |
| nine effect kinds | existing EffectKind | retain /domain/effect/<name> |
| ten invariants | existing Invariant | retain IRI; relink invariantOf |
The exact class names should follow the pending RFC-0040/0041 module-object ontology decision. Update RDF source, ontology, Lean identities, generated Turtle, and SPARQL consumers together. Verify each field IRI identifies one owner slot, each invariant target exists with the intended class, and all nine effect kinds remain distinct. Nothing is deployed, so no RDF consumer migration is required for the first release.