Skip to content

Sync Boatstack from Intelligence Flow Labs @ ebc216201492 - #144

Merged
operator-stack-publisher[bot] merged 1 commit into
mainfrom
sync/intelligence-flow-ebc216201492
Jul 28, 2026
Merged

Sync Boatstack from Intelligence Flow Labs @ ebc216201492#144
operator-stack-publisher[bot] merged 1 commit into
mainfrom
sync/intelligence-flow-ebc216201492

Conversation

@operator-stack-publisher

Copy link
Copy Markdown
Contributor

What this sync releases

Next steps now name their actor, so status replies never assign you the agent's work

Every prescribed next step is now typed by who performs it. A step belongs to
the operator only when it owes operator knowledge or authority — an approval,
a publish or cleanup reply, a feature choice, a source-plan path, a correction
fact. Every other step belongs to the agent, including steps whose evidence
the agent produces by doing the work, such as test runs and plan checks.

The rendered response marks agent-owned steps with "This step is mine to do"
and offers a single delegation key: reply g and the agent executes the step,
re-renders, and continues until the next step reaches the operator frontier.
A working response may no longer end by describing work the agent still has
to do; when a step repeats without progress the agent stops and reports the
block instead of looping. flow next --json exposes the typing as
next_actor, and the classifier fails closed to the operator, so a step it
cannot place behaves exactly as before.

Projection provenance

Generated from operatorstack/intelligence-flow@ebc2162014928c17debb1ce5186f1d6e20608f36.
Review provenance, tests, and examples before merging.

@operator-stack-publisher
operator-stack-publisher Bot enabled auto-merge (squash) July 28, 2026 14:05
@operator-stack-publisher
operator-stack-publisher Bot merged commit b63d6c7 into main Jul 28, 2026
9 checks passed
@operator-stack-publisher
operator-stack-publisher Bot deleted the sync/intelligence-flow-ebc216201492 branch July 28, 2026 14:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants