@formicoidea/labre-framework-ddd-core-domain 0.41.0 → 0.42.0

package/LICENSE

@@ -0,0 +1,384 @@
+# Mozilla Public License Version 2.0
+
+Copyright (c) TOEVERYTHING PTE. LTD. and its affiliates.
+
+1. Definitions
+
+---
+
+1.1. "Contributor"
+means each individual or legal entity that creates, contributes to
+the creation of, or owns Covered Software.
+
+1.2. "Contributor Version"
+means the combination of the Contributions of others (if any) used
+by a Contributor and that particular Contributor's Contribution.
+
+1.3. "Contribution"
+means Covered Software of a particular Contributor.
+
+1.4. "Covered Software"
+means Source Code Form to which the initial Contributor has attached
+the notice in Exhibit A, the Executable Form of such Source Code
+Form, and Modifications of such Source Code Form, in each case
+including portions thereof.
+
+1.5. "Incompatible With Secondary Licenses"
+means
+
+    (a) that the initial Contributor has attached the notice described
+        in Exhibit B to the Covered Software; or
+
+    (b) that the Covered Software was made available under the terms of
+        version 1.1 or earlier of the License, but not also under the
+        terms of a Secondary License.
+
+1.6. "Executable Form"
+means any form of the work other than Source Code Form.
+
+1.7. "Larger Work"
+means a work that combines Covered Software with other material, in
+a separate file or files, that is not Covered Software.
+
+1.8. "License"
+means this document.
+
+1.9. "Licensable"
+means having the right to grant, to the maximum extent possible,
+whether at the time of the initial grant or subsequently, any and
+all of the rights conveyed by this License.
+
+1.10. "Modifications"
+means any of the following:
+
+    (a) any file in Source Code Form that results from an addition to,
+        deletion from, or modification of the contents of Covered
+        Software; or
+
+    (b) any new file in Source Code Form that contains any Covered
+        Software.
+
+1.11. "Patent Claims" of a Contributor
+means any patent claim(s), including without limitation, method,
+process, and apparatus claims, in any patent Licensable by such
+Contributor that would be infringed, but for the grant of the
+License, by the making, using, selling, offering for sale, having
+made, import, or transfer of either its Contributions or its
+Contributor Version.
+
+1.12. "Secondary License"
+means either the GNU General Public License, Version 2.0, the GNU
+Lesser General Public License, Version 2.1, the GNU Affero General
+Public License, Version 3.0, or any later versions of those
+licenses.
+
+1.13. "Source Code Form"
+means the form of the work preferred for making modifications.
+
+1.14. "You" (or "Your")
+means an individual or a legal entity exercising rights under this
+License. For legal entities, "You" includes any entity that
+controls, is controlled by, or is under common control with You. For
+purposes of this definition, "control" means (a) the power, direct
+or indirect, to cause the direction or management of such entity,
+whether by contract or otherwise, or (b) ownership of more than
+fifty percent (50%) of the outstanding shares or beneficial
+ownership of such entity.
+
+2. License Grants and Conditions
+
+---
+
+2.1. Grants
+
+Each Contributor hereby grants You a world-wide, royalty-free,
+non-exclusive license:
+
+(a) under intellectual property rights (other than patent or trademark)
+Licensable by such Contributor to use, reproduce, make available,
+modify, display, perform, distribute, and otherwise exploit its
+Contributions, either on an unmodified basis, with Modifications, or
+as part of a Larger Work; and
+
+(b) under Patent Claims of such Contributor to make, use, sell, offer
+for sale, have made, import, and otherwise transfer either its
+Contributions or its Contributor Version.
+
+2.2. Effective Date
+
+The licenses granted in Section 2.1 with respect to any Contribution
+become effective for each Contribution on the date the Contributor first
+distributes such Contribution.
+
+2.3. Limitations on Grant Scope
+
+The licenses granted in this Section 2 are the only rights granted under
+this License. No additional rights or licenses will be implied from the
+distribution or licensing of Covered Software under this License.
+Notwithstanding Section 2.1(b) above, no patent license is granted by a
+Contributor:
+
+(a) for any code that a Contributor has removed from Covered Software;
+or
+
+(b) for infringements caused by: (i) Your and any other third party's
+modifications of Covered Software, or (ii) the combination of its
+Contributions with other software (except as part of its Contributor
+Version); or
+
+(c) under Patent Claims infringed by Covered Software in the absence of
+its Contributions.
+
+This License does not grant any rights in the trademarks, service marks,
+or logos of any Contributor (except as may be necessary to comply with
+the notice requirements in Section 3.4).
+
+2.4. Subsequent Licenses
+
+No Contributor makes additional grants as a result of Your choice to
+distribute the Covered Software under a subsequent version of this
+License (see Section 10.2) or under the terms of a Secondary License (if
+permitted under the terms of Section 3.3).
+
+2.5. Representation
+
+Each Contributor represents that the Contributor believes its
+Contributions are its original creation(s) or it has sufficient rights
+to grant the rights to its Contributions conveyed by this License.
+
+2.6. Fair Use
+
+This License is not intended to limit any rights You have under
+applicable copyright doctrines of fair use, fair dealing, or other
+equivalents.
+
+2.7. Conditions
+
+Sections 3.1, 3.2, 3.3, and 3.4 are conditions of the licenses granted
+in Section 2.1.
+
+3. Responsibilities
+
+---
+
+3.1. Distribution of Source Form
+
+All distribution of Covered Software in Source Code Form, including any
+Modifications that You create or to which You contribute, must be under
+the terms of this License. You must inform recipients that the Source
+Code Form of the Covered Software is governed by the terms of this
+License, and how they can obtain a copy of this License. You may not
+attempt to alter or restrict the recipients' rights in the Source Code
+Form.
+
+3.2. Distribution of Executable Form
+
+If You distribute Covered Software in Executable Form then:
+
+(a) such Covered Software must also be made available in Source Code
+Form, as described in Section 3.1, and You must inform recipients of
+the Executable Form how they can obtain a copy of such Source Code
+Form by reasonable means in a timely manner, at a charge no more
+than the cost of distribution to the recipient; and
+
+(b) You may distribute such Executable Form under the terms of this
+License, or sublicense it under different terms, provided that the
+license for the Executable Form does not attempt to limit or alter
+the recipients' rights in the Source Code Form under this License.
+
+3.3. Distribution of a Larger Work
+
+You may create and distribute a Larger Work under terms of Your choice,
+provided that You also comply with the requirements of this License for
+the Covered Software. If the Larger Work is a combination of Covered
+Software with a work governed by one or more Secondary Licenses, and the
+Covered Software is not Incompatible With Secondary Licenses, this
+License permits You to additionally distribute such Covered Software
+under the terms of such Secondary License(s), so that the recipient of
+the Larger Work may, at their option, further distribute the Covered
+Software under the terms of either this License or such Secondary
+License(s).
+
+3.4. Notices
+
+You may not remove or alter the substance of any license notices
+(including copyright notices, patent notices, disclaimers of warranty,
+or limitations of liability) contained within the Source Code Form of
+the Covered Software, except that You may alter any license notices to
+the extent required to remedy known factual inaccuracies.
+
+3.5. Application of Additional Terms
+
+You may choose to offer, and to charge a fee for, warranty, support,
+indemnity or liability obligations to one or more recipients of Covered
+Software. However, You may do so only on Your own behalf, and not on
+behalf of any Contributor. You must make it absolutely clear that any
+such warranty, support, indemnity, or liability obligation is offered by
+You alone, and You hereby agree to indemnify every Contributor for any
+liability incurred by such Contributor as a result of warranty, support,
+indemnity or liability terms You offer. You may include additional
+disclaimers of warranty and limitations of liability specific to any
+jurisdiction.
+
+4. Inability to Comply Due to Statute or Regulation
+
+---
+
+If it is impossible for You to comply with any of the terms of this
+License with respect to some or all of the Covered Software due to
+statute, judicial order, or regulation then You must: (a) comply with
+the terms of this License to the maximum extent possible; and (b)
+describe the limitations and the code they affect. Such description must
+be placed in a text file included with all distributions of the Covered
+Software under this License. Except to the extent prohibited by statute
+or regulation, such description must be sufficiently detailed for a
+recipient of ordinary skill to be able to understand it.
+
+5. Termination
+
+---
+
+5.1. The rights granted under this License will terminate automatically
+if You fail to comply with any of its terms. However, if You become
+compliant, then the rights granted under this License from a particular
+Contributor are reinstated (a) provisionally, unless and until such
+Contributor explicitly and finally terminates Your grants, and (b) on an
+ongoing basis, if such Contributor fails to notify You of the
+non-compliance by some reasonable means prior to 60 days after You have
+come back into compliance. Moreover, Your grants from a particular
+Contributor are reinstated on an ongoing basis if such Contributor
+notifies You of the non-compliance by some reasonable means, this is the
+first time You have received notice of non-compliance with this License
+from such Contributor, and You become compliant prior to 30 days after
+Your receipt of the notice.
+
+5.2. If You initiate litigation against any entity by asserting a patent
+infringement claim (excluding declaratory judgment actions,
+counter-claims, and cross-claims) alleging that a Contributor Version
+directly or indirectly infringes any patent, then the rights granted to
+You by any and all Contributors for the Covered Software under Section
+2.1 of this License shall terminate.
+
+5.3. In the event of termination under Sections 5.1 or 5.2 above, all
+end user license agreements (excluding distributors and resellers) which
+have been validly granted by You or Your distributors under this License
+prior to termination shall survive termination.
+
+---
+
+-                                                                      *
+- 6.  Disclaimer of Warranty \*
+- ------------------------- \*
+-                                                                      *
+- Covered Software is provided under this License on an "as is" \*
+- basis, without warranty of any kind, either expressed, implied, or \*
+- statutory, including, without limitation, warranties that the \*
+- Covered Software is free of defects, merchantable, fit for a \*
+- particular purpose or non-infringing. The entire risk as to the \*
+- quality and performance of the Covered Software is with You. \*
+- Should any Covered Software prove defective in any respect, You \*
+- (not any Contributor) assume the cost of any necessary servicing, \*
+- repair, or correction. This disclaimer of warranty constitutes an \*
+- essential part of this License. No use of any Covered Software is \*
+- authorized under this License except under this disclaimer. \*
+-                                                                      *
+
+---
+
+---
+
+-                                                                      *
+- 7.  Limitation of Liability \*
+- -------------------------- \*
+-                                                                      *
+- Under no circumstances and under no legal theory, whether tort \*
+- (including negligence), contract, or otherwise, shall any \*
+- Contributor, or anyone who distributes Covered Software as \*
+- permitted above, be liable to You for any direct, indirect, \*
+- special, incidental, or consequential damages of any character \*
+- including, without limitation, damages for lost profits, loss of \*
+- goodwill, work stoppage, computer failure or malfunction, or any \*
+- and all other commercial damages or losses, even if such party \*
+- shall have been informed of the possibility of such damages. This \*
+- limitation of liability shall not apply to liability for death or \*
+- personal injury resulting from such party's negligence to the \*
+- extent applicable law prohibits such limitation. Some \*
+- jurisdictions do not allow the exclusion or limitation of \*
+- incidental or consequential damages, so this exclusion and \*
+- limitation may not apply to You. \*
+-                                                                      *
+
+---
+
+8. Litigation
+
+---
+
+Any litigation relating to this License may be brought only in the
+courts of a jurisdiction where the defendant maintains its principal
+place of business and such litigation shall be governed by laws of that
+jurisdiction, without reference to its conflict-of-law provisions.
+Nothing in this Section shall prevent a party's ability to bring
+cross-claims or counter-claims.
+
+9. Miscellaneous
+
+---
+
+This License represents the complete agreement concerning the subject
+matter hereof. If any provision of this License is held to be
+unenforceable, such provision shall be reformed only to the extent
+necessary to make it enforceable. Any law or regulation which provides
+that the language of a contract shall be construed against the drafter
+shall not be used to construe this License against a Contributor.
+
+10. Versions of the License
+
+---
+
+10.1. New Versions
+
+Mozilla Foundation is the license steward. Except as provided in Section
+10.3, no one other than the license steward has the right to modify or
+publish new versions of this License. Each version will be given a
+distinguishing version number.
+
+10.2. Effect of New Versions
+
+You may distribute the Covered Software under the terms of the version
+of the License under which You originally received the Covered Software,
+or under the terms of any subsequent version published by the license
+steward.
+
+10.3. Modified Versions
+
+If you create software not governed by this License, and you want to
+create a new license for such software, you may create and use a
+modified version of this License if you rename the license and remove
+any references to the name of the license steward (except to note that
+such modified license differs from this License).
+
+10.4. Distributing Source Code Form that is Incompatible With Secondary
+Licenses
+
+If You choose to distribute Source Code Form that is Incompatible With
+Secondary Licenses under the terms of this version of the License, the
+notice described in Exhibit B of this License must be attached.
+
+## Exhibit A - Source Code Form License Notice
+
+This Source Code Form is subject to the terms of the Mozilla Public
+License, v. 2.0. If a copy of the MPL was not distributed with this
+file, You can obtain one at http://mozilla.org/MPL/2.0/.
+
+If it is not possible or desirable to put the notice in a particular
+file, then You may include the notice in a location (such as a LICENSE
+file in a relevant directory) where a recipient would be likely to look
+for such a notice.
+
+You may add additional accurate notices of copyright ownership.
+
+## Exhibit B - "Incompatible With Secondary Licenses" Notice
+
+This Source Code Form is "Incompatible With Secondary Licenses", as
+defined by the Mozilla Public License, v. 2.0.

package/dist/commands.d.ts

@@ -1,4 +1,19 @@
+import { type ChromeWording } from '@formicoidea/labre-core/shared/services';
 import type { CommandDescriptor } from '@formicoidea/labre-core/std';
 import { type TemplateResult } from 'lit';
+/**
+ * The automatic legend's own section titles — text stamped onto the chart the
+ * moment the legend is built, like any other seed, and declared HERE because
+ * the rows that file themselves under them are subscribed by the commands
+ * below. The box title itself is not one of them: it says the shared word
+ * "Legend" and reuses `BOARD_LEGEND_TITLE`.
+ *
+ * Three sub-titles for a framework whose ten commands all sit in ONE category:
+ * `section` is what keeps them, and in particular the one that explains the
+ * C/X/F letters (`docs/adr/0026`).
+ */
+export declare const CORE_DOMAIN_SEED_LEGEND_SUBDOMAINS: ChromeWording;
+export declare const CORE_DOMAIN_SEED_LEGEND_TEAM_MODES: ChromeWording;
+export declare const CORE_DOMAIN_SEED_LEGEND_MOVEMENT: ChromeWording;
 export declare const coreDomainCommands: CommandDescriptor[];
 export declare const coreDomainCommandIcons: Record<string, TemplateResult>;

package/dist/commands.js

@@ -1,9 +1,47 @@
-import { addDot, addMarker, cdSubdomainSeedKey, CD_SUBDOMAINS, MOVEMENT_COLOR, placeDddElement, teamTopologySeedKey, TEAM_TOPOLOGIES, } from '@formicoidea/labre-ddd-shared';
+import { addDot, addMarker, cdSubdomainSeedKey, CD_SUBDOMAINS, coreDomainToolbarIcon, MOVEMENT_COLOR, placeDddElement, teamTopologySeedKey, TEAM_TOPOLOGIES, } from '@formicoidea/labre-ddd-shared';
 import { NOTATION_NEUTRALS } from '@formicoidea/labre-core/shared/consts';
