@formicoidea/labre-framework-ddd-core-domain 0.35.0 → 0.37.0

package/dist/commands.js

@@ -18,6 +18,7 @@ const SPECS = [
         label: 'Core Domain Chart',
         iconKey: 'ddd-core-domain.chart',
         element: 'background',
+        board: true,
         icon: chartSwatch,
         run: std => placeDddElement(std, (surface, cx, cy) => createCoreDomainChart(surface, cx, cy)),
     },
@@ -77,6 +78,10 @@ export const coreDomainCommands = SPECS.map((spec, order) => ({
     defaultKeys: { mac: [], other: [] },
     availability: 'always',
     run: spec.run,
-    telemetry: { framework: 'ddd-core-domain', element: spec.element },
+    telemetry: {
+        framework: 'ddd-core-domain',
+        element: spec.element,
+        board: spec.board,
+    },
 }));
 export const coreDomainCommandIcons = Object.fromEntries(SPECS.map(spec => [spec.iconKey, spec.icon]));

package/dist/index.d.ts

@@ -12,3 +12,4 @@ export { coreDomainTemplateCategory } from './templates.js';
 export { coreDomainSeniorTool } from './toolbar/senior-tool.js';
 export { EdgelessDddCoreDomainSeniorButton } from './toolbar/senior-button.js';
 export { DddCoreDomainRenderViewExtension, DddCoreDomainViewExtension, } from './view.js';
+export { CORE_DOMAIN_MARKER_READING, CORE_DOMAIN_READING, CORE_DOMAIN_READINGS, } from './reading.js';

package/dist/index.js

@@ -15,3 +15,4 @@ export { coreDomainTemplateCategory } from './templates.js';
 export { coreDomainSeniorTool } from './toolbar/senior-tool.js';
 export { EdgelessDddCoreDomainSeniorButton } from './toolbar/senior-button.js';
 export { DddCoreDomainRenderViewExtension, DddCoreDomainViewExtension, } from './view.js';
+export { CORE_DOMAIN_MARKER_READING, CORE_DOMAIN_READING, CORE_DOMAIN_READINGS, } from './reading.js';

package/dist/reading.d.ts

@@ -0,0 +1,51 @@
+import type { ReadingProfile } from '@formicoidea/labre-core/blocks/surface';
+/**
+ * What a Core Domain Chart lets the tool read (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 this framework. Everything below is already stated in
+ * `roles.ts` and is merely POINTED AT here.
+ *
+ * Registered from the FLAG-GATED view extension: reading a chart is tooling, so
+ * a chart whose flag is off keeps every element it has and simply stops being
+ * read (ADR 0009).
+ *
+ * ## TWO profiles, because the vocabulary has two disjoint node families
+ *
+ * `roles.ts` makes the split deliberately: a sub-domain is a thing PLOTTED at a
+ * (differentiation, complexity) position, a Team Topologies marker is an
+ * annotation about how work flows between teams. Neither specialises the other,
+ * so neither `appliesTo` can cover both — and giving them a common parent would
+ * mean minting a role the notation does not have, which ADR 0007 forbids.
+ *
+ * The chart itself is the FRAME and is not read.
+ *
+ * ## No nature, no phase
+ *
+ * The framework ships no type-3 tag pack: the five dot presets ARE roles, and
+ * the panel says them on the type line with the chain above them ("Platform
+ * sub-domain › Sub-domain"). And the chart's two axes are a plane, not a set of
+ * declared zones with ids — reading a phase off it would be an invented fact, so
+ * the section is absent rather than empty. A follow-up ticket covers the
+ * variant-scoped 2D zones the engine would need.
+ */
+/**
+ * The dots: the five presets, and the two bounded-context positions.
+ *
+ * The MOVEMENT is the only typed edge on this board. ADR 0010 tier 2 on that
+ * role: the verb is "is moving to", so the SOURCE is where the context stands
+ * today and the TARGET where it is headed — an edge leaving the subject names
+ * where it goes, one arriving names where it came from.
+ */
+export declare const CORE_DOMAIN_READING: ReadingProfile;
+/**
+ * The Team Topologies markers.
+ *
+ * No relation: a movement runs between two positions of a bounded context, and
+ * `core-domain.malformed-movement` is written on exactly that. A marker is what
+ * the chart SAYS about an interaction, not a thing that moves.
+ */
+export declare const CORE_DOMAIN_MARKER_READING: ReadingProfile;
+/** Both profiles, in the order the view extension registers them. */
+export declare const CORE_DOMAIN_READINGS: readonly ReadingProfile[];

package/dist/reading.js

