Welcome to Z.E.N.

Think of this system as an invisible kitchen manager. It doesn't cook the food itself, but it hands out the recipes, tells the cooks when to start, watches the clock, and makes sure the appetizers go out before the main course.

The recipes are workflows: short text files where you write down a piece of work you keep doing by hand. The morning brief you stitch together from Slack and Notion. The weekly client update. The deep research pull you run every time a new product idea lands. Once a workflow exists, anything can fire it: you, a schedule on the wall, or an AI agent that knows the recipe by name.

To understand how it works, you only need to know six basic ideas. They're on the next page; it's a two-minute read.

What a workflow looks like

name: morning-brief
description: Summarize what's new in Slack and Notion since yesterday.

nodes:
  - id: pull-slack
    type: prompt
    prompt: |
      Summarize unread messages from #team and #leadership since yesterday 6pm.
      Quote anyone who tagged me.

  - id: pull-notion
    type: prompt
    prompt: |
      Find pages edited in the last 24 hours under Strategy and Product.
      Return titles plus a one-line summary each.

  - id: combine
    type: prompt
    depends_on: [pull-slack, pull-notion]
    prompt: |
      Combine the Slack summary and the Notion edits into a single brief.
      Headline at top, sections below.

That's the entire shape of a workflow. Three steps, two run in parallel, one waits to combine them. You can write it yourself, copy a bundled one, or describe it in English and let the builder write it for you.

The model is not baked in

You choose a different brain for each step, not for the whole recipe. A careful brain for the writing step, a fast cheap brain for the cleanup step, a coding brain for the bash step. If a better model lands tomorrow, you swap it in by changing one word.

Z.E.N. also runs anywhere. Your laptop. A cloud box. A small server in a closet. It is the layer that stays still while the rest of the stack moves.

Who Z.E.N. is for

You probably already spend two hours a day in Claude, ChatGPT, Hermes, OpenClaw, or Claude Code. You're fluent in slash commands. You know which model handles which task. You build prompt scaffolds in Notion or a private repo. You ship words, research, decks, campaigns, content. You don't ship pull requests.

Z.E.N. is built for that user. The audience this product expects is sophisticated about AI and unbothered by keyboard-first interfaces; the audience this product does not expect is someone who needs a tour of what a model is.

Engineers use Z.E.N. too. The coding workflows live under an Advanced tab, the way any product tucks its power-user surface a click away from the default view.

What Z.E.N. is not

Z.E.N. is not a chat UI. It has one (the Web UI), and you'll use it when you want to fire a workflow without typing a command, but the chat is a surface, not the product.

Z.E.N. is not a replacement for your favorite agent. Claude Code stays Claude Code. Hermes stays Hermes. Z.E.N. sits behind them and runs the structured work they're not built to handle.

Z.E.N. is not a no-code platform. There's no canvas with boxes and lines. Workflows are short YAML files. You can write them by hand, generate them from a description, or copy one from the bundled set. If "YAML" sounds like a problem, the workflow builder will write it for you; you'll never need to read it.

Next

• Concepts for the six basic ideas, in plain English.
• How it works to see the example above run end to end.
• Install when you want to skip the explanation and try it.