@formicoidea/labre-framework-ddd-context-map 0.36.0 → 0.38.1

package/dist/index.d.ts

@@ -9,3 +9,4 @@ export { contextMapTemplateCategory } from './templates.js';
 export { contextMapSeniorTool } from './toolbar/senior-tool.js';
 export { EdgelessDddContextMapSeniorButton } from './toolbar/senior-button.js';
 export { DddContextMapRenderViewExtension, DddContextMapViewExtension, } from './view.js';
+export { CONTEXT_MAP_READING } from './reading.js';

package/dist/index.js

@@ -9,3 +9,4 @@ export { contextMapTemplateCategory } from './templates.js';
 export { contextMapSeniorTool } from './toolbar/senior-tool.js';
 export { EdgelessDddContextMapSeniorButton } from './toolbar/senior-button.js';
 export { DddContextMapRenderViewExtension, DddContextMapViewExtension, } from './view.js';
+export { CONTEXT_MAP_READING } from './reading.js';

package/dist/reading.d.ts

@@ -0,0 +1,36 @@
+import type { ReadingProfile } from '@formicoidea/labre-core/blocks/surface';
+/**
+ * What a Context Map lets the tool read of a bounded context (MF3, the reversed
+ * reading).
+ *
+ * DATA, like the rules and the profiles beside it: the engine
+ * (`@labre/affine-block-surface`) knows how to read a role and a typed edge — it
+ * knows nothing about context mapping. Everything below is already stated in
+ * `roles.ts` and is merely POINTED AT here.
+ *
+ * Registered from the FLAG-GATED view extension: reading a map is tooling, so a
+ * board whose flag is off keeps every element it has and simply stops being read
+ * (ADR 0009).
+ *
+ * ## One subject, and the board is not it
+ *
+ * `context-map:context` is the only artefact this notation places; the board is
+ * the FRAME and specialises nothing, exactly so that what is written about the
+ * contexts never falls on the card they sit on.
+ *
+ * ## The nine patterns are read through their parent
+ *
+ * `appliesTo` on the relation is `context-map:relationship`, and the nine DDD
+ * Crew patterns specialise it — so `roleIsA` reaches every one of them without
+ * this file naming a single pattern. The four SYMMETRIC ones (Partnership,
+ * Shared Kernel, Separate Ways, Big Ball of Mud) declare no `direction`, and the
+ * panel still lists them under whichever side the drawing put them on: that is
+ * not a claim about upstream and downstream, it is where the link happens to
+ * start. The asymmetry is the notation's, and `roles.ts` is where it is argued.
+ *
+ * ## No nature, no phase
+ *
+ * The framework ships no type-3 tag pack, and the board declares no zones a
+ * position could be read against.
+ */
+export declare const CONTEXT_MAP_READING: ReadingProfile;

package/dist/reading.js

@@ -0,0 +1,57 @@
+import { CONTEXT_MAP_ROLE, CONTEXT_MAP_ROLES } from './roles.js';
+/**
+ * What a Context Map lets the tool read of a bounded context (MF3, the reversed
+ * reading).
+ *
+ * DATA, like the rules and the profiles beside it: the engine
+ * (`@labre/affine-block-surface`) knows how to read a role and a typed edge — it
+ * knows nothing about context mapping. Everything below is already stated in
+ * `roles.ts` and is merely POINTED AT here.
+ *
+ * Registered from the FLAG-GATED view extension: reading a map is tooling, so a
+ * board whose flag is off keeps every element it has and simply stops being read
+ * (ADR 0009).
+ *
+ * ## One subject, and the board is not it
+ *
+ * `context-map:context` is the only artefact this notation places; the board is
+ * the FRAME and specialises nothing, exactly so that what is written about the
+ * contexts never falls on the card they sit on.
+ *
+ * ## The nine patterns are read through their parent
+ *
+ * `appliesTo` on the relation is `context-map:relationship`, and the nine DDD
+ * Crew patterns specialise it — so `roleIsA` reaches every one of them without
+ * this file naming a single pattern. The four SYMMETRIC ones (Partnership,
+ * Shared Kernel, Separate Ways, Big Ball of Mud) declare no `direction`, and the
+ * panel still lists them under whichever side the drawing put them on: that is
+ * not a claim about upstream and downstream, it is where the link happens to
+ * start. The asymmetry is the notation's, and `roles.ts` is where it is argued.
+ *
+ * ## No nature, no phase
+ *
+ * The framework ships no type-3 tag pack, and the board declares no zones a
+ * position could be read against.
+ */
+export const CONTEXT_MAP_READING = {
+    id: 'context-map',
+    framework: 'ddd-context-map',
+    roles: CONTEXT_MAP_ROLES,
+    appliesTo: CONTEXT_MAP_ROLE.context,
+    relation: {
+        edgeRole: CONTEXT_MAP_ROLE.relationship,
+        // The DDD Crew wording, verbatim, and the direction `roles.ts` declares:
+        // the SOURCE is the upstream context. So an edge leaving the subject names
+        // what is downstream of it, and one arriving names what it is downstream of.
+        sides: {
+            consumer: {
+                labelKey: 'com.labre.ddd-context-map.reading.relations.consumer',
+                labelFallback: 'Upstream',
+            },
+            supplier: {
+                labelKey: 'com.labre.ddd-context-map.reading.relations.supplier',
+                labelFallback: 'Downstream',
+            },
+        },
+    },
+};

