generated from coulomb/repo-seed
Register with state-hub, accept DEC-001–004 and ADR-004 rotation policy, scaffold pilot roster, hourly ActivityDefinition copies, and bootstrap log after schedule init on three custodian pilot repos.
41 lines
1.1 KiB
Markdown
41 lines
1.1 KiB
Markdown
---
|
|
id: ADR-001
|
|
title: Workplan ID Prefix Convention
|
|
status: accepted
|
|
date: "2026-06-18"
|
|
---
|
|
|
|
# ADR-001 — Workplan ID Prefix Convention
|
|
|
|
## Status
|
|
|
|
Accepted
|
|
|
|
## Context
|
|
|
|
`register_project.sh` derives the workplan prefix from the repo slug first token:
|
|
`coulomb-loop` → `COULOMB-WP`. The engagement workplans were authored as
|
|
`LOOP-WP-0001` through `LOOP-WP-0004` before registration, and state-hub
|
|
`fix-consistency` indexed them under those IDs.
|
|
|
|
Renaming to `COULOMB-WP` would churn 4 workstreams, 30 tasks, and cross-references
|
|
in INTENT.md with no functional benefit.
|
|
|
|
## Decision
|
|
|
|
Adopt **`LOOP-WP`** as the canonical workplan prefix for `coulomb-loop`.
|
|
|
|
- File pattern: `workplans/LOOP-WP-NNNN-<slug>.md`
|
|
- Task IDs: `LOOP-WP-NNNN-Tnn`
|
|
- Override the auto-derived `COULOMB-WP` in `.claude/rules/workplan-convention.md`
|
|
|
|
## Consequences
|
|
|
|
- Consistent with engagement naming ("loop" operations)
|
|
- state-hub workstream slugs remain `loop-wp-0001-*`
|
|
- Future coulomb_social repos (e.g. product apps) should use their own prefix
|
|
|
|
## Related
|
|
|
|
- state-hub ADR-001 (workplans as repo artefacts)
|
|
- `docs/decisions/DEC-001-pilot-roster-scope.md` (separate concern) |