Skip to content

History / ADR 014 Scheduling Engine Architecture

Revisions

  • docs: add GET /api/budget/breakdown endpoint

    @claude claude committed Mar 5, 2026
    9d52d0c

  • docs: align scheduling endpoint to read-only (remove dryRun) The scheduling engine is a pure computation — returns proposed schedule without persisting changes. The client applies accepted changes via PATCH /api/work-items/:id. This aligns the wiki with the issue acceptance criteria. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

    @claude claude committed Feb 24, 2026
    76b5e5c

  • docs: update scheduling API contract for Story 6.2 - add dryRun query param, LS/LF fields, persistence behavior

    @claude claude committed Feb 24, 2026
    7c48239

  • docs: add EPIC-06 architecture — ADR-013, ADR-014, schema & API contract - ADR-013: Gantt Chart Rendering Strategy (custom SVG, no third-party lib) - ADR-014: Scheduling Engine Architecture (server-side CPM, on-demand) - Schema: milestones table, milestone_work_items junction, lead_lag_days column - API Contract: milestone CRUD, milestone-work-item links, dependency PATCH, scheduling endpoint, timeline endpoint, leadLagDays on dependency responses - ADR-Index: links to ADR-013 and ADR-014 Co-Authored-By: Claude product-architect (Opus 4.6) <noreply@anthropic.com>

    @claude claude committed Feb 23, 2026
    280c06f