package/dist/templates.d.ts

@@ -1,6 +1,2 @@
-/**
- * Context Map Templates-panel category. The builder lives in the shared package
- * so the aggregate package can register all DDD categories under the single
- * `ddd-templates` flag; re-exported here for a stable per-package API.
- */
-export { contextMapTemplateCategory } from '@formicoidea/labre-ddd-shared';
+import { type TemplateCategory } from '@formicoidea/labre-core/gfx/template';
+export declare const contextMapTemplateCategory: TemplateCategory;

package/dist/templates.js

@@ -1,6 +1,37 @@
+import { CLOUD, CM_BUBBLE } from '@formicoidea/labre-ddd-shared';
+import { templateFromCommand, } from '@formicoidea/labre-core/gfx/template';
+import { contextMapCommands } from './commands.js';
 /**
- * Context Map Templates-panel category. The builder lives in the shared package
- * so the aggregate package can register all DDD categories under the single
- * `ddd-templates` flag; re-exported here for a stable per-package API.
+ * The Context Map palette — DERIVED from the toolbox, one template per
+ * placement command.
+ *
+ * It used to be hand-written surface JSON in `ddd-shared`, untouched since
+ * 2026-06-21: the bubble carried neither `context-map:context` nor its overflow
+ * fit mode, the cloud's name was text stored on the polygon instead of the
+ * grouped label the prefab writes, there was no board template, and NINE of the
+ * eleven entries were free-floating connectors — the drawing WS2 removed from
+ * the toolbox (`docs/adr/0010`). Those nine are gone: their commands arm the
+ * connector tool, so there is no artefact to record and the user draws the
+ * relation between two real contexts.
  */
-export { contextMapTemplateCategory } from '@formicoidea/labre-ddd-shared';
+/** The command a derived template is the picture of. Throws rather than skips. */
+function byLabel(label) {
+    const command = contextMapCommands.find(entry => entry.labelFallback === label);
+    if (!command) {
+        throw new Error(`[ddd-context-map] templates: no command "${label}"`);
+    }
+    return command;
+}
+const ATTRS = 'width="100%" height="100%" viewBox="0 0 135 80" xmlns="http://www.w3.org/2000/svg"';
+/** The map, in miniature: a white card, two contexts and the line between them. */
+const BOARD_PREVIEW = `<svg ${ATTRS} fill="none"><rect x="4" y="6" width="127" height="68" rx="6" fill="#ffffff" stroke="#d5d9e0" stroke-width="1.5"/><rect x="18" y="20" width="44" height="18" rx="9" fill="${CM_BUBBLE.fill}" stroke="${CM_BUBBLE.stroke}" stroke-width="1.5"/><rect x="74" y="44" width="44" height="18" rx="9" fill="${CM_BUBBLE.fill}" stroke="${CM_BUBBLE.stroke}" stroke-width="1.5"/><path d="M62 33 L76 48" stroke="#1f2328" stroke-width="1.5"/></svg>`;
+const BUBBLE_PREVIEW = `<svg ${ATTRS} fill="none"><rect x="20" y="25" width="95" height="30" rx="15" fill="${CM_BUBBLE.fill}" stroke="${CM_BUBBLE.stroke}" stroke-width="1.6"/></svg>`;
+const CLOUD_PREVIEW = `<svg ${ATTRS} fill="none"><path d="M30 52 C18 52 16 40 26 37 C24 25 42 24 46 32 C50 22 70 24 70 35 C84 32 90 46 78 50 Z" fill="${CLOUD.fill}" stroke="${CLOUD.stroke}" stroke-width="1.4"/></svg>`;
+export const contextMapTemplateCategory = {
+    name: 'Context Map',
+    templates: [
+        templateFromCommand(byLabel('Context Map board'), BOARD_PREVIEW, 'Context Map board'),
+        templateFromCommand(byLabel('Bounded Context'), BUBBLE_PREVIEW, 'Context Map — Bounded Context'),
+        templateFromCommand(byLabel('Cloud / System (Big Ball of Mud)'), CLOUD_PREVIEW, 'Context Map — Cloud / System'),
+    ],
+};

package/dist/translations.js

@@ -3,6 +3,7 @@ import { CONTEXT_MAP_BACKGROUND } from './background.js';
 import { contextMapCommands } from './commands.js';
 import { CONTEXT_MAP_NUDGES } from './nudges.js';
 import { CONTEXT_MAP_PROFILES } from './profiles.js';
