Skip to content

W-004: ecs-schedule spec (v0)

Type: design · Size: S · Epic: E-schedule-v0 · Target: docs/specs/ecs-schedule.md · Breaking: no Depends: W-003 (the brief decides what demo-dnd needs) Refs: concept §6, reference/flecs/docs/Systems.md, reference/becsy/src/schedule.ts

Goal

Specify the v0 of ecs-schedule with SpecWriter: systems, flecs-style phases, before/after ordering, and a manual run(world, dt) entry point. The spec must cover both real-time loops (requestAnimationFrame, R3F useFrame) and turn-based stepping, since demo-dnd is turn-based. Intervals and fixed step are out of scope unless the demo-dnd brief needs them. When the spec is approved, Triage creates one feature item per requirement group.

Steps

  • S1: research flecs systems and pipelines, becsy ordering, and the koota frameloop guidance (Explorer); files: –
  • S2: write the spec; files: docs/specs/ecs-schedule.md
  • S3: user approves the spec

Log

  • 2026-10-30 created (Triage)
  • 2026-10-30 split: scope reduced to the spec; scaffold is W-011 (Triage)
  • 2026-11-01 activated (Triage)
  • 2026-11-01 S1, S2 done; draft spec docs/specs/ecs-schedule.md awaiting user approval (Triage)
  • 2026-11-01 spec approved by user; closed (Triage). Split into W-027..W-037.