A recording-to-Agent compiler for vertical AI implementation teams
Turn a screen recording into a validated workflow model.
Workflow Corp reconstructs one demonstrated task as a typed, target-neutral WorkflowModel v2. It verifies the exact operations, inputs, labels, checks, prohibitions, finish conditions, and source evidence—then deterministically compiles one copy-ready Coco draft.
ACTIVE TARGET Coco · one explicit binding · no model after validation
Open ledger.example.test/workspaces
Select workspace Northwind Demo
Export allocation-accounts.csv
Do not invent an allocation value.
9 immutable evidence atoms · exact literals retained
- OpenUrl
- ledger web application
- SelectWorkspace
- “Northwind Demo”
- NavigateMenu
- Accounting / Chart of accounts
- ExportFile
- → exported account list
- Verify
- file_downloaded
- UseAllowedValuesSource
- → allowed allocation values
- Success
- exists(allowed allocation values)
- Evidence → IR
- PASS
- Static workflow
- PASS
- Coco target binding
- PASS
- Source faithfulness
- PASS
Compiled draft ≠ accepted Agent. The exact build must still pass in Coco.
- Recording evidence
- Atomic ledger
- WorkflowModel v2
- Static validation
- Coco lowering
The model is the source. Coco Markdown is one compiled target artifact.
The canonical representation
The workflow model is the product.
A transcript is evidence. A prompt is an output format. WorkflowModel v2 is the reusable program in between: one typed source of truth for what the Agent may do, what it must verify, and how it can finish.
- 01 Actors + authority
- Separates the runtime Agent, human operator, external parties, and the effects each is allowed to cause.
- 02 Resources + bindings
- Names logical applications and files while preserving exact URLs, workspaces, labels, and filenames.
- 03 Values + operations
- Tracks required inputs, produced intermediate values, final outputs, and the typed operations connecting them.
- 04 Verification + outcomes
- Expresses what must be checked and the explicit success, stop, or failure condition for the workflow.
- 05 Prohibited effects
- Stores “must not” behavior structurally so a renderer cannot casually omit it from the target artifact.
- 06 Evidence provenance
- Links every material semantic element back to immutable recording or supporting-file evidence.
A real compiler boundary
Inference proposes the workflow. Compilation starts after it validates.
Workflow Corp keeps probabilistic reconstruction on one side of a hard gate. Coco binding, lowering, and Markdown rendering on the other side are deterministic functions of the approved workflow model.
PROBABILISTIC
- 01 Normalize evidence Exact actions, literals, checks, files, and outcomes
- 02 Build the atomic ledger One disposition for every material evidence atom
- 03 Synthesize WorkflowModel v2 One target-neutral semantic program
DETERMINISTIC
- 04 Bind to Coco Map typed resources and operations to declared capabilities
- 05 Lower + render Produce the same Coco document from the same valid model
- 06 Verify source faithfulness Trace evidence → IR → document → exact Markdown
Compiler guarantees
Plausible prose is not a successful build.
The compiler fails closed when it cannot prove the workflow. A clean-sounding draft never outranks missing evidence, invalid value flow, unsupported behavior, or a lost prohibition.
-
01
Trace every claim
Every material fact is mapped, explicitly non-material, or rejected with a diagnostic.
-
02
Preserve exact literals
URLs, workspace names, menu labels, controls, and filenames remain byte-for-byte accountable.
-
03
Prove the program
References, authority, value flow, required outputs, and terminal states must validate before lowering.
-
04
Publish atomically
A failed attempt cannot reuse an older file set or advance the one current compiled-draft pointer.
One explicit target
Built for Coco, explicitly.
Workflow Corp does not pretend one generic prompt works everywhere. The active compiler binds WorkflowModel v2 to Coco’s declared capabilities and emits one immutable, copy-ready Markdown artifact.
Available today: coco-target-v1
Target-neutral semantics, provenance, values, verification, and prohibitions.
Copy-ready Coco instructions derived from—and traceable to—the validated model.
The runtime boundary
Compiled does not mean accepted.
Start from demonstrated work
Compile one workflow—not another plausible prompt.
Upload one focused recording, optional supporting files, and optional guidance. Workflow Corp will either publish one validated Coco draft or stop with a concrete diagnostic.
Compile one workflowQuestions buyers ask
The important boundaries.
What is WorkflowModel v2?
It is Workflow Corp’s sole canonical workflow IR: a typed, target-neutral representation of actors, authority, resources, values, operations, verification, outcomes, prohibitions, and evidence provenance.
Is the output just a prompt or SKILL.md file?
No. The workflow model is the canonical semantic source. The customer receives one deterministic, copy-ready Coco Markdown artifact compiled from that validated model.
Does Workflow Corp support every runtime?
No. The active target is Coco. There is no generic runtime selector or fallback writer pretending the same free-form prompt is valid everywhere.
What happens when the recording is ambiguous?
The run fails closed with a stable diagnostic. Ambiguous evidence, unsupported control flow, unbound resources, missing outputs, or failed source-faithfulness checks publish no draft.
When does a draft become an Agent?
Only after that exact compiled-draft ID and manifest digest pass execution in Coco. Editing or rebuilding the artifact creates a new version that must pass again.