PERSISTENT MULTI-AGENT WORK

Agents diverge.Truth must hold.

Flowness means keeping serious work in motion after any one AI session ends. It gives the work a durable identity, records what changed, blocks stale interpretations from becoming shared truth, and separates a producer's “done” from real-world acceptance. Its public evidence is scoped: runnable mechanisms and dogfood do not yet establish a comparative benchmark or broad production guarantee.

See the failureRead the architecture ↗

The distinction that matters

Different local views are expected. A stale or incompatible interpretation becoming shared history is the safety failure.

View divergence is normal. Materialized drift is not.

Flowness does not require every agent to hold the same view at every moment. It narrows the problem to what may enter persistent history.

VIEW DIVERGENCE

Local views differ

Agents read different slices at different times. Temporary disagreement is a normal property of asynchronous work.

Expected condition
MATERIALIZED DRIFT

Drift enters committed history

A stale or incompatible interpretation becomes an Event and shapes what later agents do. This is the failure Flowness seeks to block.

Safety target

COMMIT GATE

Do not trust a writer's description. Check the write.

A proposed change first becomes an Envelope. The Gate checks scope, identity, freshness, conflicts, and obligations before it commits, rejects, or escalates.

01

Identity

Envelope and event identities are bound and checkable

02

Declared scope

The write stays inside its stated authority and object scope

03

Patch coverage

The declared read and write set covers the actual change

04

Freshness

The interpretation and dependencies still match the current version

05

Write conflict

Concurrent writes cannot overwrite one another silently

06

Global novelty

A superseding interpretation adds checkable information

07

Mechanical duties

Blocking obligations run before a write can commit

Trustworthy work needs four kinds of truth.

Events preserve what committed, Context Capsules bound what may be used now, Findings retain counterexamples, and Acceptance connects output to the target world.

EVENT TRUTH

What has committed

Events, identities, versions, causal history, and projections keep work outside any temporary session.

CONTEXT CAPSULE

The local world for this action

A compiled view binds authoritative facts to one cutoff and preserves Unknown as unknown.

FINDING LINEAGE

Counterexamples that survive success stories

Independent review records each finding with a source, object, version, and required disposition.

REALITY AND ACCEPTANCE

Whether the target world accepted the result

Built, Integrated, Activated, and Accepted are separate states that require different evidence.

Six roles compose through events, not remembered chat.

Each role reads the events it needs and submits its output through the same boundary. Shared history carries the collaboration.

  1. 01
    Interview

    Receive external intent

    Turn a requester's words into a traceable brief without inventing certainty on their behalf.

  2. 02
    Consensus

    Version the interpretation

    Create or supersede Concepts while preserving the causal history behind the current meaning.

  3. 03
    Planner

    Compile obligations into work

    Read current concepts and constraints, then derive tasks with explicit completion conditions.

  4. 04
    Execution

    Write inside declared scope

    Perform bounded work and send every proposed write through an Envelope and the Commit Gate.

  5. 05
    Review

    Search for counterexamples

    Remain independent from production and preserve each finding with an object, source, and lineage.

  6. 06
    Fix

    Repair the affected slice

    Respond to findings with targeted rework, replanning, or escalation to the appropriate authority.

Six roles describe a protocol split, not a requirement for six permanent agents. Implementations may combine roles only when their independence and authority boundaries remain intact.

FLOWNESS AND TOWOW

One problem space. Two independent research lines.

ToWow

How agents form relationships across trust boundaries

ToWow studies discovery, Principals, authority, proposals, commitments, actions, and how a relationship evolves.

Flowness

How established work preserves meaning and evidence

Flowness studies persistent state, interpretation versions, compiled context, review, repair, and target-side acceptance.

Flowness offers Harness mechanisms that a ToWow deployment could compose with. This is a research and architecture direction, not evidence of a current product integration or complete shared runtime.

EVIDENCE BOUNDARY

What the public record supports, and what remains open.

Evidence reviewed on 19 August 2026. The public Assurance Kernel, wider mechanism surface, and research program carry different evidence states.

Supported today

  • The deterministic Open Alpha Assurance Kernel is documented as RUNNABLE for a narrow review, rework, and fresh-verdict path for a successor candidate. That verdict is not target-domain Effect or responsible-party acceptance.
  • Append-only events, projections, Context Capsules, Envelopes, gates, and selected runtime mechanisms are publicly INSPECTABLE.
  • The English whitepaper, architecture set, claims register, FlowBench specification, and source are public.

Open or not established

  • FlowBench v0.1 is marked DESIGNED. No frozen comparative result establishes superiority, lower cost, or lower human load.
  • A complete organic public goal reaching accepted outcome remains an OPEN QUESTION.
  • A general cross-domain Flow runtime and completed mechanical verification are not established by the current artifacts.

A repository is not runtime proof

Code, papers, tests, or install artifacts do not by themselves prove that a service is online, an organic field path is active, or a target environment has accepted the result. Each claim needs its own readback.

Continue from primary sources.

This page follows the public repository's evidence vocabulary. Check the linked version when the material changes.

  1. 01Flowness READMECurrent Open Alpha status, runnable proof, mechanism map, and explicit limits.
  2. 02Flowness ArchitecturePersistent Work, Human Constitution, five runtime layers, and reality boundaries.
  3. 03Flow Engineering WhitepaperThe English position paper, ontology, evidence states, and open research questions.
  4. 04Claims and Evidence RegisterWhat is runnable, inspectable, designed, dogfood evidence, or still an open question.
  5. 05FlowBench SpecificationA designed qualification method, not a published comparative benchmark result.

Related ToWow guides

Research and public evidence hubRead and verify the public paper packageRead ToWow NotesExplore ToWow conceptsTrusted and untrusted agent collaborationRead the Agent-to-Agent Harness guideCompare A2A, MCP, runtimes, and harnessesRead the multi-agent verification method