New: plan work with a reserved exit budget
Check exact terms, physical retries and ordinary/cleanup limits; export an unsent request. Open planner · Unattended Python tools · Implementation evidence. Planning is not execution or source closure.
Workstream evidence and memory
Resource accounting and interruption recovery
Source-grounded findings, explicit boundaries and traceable report sections.
Keep unknown effects and accounting durable
Protected work reports describe exact intent saved before dispatch, retained unknown exposure, current read accounting, generation-bound subsequent tasks, compact spent/unknown totals and permanent replay fences. Recovery must not mint a new logical operation or refund unknown effects.
Evidence: Protected work-client integration checkpoint · Exact work-intent resolution — September 12, 2026 · Metered current reads and contained work transport — September 12, 2026 · Work task continuity and current-runtime recovery
Local/native recovery is not all production transition evidence
The latest source reports distinguish passing native cold-process recovery from an incomplete warm-upgrade run, actual Passenger transition and deployed public-document pilot evidence. Credential-lifecycle metering/transport is explicitly still named as remaining work. Preserve the failed/incomplete test record beside its later narrow success.
Evidence: Work task continuity and current-runtime recovery · v049 work warm upgrade native failed 20260913 · v049 work recovery native 20260913
Implemented: bounded workbench tools
The public workbench now offers current public discovery, exact terms/results inspection, selected contract comparison and local byte checks. This locally tested subset does not close wider pilot, rights or lifecycle work. Implementation mapping · Test evidence and limitations.
Related reports
19 reports shown