diff --git a/history/2026-08-09-prj-flavor-canon.md b/history/2026-08-09-prj-flavor-canon.md
new file mode 100644
index 0000000..a34ad41
--- /dev/null
+++ b/history/2026-08-09-prj-flavor-canon.md
@@ -0,0 +1,33 @@
+# Milestone — project repository flavor canonized
+
+**Recorded:** 2026-08-09  
+**Workplan task:** SHR-WP-0001-T01
+
+## What landed
+
+Durable fleet standard:
+
+- `the-custodian/canon/standards/project-repository-flavor_v0.1.md`
+
+Cross-links:
+
+- ADR-005 naming section → standard (`prj-` prefix; closes deferred naming)
+- Repo Classification Standard §5.3 → project-repo vs ordinary `category: project`
+- CUST-WP-0050 D1a → resolved 2026-08-09
+
+## Decisions fixed
+
+| Topic | Decision |
+| --- | --- |
+| Naming | `prj-<kebab-slug>` only for new project repos |
+| Purpose document | `GOAL.md` (not durable-product `INTENT.md`) |
+| Authority | coordination + evidence here; implementation in child repos |
+| Lifecycle | `draft → active → completed → archived` |
+| Retirement | archive read-only with completion record; never delete |
+
+## Residual
+
+`statehub register` and related bootstrap still assume `INTENT.md` for ordinary
+repos. Adapting that path for `repo_flavor: project` / `GOAL.md` belongs in a
+state-hub implementation workplan (see SHR-WP-0001-T05 map), not as a
+hand-edited exception in this repository.
diff --git a/workplans/SHR-WP-0001-foundation.md b/workplans/SHR-WP-0001-foundation.md
index be0312c..536400a 100644
--- a/workplans/SHR-WP-0001-foundation.md
+++ b/workplans/SHR-WP-0001-foundation.md
@@ -4,7 +4,7 @@ type: workplan
 title: "Project foundation and architecture baseline"
 domain: infotech
 repo: prj-state-hub-retirement
-status: proposed
+status: active
 owner: codex
 topic_slug: state-hub-retirement
 created: "2026-08-09"
@@ -24,7 +24,7 @@ migration begins.
 
 ```task
 id: SHR-WP-0001-T01
-status: todo
+status: done
 priority: high
 state_hub_task_id: "528ed9c9-57a6-4f44-b1cf-9d2c1a5cbca4"
 ```
@@ -33,6 +33,15 @@ Define the `prj-` repository flavor, lifecycle, required files, authority
 boundary, and archive procedure in the Custodian canon. Confirm that project
 repositories use `GOAL.md` rather than durable-product `INTENT.md`.
 
+**Result (2026-08-09):** Fleet standard published at
+`the-custodian/canon/standards/project-repository-flavor_v0.1.md`. ADR-005
+naming section points at the standard; classification standard §5.3 cross-links
+it; CUST-WP-0050 open question D1a marked resolved. Reference instance: this
+repository (`prj-state-hub-retirement`, `GOAL.md` only — no durable
+`INTENT.md`). Residual tooling gap: `statehub register` still scaffolds
+`INTENT.md` for ordinary repos — capture under a state-hub child workplan when
+T05 maps implementation streams (do not invent `INTENT.md` on `prj-` repos).
+
 ## Inventory State Hub
 
 ```task
@@ -102,7 +111,7 @@ in `GOAL.md` into executable or evidence-backed gates.
 
 ## Acceptance
 
-- [ ] The `prj-` flavor has a durable canonical definition.
+- [x] The `prj-` flavor has a durable canonical definition.
 - [ ] State Hub has a complete disposition inventory.
 - [ ] The information and extension architectures are reviewable.
 - [ ] Each implementation stream has one local owner and workplan.