Flowness

Work persists. Agents assemble.

Flowness is a work-centered runtime for agentic software engineering.

It keeps engineering work alive across changing agents, sessions, contexts, and plans, then compiles the next execution from the current state of the world.

Humans define the goals, rules, judgments, and irreversible boundaries. Agents organize and act within them.

Flow is primary. Work gives it an address. Agents are temporary forms of execution.

A session may end. The work keeps its name, its history, and its next question.

简体中文 · Run the public proof · Flow Engineering · Architecture · Failure Atlas

Public status: today’s Open Alpha ships a runnable, deterministic Assurance Kernel for execution → independent review → targeted rework → fresh acceptance. The broader work-centered Flow runtime is present as a substantial inspectable mechanism set and private dogfood system, but its new public hero demo and a complete organic public end-to-end run are not shipped yet. See What is actually available.

---

The next unit of software engineering is not the session

Interactive coding agents are getting stronger. The bottleneck is moving.

A serious engineering task may outlive:

• the agent that started it;
• the context window that explained it;
• the first plan that organized it;
• the graph that routed it;
• the pull request that materialized one part of it.

Most agent systems still organize around one of those temporary containers. Flowness organizes around the flow.

session-centered:  choose and supervise the next agent session

graph-centered:    choose the next node or transition

flow-centered:     read the work's current state,
                   determine what it now needs,
                   and assemble the next execution around it

Agent does not own the flow. The flow temporarily assembles an agent.

---

From Harness to Flow

These engineering ideas are not competitors. They expand the object being engineered.

Engineering focus	What it makes explicit
Prompt Engineering	The instruction given to a model
Context Engineering	The local world the model can see now
Harness Engineering	The environment, tools, rules, and feedback that let one agent act
Loop Engineering	How action observes, corrects, retries, and improves over time
Graph Engineering	How multiple execution units connect, branch, merge, and coordinate
Flow Engineering	How work itself moves through changing execution structures and keeps finding a valid next step

A useful shorthand:

A loop is one execution unit unfolding through time.
A graph is many execution units organized in space.
A flow is work moving through a succession of graphs—and sometimes changing the graph itself.

Read the full concept

---

The 30-second runtime model