feat: CR-ECF-006 ECF Domain Transformation (v2.3.0)

[emmanuel-a-otchere]

Summary

Five of the seven canonical ECF Domains are renamed; one Domain is replaced. The restructure is grounded in ADR-ECF-001 (the first ADR in this repository), which introduces a five-tests rubric (Semantic Anchor, Lifecycle Completeness, Boundary Integrity, Technology Independence, Collective Exhaustiveness) used to assess each Domain.

Domain enumeration (v2.2.0 -> v2.3.0)

Before	After	Change
Governance & Existence	Governance & Existence	Retained, enhanced definition
Supply & Resources	Strategy & Direction	Replaced; substance redistributed
People & Organization	People & Organization	Retained, enhanced definition
Customer & Demand	Party & Relationship	Renamed and expanded
Product & Offering	Product & Value	Renamed and sharpened
Operations & Delivery	Operations & Enablement	Renamed and expanded
Finance & Value	Finance & Accounting	Renamed and sharpened

The Supply & Resources content is redistributed per CR-ECF-006 §2: physical/virtual assets move to Operations & Enablement (as enablers); financial resources move to Finance & Accounting; human resources remain in People & Organization.

Version semantics

v2.3.0, not v3.0.0. The seven-Domain cardinality is unchanged, the matrix M = D x S still defines 49 coordinates, and the no-cell-filling rule still applies. What changes is the rigor and precision of the Domain names so the framework can ground downstream mapping work more rigorously and correctly.

Files changed (18)

• + change-requests/ADR-ECF-001.md (new, byte-identical to source)
• + change-requests/CR-ECF-006.md (new, byte-identical to source)
• M change-requests/README.md (CR-006 + ADR-001 entries added)
• M CHANGELOG.md (v2.3.0 section)
• M CITATION.cff (version bump 2.2.0 -> 2.3.0)
• M REPORT.md (4 tables, 3 JSON examples, 1 paragraph)
• M framework/axiom.md (derivation table; persists->3 facets, exchanging->3)
• M framework/constructs.md (Domain list)
• M framework/domain-grounding.md (full rewrite of all 7 grounding records)
• M framework/matrix.md (3 tables: enumeration, cells, subdomains)
• M framework/case-studies/telecom.md (cells + worked example)
• M framework/case-studies/digital-services.md (cells + worked example + cross-industry)
• M pages/assets/site.js (DOMAINS array, cell keys, cell content, row comments)
• M pages/assets/site.css (domain palette labels)
• M schemas/ecf-domain.schema.json (PascalCase enum)
• M specification/ecf-coordinates.md (section 4 + section 9 + migration note)
• M tests/conformance/test_005_coordinate_spec.py (validator fixtures)
• M tools/ecf_coordinates.py (DOMAINS + DOMAIN_DISPLAY)

Files NOT touched (per spec section 14)

• schemas/capability.schema.json, schemas/entity.schema.json, schemas/traceability.schema.json predate the canonical enum; their reconciliation is the responsibility of the post-gate downstream reconciliation CRs (CR-MM-ECF-01, CR-BC-ECF-01, CR-BP-ECF-01).

Verification

• tests/: 39/39 pass (conformance + machinery + structure)
• 0 en/em dashes introduced in any new authored content
• ADR-001 + CR-006 landed byte-identical to source (landing rule)

Pause-for-merge

Per CR-programme convention. After you say Merge, I will:

1. Merge this PR to main.
2. Create a per-repo task list for the downstream migration (the 6 repos that consume ECF coordinates) and the L1 process discovery in dea-catalog-processes + dea-catalog-business-capabilities (per your direction: L1 candidates are a separate task, not bundled here).
3. Update all pointers to the v2.3.0 release (READMEs, framework pointers, change-requests/README.md in each downstream repo) so consumers can sync.
4. Backfill the v2.3.0 git tag (annotated, against the merge commit) and cut the GitHub Release.
5. The downstream reconciliation CRs (CR-MM-ECF-01, CR-BC-ECF-01, CR-BP-ECF-01) become unblocked against v2.3.0; each downstream migration PR lands against one of them.

Nothing moves until you say Merge.

[bolt-new-by-stackblitz]

Run & review this pull request in StackBlitz Codeflow.