Skip to content

roadmap.md

Latest commit

 

History

History
71 lines (52 loc) · 2.94 KB

roadmap.md

File metadata and controls

71 lines (52 loc) · 2.94 KB
Raw

Roadmap

Milestones are capability gates, not dates. Each one ends with something a customer could actually run.

v1 = M0 + M1 + M2. Dispatch plus visibility is the shippable product; M3 and M4 are planned and specified but do not gate the first release.

M0 — Foundation ✅

The repo boots, validates, type-checks, tests and builds. Five objects, five view containers, one app, CI, and the product docs that the rest of the work is measured against.

M1 — The dispatch spine

Gate: a duty defined on Monday produces the right task, in the right period, on the right date, in the owner's timezone — and running the dispatcher twice changes nothing.

  • Period engine (period_key, boundaries, due-date resolution, DST-safe)
  • Dispatcher job — idempotent, backfill-capable, skips standing duties
  • Task lifecycle hook — completed_at and last_update_at stamping
  • One-click completion action with undo
  • Catalog instantiation — a position's catalog onto a person
  • Assignment fan-out flow

M2 — Visibility without reporting

Gate: a manager can answer "what is late and what has stopped, across my unit" in one screen, having entered no data.

  • Positions and permission sets, authored against the ADR-0057 depth scopes. @objectstack/security-enterprise resolves them in enterprise deployments; no application-level fallback is built, and an open-edition checkout correctly shows owner-only rows
  • Unit rollups and the duty-health dataset
  • Manager dashboard: late, not-moving, on-time rate by unit — no rankings
  • Lead-time reminders, overdue escalation, stagnation alerts
  • Kanban / calendar / gantt lenses over the same data

M3 — The individual's reason to use it (post-v1)

Gate: a user who has kept the system current for a year can produce their own review material from it in under a minute.

  • Work log UI, private by default
  • Period summary export (document + copyable text)
  • Mobile-first task list and completion (PWA; note there is no ready-made navigation shell — mobileNavigation was removed in spec 17.0.0)
  • Offline completion queue

M4 — Sellable as a product, worldwide (post-v1)

Gate: a customer can install it, load their own catalog, and run it without us.

  • i18n complete: en source, zh-CN, and the extraction gate in CI
  • Spreadsheet import mapping for an existing duty catalog
  • Seed/demo dataset that shows the product working on first boot
  • Container image, docker-compose, deployment and upgrade docs
  • MCP surface documented — "ask the system what is late" without a chat feature
  • Accessibility and dark-mode pass

Explicitly out of scope

Daily status reporting · performance scores and league tables · timesheets · project planning (dependencies, critical path, resource levelling) · mandatory evidence on completion · any manager-side data entry beyond assigning.

See positioning for why each of these is declined rather than deferred.