Ecosystem review / Steward Improvements
Steward Improvements: review and next steps
Steward should distinguish a finished session from a finished task. A session may deliver a valid slice while the same task still has eligible work to do, with cumulative limits and dependencies preserved.
What the evidence supports
Scripts main observed during this review contains the merge for the typed next-action contract and its consumers. The retained supervision demo records bounded provider-free scheduling and session-loss observations, while explicitly keeping broader acceptance open.
Reevaluation: ST-01 is now a qualification/adoption task, not a request to implement the missing contract again. Automatic continuation and installed coverage still require evidence on the actual route.
The next useful outcome
An eligible unfinished slice resumes as the same task, keeps cumulative limits, and holds dependents until the task is actually accepted.
Separate workstream plan
ST-01 · Proposed / reuse existing work
Qualify the landed contract
Verify typed next-action and partial-handoff behavior on the installed consumers.
Acceptance: The installed route distinguishes partial progress, accepted completion and a truthful blocker.
ST-02 · Proposed / reuse existing work
Accept same-task continuation
Exercise an unfinished slice through automatic continuation within its existing authority.
Acceptance: Task identity and cumulative limits survive; dependent work stays held until acceptance.
ST-03 · Proposed / reuse existing work
Qualify supervision and recovery
Reconcile interruption, lost session, resume and uncertain-effect handling.
Acceptance: No orphan process or unknown effect is silently marked complete.
ST-04 · Proposed / reuse existing work
Improve only demonstrated scheduling gaps
Use measured eligibility, resource and authorization evidence to scope the next narrow improvement.
Acceptance: A scheduling change has an explicit requirement and preserves existing limits and ownership.
ST-05 · Proposed / reuse existing work
Expose owned blockers
Surface bridge requests, disk holds, stale ownership and dependency holds through the existing Steward surface.
Acceptance: Each actionable hold identifies its resolving owner and supported next step.
Dependencies and sequence
Landed next-action source, task identity, Worker/A2A integration and qualified installed executables.
Start with the first eligible unfinished task above, after checking its existing owner and admission. Later tasks depend on the preceding proof where applicable; this ordering does not override a current implementation plan.
Deferred work
Unreviewed concurrency changes, new timers and broad provider fairness claims based only on provider-free demos.
Evidence and updates
This article combines the supplied 8 November ecosystem review with selected current source and retained planning records. It is an editorial snapshot, not a live service census. Detailed revision bindings and task authority remain in Workspace Docs and private execution records. Publish subsequent accepted changes as linked engineering or release notes rather than silently rewriting this baseline.
Shared roadmap · All Steward Improvements articles · Explore all areas
