IDY-007A Workflow Vocabulary and Node Binding Contract

Contract identifier: IDY-007A-WORKFLOW-NODES-V2

Status: IMPLEMENTED AMENDMENT

IDY-007A registers the addressable Workflow Definition Type and Workflow Node Type in the existing generic object vocabulary. It does not create a workflow-specific persistence system, operation or table.

Stable Types

The existing Workflow Definition Type remains 9a4f6b8c-3d2e-4f10-8a11-223344556692. The independently addressable Workflow Node Type is 9a4f6b8c-3d2e-4f10-8a11-223344556695; ...693 and ...694 are already assigned to Workflow Execution and authority binding. Both are Business-scoped ordinary Objects with retained generic revisions.

A Workflow Node value retains the existing five-kind grammar:

• `condition`
• `wait_for_event`
• `request_approval`
• `local_command`
• `end`

The node_id inside a Node value is a readable graph label. It is not the Object identity.

Definition Revision Binding

A Workflow Definition revision contains node_bindings, a complete list of unique objects with:

• `node_id`: the UUIDv4 address of a Workflow Node Object;
• `node_revision`: the exact retained generic Object revision to use.

entry_node_id is the UUIDv4 address of exactly one member of node_bindings. The Definition revision is invalid unless every binding resolves to the Workflow Node Type, the requested revision exists, and the Node belongs to the Definition Business.

Node configuration is authoritative only in the independently stored Node revision. A Definition does not embed a second Node configuration. A later Node revision cannot change an existing Definition revision or an execution pinned to it.

Graph Validation

The validator resolves each exact binding before validating the existing Node grammar. Continuation and branch labels are resolved only against labels in the complete bound set. Missing, duplicate, cross-Business or unbound targets fail closed. Existing active-definition reachability, incoming-edge, expression, dependency-reference and size limits remain unchanged.

Runtime and Evidence

007B continues to pin the exact Workflow Definition object revision. Runtime resolution is:

Workflow Execution -> pinned Definition revision -> exact Node binding -> exact Node revision

007C step evidence records the stable Node Object identity and exact Node revision in addition to the pinned Workflow Definition identity/revision, execution identity and Step Attempt identity. Generic Object history and provenance remain the sole historical evidence mechanisms.

The former embedded nodes shape is not accepted by the registered authoritative Definition Type. Repository-free legacy validator fixtures may retain the old grammar only as a test compatibility path; no persisted production Definition may use it.