@formicoidea/labre-framework-ddd-event-storming 0.36.0 → 0.37.0

package/dist/index.d.ts

@@ -10,3 +10,4 @@ export { eventStormingTemplateCategory } from './templates.js';
 export { eventStormingSeniorTool } from './toolbar/senior-tool.js';
 export { EdgelessDddEventStormingSeniorButton } from './toolbar/senior-button.js';
 export { DddEventStormingRenderViewExtension, DddEventStormingViewExtension, } from './view.js';
+export { EVENT_STORMING_READING } from './reading.js';

package/dist/index.js

@@ -13,3 +13,4 @@ export { eventStormingTemplateCategory } from './templates.js';
 export { eventStormingSeniorTool } from './toolbar/senior-tool.js';
 export { EdgelessDddEventStormingSeniorButton } from './toolbar/senior-button.js';
 export { DddEventStormingRenderViewExtension, DddEventStormingViewExtension, } from './view.js';
+export { EVENT_STORMING_READING } from './reading.js';

package/dist/reading.d.ts

@@ -0,0 +1,33 @@
+import type { ReadingProfile } from '@formicoidea/labre-core/blocks/surface';
+/**
+ * What an Event Storming board lets the tool read of a sticky (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 Event Storming. Everything below is already stated in
+ * `roles.ts` and is merely POINTED AT here.
+ *
+ * Registered from the FLAG-GATED view extension: reading a board is tooling, so
+ * a roll whose flag is off keeps every sticky it has and simply stops being read
+ * (ADR 0009).
+ *
+ * ## One subject, nine kinds
+ *
+ * `es:sticky` is the parent of all nine, so one profile reads them all and the
+ * panel's type line says which ("Domain event › Sticky"). The board is the
+ * FRAME and specialises nothing, exactly so that what is written about the
+ * stickies never falls on the roll they are stuck to.
+ *
+ * The two kinds outside the grammar — the hotspot and the constraint — are read
+ * like the other seven, and deliberately: being outside `es.forbidden-arc`'s
+ * alphabet means no rule judges them, not that nobody may ask what they are.
+ *
+ * ## No nature, no phase
+ *
+ * The framework ships no type-3 tag pack: the nine kinds ARE the roles. And the
+ * roll's timeline is a direction the FLOW states, not a set of declared zones a
+ * position could be read against — `es.against-timeline` reads the edge, and so
+ * does the section below.
+ */
+export declare const EVENT_STORMING_READING: ReadingProfile;

package/dist/reading.js

@@ -0,0 +1,54 @@
+import { ES_ROLE, EVENT_STORMING_ROLES } from './roles.js';
+/**
+ * What an Event Storming board lets the tool read of a sticky (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 Event Storming. Everything below is already stated in
+ * `roles.ts` and is merely POINTED AT here.
+ *
+ * Registered from the FLAG-GATED view extension: reading a board is tooling, so
+ * a roll whose flag is off keeps every sticky it has and simply stops being read
+ * (ADR 0009).
+ *
+ * ## One subject, nine kinds
+ *
+ * `es:sticky` is the parent of all nine, so one profile reads them all and the
+ * panel's type line says which ("Domain event › Sticky"). The board is the
+ * FRAME and specialises nothing, exactly so that what is written about the
+ * stickies never falls on the roll they are stuck to.
+ *
+ * The two kinds outside the grammar — the hotspot and the constraint — are read
+ * like the other seven, and deliberately: being outside `es.forbidden-arc`'s
+ * alphabet means no rule judges them, not that nobody may ask what they are.
+ *
+ * ## No nature, no phase
+ *
+ * The framework ships no type-3 tag pack: the nine kinds ARE the roles. And the
+ * roll's timeline is a direction the FLOW states, not a set of declared zones a
+ * position could be read against — `es.against-timeline` reads the edge, and so
+ * does the section below.
+ */
+export const EVENT_STORMING_READING = {
+    id: 'event-storming',
+    framework: 'ddd-event-storming',
+    roles: EVENT_STORMING_ROLES,
+    appliesTo: ES_ROLE.sticky,
+    relation: {
+        edgeRole: ES_ROLE.flow,
+        // ADR 0010 tier 2 on this role: the verb is "leads to", so the SOURCE is
+        // what happens FIRST. An edge leaving the subject names what follows it,
+        // one arriving names what it follows.
+        sides: {
+            consumer: {
+                labelKey: 'com.labre.event-storming.reading.relations.consumer',
+                labelFallback: 'Follows',
+            },
+            supplier: {
+                labelKey: 'com.labre.event-storming.reading.relations.supplier',
+                labelFallback: 'Leads to',
+            },
+        },
+    },
+};

package/dist/translations.js

@@ -3,6 +3,7 @@ import { EVENT_STORMING_BACKGROUND } from './background.js';
 import { eventStormingCommands } from './commands.js';
 import { EVENT_STORMING_NUDGES } from './nudges.js';
 import { EVENT_STORMING_PROFILES } from './profiles.js';
+import { EVENT_STORMING_READING } from './reading.js';
 import { EVENT_STORMING_ROLES } from './roles.js';
 import { EVENT_STORMING_RULES } from './rules.js';
 /**
@@ -25,4 +26,9 @@ export const eventStormingTranslationEntries = mergeTranslationEntries(commandTr
 // 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(eventStormingCommands), collectTranslationKeys('role', EVENT_STORMING_ROLES), collectTranslationKeys('background', EVENT_STORMING_BACKGROUND), collectTranslationKeys('rule', EVENT_STORMING_RULES), collectTranslationKeys('nudge', EVENT_STORMING_NUDGES), collectTranslationKeys('profile', EVENT_STORMING_PROFILES));
+commandCategoryTranslationEntries(eventStormingCommands), collectTranslationKeys('role', EVENT_STORMING_ROLES), collectTranslationKeys('background', EVENT_STORMING_BACKGROUND), collectTranslationKeys('rule', EVENT_STORMING_RULES), collectTranslationKeys('nudge', EVENT_STORMING_NUDGES), collectTranslationKeys('profile', EVENT_STORMING_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', EVENT_STORMING_READING));

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';
@@ -10,6 +10,7 @@ import { EventStormingInteraction, EventStormingView } from './element-view.js';
 import { EVENT_STORMING_MORPH_SPEC } from './morph.js';
 import { EVENT_STORMING_NUDGES } from './nudges.js';
 import { EVENT_STORMING_PROFILES } from './profiles.js';
+import { EVENT_STORMING_READING } from './reading.js';
 import { EVENT_STORMING_ROLES } from './roles.js';
 import { EVENT_STORMING_RULES } from './rules.js';
 import { eventStormingBoardToolbarExtension } from './toolbar/board-config.js';
@@ -81,6 +82,12 @@ export class DddEventStormingViewExtension extends ViewExtensionProvider {
                 id: BlockFlavourIdentifier('custom:affine:surface:eventStorming'),
                 config: validationToolbarConfig,
             }));
+            // The reversed reading (MF3): what the board says about a sticky, on
+            // demand. One declaration — the roles and the flow 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(EVENT_STORMING_READING));
             context.register(eventStormingSeniorTool);
             context.register(CommandExtension(eventStormingCommands, eventStormingCommandIcons));
             // The "Change type" dropdown on a selected STICKY's contextual toolbar —

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@formicoidea/labre-framework-ddd-event-storming",
   "description": "Labre ddd-event-storming framework for @formicoidea/labre-core.",
-  "version": "0.36.0",
+  "version": "0.37.0",
   "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.37.0",
+    "@formicoidea/labre-ddd-shared": "0.37.0",
     "lit": "^3.2.0"
   }
 }