Extract Hermes async scheduler into standalone async-scheduler

Next move

Launch the first implementation slice and begin repository skeleton work.

Current objective

Design async-scheduler as an independent system, separate from hermes cron and not constrained by the current Hermes implementation.

Where it stands

Phase: closure
Phase group: resolution
Attention: normal
Project: async-scheduler
Updated: 2026-04-14T01:26:34+08:00

People and execution

Decision owner: Danny
Execution owner: Vance
Execution shape: one-shot
Control mode: shared

Supporting context

Scope

Standalone async-scheduler extracted from Hermes async queue/runner path; exclude hermes cron.

Direction

Use the standalone async-scheduler design package in async-scheduler.git as the v1 baseline. Prioritize queue core, notification events, attention inbox, and agent recovery path.

Verification target

Replace the old simple one-shot async scheduler with async-scheduler core plus Hermes plugin integration for one-shot tasks.

Review question

Accept async-scheduler v1 as the replacement for the old simple one-shot scheduler, with recurring/chained/app-lifecycle behavior left to a separate future system?

Authorization

Proceed with v1 implementation planning from the current execution-ready design package.

Exclusions

Do not broaden scope into hermes cron integration or speculative push-to-chat alerting.

Exception criteria

scope expansion
notification contract contradiction
file queue atomicity ambiguity

Other recorded fields

created_at: 2026-04-13T00:47:02+08:00
created_by: Vance
last_meaningful_update_at: 2026-04-14T01:26:34+08:00
last_meaningful_update_summary: Record new follow-up item for origin-chat notification validation.
priority_hint: normal
primary_artifact_kind: checkpoint
primary_artifact_ref: ch-async-scheduler-001-close-20260413162957929562
not_before: 2026-04-13T10:52:07+08:00
closure_reason: Accepted as complete for its intended one-shot scope; recurring, chained execution, and app-lifecycle behavior are intentionally excluded and tracked separately.

Inspect

Artifacts

worklog

wo-async-scheduler-001-capture-20260413004702877144
wo-async-scheduler-001-advance-20260413004712532430
wo-async-scheduler-001-advance-20260413004712639847
wo-async-scheduler-001-note-20260413004712748906
wo-async-scheduler-001-note-20260413004921298781
wo-async-scheduler-001-update-20260413004928653930
wo-async-scheduler-001-note-20260413005324947258
wo-async-scheduler-001-update-20260413005325071872
wo-async-scheduler-001-note-20260413011310619234
wo-async-scheduler-001-note-20260413012347436528
wo-async-scheduler-001-note-20260413100703300082
wo-async-scheduler-001-note-20260413101507964086
wo-async-scheduler-001-note-20260413103651597608
wo-async-scheduler-001-note-20260413104627370961
wo-async-scheduler-001-note-20260413105824789098
wo-async-scheduler-001-note-20260413112444915865
wo-async-scheduler-001-note-20260413115617904971
wo-async-scheduler-001-note-20260413120722397204
wo-async-scheduler-001-note-20260413124148622031
wo-async-scheduler-001-note-20260413135035670950
wo-async-scheduler-001-note-20260413135718269825
wo-async-scheduler-001-note-20260413162932597929
wo-async-scheduler-001-note-20260414012634593030

checkpoint

ch-async-scheduler-001-advance-20260413100058386138
ch-async-scheduler-001-advance-20260413100058495835
ch-async-scheduler-001-advance-20260413100058608265
ch-async-scheduler-001-launch-20260413105207667034
ch-async-scheduler-001-submit-review-20260413162946335051
ch-async-scheduler-001-close-20260413162957929562

scheduler

sc-async-scheduler-001-update-20260413103848555954
sc-async-scheduler-001-update-20260413104706217082
sc-async-scheduler-001-launch-20260413105207665267

Metadata

Runtime summary

Status: launched
Session: n/a
Owner: Vance
Verification target: Produce the first implementation slice for async-scheduler: repository skeleton, CLI scaffold, queue storage skeleton, inbox surface skeleton, and basic tests.