Skip to content

Journal bounded turn deadlines and remote stop intent - #1744

Draft
jhgaylor wants to merge 1 commit into
mainfrom
feat/durable-turn-deadlines
Draft

Journal bounded turn deadlines and remote stop intent#1744
jhgaylor wants to merge 1 commit into
mainfrom
feat/durable-turn-deadlines

Conversation

@jhgaylor

@jhgaylor jhgaylor commented Sep 7, 2026

Copy link
Copy Markdown
Collaborator

A late ACP response must not turn an expired review into success, and a lost stop acknowledgment must not authorize another execution. This draft adds the durable journal and database fences needed for those guarantees.

It persists immutable deadlines and remote bindings, arbitrates completion versus expiry, preserves failed/interrupted turns until remote termination is confirmed, prevents reset while execution remains unresolved, and recovers abandoned stop attempts without replay.

Timeout activation remains pending API/account policy, trusted session-identity transport, scheduling and the remaining lifecycle integration. Sprites session metadata awaits superfly/sprites-ex#33. The proposed ADR records the integration checklist and validation limits. This supplies the journal foundation for #1732.

Validation: full mix precommit passed (4,632 tests + six doctests; zero failures, two skips, seven exclusions). The standalone PostgreSQL proof ran 20 completion/expiry races and competing termination claims on separate connections, plus confirmed parent/turn lock-delay cases. It made no provider calls. Source hashes and results are in decisions/evidence/turn-deadline-races.json.

No production deadline has been activated.

…ntent

Signed-off-by: Jake Gaylor <jhgaylor@gmail.com>
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