# "Timebox vs work item" is the load-bearing distinction in this PM module

Taught in Lesson 0001 as the resolution to the merge question, and established
in the verdict: `pm_sprints` must **not** be merged into `tasks`, while the
`/pm/sprints` and `/tasks` **screens** should be merged.

The schema itself corroborates the distinction — `pm_sprints.status` is
CHECK-constrained to three lifecycle values, `pm_sprints` has no `owner_id`, and
`tasks.sprint_id` is a nullable child pointer with `ON DELETE SET NULL`. The
user accepted the framing and took the verdict.

Secondary conclusions from the same lesson:

- `capacity_points` / `committed_points` / `completed_points` are the columns to
  delete first. Velocity-as-commitment is exactly what the 2020 Scrum Guide
  removed, and `capacity.service.ts` already measures capacity properly in hours.
- The real interlock with HRMS is `capacity.service.ts`, not the sprint side.
- Tenancy hazard: `pm_sprints.organization_id` is nullable while `project_id` is
  NOT NULL, and RLS on this table is `USING (true)` like 95 others in the repo.

**Implications:** this vocabulary (work item, timebox, MoE, MOP, cycle time) is
now canonical in the glossary — reuse it verbatim. Next session should verify
the user can apply "timebox vs work item" to *Action Required* on their own,
since that concept is currently faked from `owner_id` and the same argument
applies to it.

**Related:** [[0003-repo-docs-describe-nonexistent-schema]], [[0002-mission-is-the-merge-decision]]