@@ -0,0 +1,77 @@
+import { CORE_DOMAIN_ROLE, CORE_DOMAIN_ROLES } from './roles.js';
+/**
+ * What a Core Domain Chart lets the tool read (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 this framework. Everything below is already stated in
+ * `roles.ts` and is merely POINTED AT here.
+ *
+ * Registered from the FLAG-GATED view extension: reading a chart is tooling, so
+ * a chart whose flag is off keeps every element it has and simply stops being
+ * read (ADR 0009).
+ *
+ * ## TWO profiles, because the vocabulary has two disjoint node families
+ *
+ * `roles.ts` makes the split deliberately: a sub-domain is a thing PLOTTED at a
+ * (differentiation, complexity) position, a Team Topologies marker is an
+ * annotation about how work flows between teams. Neither specialises the other,
+ * so neither `appliesTo` can cover both — and giving them a common parent would
+ * mean minting a role the notation does not have, which ADR 0007 forbids.
+ *
+ * The chart itself is the FRAME and is not read.
+ *
+ * ## No nature, no phase
+ *
+ * The framework ships no type-3 tag pack: the five dot presets ARE roles, and
+ * the panel says them on the type line with the chain above them ("Platform
+ * sub-domain › Sub-domain"). And the chart's two axes are a plane, not a set of
+ * declared zones with ids — reading a phase off it would be an invented fact, so
+ * the section is absent rather than empty. A follow-up ticket covers the
+ * variant-scoped 2D zones the engine would need.
+ */
+/**
+ * The dots: the five presets, and the two bounded-context positions.
+ *
+ * The MOVEMENT is the only typed edge on this board. ADR 0010 tier 2 on that
+ * role: the verb is "is moving to", so the SOURCE is where the context stands
+ * today and the TARGET where it is headed — an edge leaving the subject names
+ * where it goes, one arriving names where it came from.
+ */
+export const CORE_DOMAIN_READING = {
+    id: 'core-domain',
+    framework: 'ddd-core-domain',
+    roles: CORE_DOMAIN_ROLES,
+    appliesTo: CORE_DOMAIN_ROLE.subdomain,
+    relation: {
+        edgeRole: CORE_DOMAIN_ROLE.movement,
+        sides: {
+            consumer: {
+                labelKey: 'com.labre.core-domain.reading.relations.consumer',
+                labelFallback: 'Moved from',
+            },
+            supplier: {
+                labelKey: 'com.labre.core-domain.reading.relations.supplier',
+                labelFallback: 'Moves to',
+            },
+        },
+    },
+};
+/**
+ * The Team Topologies markers.
+ *
+ * No relation: a movement runs between two positions of a bounded context, and
+ * `core-domain.malformed-movement` is written on exactly that. A marker is what
+ * the chart SAYS about an interaction, not a thing that moves.
+ */
+export const CORE_DOMAIN_MARKER_READING = {
+    id: 'core-domain-marker',
+    framework: 'ddd-core-domain',
+    roles: CORE_DOMAIN_ROLES,
+    appliesTo: CORE_DOMAIN_ROLE.marker,
+};
+/** Both profiles, in the order the view extension registers them. */
+export const CORE_DOMAIN_READINGS = [
+    CORE_DOMAIN_READING,
+    CORE_DOMAIN_MARKER_READING,
+];

package/dist/translations.js

@@ -3,6 +3,7 @@ import { 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';
 /**
@@ -23,4 +24,9 @@ export const coreDomainTranslationEntries = 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(coreDomainCommands), collectTranslationKeys('role', CORE_DOMAIN_ROLES), collectTranslationKeys('background', CORE_DOMAIN_BACKGROUND), collectTranslationKeys('rule', CORE_DOMAIN_RULES), collectTranslationKeys('nudge', CORE_DOMAIN_NUDGES), collectTranslationKeys('profile', CORE_DOMAIN_PROFILES));
+commandCategoryTranslationEntries(coreDomainCommands), collectTranslationKeys('role', CORE_DOMAIN_ROLES), collectTranslationKeys('background', CORE_DOMAIN_BACKGROUND), collectTranslationKeys('rule', CORE_DOMAIN_RULES), collectTranslationKeys('nudge', CORE_DOMAIN_NUDGES), collectTranslationKeys('profile', CORE_DOMAIN_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', CORE_DOMAIN_READINGS));

package/dist/view.js

@@ -1,4 +1,4 @@
-import { morphToolbarConfig, QualityNudgeExtension, validationToolbarConfig, ValidationProfileExtension, ValidationRuleExtension, } from '@formicoidea/labre-core/blocks/surface';
+import { morphToolbarConfig, QualityNudgeExtension, ReadingProfileExtension, validationToolbarConfig, ValidationProfileExtension, ValidationRuleExtension, } from '@formicoidea/labre-core/blocks/surface';
 import { ViewExtensionProvider, } from '@formicoidea/labre-core/ext-loader';
 import { ToolbarModuleExtension, toolbarModuleKey, } from '@formicoidea/labre-core/shared/services';
 import { BlockFlavourIdentifier, CommandExtension } from '@formicoidea/labre-core/std';
@@ -11,6 +11,7 @@ import { coreDomainEffects } from './effects.js';
 import { CORE_DOMAIN_MORPH_SPEC } from './morph.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';
 import { coreDomainSeniorTool } from './toolbar/senior-tool.js';
@@ -78,6 +79,14 @@ export class DddCoreDomainViewExtension extends ViewExtensionProvider {
                 id: BlockFlavourIdentifier('custom:affine:surface:coreDomain'),
                 config: validationToolbarConfig,
             }));
+            // The reversed reading (MF3): what the chart says about an artefact, on
+            // demand. Two profiles, because the vocabulary has two disjoint node
+            // families and neither may inherit the other's rules (`reading.ts`). The
+            // CLICK that triggers it is registered once by the surface and gated by
+            // the presence of a profile.
+            for (const reading of CORE_DOMAIN_READINGS) {
+                context.register(ReadingProfileExtension(reading));
+            }
             context.register(coreDomainSeniorTool);
             context.register(CommandExtension(coreDomainCommands, coreDomainCommandIcons));
             // The "Change type" dropdown on a selected dot's or marker's contextual

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.35.0",
+  "version": "0.37.0",
   "type": "module",
   "sideEffects": false,
   "author": "lajola",
@@ -31,8 +31,8 @@
     "dist"
   ],
   "dependencies": {
-    "@formicoidea/labre-core": "0.35.0",
-    "@formicoidea/labre-ddd-shared": "0.35.0",
+    "@formicoidea/labre-core": "0.37.0",
+    "@formicoidea/labre-ddd-shared": "0.37.0",
     "lit": "^3.2.0"
   }
 }