RFC-0043 manifest field ownership review
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 classification complete for 31 Field nodes; ontology corrections remain proposed. Owners: Compiler, Graph Runtime, RDF ontology. No RDF classes or normative source facts changed.
Authoritative boundary
RFC-0043 §1 distinguishes .gnm procedure source from operation objects in
module manifests. §3 specifies the manifest object; §9.1 validates and registers
it; §11.2 lowers procedure syntax to that object. RFC-0049 additionally lowers
query and mutation syntax to operation transport records. Thus a lexical
field/operation/* prefix is insufficient evidence of a grammar slot.
The framework model at
graph/packages/graph-module-model/model/objects/operation.ts uses existing
Zod schemas for this serialized record. This is an established schema-layer
exception to the global proto default; no replacement DTO is introduced here.
Schema presence alone does not prove execution conformance.
Classification of all authored fields
All following IRIs have prefix https://gnomon.sh/domain/field/.
| Family | Suffixes | Count | Canonical semantic owner |
|---|---|---|---|
| operation | authorization, conflictPolicy, description, effects, errorCatalogRef, guards, idempotency, inputSchemaRef, maxPayloadBytes, outputSchemaRef, tenantBoundaryRef, timeoutMs, transport, version, workflow | 15 | Module-manifest operation record (§3) |
| authorization | policy, requiresAuth, requiresPermissions, requiresRoles | 4 | Nested operation authorization record (§4) |
| effect | key, kind, with | 3 | Effect-pipeline step record (§5) |
| guard | errorCode, message, when | 3 | Guard record (§7.1) |
| idempotency | keyRef, requiredKey | 2 | Operation idempotency record (§6) |
| workflow | initialState, states, terminalStates, transitions | 4 | Nested workflow record (§8) |
These 31 nodes describe serialized manifest fields. They should not be swept into a DeclarationSlot class when repairing RFC-0049’s grammar-slot identities. The corpus candidate inventory includes only 19 of these nodes (operation and workflow families), because its lexical filter does not capture every nested record family. It is therefore neither an exhaustive field inventory nor an ontology migration list.
Concrete ontology direction
Keep syntax-slot ownership separate from record-field ownership. For these nodes, introduce or reuse a serialized record concept only after defining its class and class-safe field relation. Do not attach hasField to the operation DeclarationKind: its current ontology domain infers NamedDeclaration. Likewise do not create fake named language types solely to own nested blocks.
Preserve existing IRIs unless a collision proves that one IRI denotes multiple concepts. Record any class change, regenerate projections, and check reasoner inferences and consumers before publishing. An explicit RecordSchema class and hasRecordField relation may be appropriate, but requires a corpus-wide proposal covering existing runtime/artifact schema classes and their properties.
Implementation gap observed during classification
The inherited framework effect schema includes additional effect kinds beyond RFC-0043 §5’s nine-kind catalog. Its template.compose comment describes a best-effort post-commit effect, while this RFC’s request-handling contract says pipeline execution occurs in one transaction. This is static source evidence of a potential implementation/contract discrepancy, not a runtime result. A focused execution audit must distinguish schema extensions, transactional writes, and deferred external effects before claiming full RFC-0043 support.
Acceptance
- Use this classification to exclude these 31 manifest-field nodes from a grammar-slot rewrite.
- Inventory field ownership across runtime, artifact, and syntax boundaries.
- Prepare exact ontology classes/properties and reasoner consequences for owner review before changing published semantics.
- Trace each manifest schema and effect executor to the RFC; exercise rollback and post-commit failure behavior to resolve the observed transaction gap.
The template transaction repair proposal now traces normalization and dispatch, confirms that failures are swallowed in the post-commit phase, and specifies the exact transactional repair and backend acceptance tests. The runtime discrepancy remains unresolved pending the owner decision and implementation verification.