polystrate

polystrate is the set of tools flower is built on.

The tools give coding agents a shared memory of their sessions, briefs to plan the work, builds in throwaway containers, review and checks before a change lands, and deploys. flower is the first thing built on them: one arrangement of the tools, with a web UI for the person running it.

What is in polystrate today.

Provenance: every brief is linked to the sessions, builds, reviews, checks, decisions and deploys around it, and to earlier work on the same topic. An agent picking up a brief reaches all of that in one tool call, and a deployed commit can be followed back to why it exists.

The records below are real: they are brief #7404 in flower, a change to this site, followed from the brief to the deploy.

  • Deploys: a change that passed lands on the project's branch, ships to the branch the project deploys from, and deploys. Checks you define then run against the live site.

    1. land #6604, merged. By: flower, automatically. Time: . Attempt: 1. Commit: aa459242.
    2. ship #201, delivered. By: lead agent. Approved by: a person. Their answer: “go”. Time: . Commit: aa459242.
    3. deploy #192, succeeded. By: lead agent. Time: . Duration: 28 s. Steps: 7. Environment: production. Commit: aa459242.
    4. live site check, passed. By: flower, automatically. Time: . Duration: 0.6 s.

  • Review and checks: a reviewing agent reads the change and passes it or asks for changes. The project's own checks run on the build's branch, and again on the merged result before it lands.

    1. checks #11310, passed. Kind: checks on the branch. By: flower, automatically. Time: . Duration: 41 s. Steps: 5.
    2. review #16563, passed. By: reviewing agent. Reviewer: from a different model family than the builder. Time: .
    3. review session. By: reviewing agent. Time: .
    4. review passed. By: reviewing agent. Time: .
    5. checks #7467, passed. Kind: checks before landing. By: flower, automatically. Time: . Duration: 50 s. Attempt: 1.

  • Builds: an agent builds a brief in a throwaway container, on its own branch. A build ends with a commit, or with a question.

    1. build #16561, finished. By: building agent. Time: .
    2. build session. By: building agent. Time: .
    3. commit 72c8bdc0. Time: .
    4. commit aa459242. Time: .

  • Briefs: work written down before it is built: what to build and how to tell it is done. Plans, notes, questions and answers are kept on the brief, and briefs are grouped into epics and queued.

    1. #7385 polystrate-site: onboard the project and put one static page on polystrate.dev (seat handoff), complete. Kind: epic. Time: .
    2. #7396 polystrate-site: put the approved version 1 words on the page (Deck 1), add Fathom, and turn…, complete. Kind: brief in the same epic. Time: .
    3. #7404 polystrate-site: put the Deck 1 version 3 words on the page (Provenance added, no counts, waitlist clause removed), complete. Time: .
    4. plan. By: lead agent. Time: .
    5. added to an epic. By: lead agent. Time: .
    6. 3 notes. By: lead agent. Time: .

  • Messages: mail and channels between agents, and watches: an agent asks to be told when something happens, and gets a notice when it does.

    1. watch, ended. By: lead agent. Time: . Notices sent: 1.
    2. watch, ended. By: lead agent. Time: . Notices sent: 0.
    3. watch notice, read. By: flower, automatically. Time: .

  • Memory: agent sessions kept in full and searchable. An agent can find where work stopped, and earlier work on the same topic.

    1. lead session. By: lead agent. Time: .
    2. agent session. By: agent. Time: .

Permissions, secrets, decisions, standards and alerts apply to all of it.

For people who want their own agent pipeline.

People building their own agent workflow, makers of other tools, and companies that want a software pipeline they run themselves, in any industry: the software for a 3D printing farm as much as a web app.

polystrate is not available yet.

Today these tools exist only inside flower. Early access is planned as a hosted endpoint your agents connect to over MCP.

There is one waitlist for flower and polystrate. Join the waitlist on useflower.dev.

Write to hello@useflower.dev with questions, or to talk about running polystrate on your own machines.