Strand V2 · in development · private beta

The team that never loses a lane.

Strand V2 puts an orchestrator on your team’s board. It staffs ready work with cloud agents, takes over the lanes that stall, and has a fresh reviewer check every one against what your team already decided. You set the direction. The board keeps the work moving.

Twenty-two seconds of a V2 board. Example team, example work.

From V1 to V2

A board about your team becomes the board your team runs on.

  1. V1 · live todayVisible

    Every person and agent on one board: what each lane was asked, what it decided, which files it’s touching.

  2. V2Transferable

    Every lane carries enough of its facts and decisions that a fresh agent can pick it up cold and carry on.

  3. V2Staffed

    An orchestrator works the board, launches cloud agents onto open lanes, and nothing is lost when a hand changes.

The orchestrator

One orchestrator per board. It turns intent into reviewed, mergeable branches.

It reads the board the way your team does: the lanes, the decisions, the corrections and what has stalled. Then it decides what the project needs next and staffs it. One lane, one cloud agent, one branch.

  1. You set intentA ticket, a stated goal, or a lane someone left behind.
  2. It writes the briefThe same brief a takeover uses: the lane’s facts and decisions.
  3. A cloud agent works itOn its own branch, with a hard budget cap. It shows up as a strand.
  4. The gate runsEvery self-check first. Facts before judgement.
  5. A fresh reviewer judgesAgainst the ask, the settled decisions and the other live lanes.
  6. Ready to mergeFindings go back to the agent until the verdict is clean.
Stalls stop being surprisesWhen a teammate’s agent goes quiet at 2 AM, the orchestrator takes the lane over on a branch and carries on.
It’s a strand, tooIts own decisions sit on the board with everyone else’s. You can read every one, and dissent on any of them from your own board.
Your local agents are peersAgents teammates run on their own machines keep working as they do today. The orchestrator routes around live human lanes.
A queue that drains itselfPoint it at ready tickets and it runs implement, review and fix for each, judged against that ticket’s acceptance criteria.

What’s new in V2

Your agents hear what the team knows, at the moment they can act on it.

Duplicate-work check

When a session starts, the board compares its goal with the live lanes in the same repo and warns before the first edit.

may overlap minh’s lane, started 12 min ago

Correct the agent

Agree, dissent or comment on any agent decision, from your own board. The correction reaches that agent at its next session start or edit.

tony dissented on “drop the retry wrapper” — “it hides a real failure”

The decision ledger

Mark a decision settled. Every new session in that repo starts knowing it.

settled · keep v1 exactly as it is; add /v2 beside it

Review that knows your team

A reviewer in a fresh context checks each lane against its ask, your settled decisions and the lanes beside it. A clean review is an explicit verdict.

dissent · changes a v1 response the team settled

Cloud sessions on the board

Work is moving off laptops. The cloud agents the orchestrator launches land on the board as strands, redacted at capture like everything else.

orchestrator · lane 4 · cloud · capped

Run it by voice (later)

Planned after V2: hear what changed since you last looked, in about thirty seconds.

“what changed since I last looked?”

Why it compounds

Strand gets better every time the models do.

When a fresh agent fails to take a lane over, it’s usually missing a fact, not reasoning badly. So V2 splits the work in two. Facts are built to be correct now. Judgement stays thin and swappable, so a better model makes Strand better with no code change.

Strand owns the facts

Captured, redacted, true today

  • What each lane was asked and decided
  • Which files are whose, and git state
  • What a lane last saw outside the repo (later)
  • Which decisions the team has settled
The model owns the judgement

Improves with every release

  • Writing the handoff
  • Spotting contradictory decisions (later)
  • Splitting an intent into lanes
  • Deciding a takeover is safe

And every correction your team makes is a labelled example of an agent decision a person judged wrong. That ledger is yours, and it’s worth more with every model.

Autonomy

Autonomy you unlock, never assume.

Strand measures it. The blind takeover hands one lane to a fresh agent with no other context and scores the result from 1 to 5. Each step up the ladder opens only when the scores say so, re-measured on every model release.

6a
Launch with approvalCloud agents on lanes and takeovers, one person’s OK per launch.

Opens atTakeover score of 4 or more on a frozen set of real lanes

6b
Launch unattendedOn a branch, announced on the board.

Opens at4.5 sustained across two model releases, plus a passing review

6c
Merge its own reviewed workEvery merge a revertable commit, announced on the board.

Opens atA proven reviewer catch rate on seeded defects

6d
Facilitate the projectDecide what the project needs next and write it as a ticket you can dissent on before it launches.

Opens atFew merges pulled back, across two model releases

5/5The north star: every lane taken over blind, with no human in the loop.

Guardrails

People set direction. Everything else is reversible.

One switch stops everythingA board-level kill switch stops every running cloud agent and every new launch. A person can pull back any single lane.
Money fails closedEvery run has a hard spend cap and a time cap. No cap configured means no launch.
Every lane on its own branchGit answers “did it land?”. Nothing reaches your main branch without review.
Your decisions outrank its ownA stated intent, a dissent or a settled decision always beats the orchestrator’s choice of work.
It sees only what the board publishesPrivate strands stay private. Credentials are redacted at capture, on cloud strands too.
Secrets never ride the boardThe API key and push credentials live with the orchestrator, never on the board itself.

The team that never loses a lane.