# AI Artifact Naming

AI workflow artifacts use sortable, zero-padded filenames. New artifacts must
use six-digit IDs, and lifecycle helpers should accept numeric IDs with at least
three digits during migration.

## Conventions

- Chunks: `chunk-000001-slug.md`
- Requirements: `requirements-000001-slug.md`
- Work packages: `work-package-000001-slug.md`
- Reports: `report-000001-YYYYMMDD-slug.md`

## ID Width

- Use six digits for new and renamed artifact IDs.
- Do not reuse IDs after an artifact is moved, archived, or renamed.
- Helpers may accept older numeric widths during transition, but generated
  filenames should use six digits.

## Slug Rules

- Use lowercase kebab-case.
- Use descriptive nouns and verbs.
- Avoid dates, status labels, or role names in slugs unless they are part of
  the actual artifact topic.

## Lifecycle Folders

- Chunks: `ai/chunks/drafts`, `ai/chunks/backlog`, `ai/chunks/active`,
  `ai/chunks/completed`.
- Requirements: `ai/requirements/drafts`, `ai/requirements/active`,
  `ai/requirements/approved`, `ai/requirements/completed`.
- Work packages: `ai/work-packages/drafts`, `ai/work-packages/active`,
  `ai/work-packages/completed`.
- Reports: `ai/reports`.

## Reference Updates

When an artifact is renamed:

- Update references in chunks, requirements, work packages, reports, roles,
  standards, templates, helper scripts, and tests.
- Run old-name searches for stale three-digit references and legacy report
  names.
- Keep migration notes explicit if an old name must be mentioned historically.
- Do not rename app source files or dependency files as part of workflow
  artifact naming migrations.