gnomonlearn
Docs/RFC-0024 I/O domain model proposal

RFC-0024 I/O domain model 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. Owner: IO Runtime, Module Platform, and specification maintainers.

Evidence

The domain ontology defines DeclarationKind as a top-level declaration, Operation as a kind in the algebra, EffectKind as a typed pipeline step, and DataType as a Gnomon type-model member. RFC-0024 §3 defines operation only inside a client; it has no independent top-level declaration syntax. The projection nevertheless types it as DeclarationKind. The projected adapter.call effect is not defined by the authored RFC. adapter.resolve and openapi are adapter functions, not algebra operation kinds.

RFC-0024 §5 cites action, actuator, and saga from RFC-0008; §8 delegates the HTTP, gRPC, GraphQL, and OpenAPI module contracts to RFC-0025–0028. The projection assigns these seven borrowed identities definedIn RFC-0024. Their cited ownership should remain with the defining RFC, while RFC-0024 may reference them.

The projected DataType nodes include TypeScript adapter interfaces, compiler tokens, grammar alternatives, a JSON lockfile, and two types used only as examples. These are not named Gnomon value types in §3 or §6. The adapter interfaces cross the compiler-to-adapter stage boundary. For an implementable first-release contract, define their serialized interchange and lockfile snapshot using protobuf messages, then specify language bindings and cache semantics. The current JSON lock entry records only operation names and count, so it cannot reconstruct typed operations offline; see RFC0031_GRAPHQL_PROPOSAL.md.

  1. Model the nested operation as a SyntaxForm owned by RFC-0024, with client remaining the top-level declaration. Model adapter functions as compiler integration functions, not algebra operations. Remove the unsupported adapter.call effect unless the RFC defines a typed effect.
  2. Make RFC-0008 and RFC-0025–0028 the definedIn owners of cited kinds and modules. Use references links from RFC-0024 concepts where useful.
  3. Replace invented DataType assertions with appropriate syntax, compiler, file, or adapter-contract classes. Keep Text under its defining type RFC and HTTPMethod under the HTTP binding RFC. Define protobuf messages for serialized adapter results and the pinned generated-schema snapshot before claiming portable cross-stage interchange.

Acceptance checks

  • Reconcile RFC-0024, the defining RFCs, Lean catalogs, ontology, authored domain facts, emitted Turtle, and site reference output in one review.
  • Query the RDF for a single top-level client kind, nested operation syntax, source-owned modules, and no adapter method under the algebra Operation class. Check exact IRI, class, and owner changes with affected consumers.
  • Compile and type-check a hand-authored client and a spec-backed client from a pinned, complete adapter snapshot without network access. Reject a missing or mismatched snapshot deterministically.
  • Run projection drift, domain identity, semantic review, and consumer query gates. Rebind review hashes after authored source changes.

No RDF triples or adapter runtime behavior change in this review.