+import { CONTEXT_MAP_READING } from './reading.js';
 import { CONTEXT_MAP_ROLES } from './roles.js';
 import { CONTEXT_MAP_RULES } from './rules.js';
 /**
@@ -23,4 +24,9 @@ export const contextMapTranslationEntries = mergeTranslationEntries(commandTrans
 // registry names no framework category in the bundled distribution, so a
 // host that composed core's manifest alone drew translated entries under
 // English headers (#183).
-commandCategoryTranslationEntries(contextMapCommands), collectTranslationKeys('role', CONTEXT_MAP_ROLES), collectTranslationKeys('background', CONTEXT_MAP_BACKGROUND), collectTranslationKeys('rule', CONTEXT_MAP_RULES), collectTranslationKeys('nudge', CONTEXT_MAP_NUDGES), collectTranslationKeys('profile', CONTEXT_MAP_PROFILES));
+commandCategoryTranslationEntries(contextMapCommands), collectTranslationKeys('role', CONTEXT_MAP_ROLES), collectTranslationKeys('background', CONTEXT_MAP_BACKGROUND), collectTranslationKeys('rule', CONTEXT_MAP_RULES), collectTranslationKeys('nudge', CONTEXT_MAP_NUDGES), collectTranslationKeys('profile', CONTEXT_MAP_PROFILES), 
+// LAST, and the order is load-bearing: a reading profile carries the
+// framework's own `roles`, so walking it reaches every role key the `role`
+// line above already named. `mergeTranslationEntries` keeps the FIRST
+// occurrence, which is what makes each key report the source it comes from.
+collectTranslationKeys('reading', CONTEXT_MAP_READING));

package/dist/view.d.ts

@@ -19,8 +19,7 @@ export declare class DddContextMapRenderViewExtension extends ViewExtensionProvi
  * flag comes back.
  *
  * Note: its Templates-panel category is registered by the aggregate package's
- * {@link DddTemplatesViewExtension} (gated by `ddd-templates`), so templates
- * stay available even when this senior button is disabled.
+ * The Templates-panel category is registered here too (see `effect`).
  */
 export declare class DddContextMapViewExtension extends ViewExtensionProvider {
     name: string;

package/dist/view.js

@@ -1,14 +1,17 @@
-import { QualityNudgeExtension, validationToolbarConfig, ValidationProfileExtension, ValidationRuleExtension, } from '@formicoidea/labre-core/blocks/surface';
+import { QualityNudgeExtension, ReadingProfileExtension, validationToolbarConfig, ValidationProfileExtension, ValidationRuleExtension, } from '@formicoidea/labre-core/blocks/surface';
 import { ViewExtensionProvider, } from '@formicoidea/labre-core/ext-loader';
 import { ToolbarModuleExtension } from '@formicoidea/labre-core/shared/services';
+import { extendTemplateCategory } from '@formicoidea/labre-core/gfx/template';
 import { BlockFlavourIdentifier, CommandExtension } from '@formicoidea/labre-core/std';
 import { RoleVocabularyExtension } from '@formicoidea/labre-core/std/gfx';
 import { contextMapCommandIcons, contextMapCommands } from './commands.js';
+import { contextMapTemplateCategory } from './templates.js';
 import { contextMapEffects } from './effects.js';
 import { ContextMapRendererExtension } from './element-renderer.js';
 import { ContextMapInteraction, ContextMapView } from './element-view.js';
 import { CONTEXT_MAP_NUDGES } from './nudges.js';
 import { CONTEXT_MAP_PROFILES } from './profiles.js';
+import { CONTEXT_MAP_READING } from './reading.js';
 import { CONTEXT_MAP_ROLES } from './roles.js';
 import { CONTEXT_MAP_RULES } from './rules.js';
 import { contextMapBoardToolbarExtension } from './toolbar/board-config.js';
@@ -51,8 +54,7 @@ export class DddContextMapRenderViewExtension extends ViewExtensionProvider {
  * flag comes back.
  *
  * Note: its Templates-panel category is registered by the aggregate package's
- * {@link DddTemplatesViewExtension} (gated by `ddd-templates`), so templates
- * stay available even when this senior button is disabled.
+ * The Templates-panel category is registered here too (see `effect`).
  */
 export class DddContextMapViewExtension extends ViewExtensionProvider {
     constructor() {
@@ -62,6 +64,10 @@ export class DddContextMapViewExtension extends ViewExtensionProvider {
     effect() {
         super.effect();
         contextMapEffects();
+        // 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.
+        extendTemplateCategory(contextMapTemplateCategory);
     }
     setup(context) {
         super.setup(context);
@@ -80,6 +86,12 @@ export class DddContextMapViewExtension extends ViewExtensionProvider {
                 id: BlockFlavourIdentifier('custom:affine:surface:contextMap'),
                 config: validationToolbarConfig,
             }));
+            // The reversed reading (MF3): what the map says about a bounded context,
+            // on demand. One declaration — the roles and the relationship edge, both
+            // already stated elsewhere in this framework. The CLICK that triggers it
+            // is registered once by the surface and gated by the presence of this
+            // profile, so it goes with the flag without either side naming the other.
+            context.register(ReadingProfileExtension(CONTEXT_MAP_READING));
             context.register(contextMapSeniorTool);
             context.register(CommandExtension(contextMapCommands, contextMapCommandIcons));
         }

package/package.json

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