compile-3d-workflow

Compile 3D workflow

Contract

Field	Bound contract
Trigger	The user asks for direction and a compilable 3D workflow from an interview.
Authority	Reversible local: writes only the named local 3D workflow artifact file; rollback is deleting that file. No remote mutation.
Side effect	Writes one local 3D workflow artifact file.
Done	A validated local 3D workflow artifact file exists and passes every structural check.

Inputs

• A direction interview with the user, supplying: the problem being solved, what success looks like, binding constraints, and what is explicitly out of scope. All four required; none inferred.
• The output file path for the workflow artifact. Required.

Artifact schema

The workflow artifact is a YAML file with this structure:

problem: <string>
success_criteria: <string>
constraints: [<string>, ...]
out_of_scope: [<string>, ...]
topology:
  nodes:
    - id: <string>
      task: <string>
      depends_on: [<node_id>, ...]
ontology:
  groups:
    - name: <string>
      members: [<node_id>, ...]
feedback_loops:
  - name: <string>
    sensor: <string>
    comparator: <string>
    actuator: <string>

Every node id referenced in depends_on must exist in nodes. Every node id in ontology group members must exist in nodes. Every feedback loop must name a sensor, comparator, and actuator as non-empty strings.

Procedure

1. Conduct the direction interview. Ask the user for the problem, success criteria, binding constraints, and explicit out-of-scope. Record the answers verbatim. Done when: all four interview inputs are recorded verbatim, or the missing input is named and the skill stops.
2. Author the workflow artifact from the interview answers. Build the three dimensions:
   • Topology: a DAG of tasks. Each node has an id, a task description, and a depends_on list naming the node ids it waits on. No cycles. No node depends on itself. Every depends_on entry must reference an existing node id.
   • Ontology groups: named concept clusters classifying the work domains. Each group names its member node ids. Every group is non-empty. Every member must exist in the topology.
   • Feedback loops: cybernetic control cycles. Each loop names its sensor (what is measured), comparator (what is expected), and actuator (what action re-routes). All three are non-empty strings. Done when: the artifact combines all three dimensions from the interview answers.
3. Validate the artifact against the schema. Check every rule:
   • Every node has a unique id and a non-empty task.
   • Every depends_on entry references an existing node id.
   • No cycle exists in the dependency graph (topological sort succeeds).
   • Every ontology group is non-empty and every member references an existing node id.
   • Every feedback loop names a non-empty sensor, comparator, and actuator. Done when: every check passes, or the specific defect is named and the skill stops.
4. Write the validated artifact to the output file path as YAML. State the rollback path: delete the local artifact file. No remote state was touched. Done when: the artifact file is written and the rollback path is stated.