Skip to content

docs(stride): define meta-goals within a Todo - #9209

Open
cocolord wants to merge 5 commits into
mainfrom
codex/stride-meta-goal-20261121
Open

cocolord wants to merge 5 commits into
mainfrom
codex/stride-meta-goal-20261121

Conversation

@cocolord

@cocolord cocolord commented Nov 21, 2026 •

Copy link
Copy Markdown
Member

Goal and delivered outcome

Define a meta-goal by the plan, candidate choice, or plan relationship it targets. Both RFC mirrors show how Stride can use grow, switch, and verify to resolve goal conflicts, combine overlapping plans, and compare feasible continuations by expected goal value.

The value comparison counts current utility and time-discounted future utility. Information is valued through improved later decisions. Lower full cost resolves cases with equivalent expected outcomes, risks, and options.

The first acceptance trial uses one scheduler Todo. A matched peak-load comparison informs the next action, and decision followthrough ties that action to the observed result. The cases cover justified growth, testing a different mechanism, and an unresolved choice when the cost bound is reached. A worked example compares direct growth, direct switching, and a probe followed by a choice within the same 10 budget units. It derives the posterior decision and the break-even cost and accuracy.

Author declaration

Written by Codex (OpenAI). The proposal is based on Hierarchical Agent Stride Control §7.6 at d28ec76f4 and the existing Stride probe and followthrough contract.

Criterion Disposition Evidence
Define planning objectives and their relationship to Stride actions Specified in the RFC proposal Matched definition, examples, action semantics, and value comparison in both languages
Define acceptance for one scheduler Todo Specified in the RFC proposal Matched peak-load probe, three followthrough cases, independent checks, and complete costs
Preserve normal work admission and settlement Addressed in the design The proposal uses existing Stride and Todo paths

Scope and continuation

The PR changes the two RFC mirrors. Cross-Todo shared validation and versioned cross-task strategy evolution are follow-up work.

Validation

Local document checks passed on c59a475093a8888ab06c56640b73dbb3b2835d11.

Check Result Evidence
Bilingual RFC diff Passed Staged and committed checks against the verified main base
RFC lifecycle index Passed scripts/generate_rfc_status_index.py --check
Worked example arithmetic Passed Independent exact recomputation of expected values, posteriors, and both break-even points
Public boundary Passed loopx check on both RFC files using an empty isolated registry
Links and diff hygiene Passed Matched equation, section and relative link anchors, git diff --check, and semantic comparison of both mirrors

Frontend and visual evidence

The change is RFC prose.

Type and area

Documentation update in the public architecture RFC. All PR commits include DCO sign-offs.

Signed-off-by: cicolord <cicolord@outlook.com>
Signed-off-by: cicolord <cicolord@outlook.com>
…ride-rfc-docs-20261122

Signed-off-by: cicolord <cicolord@outlook.com>
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