You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit d22fe96
Browse filesBrowse the repository at this point in the historyBrowse files
📝 Settle what an exhausted planning loop asks for, and start proving it
#290 settled the exhaustion behavior these documents still called an unresolved
product decision. Exhausting the bounded attempts is neither convergence nor
ordinary successful completion: it starts no implementation and no later durable
effect, and it asks the user for direction rather than answering on the stage's
own account. A composed workflow turns that request into a durable suspension,
which is #367's and unbuilt.
No return schema changes. The pair a stage already returns — `decision.proceed`
true with `verdictPassed` false — is what makes exhaustion distinct, and nothing
else produces it, so the rule against returning a second copy of a derivable
answer still holds. What changes is that the report asks instead of stopping:
the two exhaustion branches now await direction, while a decline still stops.
The proof #290 asks for begins beside the stages it exercises. `Agent.AddDir` is
#302's and does not exist, so a no-op stub sits in the test directory alone —
repository resolution is scope-local, so every name the inventory calls
unresolved still resolves to nothing from the workflow directory, which the
component probe confirms.
One of the seven acceptance criteria is proven so far: the exact instruction
paths and contents reach the planner prompt, constrained literally in the
scenario so a dropped or summarized instruction fails rather than matching.
template="{?before}## `workflows/adversarial-implementation/tests/fixtures/AGENTS.md`{?gap}Root instructions: prefer evidence over assertion.{?middle}## `workflows/adversarial-implementation/tests/fixtures/nested/AGENTS.md`{?gap2}Nested instructions: never edit a test to make it pass.{?rest}Add a health endpoint{?tail}"
4
+
/>
5
+
6
+
HANDOFF
7
+
8
+
Purpose: add a health endpoint.
9
+
10
+
User decisions: the route is `/health`.
11
+
12
+
Hypotheses the implementor must test: the router already exposes a mount point.
0 commit comments