-import { translateKey } from '@formicoidea/labre-core/shared/services';
+import { translateKey, } from '@formicoidea/labre-core/shared/services';
 import { svg } from 'lit';
 import { activateMovement, createCoreDomainChart } from './actions.js';
-import { markerRole, subdomainRole } from './roles.js';
+import { CORE_DOMAIN_ROLE, CORE_DOMAIN_ROLES, markerRole, subdomainRole, } from './roles.js';
+/**
+ * The legend wording of a sub-domain dot: the ROLE's own i18n key — so a host
+ * catalogue still wins and no key is invented — with the PALETTE's shorter
+ * label as the fallback.
+ *
+ * The two differ for three of the five: `roles.ts` spells out "Bounded context
+ * (current position)" where the chart's legend has always read "Bounded
+ * context". A host resolving the key reads the same word either way; this keeps
+ * the host-less fallback reading what it has read since the button shipped.
+ * Both halves come from declarations that already exist — neither is restated.
+ */
+function subdomainWording(role, label) {
+    const { labelKey } = CORE_DOMAIN_ROLES[role];
+    return labelKey ? [labelKey, label] : undefined;
+}
+/**
+ * The automatic legend's own section titles — text stamped onto the chart the
+ * moment the legend is built, like any other seed, and declared HERE because
+ * the rows that file themselves under them are subscribed by the commands
+ * below. The box title itself is not one of them: it says the shared word
+ * "Legend" and reuses `BOARD_LEGEND_TITLE`.
+ *
+ * Three sub-titles for a framework whose ten commands all sit in ONE category:
+ * `section` is what keeps them, and in particular the one that explains the
+ * C/X/F letters (`docs/adr/0026`).
+ */
+export const CORE_DOMAIN_SEED_LEGEND_SUBDOMAINS = [
+    'com.labre.ddd-core-domain.seed.legend-subdomains',
+    'Sub-domains',
+];
+export const CORE_DOMAIN_SEED_LEGEND_TEAM_MODES = [
+    'com.labre.ddd-core-domain.seed.legend-team-modes',
+    'Team interaction modes',
+];
+export const CORE_DOMAIN_SEED_LEGEND_MOVEMENT = [
+    'com.labre.ddd-core-domain.seed.legend-movement',
+    'Movement',
+];
 /**
  * The Core Domain Chart palette as commands: the background, the five
  * sub-domain dots, the three Team Topologies markers and the movement arrow.
@@ -32,13 +70,22 @@ const SPECS = [
         icon: dotSwatch(preset.fill),
         run: std => placeDddElement(std, (surface, cx, cy) => addDot(surface, std, cx, cy, preset.fill, 
         // Translated HERE and once: the caption is document content the
-        // moment it lands (ADR 0016), so the host's catalogue is asked at
+        // moment it lands (ADR 0023), so the host's catalogue is asked at
         // placement and never again.
         translateKey(std, cdSubdomainSeedKey(preset.kind), preset.label), 
         // The dot IS the sub-domain: the role rides on the ellipse, so a
         // rule about where a sub-domain sits measures the artefact and not
         // the group that also holds its name.
         subdomainRole(preset.kind))),
+        // Row and command out of the SAME preset, which also keeps this list and
+        // `core-domain.off-legend-colour` naming the same five colours by
+        // construction.
+        legend: {
+            role: subdomainRole(preset.kind),
+            section: CORE_DOMAIN_SEED_LEGEND_SUBDOMAINS,
+            labelWording: subdomainWording(subdomainRole(preset.kind), preset.label),
+            row: { swatch: 'dot', color: preset.fill },
+        },
     })),
     ...TEAM_TOPOLOGIES.map((preset) => ({
         id: `add${preset.kind[0].toUpperCase()}${preset.kind.slice(1)}`,
@@ -50,7 +97,7 @@ const SPECS = [
             fill: preset.fill,
             letter: preset.letter,
             // Translated HERE and once: the caption is document content the
-            // moment it lands (ADR 0016), so the host's catalogue is asked at
+            // moment it lands (ADR 0023), so the host's catalogue is asked at
             // placement and never again.
             label: translateKey(std, teamTopologySeedKey(preset.kind), preset.label),
             // The square IS the marker, so the role rides on it and not on the
@@ -59,6 +106,14 @@ const SPECS = [
             // by role, could not see the markers at all.
             role: markerRole(preset.kind),
         })),
+        // The LETTER is what identifies a marker on the chart — the squares are
+        // three colours a reader has no key to — so the row shows the same square
+        // with the same letter in it, from the same preset the palette draws with.
+        legend: {
+            role: markerRole(preset.kind),
+            section: CORE_DOMAIN_SEED_LEGEND_TEAM_MODES,
+            row: { swatch: 'square', color: preset.fill, letter: preset.letter },
+        },
     })),
     {
         id: 'addMovement',
@@ -66,17 +121,25 @@ const SPECS = [
         iconKey: 'ddd-core-domain.movement',
         // Historical telemetry value, unchanged by the gesture becoming a drag.
         element: 'movement',
+        kind: 'tool',
         icon: movementSwatch,
         // No longer a free arrow dropped at the viewport centre: the movement is a
         // typed edge, so the user draws it from the current position to the future
         // one and the pair they drew IS the statement (`docs/adr/0010`).
         run: activateMovement,
+        legend: {
+            role: CORE_DOMAIN_ROLE.movement,
+            section: CORE_DOMAIN_SEED_LEGEND_MOVEMENT,
+            // The style `activateMovement` arms the connector tool with: a red dashed
+            // line.
+            row: { swatch: 'line', color: MOVEMENT_COLOR, dashed: true },
+        },
     },
 ];
 export const coreDomainCommands = SPECS.map((spec, order) => ({
     id: `ddd-core-domain.${spec.id}`,
     owner: 'ddd-core-domain',
-    kind: 'artefact',
+    kind: spec.kind ?? 'artefact',
     labelKey: `com.labre.commands.ddd-core-domain.${spec.id}`,
     labelFallback: spec.label,
     category: 'chart',
@@ -92,5 +155,11 @@ export const coreDomainCommands = SPECS.map((spec, order) => ({
         element: spec.element,
         board: spec.board,
     },
+    legend: spec.legend,
 }));
-export const coreDomainCommandIcons = Object.fromEntries(SPECS.map(spec => [spec.iconKey, spec.icon]));
+export const coreDomainCommandIcons = {
+    ...Object.fromEntries(SPECS.map(spec => [spec.iconKey, spec.icon])),
+    // The senior button's 56×56 glyph, so `FrameworkDescriptor.iconKey` resolves
+    // through `getCommandIcon`.
+    'ddd-core-domain.toolbar': coreDomainToolbarIcon,
+};

package/dist/core-domain/background.js

@@ -94,10 +94,20 @@ const MIGRATION_TEXT = {
     weight: 700,
     color: '@zoneLabelDark',
 };
-/** A centred zone name, gated by `showLabels` like every other word on the chart. */
-function zoneLabel(id, key, fallback, x, y, style) {
+/**
+ * A centred zone name, gated by `showLabels` like every other word on the chart.
+ *
+ * `prop` is what makes it RENAMABLE (issue #355): the model prop the in-place
+ * editor writes to, which `backgroundLabelText` reads BEFORE the catalogue — so
+ * a chart the user has renamed keeps their words, and every other chart keeps
+ * the vocabulary in whatever language the host serves it. The id and the prop
+ * are deliberately two strings: the id names a piece of this declaration, the
+ * prop names a key in somebody's document, and only the first may ever change.
+ */
+function zoneLabel(id, prop, key, fallback, x, y, style) {
     return {
         id,
+        prop,
         labelKey: `com.labre.core-domain.background.zone.${key}`,
         fallback,
         anchor: { x: rx(x), y: ry(y) },
@@ -127,7 +137,7 @@ const CLASSIC_ZONES = [
         rect: { x: rx(70), y: ry(30), w: rw(150), h: rh(720) },
         fill: '@zoneGeneric',
         fillVisibleProp: 'showZones',
-        label: zoneLabel('generic', 'generic', 'Generic', 150, 474, ZONE_TEXT),
+        label: zoneLabel('generic', 'zoneGeneric', 'generic', 'Generic', 150, 474, ZONE_TEXT),
     },
     {
         id: 'supporting-low-diff',
@@ -135,7 +145,7 @@ const CLASSIC_ZONES = [
         rect: { x: rx(220), y: ry(30), w: rw(220), h: rh(720) },
         fill: '@zoneSupporting',
         fillVisibleProp: 'showZones',
-        label: zoneLabel('supporting', 'supporting', 'Supporting', 340, 474, ZONE_TEXT),
+        label: zoneLabel('supporting', 'zoneSupporting', 'supporting', 'Supporting', 340, 474, ZONE_TEXT),
     },
     {
         id: 'core',
@@ -143,7 +153,7 @@ const CLASSIC_ZONES = [
         rect: { x: rx(440), y: ry(30), w: rw(400), h: rh(360) },
         fill: '@zoneCore',
         fillVisibleProp: 'showZones',
-        label: zoneLabel('core', 'core', 'Core', 640, 214, CORE_TEXT),
+        label: zoneLabel('core', 'zoneCore', 'core', 'Core', 640, 214, CORE_TEXT),
     },
     {
         // The template tints this one and writes nothing on it, so neither does the
@@ -173,6 +183,7 @@ const MIGRATION_ZONES = [
         fillVisibleProp: 'showZones',
         label: {
             id: 'lastToothpaste',
+            prop: 'zoneLastToothpaste',
             labelKey: 'com.labre.core-domain.background.zone.last-toothpaste',
             fallback: 'Last toothpaste',
             anchor: { x: 0.25, y: 0.25 },
@@ -189,6 +200,7 @@ const MIGRATION_ZONES = [
         fillVisibleProp: 'showZones',
         label: {
             id: 'riskSeeking',
+            prop: 'zoneRiskSeeking',
             labelKey: 'com.labre.core-domain.background.zone.risk-seeking',
             fallback: 'Risk-seeking',
             anchor: { x: 0.75, y: 0.25 },
@@ -205,6 +217,7 @@ const MIGRATION_ZONES = [
         fillVisibleProp: 'showZones',
         label: {
             id: 'riskAverse',
+            prop: 'zoneRiskAverse',
             labelKey: 'com.labre.core-domain.background.zone.risk-averse',
             fallback: 'Risk-averse',
             anchor: { x: 0.25, y: 0.75 },
@@ -221,6 +234,7 @@ const MIGRATION_ZONES = [
         fillVisibleProp: 'showZones',
         label: {
             id: 'lowHangingFruit',
+            prop: 'zoneLowHangingFruit',
             labelKey: 'com.labre.core-domain.background.zone.lhf',
             fallback: 'Low-hanging fruit',
             anchor: { x: 0.75, y: 0.75 },
@@ -254,6 +268,7 @@ const CORE_DOMAIN_AXES = [
         stroke: { color: '@axis', width: 2 },
         title: {
             id: 'complexityTitle',
+            prop: 'complexityTitle',
             // The classic reading's vertical axis. The migration one relabels it —
             // see `MIGRATION_AXIS_TITLE` below, and why it rides in `endLabels`.
             variants: ['classic'],
@@ -267,6 +282,7 @@ const CORE_DOMAIN_AXES = [
         endLabels: [
             {
                 id: 'complexityLow',
+                prop: 'complexityLow',
                 labelKey: 'com.labre.core-domain.background.complexity.low',
                 fallback: 'Low',
                 anchor: { x: 0, y: ry(758), dx: -12 },
@@ -276,6 +292,7 @@ const CORE_DOMAIN_AXES = [
             },
             {
                 id: 'complexityHigh',
+                prop: 'complexityHigh',
                 labelKey: 'com.labre.core-domain.background.complexity.high',
                 fallback: 'High',
                 anchor: { x: 0, y: ry(44), dx: -22 },
@@ -295,6 +312,7 @@ const CORE_DOMAIN_AXES = [
              */
             {
                 id: 'complexityTitleMigration',
+                prop: 'migrationCostTitle',
                 variants: ['migration'],
                 labelKey: 'com.labre.core-domain.background.axis.migration-cost',
                 fallback: 'Cost of migration',
@@ -314,6 +332,7 @@ const CORE_DOMAIN_AXES = [
         stroke: { color: '@axis', width: 2 },
         title: {
             id: 'differentiationTitle',
+            prop: 'differentiationTitle',
             labelKey: 'com.labre.core-domain.background.axis.differentiation',
             fallback: 'Business differentiation',
             anchor: { x: rx(450), y: 1, dy: 30 },
@@ -324,6 +343,7 @@ const CORE_DOMAIN_AXES = [
         endLabels: [
             {
                 id: 'differentiationLow',
+                prop: 'differentiationLow',
                 labelKey: 'com.labre.core-domain.background.differentiation.low',
                 fallback: 'Low',
                 anchor: { x: rx(84), y: 1, dy: 22 },
@@ -333,6 +353,7 @@ const CORE_DOMAIN_AXES = [
             },
             {
                 id: 'differentiationHigh',
+                prop: 'differentiationHigh',
                 labelKey: 'com.labre.core-domain.background.differentiation.high',
                 fallback: 'High',
                 anchor: { x: rx(838), y: 1, dy: 22 },

package/dist/core-domain/element-view.d.ts

@@ -1,11 +1,20 @@
+import type { FrameworkBackgroundDef } from '@formicoidea/labre-core/blocks/surface';
+import { DeclaredBackgroundView } from '@formicoidea/labre-core/blocks/surface';
 import type { CoreDomainChartElementModel } from '@formicoidea/labre-core/model';
-import { GfxElementModelView } from '@formicoidea/labre-core/std/gfx';
 /**
  * View for the Core Domain Chart background. Registering it ensures
  * `gfx.view.get(model)` returns a view (required so move / select work).
+ *
+ * Extends {@link DeclaredBackgroundView}, so every word the chart writes on
+ * itself — the two axis titles, the four Low/High ticks and the zone names of
+ * both readings — is renamed in place by a double-click, aimed by the very
+ * declaration the renderer paints (issue #355). The chart had no such gesture
+ * before, which is the whole of the bug: the labels were i18n keys and nothing
+ * else, so a team that calls its axis something else had nowhere to say so.
  */
-export declare class CoreDomainView extends GfxElementModelView<CoreDomainChartElementModel> {
+export declare class CoreDomainView extends DeclaredBackgroundView<CoreDomainChartElementModel> {
     static type: string;
+    protected get def(): FrameworkBackgroundDef;
 }
 /**
  * Resize gating, driven by the declaration: the handles are offered while

package/dist/core-domain/element-view.js

@@ -1,12 +1,21 @@
-import { FrameworkBackgroundInteractionExtension } from '@formicoidea/labre-core/blocks/surface';
-import { GfxElementModelView } from '@formicoidea/labre-core/std/gfx';
+import { DeclaredBackgroundView, FrameworkBackgroundInteractionExtension, } from '@formicoidea/labre-core/blocks/surface';
 import { CORE_DOMAIN_BACKGROUND } from './background.js';
 /**
  * View for the Core Domain Chart background. Registering it ensures
  * `gfx.view.get(model)` returns a view (required so move / select work).
+ *
+ * Extends {@link DeclaredBackgroundView}, so every word the chart writes on
+ * itself — the two axis titles, the four Low/High ticks and the zone names of
+ * both readings — is renamed in place by a double-click, aimed by the very
+ * declaration the renderer paints (issue #355). The chart had no such gesture
+ * before, which is the whole of the bug: the labels were i18n keys and nothing
+ * else, so a team that calls its axis something else had nowhere to say so.
  */
-export class CoreDomainView extends GfxElementModelView {
+export class CoreDomainView extends DeclaredBackgroundView {
     static { this.type = 'coreDomain'; }
+    get def() {
+        return CORE_DOMAIN_BACKGROUND;
+    }
 }
 /**
  * Resize gating, driven by the declaration: the handles are offered while

package/dist/core-domain/toolbar-config.d.ts

@@ -1 +1,22 @@
-export declare const coreDomainToolbarExtension: import("@formicoidea/labre-core/store").ExtensionType;
+import type { ToolbarModuleConfig } from '@formicoidea/labre-core/shared/services';
+/**
+ * The selected chart's FLAG-GATED row, whole: the legend button and the
+ * Validation dropdown, in one module.
+ *
+ * They cannot be two, and that is a hard constraint rather than a preference:
+ * `ToolbarModuleExtension` binds by DI variant, so a second module claiming
+ * `custom:affine:surface:coreDomain` throws `DuplicateServiceDefinitionError`
+ * before the editor finishes setting up. The C4 board's own row was merged this
+ * way first (`c4BoardToolingToolbarConfig`).
+ *
+ * The chart has no always-on row left at all: the legend was its only entry, and
+ * generating one is a gesture the `ddd-core-domain` flag may take away
+ * (`docs/adr/0026`) — while what the gesture already WROTE is document content,
+ * painted by the always-on renderers whatever the flag says. A stored chart with
+ * the flag off keeps its elements, its handles and its legend boxes; it simply
+ * offers no button.
+ *
+ * The rows themselves are derived from `coreDomainCommands` — this module writes
+ * no table.
+ */
+export declare const coreDomainChartToolingToolbarConfig: ToolbarModuleConfig;

package/dist/core-domain/toolbar-config.js

@@ -1,39 +1,43 @@
-import { createAutoLegend, dddLegendIcon } from '@formicoidea/labre-ddd-shared';
+import { legendToolbarAction, validationToolbarConfig, } from '@formicoidea/labre-core/blocks/surface';
 import { CoreDomainChartElementModel } from '@formicoidea/labre-core/model';
-import { BOARD_LEGEND_NOTATION, TelemetryProvider, ToolbarModuleExtension, } from '@formicoidea/labre-core/shared/services';
-import { BlockFlavourIdentifier } from '@formicoidea/labre-core/std';
-import { CORE_DOMAIN_AUTO_LEGEND } from './legend.js';
-/** Contextual toolbar for a selected Core Domain background: insert its legend. */
-const coreDomainToolbarConfig = {
+/**
+ * The selected chart's FLAG-GATED row, whole: the legend button and the
+ * Validation dropdown, in one module.
+ *
+ * They cannot be two, and that is a hard constraint rather than a preference:
+ * `ToolbarModuleExtension` binds by DI variant, so a second module claiming
+ * `custom:affine:surface:coreDomain` throws `DuplicateServiceDefinitionError`
+ * before the editor finishes setting up. The C4 board's own row was merged this
+ * way first (`c4BoardToolingToolbarConfig`).
+ *
+ * The chart has no always-on row left at all: the legend was its only entry, and
+ * generating one is a gesture the `ddd-core-domain` flag may take away
+ * (`docs/adr/0026`) — while what the gesture already WROTE is document content,
+ * painted by the always-on renderers whatever the flag says. A stored chart with
+ * the flag off keeps its elements, its handles and its legend boxes; it simply
+ * offers no button.
+ *
+ * The rows themselves are derived from `coreDomainCommands` — this module writes
+ * no table.
+ */
+export const coreDomainChartToolingToolbarConfig = {
     actions: [
-        {
+        legendToolbarAction({
+            // FIRST in the row, as it has been since the chart's legend button
+            // shipped: the toolbar sorts lexicographically by id.
             id: 'a.legend',
-            tooltipWording: BOARD_LEGEND_NOTATION,
-            icon: dddLegendIcon,
-            run(ctx) {
-                const bg = ctx.getSurfaceModelsByType(CoreDomainChartElementModel)[0];
-                if (!bg)
-                    return;
-                createAutoLegend(ctx.std, bg, CORE_DOMAIN_AUTO_LEGEND);
-                ctx.std
-                    .getOptional(TelemetryProvider)
-                    ?.track('FrameworkLegendCreated', {
-                    // The WIRE value, which is not the module id: the framework is
-                    // `ddd-core-domain` in code and `core-domain` in PostHog
-                    // (`frameworks.ts` `telemetryKey`). Unchanged by this rework — the
-                    // button is the same gesture, it just detects by role now.
-                    framework: 'core-domain',
-                    element: 'legend',
-                    page: 'whiteboard editor',
-                    segment: 'element toolbar',
-                    module: 'core-domain toolbar',
-                });
-            },
-        },
+            Model: CoreDomainChartElementModel,
+            owner: 'ddd-core-domain',
+            // The WIRE value, which is not the module id: the framework is
+            // `ddd-core-domain` in code and `core-domain` in PostHog
+            // (`frameworks.ts` `telemetryKey`). Unchanged by the button becoming
+            // shared.
+            framework: 'core-domain',
+        }),
+        // The generic dropdown, not a Core Domain variant of it: the config names no
+        // framework — it reads the registered rules and profiles — so this is the
+        // very same object c4, wardley and bpmn register.
+        ...validationToolbarConfig.actions,
     ],
-    when: ctx => ctx.getSurfaceModelsByType(CoreDomainChartElementModel).length > 0,
+    when: (ctx) => ctx.getSurfaceModelsByType(CoreDomainChartElementModel).length > 0,
 };
-export const coreDomainToolbarExtension = ToolbarModuleExtension({
-    id: BlockFlavourIdentifier('affine:surface:coreDomain'),
-    config: coreDomainToolbarConfig,
-});

package/dist/toolbar/palette.d.ts

@@ -0,0 +1,31 @@
+import type { FrameworkPalette, NamedPalette } from '@formicoidea/labre-core/components/color-picker';
+import type { ChromeWording } from '@formicoidea/labre-core/shared/services';
+/**
+ * The Core Domain Chart swatches' own names, resolved by `resolvePaletteLabel`
+ * (`@labre/affine-components/color-picker`) through each swatch's own
+ * {@link NamedPalette.labelWording} — the mechanism `WARDLEY_PALETTE_WORDINGS`
+ * established, reused here without either package naming the other.
+ *
+ * Exported so `../translations.ts` can list them under source `chrome`: a
+ * swatch's name is toolbar chrome, never seeded into a document. The keys are
+ * this framework's own even though the colours come from `ddd-shared`, which
+ * declares no `com.labre.*` key of its own by design (see its header).
+ */
+export declare const CORE_DOMAIN_PALETTE_WORDING_BIG_BET: ChromeWording;
+export declare const CORE_DOMAIN_PALETTE_WORDING_PLATFORM: ChromeWording;
+export declare const CORE_DOMAIN_PALETTE_WORDING_OUTSOURCED: ChromeWording;
+export declare const CORE_DOMAIN_PALETTE_WORDING_BC_CURRENT: ChromeWording;
+export declare const CORE_DOMAIN_PALETTE_WORDING_BC_FUTURE: ChromeWording;
+export declare const CORE_DOMAIN_PALETTE_WORDINGS: readonly ChromeWording[];
+/**
+ * From the default editor palette we keep ONLY the neutrals — the historical
+ * colours say nothing in this notation.
+ */
+export declare const CORE_DOMAIN_PALETTE_LIST: NamedPalette[];
+/**
+ * The Core Domain Chart's page of the colour pickers' carousel
+ * (`docs/adr/0027`). Registered from the FLAG-GATED view extension, because
+ * offering hues is TOOLING: a chart drawn while the flag was on keeps every
+ * colour it was painted with when the flag goes off (`docs/adr/0009`).
+ */
+export declare const CORE_DOMAIN_FRAMEWORK_PALETTE: FrameworkPalette;

package/dist/toolbar/palette.js

@@ -0,0 +1,104 @@
+import { CD_SUBDOMAINS } from '@formicoidea/labre-ddd-shared';
+import { neutralPalettes } from '@formicoidea/labre-core/gfx/shape';
+/**
+ * The Core Domain Chart swatches' own names, resolved by `resolvePaletteLabel`
+ * (`@labre/affine-components/color-picker`) through each swatch's own
+ * {@link NamedPalette.labelWording} — the mechanism `WARDLEY_PALETTE_WORDINGS`
+ * established, reused here without either package naming the other.
+ *
+ * Exported so `../translations.ts` can list them under source `chrome`: a
+ * swatch's name is toolbar chrome, never seeded into a document. The keys are
+ * this framework's own even though the colours come from `ddd-shared`, which
+ * declares no `com.labre.*` key of its own by design (see its header).
+ */
+export const CORE_DOMAIN_PALETTE_WORDING_BIG_BET = [
+    'com.labre.ddd-core-domain.palette.big-bet-purple',
+    'Big-bet purple',
+];
+export const CORE_DOMAIN_PALETTE_WORDING_PLATFORM = [
+    'com.labre.ddd-core-domain.palette.platform-blue',
+    'Platform blue',
+];
+export const CORE_DOMAIN_PALETTE_WORDING_OUTSOURCED = [
+    'com.labre.ddd-core-domain.palette.outsourced-green',
+    'Outsourced green',
+];
+export const CORE_DOMAIN_PALETTE_WORDING_BC_CURRENT = [
+    'com.labre.ddd-core-domain.palette.bounded-context-red',
+    'Bounded context red',
+];
+export const CORE_DOMAIN_PALETTE_WORDING_BC_FUTURE = [
+    'com.labre.ddd-core-domain.palette.future-position-grey',
+    'Future position grey',
+];
+export const CORE_DOMAIN_PALETTE_WORDINGS = [
+    CORE_DOMAIN_PALETTE_WORDING_BIG_BET,
+    CORE_DOMAIN_PALETTE_WORDING_PLATFORM,
+    CORE_DOMAIN_PALETTE_WORDING_OUTSOURCED,
+    CORE_DOMAIN_PALETTE_WORDING_BC_CURRENT,
+    CORE_DOMAIN_PALETTE_WORDING_BC_FUTURE,
+];
+/**
+ * The sub-domain / bounded-context dot fills, by kind — derived from
+ * {@link CD_SUBDOMAINS} rather than restated.
+ */
+const CD_FILL = Object.fromEntries(CD_SUBDOMAINS.map(subdomain => [subdomain.kind, subdomain.fill]));
+/**
+ * The Core Domain Chart's own five hues: the three sub-domain classes
+ * (big-bet, platform, outsourced), the bounded context as it stands today, and
+ * the grey it is plotted in where it is meant to go next.
+ *
+ * The movement arrow between those last two is drawn in `MOVEMENT_COLOR`,
+ * which IS the current bounded context's red — one statement in one colour —
+ * so it contributes no sixth swatch. `__tests__/palette.unit.spec.ts` pins the
+ * two together, so the day they part the shelf gains its swatch.
+ *
+ * They are SHORTCUTS, never constraints: a dot's class is written in its role,
+ * not read off its fill.
+ */
+const CORE_DOMAIN_PALETTES = [
+    {
+        key: 'Big-bet purple',
+        value: CD_FILL.bigBet,
+        labelWording: CORE_DOMAIN_PALETTE_WORDING_BIG_BET,
+    },
+    {
+        key: 'Platform blue',
+        value: CD_FILL.platform,
+        labelWording: CORE_DOMAIN_PALETTE_WORDING_PLATFORM,
+    },
+    {
+        key: 'Outsourced green',
+        value: CD_FILL.outsourced,
+        labelWording: CORE_DOMAIN_PALETTE_WORDING_OUTSOURCED,
+    },
+    {
+        key: 'Bounded context red',
+        value: CD_FILL.bcCurrent,
+        labelWording: CORE_DOMAIN_PALETTE_WORDING_BC_CURRENT,
+    },
+    {
+        key: 'Future position grey',
+        value: CD_FILL.bcFuture,
+        labelWording: CORE_DOMAIN_PALETTE_WORDING_BC_FUTURE,
+    },
+];
+/**
+ * From the default editor palette we keep ONLY the neutrals — the historical
+ * colours say nothing in this notation.
+ */
+export const CORE_DOMAIN_PALETTE_LIST = [
+    ...CORE_DOMAIN_PALETTES,
+    ...neutralPalettes(),
+];
+/**
+ * The Core Domain Chart's page of the colour pickers' carousel
+ * (`docs/adr/0027`). Registered from the FLAG-GATED view extension, because
+ * offering hues is TOOLING: a chart drawn while the flag was on keeps every
+ * colour it was painted with when the flag goes off (`docs/adr/0009`).
+ */
+export const CORE_DOMAIN_FRAMEWORK_PALETTE = {
+    framework: 'ddd-core-domain',
+    labelWording: ['com.labre.framework.ddd-core-domain', 'Core Domain Chart'],
+    palettes: CORE_DOMAIN_PALETTE_LIST,
+};

package/dist/toolbar/senior-button.d.ts

@@ -4,4 +4,5 @@ export declare class EdgelessDddCoreDomainSeniorButton extends DddSeniorButtonBa
     protected label: string;
     protected labelKey: string;
     protected icon: import("lit-html").TemplateResult<2>;
+    protected owner: "ddd-core-domain";
 }

package/dist/toolbar/senior-button.js

@@ -6,5 +6,6 @@ export class EdgelessDddCoreDomainSeniorButton extends DddSeniorButtonBase {
         this.label = 'Core Domain Chart';
         this.labelKey = 'com.labre.framework.ddd-core-domain';
         this.icon = coreDomainToolbarIcon;
+        this.owner = 'ddd-core-domain';
     }
 }

package/dist/translations.d.ts

@@ -1,15 +1,4 @@
-import type { ChromeWording } from '@formicoidea/labre-core/shared/services';
 import { type TranslationKeyManifestEntry } from '@formicoidea/labre-core/std';
-/**
- * The automatic legend's own section titles (`core-domain/legend.ts`) — text
- * stamped onto the chart the moment the legend is built
- * (`createAutoLegend`), like any other seed. The box title itself is NOT
- * here: it says the shared word "Legend", so it reuses `BOARD_LEGEND_TITLE`
- * (`@labre/affine-shared/services`) instead of a key of its own.
- */
-export declare const CORE_DOMAIN_SEED_LEGEND_SUBDOMAINS: ChromeWording;
-export declare const CORE_DOMAIN_SEED_LEGEND_TEAM_MODES: ChromeWording;
-export declare const CORE_DOMAIN_SEED_LEGEND_MOVEMENT: ChromeWording;
 /**
  * THIS framework's contribution to the translation-key manifest — every
  * `com.labre.*` key the Core Domain Chart can hand to `TranslationProvider.t`,

package/dist/translations.js

@@ -1,31 +1,13 @@
 import { dddSharedTranslationEntries } from '@formicoidea/labre-ddd-shared';
 import { collectTranslationKeys, commandCategoryTranslationEntries, commandTranslationEntries, mergeTranslationEntries, } from '@formicoidea/labre-core/std';
-import { coreDomainCommands } from './commands.js';
+import { CORE_DOMAIN_SEED_LEGEND_MOVEMENT, CORE_DOMAIN_SEED_LEGEND_SUBDOMAINS, CORE_DOMAIN_SEED_LEGEND_TEAM_MODES, coreDomainCommands, } from './commands.js';
 import { CORE_DOMAIN_BACKGROUND } from './core-domain/background.js';
 import { CORE_DOMAIN_NUDGES } from './nudges.js';
 import { CORE_DOMAIN_PROFILES } from './profiles.js';
 import { CORE_DOMAIN_READINGS } from './reading.js';
 import { CORE_DOMAIN_ROLES } from './roles.js';
 import { CORE_DOMAIN_RULES } from './rules.js';
-/**
- * The automatic legend's own section titles (`core-domain/legend.ts`) — text
- * stamped onto the chart the moment the legend is built
- * (`createAutoLegend`), like any other seed. The box title itself is NOT
- * here: it says the shared word "Legend", so it reuses `BOARD_LEGEND_TITLE`
- * (`@labre/affine-shared/services`) instead of a key of its own.
- */
-export const CORE_DOMAIN_SEED_LEGEND_SUBDOMAINS = [
-    'com.labre.ddd-core-domain.seed.legend-subdomains',
-    'Sub-domains',
-];
-export const CORE_DOMAIN_SEED_LEGEND_TEAM_MODES = [
-    'com.labre.ddd-core-domain.seed.legend-team-modes',
-    'Team interaction modes',
-];
-export const CORE_DOMAIN_SEED_LEGEND_MOVEMENT = [
-    'com.labre.ddd-core-domain.seed.legend-movement',
-    'Movement',
-];
+import { CORE_DOMAIN_PALETTE_WORDINGS } from './toolbar/palette.js';
 /**
  * THIS framework's contribution to the translation-key manifest — every
  * `com.labre.*` key the Core Domain Chart can hand to `TranslationProvider.t`,
@@ -58,4 +40,12 @@ dddSharedTranslationEntries, [
     CORE_DOMAIN_SEED_LEGEND_SUBDOMAINS,
     CORE_DOMAIN_SEED_LEGEND_TEAM_MODES,
     CORE_DOMAIN_SEED_LEGEND_MOVEMENT,
-].map(([key, fallback]) => ({ key, fallback, source: 'seed' })));
+].map(([key, fallback]) => ({ key, fallback, source: 'seed' })), 
+// The carousel swatches' own names (`toolbar/palette.ts`) — chrome,
+// re-rendered by the colour picker on every locale switch, never seeded
+// into a document. Same treatment as Wardley's and EDGY's.
+CORE_DOMAIN_PALETTE_WORDINGS.map(([key, fallback]) => ({
+    key,
+    fallback,
+    source: 'chrome',
+})));

package/dist/view.d.ts

@@ -1,10 +1,13 @@
 import { type ViewExtensionContext, ViewExtensionProvider } from '@formicoidea/labre-core/ext-loader';
 /**
  * Core Domain Chart rendering — ALWAYS registered, independent of any flag.
- * Disabling `ddd-core-domain` hides only the senior toolbar button (see
+ * Disabling `ddd-core-domain` hides only the tooling (see
  * {@link DddCoreDomainViewExtension}); placed `coreDomain` elements must still
- * paint, stay selectable, and keep their contextual toolbar, and Templates-
- * panel insertion must still render them.
+ * paint, stay selectable and stay movable, and Templates-panel insertion must
+ * still render them.
+ *
+ * The chart claims no always-on toolbar module: the legend button was its only
+ * contextual entry and it moved to the gated half (`docs/adr/0026`).
  */
 export declare class DddCoreDomainRenderViewExtension extends ViewExtensionProvider {
     name: string;

package/dist/view.js

@@ -1,4 +1,5 @@
-import { morphToolbarConfig, QualityNudgeExtension, ReadingProfileExtension, validationToolbarConfig, ValidationProfileExtension, ValidationRuleExtension, } from '@formicoidea/labre-core/blocks/surface';
+import { morphToolbarConfig, QualityNudgeExtension, ReadingProfileExtension, ValidationProfileExtension, ValidationRuleExtension, } from '@formicoidea/labre-core/blocks/surface';
+import { FrameworkPaletteExtension } from '@formicoidea/labre-core/components/color-picker';
 import { ViewExtensionProvider, } from '@formicoidea/labre-core/ext-loader';
 import { ToolbarModuleExtension, toolbarModuleKey, } from '@formicoidea/labre-core/shared/services';
 import { TemplateCategoryExtension } from '@formicoidea/labre-core/gfx/template';
@@ -8,7 +9,7 @@ import { coreDomainCommandIcons, coreDomainCommands } from './commands.js';
 import { coreDomainTemplateCategory } from './templates.js';
 import { CoreDomainRendererExtension } from './core-domain/element-renderer.js';
 import { CoreDomainInteraction, CoreDomainView, } from './core-domain/element-view.js';
-import { coreDomainToolbarExtension } from './core-domain/toolbar-config.js';
+import { coreDomainChartToolingToolbarConfig } from './core-domain/toolbar-config.js';
 import { coreDomainEffects } from './effects.js';
 import { CORE_DOMAIN_MORPH_SPEC } from './morph.js';
 import { CORE_DOMAIN_NUDGES } from './nudges.js';
@@ -16,13 +17,17 @@ import { CORE_DOMAIN_PROFILES } from './profiles.js';
 import { CORE_DOMAIN_READINGS } from './reading.js';
 import { CORE_DOMAIN_ROLES } from './roles.js';
 import { CORE_DOMAIN_RULES } from './rules.js';
+import { CORE_DOMAIN_FRAMEWORK_PALETTE } from './toolbar/palette.js';
 import { coreDomainSeniorTool } from './toolbar/senior-tool.js';
 /**
  * Core Domain Chart rendering — ALWAYS registered, independent of any flag.
- * Disabling `ddd-core-domain` hides only the senior toolbar button (see
+ * Disabling `ddd-core-domain` hides only the tooling (see
  * {@link DddCoreDomainViewExtension}); placed `coreDomain` elements must still
- * paint, stay selectable, and keep their contextual toolbar, and Templates-
- * panel insertion must still render them.
+ * paint, stay selectable and stay movable, and Templates-panel insertion must
+ * still render them.
+ *
+ * The chart claims no always-on toolbar module: the legend button was its only
+ * contextual entry and it moved to the gated half (`docs/adr/0026`).
  */
 export class DddCoreDomainRenderViewExtension extends ViewExtensionProvider {
     constructor() {
@@ -42,7 +47,6 @@ export class DddCoreDomainRenderViewExtension extends ViewExtensionProvider {
         context.register(RoleVocabularyExtension(CORE_DOMAIN_ROLES));
         if (this.isEdgeless(context.scope)) {
             context.register(CoreDomainInteraction);
-            context.register(coreDomainToolbarExtension);
         }
     }
 }
@@ -68,16 +72,13 @@ export class DddCoreDomainViewExtension extends ViewExtensionProvider {
             context.register(ValidationRuleExtension(CORE_DOMAIN_RULES));
             context.register(ValidationProfileExtension(CORE_DOMAIN_PROFILES));
             context.register(QualityNudgeExtension(CORE_DOMAIN_NUDGES));
-            // The Validation dropdown on a selected chart's contextual toolbar. A
-            // SECOND module on the same element, through the `custom:` flavour slot:
-            // `coreDomainToolbarExtension` is registered always-on because a stored
-            // chart must keep its legend action, while choosing how hard to check it
-            // is tooling and belongs here. The config itself names no framework — it
-            // reads roles and profiles — so it is the very same object Wardley
-            // registers on its own flavour.
+            // The chart's WHOLE contextual row — the Legend button and the Validation
+            // dropdown, merged into ONE module because a flavour may carry exactly one
+            // (`core-domain/toolbar-config.ts`). Both are tooling: with the flag off a
+            // stored chart keeps everything drawn on it and simply offers no button.
             context.register(ToolbarModuleExtension({
                 id: BlockFlavourIdentifier('custom:affine:surface:coreDomain'),
-                config: validationToolbarConfig,
+                config: coreDomainChartToolingToolbarConfig,
             }));
             // The reversed reading (MF3): what the chart says about an artefact, on
             // demand. Two profiles, because the vocabulary has two disjoint node
@@ -88,6 +89,11 @@ export class DddCoreDomainViewExtension extends ViewExtensionProvider {
                 context.register(ReadingProfileExtension(reading));
             }
             context.register(coreDomainSeniorTool);
+            // The Core Domain Chart's page of the colour pickers' carousel
+            // (`docs/adr/0027`). Here, beside the senior tool, because offering hues
+            // is TOOLING — the colours already painted on a stored chart are content
+            // and do not move (`docs/adr/0009`).
+            context.register(FrameworkPaletteExtension(CORE_DOMAIN_FRAMEWORK_PALETTE));
             // The Templates-panel category, gated by this framework's own flag like
             // every other framework's: a template is tooling (`docs/adr/0009`), and it
             // is DERIVED from this package's commands, so it registers where they do.

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@formicoidea/labre-framework-ddd-core-domain",
   "description": "Labre ddd-core-domain framework for @formicoidea/labre-core.",
-  "version": "0.41.0",
+  "version": "0.42.0",
   "type": "module",
   "sideEffects": false,
   "author": "lajola",
@@ -31,8 +31,8 @@
     "dist"
   ],
   "dependencies": {
-    "@formicoidea/labre-core": "0.41.0",
-    "@formicoidea/labre-ddd-shared": "0.41.0",
+    "@formicoidea/labre-core": "0.42.0",
+    "@formicoidea/labre-ddd-shared": "0.42.0",
     "lit": "^3.2.0"
   }
 }

package/dist/core-domain/legend.d.ts

@@ -1,29 +0,0 @@
-import { type AutoLegendSpec } from '@formicoidea/labre-ddd-shared';
-/**
- * What the Core Domain Chart's automatic legend can say — a TABLE, and nothing
- * else: the scan, the placement and the box are `createAutoLegend`'s job.
- *
- * Every row is DERIVED from the presets the palette draws its dots with
- * ({@link CD_SUBDOMAINS}) and from the role vocabulary's own labels, never
- * restated — which also keeps this table and `core-domain.off-legend-colour`
- * naming the same five colours by construction.
- *
- * ## What changed
- *
- * The chart's legend button predates roles: until now it scanned the perimeter
- * for FILL COLOURS, which is why it fell back to the full notation when it
- * recognised nothing. Detection is now by role, like every other reader of the
- * board, with one consequence worth stating: a chart on which nothing is
- * recognised yields a legend box with a title and no rows, rather than the whole
- * notation. That is Wardley's behaviour and the honest one — a legend lists what
- * is drawn, not what could have been.
- *
- * The **Team Topologies markers** were the casualty of that change for one
- * release: `addMarker` stamped no role, so a chart covered in them produced a
- * legend that mentioned none (PO recette, 26/08/2026). They now carry
- * `core-domain:marker-*` and their section is here, derived from
- * `TEAM_TOPOLOGIES` like everything else — swatch, letter and colour from the
- * preset the palette draws with, wording from the vocabulary that names the
- * role.
- */
-export declare const CORE_DOMAIN_AUTO_LEGEND: AutoLegendSpec;

package/dist/core-domain/legend.js

@@ -1,84 +0,0 @@
-import { CD_SUBDOMAINS, MOVEMENT_COLOR, roleLabel, TEAM_TOPOLOGIES, } from '@formicoidea/labre-ddd-shared';
-import { BOARD_LEGEND_TITLE } from '@formicoidea/labre-core/shared/services';
-import { CORE_DOMAIN_ROLE, CORE_DOMAIN_ROLES } from '../roles.js';
-import { CORE_DOMAIN_SEED_LEGEND_MOVEMENT, CORE_DOMAIN_SEED_LEGEND_SUBDOMAINS, CORE_DOMAIN_SEED_LEGEND_TEAM_MODES, } from '../translations.js';
-/**
- * What the Core Domain Chart's automatic legend can say — a TABLE, and nothing
- * else: the scan, the placement and the box are `createAutoLegend`'s job.
- *
- * Every row is DERIVED from the presets the palette draws its dots with
- * ({@link CD_SUBDOMAINS}) and from the role vocabulary's own labels, never
- * restated — which also keeps this table and `core-domain.off-legend-colour`
- * naming the same five colours by construction.
- *
- * ## What changed
- *
- * The chart's legend button predates roles: until now it scanned the perimeter
- * for FILL COLOURS, which is why it fell back to the full notation when it
- * recognised nothing. Detection is now by role, like every other reader of the
- * board, with one consequence worth stating: a chart on which nothing is
- * recognised yields a legend box with a title and no rows, rather than the whole
- * notation. That is Wardley's behaviour and the honest one — a legend lists what
- * is drawn, not what could have been.
- *
- * The **Team Topologies markers** were the casualty of that change for one
- * release: `addMarker` stamped no role, so a chart covered in them produced a
- * legend that mentioned none (PO recette, 26/08/2026). They now carry
- * `core-domain:marker-*` and their section is here, derived from
- * `TEAM_TOPOLOGIES` like everything else — swatch, letter and colour from the
- * preset the palette draws with, wording from the vocabulary that names the
- * role.
- */
-export const CORE_DOMAIN_AUTO_LEGEND = {
-    title: BOARD_LEGEND_TITLE[1],
-    titleKey: BOARD_LEGEND_TITLE[0],
-    roles: CORE_DOMAIN_ROLES,
-    sections: [
-        {
-            title: CORE_DOMAIN_SEED_LEGEND_SUBDOMAINS[1],
-            titleKey: CORE_DOMAIN_SEED_LEGEND_SUBDOMAINS[0],
-            entries: CD_SUBDOMAINS.map(preset => ({
-                role: CORE_DOMAIN_ROLE[preset.kind],
-                row: {
-                    swatch: 'dot',
-                    color: preset.fill,
-                    label: preset.label,
-                },
-            })),
-        },
-        {
-            // The letter is what identifies a marker on the chart — the squares are
-            // three colours a reader has no key to — so the legend shows the same
-            // square with the same letter in it, which is what `LegendRow.letter`
-            // exists for.
-            title: CORE_DOMAIN_SEED_LEGEND_TEAM_MODES[1],
-            titleKey: CORE_DOMAIN_SEED_LEGEND_TEAM_MODES[0],
-            entries: TEAM_TOPOLOGIES.map(preset => ({
-                role: CORE_DOMAIN_ROLE[preset.kind],
-                row: {
-                    swatch: 'square',
-                    color: preset.fill,
-                    letter: preset.letter,
-                    label: roleLabel(CORE_DOMAIN_ROLES, CORE_DOMAIN_ROLE[preset.kind]),
-                },
-            })),
-        },
-        {
-            title: CORE_DOMAIN_SEED_LEGEND_MOVEMENT[1],
-            titleKey: CORE_DOMAIN_SEED_LEGEND_MOVEMENT[0],
-            entries: [
-                {
-                    role: CORE_DOMAIN_ROLE.movement,
-                    row: {
-                        swatch: 'line',
-                        // The style `activateMovement` arms the connector tool with: a red
-                        // dashed line.
-                        color: MOVEMENT_COLOR,
-                        dashed: true,
-                        label: roleLabel(CORE_DOMAIN_ROLES, CORE_DOMAIN_ROLE.movement),
-                    },
-                },
-            ],
-        },
-    ],
-};