Skip to content

feat(stride): persist Todo meta-goals across Turns - #9214

Open
cocolord wants to merge 2 commits into
mainfrom
codex/stride-meta-goal-runtime-20261122
Open

cocolord wants to merge 2 commits into
mainfrom
codex/stride-meta-goal-runtime-20261122

Conversation

@cocolord

Copy link
Copy Markdown
Member

Goal And Delivered Outcome

Implement Todo-scoped meta-goals in Stride. The Agent records what it is trying to establish and the evidence needed to decide in the same decision as grow, switch, or verify and next_probe.

An open question follows its Todo across ordinary Turns. A later decision can cite exact subsequent work on that Todo and record an answer. The Todo details and CLI show the question, action, probe, and cited evidence. history --evidence-ref resolves the original records.

Related RFC #9209. This PR implements the single-Todo runtime behavior against main.

Author Declaration

Written by Codex (OpenAI). The implementation uses the existing Stride and Goal Vision replan owners and the Todo details reader.

Criterion Disposition Validation
Persist and continue one Todo-scoped question Implemented Two ordinary Turns carry the same open question in File and SQLite
Bind references to subsequent work on that Todo Implemented A foreign Todo's evidence is rejected and the valid result is readable from history
Show the decision in the existing Todo journey Implemented The packaged task drawer reads the same journal through the local Chat API

Scope And Continuation

The optional field is authored through an admitted Stride review. Existing Todo selection, scheduling, and settlement govern execution. Closure removes the question from ordinary Turn context and preserves the record for readback.

The checks below use synthetic Todo fixtures. Research reporting follows evaluation on real Todos.

Validation

Tested implementation revision 82af2151699fce0046509c49089cc0da1349a11f.

Check Result Evidence
CLI with File and SQLite Passed tests/control_plane/test_todo_stride_meta_goal_cli.py covers continuity, cross-Todo rejection, and exact evidence readback after resolution
TypeScript control plane Passed Typecheck and 204 targeted Stride, replan, TurnEnvelope, and progressive-context tests
Existing downstream paths Passed Focused Python regression suites, including Todo details, source routing, Vision budget, and 22 Steward replan tests
Packaged workspace Passed Desktop and narrow Todo details against the SQLite fixture, with an injected read failure and recovery through the native HTTP route

Frontend / Visual Evidence

The same synthetic Todo was read with locally packaged main (55bae0ac5) and the implementation above. The Meta-goal disclosure keeps the task request and controls visible when closed. Opening it shows the question, conclusion, next probe, and exact cited evidence.

Viewport Before After
Desktop 1440 × 960 Todo details on main at desktop width Expanded meta-goal and evidence at desktop width
Narrow 390 × 844 Todo details on main at narrow width Expanded meta-goal and evidence at narrow width

Injected read failure on the narrow drawer, followed by successful retry against the native backend.

Narrow Todo details with an injected read failure and a retry control

Type of Change

Feature and protocol documentation. Both commits carry a DCO sign-off.

Technical Direction

The existing built-in todo_replan_cadence capability and loopx-core provider own Stride. The new field extends their typed decision and readback path.

Signed-off-by: cicolord <cicolord@outlook.com>
Signed-off-by: cicolord <cicolord@outlook.com>

This branch has not been deployed

No deployments
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.

1 participant