# Work Packages

Work packages group related chunks into milestones with explicit automation, commit, and human review policy.

Artifact filenames follow `ai/standards/artifact-naming.md`.

Work packages are Orchestrator-owned lifecycle artifacts. Humans approve
requirements, approve the chunk plan/work package, review configured milestones,
and review final reports. During normal operation, humans should not manually
maintain work package progress or archive state.

Use `ai/standards/work-package-orchestration.md` as the lifecycle standard and `ai/tasks/work-package-template.md` as the authoring template.

## Folders

- `drafts`: work packages being planned.
- `active`: work packages currently orchestrating chunks.
- `completed`: work packages whose milestones are complete or intentionally superseded.

The Orchestrator updates progress, records final report references, and moves a
work package from `active` to `completed` after all planned chunks are complete
and final review material exists.

Final review material should include carry-forward state from
`ai/governance/registries/carry-forward-debt.yaml` or Runtime
scorecard/health projections when relevant. Work-package summaries must
distinguish blocking carry-forward debt from non-blocking warnings,
advisories, compatibility debt, pending enforcement, observations, and
follow-ups.

## Safety

- Work packages coordinate chunks; they do not authorize product implementation outside approved requirements or explicit human scope.
- Human milestone review is required by default.
- Auto-completion and auto-commit must be explicitly enabled in the work package policy.
- Auto-merge/release is never allowed by default.