CUST-WP-0060 T01-T03: canon ratified active, terminology v0.2, schemas + validator

- work-record-types_v0.1.md + autonomy-lanes_v0.1.md: status active
  (founder ratification 2026-07-20, hub decision f4640f9e); registry
  grandfathers legacy task-id variants (-T1, -LEGACY-Txx)
- workplan-terminology-fleet: v0.2 addendum — work-record umbrella,
  kind vocabulary, suggestion as legacy bridge name (T02)
- canon/standards/schemas/work-records/: spine + intake/decision/
  engagement JSON schemas (T03); conditional spine requirements,
  historical grace for terminal records
- tools/validate_work_records.py: registry+schema validator for CI
  (T04); jsonschema with inlined spine refs, fallback checks without;
  proof runs clean: the-custodian 384 records, binky-control 45

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

canon/standards/workplan-terminology-fleet_v0.1.md

@@ -4,14 +4,15 @@ type: standard
 title: "Workplan Terminology (Fleet) v0.1"
 domain: custodian
 status: active
-version: "0.1"
+version: "0.2"
 created: "2026-07-08"
-updated: "2026-07-08"
+updated: "2026-07-20"
 scope: fleet
 related_workplans:
   - CUST-WP-0055
   - STATE-WP-0054
   - STATE-WP-0069
+  - CUST-WP-0060
 supersedes: none
 ---
 
@@ -43,6 +44,21 @@ Authoritative interface matrix for State Hub:
 | Hub index row | **workplan** (product term) | DB entity keyed by UUID; may still use legacy column names internally |
 | Task within a workplan | **task** | `id: {WP}-TNN` in workplan file blocks |
 
+## Work-record umbrella (v0.2 addendum, CUST-WP-0060)
+
+The workplan and task definitions above are unchanged. Since v0.2 they are
+two *kinds* of the fleet umbrella term **work record** — any identified,
+lifecycle-bearing coordination artefact. The full kind registry (workplan,
+task, **intake item**, **decision**, **engagement**, **register entry**),
+the conventional spine, identity layering (UUIDv7 internal, canonical names
+external), and grandfathered legacy id schemes (`AWQ-`, `DEC-`, `OH-`) are
+normative in `work-record-types_v0.1.md` (+ machine registry
+`work-record-types.yaml`). Autonomy-lane vocabulary is normative in
+`autonomy-lanes_v0.1.md`. "Suggestion" is a legacy bridge name for the
+intake kind (state-hub suggestions table: read-only legacy pending
+close-out). This file keeps its `_v0.1` name for reference stability; the
+frontmatter `version` field is authoritative.
+
 Use **workplan** in human-facing prose: `SCOPE.md`, `AGENTS.md`, `INTENT.md`,
 README, workplan bodies, operator runbooks, and agent session guidance.