enocone
Business flows, written down

The spec your team reviews is the test that runs.

enocone flows are plain documents: why a journey matters, the rules, and the steps in sentences anyone can read. AI fills in the steps, the flow runs against your app, and its chart turns green as the steps pass.

Draft→ Review→ Approved→ Implemented

Open source · MIT or Apache-2.0 · run your own with enocone serve

Sign in

Your team's flows

Continue with GitHub
or, without a GitHub account

Projects are private. Only people a project owner invites, or members of a GitHub team it's shared with, can sign in.

One document

A flow reads like a page, not like code

Product owners, testers and developers read the same thing: the outcome as a title, why it matters, the rules, then numbered steps. The blocks that make it run sit underneath, folded away.

This one is from enocone's own suite: enocone is specified and tested with enocone.

Hosted siteImplemented · 7 of 7 passed

A run is published to enoc.one from a laptop or from CI

A report on someone's laptop or buried in CI artifacts is hard to discuss. enocone publish sends a run to the team's site, where everyone sees the same pages.

Flow chart
enocone login enocone publish CI with publish: true Run on the project page
  1. ✓Priya is a member of shop and has run enocone login
  2. ✓Priya runs the prototype and publishes it
  3. ✓The CI workflow for acme/shop runs with publish: true
  4. ✓An upload containing an HTML file is refused
From idea to green

Agree on behaviour first. Then build it.

DraftSentences and mockupsSteps in plain words, screens drawn in your product's own style, a storyboard of how one leads to the next.
ReviewComments in the marginThe team clicks through the prototype and comments beside the rule or step they mean.
ApprovedSigned off in gitstage: approved and approved_by in the flow file, reviewed like any other change.
ImplementedEvery step runsBrowser, HTTP, email and command steps check the real app. The chart goes green step by step.
Designed
/login
Continue with GitHub
Email me a sign-in link
Built · passed
enoc.one/login
Welcome
Continue with GitHub
Email me a sign-in link
Designed, then built

The mockup you agreed, beside the real screen

After a passing run, each step shows the screenshot next to the mockup that was signed off. Anyone can see whether they match, without opening the app.

Before the feature exists, the same browser steps run against the clickable prototype.

Review together

Comments stay beside the words they're about

Quote a rule, ask a question, reply. When the flow changes, a comment on text that's gone is marked outdated, still readable. People without GitHub sign in with a one-time email link.

RulesThe link in the quote email expires after 30 days.
SSam reviewer · RulesOutdated
expires after 14 days

14 days is too short for conveyancing; clients often wait for a mortgage offer.

PPriya Agreed, I'll make it 30 days.
Run anywhere, read in one place

From a laptop or CI, every run lands here

A run sends its results and screenshots, never HTML; the site draws every page itself. In GitHub Actions there's no secret to store: GitHub vouches for the workflow.

$ enocone run
enocone · env: local
  ✓ A flow chart in the document turns green as its steps pass
  ✓ Teammates sign in with GitHub or a one-time email link
  ✓ Reviewers comment beside a draft flow
  ✓ A run is published to enoc.one from a laptop or from CI
  … 9 more

13 passed   0 failed   0 pending

$ enocone publish
published 13 flows and 26 screenshots
https://enoc.one/enocone/runs/1/
# .github/workflows/e2e.yml
permissions:
  contents: read
  id-token: write   # GitHub vouches; no secret

steps:
  - uses: actions/checkout@v4
  - uses: driftwerk/enocone@v0
    with:
      project: e2e
      publish: true
Step kinds
6
browser, http, email, exec…
Secrets stored for CI
0
GitHub vouches (OIDC)
Runs kept
30
days; flows and comments stay
HTML uploaded
0
the site draws every page
Get started

Three steps, then ask your AI tool

enocone's MCP server teaches Claude Code, Cursor or any MCP client the flow format, lets it explore your app, and run and publish what it writes.

1Install
On macOS or Linux, with Homebrew. Then download Chromium for browser steps. 
$ brew tap driftwerk/tap
$ brew install enocone
$ enocone install-browsers
2Connect your project
In your repository: enocone.toml, a CI workflow that publishes here, and .mcp.json for your AI tool. 
$ enocone init --name shop \
    --hub https://enoc.one
$ enocone login
3Ask for flows
Open your AI tool in the project. It drafts flows for people to review here, then implements them once approved. 
# in Claude Code or Cursor
"Design flows for the checkout
 feature, with mockups"

The full guide: enocone on GitHub. Create the project here and link it to your GitHub repository so CI publishes without a secret.

Open source

Rather keep flows on your own server? One command.

enocone serve is everything this site runs: one binary, one data folder, Caddy in front for HTTPS.

$ ENOCONE_PUBLIC_URL=https://flows.example.com \
  ENOCONE_OWNER_EMAIL=you@example.com \
  enocone serve

Bring your team's flows here

Sign in, create a project, invite people by email, GitHub handle or team.

Continue with GitHub Sign in with email
enoc.one · enocone reads the same both ways GitHubDocsSelf-host guide