gnomonlearn
Docs/RFC-0022 workflow domain model proposal

RFC-0022 workflow 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: Runtime, AI, and specification maintainers.

Source evidence

RFC-0022 defines one named declaration kind, workflow. The step, parallel, if, repeat, and gate forms are syntax inside that declaration (§3.1), not independently declared kinds. The projection nevertheless types five nested forms as DeclarationKind and gives them Composition kind classes.

Section 7 defines eleven workflow.* names as structured event-log events. The projection types them as EffectKind. An event produced by execution is not a user-authored effect declaration. RFC-0010 owns the event log contract.

The grammar names condition-expr, error-policy, and trigger-decl; §§4–5 discuss workflow state and variables. It does not declare ConditionExpr, ErrorPolicy, TriggerDecl, WorkflowState, or WorkflowVariable as named Gnomon data types. The projection’s DataType and FQN assertions therefore add identities not present in the authored DSL. The same concepts may be useful as structured ontology nodes, but their class and names must say that.

  1. Keep declaration/workflow as the sole declaration kind. Model the five nested syntax forms as workflow coordination constructs with an ontology class that does not assert top-level declaration status. Define the class and ownership in the domain ontology before changing their RDF types.
  2. Model the eleven workflow.* names as event kinds emitted to the RFC-0010 log. Define or reuse an event-kind class and preserve the event names as literal identifiers. Do not treat them as effect declarations.
  3. Model grammar and runtime concepts as syntax forms or conceptual types, with provenance to the exact RFC sections. Do not publish invented Gnomon FQNs unless a future RFC declares them. Audit existing RDF consumers before changing classes or IRIs.

Acceptance checks

  • Reconcile the authored RFC, Lean catalog, domain ontology, source-domain projection, and generated Turtle in one reviewable change.
  • Query RDF for exactly one RFC-0022 declaration kind, eleven event kinds, and five coordination constructs with no declaration-kind class.
  • Verify consumer queries that select DeclarationKind, EffectKind, and DataType, including site output. Run the projection drift and semantic review gates, then rebind source hashes for changed nodes.

No RDF triples are changed by this proposal.