Design · Route · Enforce

Every process bottlenecks
at a document.

FormWorkbench is the engineering platform for document-driven processes. Define multi-party documents in code. Compose them into processes. Close the loop automatically.

What is a business process? It's documents.

Strip away the software. Every process is a human filling out a structured document, routing it to the next person, and waiting for them to fill out theirs.

Employee Onboarding

I-9 → W-4 → Direct Deposit → Handbook. Four documents, three parties, one deadline.

Compliance Renewal

A form with an expiration date and a rule that fires when it lapses.

Approval

A form with a signature field and a section that depends on the previous.

Audit

Historical document instances queried over time. "Show me every W-4 filed in Q1."

You're using five tools to solve one problem.

A form builder that doesn't understand process. A process tool that doesn't understand documents. An approval system. A compliance tracker. A document manager. They're all the same thing.

What you have todayWhat it actually is
Google Forms / TypeformForm without process
Zapier / Power AutomateProcess without documents
DocuSign / Adobe SignForm with one field (signature)
JIRA / ServiceNowTask tracker without form context
Compliance spreadsheetRules without enforcement

FormWorkbench unifies all five. One primitive. One DSL. One runtime.

Code-first form engineering

Define documents, compose processes, and enforce rules from the canonical Lisp source the runtime actually deploys.

Forms with parties and dependencies

Define multi-section documents with assignees, conditional fields, and section sequencing. Each section depends on the previous — the employer can't review until the employee submits.

A workbench, not a document builder.

Document builders generate HTML. FormWorkbench engineers processes.

1

Design

Multi-party documents in canonical Lisp. Sections, assignees, conditional fields, signatures, and locales.

2

Compose

Chain documents into DAG processes with parallel branches, wait nodes, and guards.

3

Route

Assign sections by role. Set deadlines. Send magic links to external parties.

4

Test

Query submissions with Datalog. Time travel to any point. Audit trails built in.

5

Deploy

Node.js or Cloudflare. SQLite storage. Multi-tenant by default.

Built on primitives that compose.

Document is the center. Everything else orbits it.

Document

Entity

Long-lived identity across systems

Fact

Immutable, timestamped assertion

Rule

Declarative Datalog constraint

Violation

First-class, queryable divergence

Task

Auto-routed remediation work

Action

Parameterized state mutation

Triples

[entity, attribute, value]

Append-only. Time travel. Schema-flexible.

Datalog

find → where → compile → SQL

Pattern matching. Recursive CTEs. Compiles to SQL.

Effect-TS

yield* Effect.gen()

Type-safe async. Composable layers. Dependency injection.

Built for teams that own processes.

If you manage compliance, run operations, or build the platform underneath.

Compliance Officers

Regulatory documents, deadlines, multi-party signatures, audit trails. Define rules that fire when certifications lapse. Query every submission historically.

HR Operations

Onboarding flows, recurring certifications, approval routing. Compose multi-form processes with parallel branches and deadline enforcement.

Platform Engineers

Multi-tenancy, auth, time travel, query engine, deploy targets. SQLite storage, Cloudflare or Node.js, Effect-TS throughout.

Stop building documents. Start engineering them.

Your processes are too important for drag-and-drop.