Architecture decision record: scheduling destination matrix entry in migration-decisions.md #781

Closed
opened 2026-10-27 13:37:43 +00:00 by sam · 0 comments
Owner

migration-decisions.md section 1 explicitly names scheduling among the largest unreviewed areas needing a destination matrix entry: 'every current package MUST receive one explicit disposition' includes the cron/scheduling capability.

The ticker engine scheduling.Engine is already in internal/domain/scheduling (decided by being built there). The remaining slices — store, runner/router, blueprints, lifecycle guard — need their target paths, dependencies, contracts, and deletion criteria recorded.

Acceptance criteria

  • Section 1 (or a new section row) lists each scheduling slice — store, runner/router, blueprints, lifecycle guard, config, composition, ticker — with its target path, dependencies to remove, contracts preserved, and migration prerequisites.
  • Names the existing JobSource / Runner / Sink / Clock interfaces as the contracts that bound the destination choices (so future maintainers see why no runner / store ended up under the engine package).
  • Marks the recording as approved-by-position (the maintainer approved this placement implicitly by accepting the engine PR) so it is not re-litigated.

Close reason

Closed on GitHub; syncing bead state


Imported from beads archie-core-1786637496320-249-be6d9a20.7 · GitHub #674 · type task · priority P2 · created 2026-08-27 · closed 2026-09-26

`migration-decisions.md` section 1 explicitly names scheduling among the largest unreviewed areas needing a destination matrix entry: 'every current package MUST receive one explicit disposition' includes the cron/scheduling capability. The ticker engine `scheduling.Engine` is already in `internal/domain/scheduling` (decided by being built there). The remaining slices — store, runner/router, blueprints, lifecycle guard — need their target paths, dependencies, contracts, and deletion criteria recorded. ### Acceptance criteria - Section 1 (or a new section row) lists each scheduling slice — store, runner/router, blueprints, lifecycle guard, config, composition, ticker — with its target path, dependencies to remove, contracts preserved, and migration prerequisites. - Names the existing `JobSource` / `Runner` / `Sink` / `Clock` interfaces as the contracts that bound the destination choices (so future maintainers see why no runner / store ended up under the engine package). - Marks the recording as approved-by-position (the maintainer approved this placement implicitly by accepting the engine PR) so it is not re-litigated. ### Close reason Closed on GitHub; syncing bead state --- _Imported from beads `archie-core-1786637496320-249-be6d9a20.7` · GitHub #674 · type task · priority P2 · created 2026-08-27 · closed 2026-09-26_
sam added the mediumfeaturetask labels 2026-10-27 13:37:43 +00:00
sam self-assigned this 2026-10-27 13:37:43 +00:00
sam closed this issue 2026-10-27 13:37:43 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#781