[spec 9] Share timer sends between the spec 9 engines

Open
#5,167 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript

Research direction

Start with spec9/step-message.ts and the linked discussion, then trace how both spec 9 engines currently build and send wait-timer messages. Identify the shared creator rules and verify where each send must happen relative to commit. Done means both engines use a shared timer-intent builder and sender while keeping that before-commit ordering visible at each call site.

Written by the indexing model from the issue text.

Description

(AI) Follow-up from #4661 (spec 9, the experimental single-orchestrator runtime, opt-in via WORKFLOW_SPEC_VERSION=9). Tracked as follow-up 14 on the spec 9 changelog.

Both engines implement owned-chain filtering, pre-completion sends, near-due keys and the sent-set with its rollback for wait timers, on top of the shared creator rules. A shared timer-intent builder and sender, like spec9/step-message.ts for step messages, with the before-commit ordering kept visible at each call site. 4403942443.

Dominant language
TypeScript
Stars
2.5k
Forks
401
Avg merge
1d 21h
Merged PRs (30d)
201

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from vercel/workflow

All issues in vercel/workflow

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.