@formicoidea/labre-framework-edgy 0.32.0 → 0.34.1

package/dist/metamodel.js

@@ -0,0 +1,128 @@
+/**
+ * The EDGY metamodel, as DATA — the 12 official elements and the 24 canonical
+ * relations that link them.
+ *
+ * It used to live in `templates/index.ts`, where it was drawn. It moved here
+ * the day the roles started being DERIVED from it (`./roles.ts`): the template
+ * needs the vocabulary to stamp its elements, and the vocabulary needs the
+ * metamodel to know which verbs exist, so a single module holding both would be
+ * a cycle. Nothing was renamed — `templates/index.ts` re-exports both tables
+ * under the names they always had.
+ *
+ * This file is the ONE place the metamodel is written down. `roles.ts` derives
+ * an edge role per verb from it, `rules.ts` derives the sanctioned sentences of
+ * `edgy.non-canonical-link` from it, and the template draws it. Restating the
+ * matrix anywhere else would be inviting the three to disagree.
+ */
+/**
+ * Official pastel fills per zone (the `pictograms/Shape-*.svg` colors) — the
+ * colour an element of that zone is DRAWN with, on the diagram and therefore in
+ * the legend that documents it.
+ *
+ * Exported because the legend needs the same swatch the board uses: a swatch
+ * restated as a second literal would be a colour free to drift away from the
+ * one the eye sees.
+ */
+export const EDGY_ZONE_FILL = {
+    identity: '#80ffb7',
+    architecture: '#a6c0ff',
+    experience: '#ff99bd',
+    organisation: '#80eaff',
+    brand: '#ffd580',
+    product: '#e599ff',
+};
+/**
+ * The six zones, in reading order — the three FACETS first, then the three
+ * INTERSECTIONS, each named by the pair of circles it is the lens of (the very
+ * pairs `element-renderer.ts` clips: A∩B, B∩C, A∩C).
+ *
+ * Written down as data because the split is otherwise readable only inside the
+ * renderer's paint calls, and the legend has to group the twelve elements by
+ * it. `group` is the only thing here a reader could not already derive from
+ * {@link EDGY_DYNAMIC_NODES}.
+ */
+export const EDGY_ZONES = [
+    { id: 'identity', group: 'facet' },
+    { id: 'architecture', group: 'facet' },
+    { id: 'experience', group: 'facet' },
+    // Identity ∩ Architecture, Architecture ∩ Experience, Experience ∩ Identity.
+    { id: 'organisation', group: 'intersection' },
+    { id: 'product', group: 'intersection' },
+    { id: 'brand', group: 'intersection' },
+];
+/**
+ * The 24 canonical EDGY relations (source, target, verb, label position along
+ * the link) — exported for the unit tests. 7 per facet + 3 between the
+ * intersections. The optional 4th member mirrors the reference diagram's
+ * placements: verbs of intersection-outgoing links sit near the far element
+ * (`labelOffset.distance` ≈ .75), short peer links keep the middle.
+ *
+ * Read the way `docs/adr/0010` reads every typed edge: the SOURCE is the
+ * subject of the verb and the TARGET its object, so each row is one sentence a
+ * practitioner would say out loud — "content expresses purpose". That is what
+ * makes the row usable as an {@link EndpointTriplet} without a single
+ * coordinate taking part.
+ */
+export const EDGY_DYNAMIC_RELATIONS = [
+    // Identity
+    ['content', 'purpose', 'expresses'],
+    ['content', 'story', 'conveys', 0.75],
+    ['story', 'purpose', 'contextualises', 0.8],
+    ['organisation', 'purpose', 'pursues', 0.8],
+    ['organisation', 'story', 'authors', 0.6],
+    ['brand', 'purpose', 'represents', 0.8],
+    ['brand', 'story', 'evokes', 0.65],
+    // Architecture
+    ['organisation', 'process', 'performs', 0.8],
+    ['process', 'capability', 'realises', 0.75],
+    ['process', 'asset', 'requires'],
+    ['capability', 'asset', 'requires', 0.75],
+    ['organisation', 'capability', 'has', 0.6],
+    ['product', 'capability', 'requires', 0.75],
+    ['process', 'product', 'creates', 0.65],
+    // Experience
+    ['task', 'journey', 'is part of', 0.6],
+    ['task', 'channel', 'uses', 0.6],
+    ['journey', 'channel', 'traverses', 0.6],
+    ['product', 'task', 'serves', 0.9],
+    ['product', 'journey', 'features in', 0.8],
+    ['brand', 'task', 'supports', 0.8],
+    ['brand', 'journey', 'appears in', 0.9],
+    // Intersections
+    ['organisation', 'brand', 'builds', 0.85],
+    ['organisation', 'product', 'makes', 0.65],
+    ['product', 'brand', 'embodies', 0.8],
+];
+/**
+ * The metamodel's own wording for one of its lowercase names — one of the
+ * twelve elements, or one of the six zones. It is the name written on the
+ * diagram, so it is also what the vocabulary falls back to and what the legend
+ * prints as a row label or a section title. One expression, one wording.
+ */
+export const edgyElementLabel = (name) => name.charAt(0).toUpperCase() + name.slice(1);
+export const EDGY_DYNAMIC_NODES = {
+    content: { kind: 'object', cx: 237.5, cy: 100, zone: 'identity' },
+    purpose: { kind: 'outcome', cx: 282.5, cy: 100, zone: 'identity' },
+    organisation: {
+        kind: 'object',
+        cx: 340,
+        cy: 100,
+        w: 175,
+        zone: 'organisation',
+    },
+    process: { kind: 'activity', cx: 397.5, cy: 100, zone: 'architecture' },
+    asset: { kind: 'object', cx: 442.5, cy: 100, zone: 'architecture' },
+    story: { kind: 'activity', cx: 255, cy: 152.5, zone: 'identity' },
+    capability: {
+        kind: 'outcome',
+        cx: 425,
+        cy: 152.5,
+        w: 150,
+        zone: 'architecture',
+    },
+    brand: { kind: 'object', cx: 280, cy: 195, zone: 'brand' },
+    product: { kind: 'object', cx: 400, cy: 195, zone: 'product' },
+    task: { kind: 'outcome', cx: 310, cy: 257.5, zone: 'experience' },
+    journey: { kind: 'activity', cx: 370, cy: 257.5, zone: 'experience' },
+    channel: { kind: 'object', cx: 340, cy: 297.5, zone: 'experience' },
+};

package/dist/node/consts.d.ts

@@ -21,6 +21,18 @@ export declare const NODE_SIZE: Record<EdgyNodeKind, {
 export declare const INNER_FONT_SIZE = 20;
 export declare const LABEL_FONT_SIZE = 18;
 export declare const LABEL_GAP = 8;
+/**
+ * The i18n key {@link NODE_LABEL} is the English default of, when the label is
+ * written onto the canvas.
+ *
+ * Resolved AT PLACEMENT (`createEdgyBox`, `createEdgyPeople`) and never
+ * afterwards: the text a gesture writes is content the author owns from that
+ * moment on, and re-translating it on every paint would overwrite a name
+ * somebody typed. The same words also name the ROLES (`roles.ts`), under their
+ * own keys — a role is a fact about an element and is read live, which is a
+ * different question with a different answer.
+ */
+export declare const nodeLabelKey: (kind: EdgyNodeKind) => string;
 /** Default inner text / label per kind. */
 export declare const NODE_LABEL: Record<EdgyNodeKind, string>;
 /**

package/dist/node/consts.js

@@ -28,6 +28,18 @@ export const NODE_SIZE = {
 export const INNER_FONT_SIZE = 20;
 export const LABEL_FONT_SIZE = 18;
 export const LABEL_GAP = 8;
+/**
+ * The i18n key {@link NODE_LABEL} is the English default of, when the label is
+ * written onto the canvas.
+ *
+ * Resolved AT PLACEMENT (`createEdgyBox`, `createEdgyPeople`) and never
+ * afterwards: the text a gesture writes is content the author owns from that
+ * moment on, and re-translating it on every paint would overwrite a name
+ * somebody typed. The same words also name the ROLES (`roles.ts`), under their
+ * own keys — a role is a fact about an element and is read live, which is a
+ * different question with a different answer.
+ */
+export const nodeLabelKey = (kind) => `com.labre.edgy.seed.${kind}`;
 /** Default inner text / label per kind. */
 export const NODE_LABEL = {
     people: 'People',

package/dist/nudges.d.ts

@@ -0,0 +1,26 @@
+import type { QualityNudge } from '@formicoidea/labre-core/blocks/surface';
+/**
+ * EDGY **work quality** — the checklist (WS1).
+ *
+ * Level 1 is `./rules.ts`: deterministic, decidable, real time. This file is
+ * level 2, and the split is the whole point of the taxonomy — a rule only
+ * enters the deterministic engine if an algorithm can decide it on persisted
+ * data inside the ~16 ms budget. Everything else is a NUDGE: an expectation
+ * offered as a checklist, never evaluated, never blocking anything. Ticking is
+ * assuming.
+ *
+ * ## Why q1 and q2 are here and not in `rules.ts` (PO arbitration, 26/08/2026)
+ *
+ * They read like rules, and they are not. "Each intersection element is linked
+ * to both of its parent facets" would need the tool to know which circle an
+ * element belongs to — and nothing says so except where somebody dropped it,
+ * which is the layout answering a question about meaning. "Each element wears
+ * its facet's colour" would indict every board whose author uses their own
+ * palette, which is most of them after the first workshop. Both are judgements
+ * a modeller makes; the tool can put them on screen and cannot answer them.
+ *
+ * Registered from the flag-gated `EdgyViewExtension`, beside the rules and the
+ * profiles: a checklist is tooling. Switching the flag off takes it away and
+ * leaves the ticks written on the board, unread, until it comes back (PF7.10).
+ */
+export declare const EDGY_NUDGES: readonly QualityNudge[];

package/dist/nudges.js

@@ -0,0 +1,54 @@
+/**
+ * EDGY **work quality** — the checklist (WS1).
+ *
+ * Level 1 is `./rules.ts`: deterministic, decidable, real time. This file is
+ * level 2, and the split is the whole point of the taxonomy — a rule only
+ * enters the deterministic engine if an algorithm can decide it on persisted
+ * data inside the ~16 ms budget. Everything else is a NUDGE: an expectation
+ * offered as a checklist, never evaluated, never blocking anything. Ticking is
+ * assuming.
+ *
+ * ## Why q1 and q2 are here and not in `rules.ts` (PO arbitration, 26/08/2026)
+ *
+ * They read like rules, and they are not. "Each intersection element is linked
+ * to both of its parent facets" would need the tool to know which circle an
+ * element belongs to — and nothing says so except where somebody dropped it,
+ * which is the layout answering a question about meaning. "Each element wears
+ * its facet's colour" would indict every board whose author uses their own
+ * palette, which is most of them after the first workshop. Both are judgements
+ * a modeller makes; the tool can put them on screen and cannot answer them.
+ *
+ * Registered from the flag-gated `EdgyViewExtension`, beside the rules and the
+ * profiles: a checklist is tooling. Switching the flag off takes it away and
+ * leaves the ticks written on the board, unread, until it comes back (PF7.10).
+ */
+export const EDGY_NUDGES = [
+    {
+        id: 'edgy.q1-intersection-links',
+        framework: 'edgy',
+        labelKey: 'com.labre.edgy.quality.intersection-links',
+        fallback: 'Each intersection element is linked to both of its parent facets.',
+        order: 1,
+    },
+    {
+        id: 'edgy.q2-facet-colour',
+        framework: 'edgy',
+        labelKey: 'com.labre.edgy.quality.facet-colour',
+        fallback: "Each element wears its facet's colour.",
+        order: 2,
+    },
+    {
+        id: 'edgy.q3-readable-relations',
+        framework: 'edgy',
+        labelKey: 'com.labre.edgy.quality.readable-relations',
+        fallback: 'Relations read correctly (the source is the subject of the verb).',
+        order: 3,
+    },
+    {
+        id: 'edgy.q4-three-facets',
+        framework: 'edgy',
+        labelKey: 'com.labre.edgy.quality.three-facets',
+        fallback: 'All three facets have been explored.',
+        order: 4,
+    },
+];

package/dist/profiles.d.ts

@@ -0,0 +1,2 @@
+import type { ValidationProfile } from '@formicoidea/labre-core/blocks/surface';
+export declare const EDGY_PROFILES: readonly ValidationProfile[];

package/dist/profiles.js

@@ -0,0 +1,66 @@
+/**
+ * EDGY validation profiles (WS1).
+ *
+ * DATA owned by the framework, like its rules and its roles: the engine knows
+ * how to APPLY a profile, never which ones EDGY has. Adding a level of
+ * requirement is adding an entry to this array.
+ *
+ * A profile is chosen per BACKGROUND, not per document (PF9.1) — a workshop
+ * scribble and a deliverable model coexist on the same canvas with different
+ * requirements, and the choice rides on the facets diagram or board itself.
+ *
+ * Registered from the flag-gated `EdgyViewExtension`, beside the rules:
+ * switching the EDGY flag off takes the choice away with the rest of the
+ * tooling, and a board already set to `strict` simply stops being checked until
+ * it comes back — the id stays written, untouched.
+ */
+/**
+ * Sketch: every rule demoted to `audit`, so findings still reach `violations$`
+ * — a host panel and a conformance report see them — and the canvas says
+ * nothing at all.
+ *
+ * The DEFAULT, and deliberately so (PRD principle 3). EDGY is a WORKSHOP
+ * notation: elements land on the diagram in the order people say them, half the
+ * relations point the wrong way for the ten minutes it takes to argue about
+ * them, and boxes pile up in a corner before anybody sorts them into facets. A
+ * tool warning about all of that in real time would be arguing with the
+ * workshop.
+ *
+ * Being the default also means it is the one profile that WRITES NOTHING: a
+ * board on `sketch` carries no profile key, so every EDGY diagram ever drawn is
+ * on it, with no migration and no backfill.
+ */
+const sketch = {
+    id: 'edgy.sketch',
+    framework: 'edgy',
+    labelKey: 'com.labre.edgy.profile.sketch',
+    fallback: 'Sketch',
+    isDefault: true,
+    rules: {
+        'edgy.non-canonical-link': 'audit',
+        'edgy.overlapping-artefacts': 'audit',
+    },
+};
+/**
+ * Strict: the deliverable level. Both rules bite, and both severities are
+ * spelled out here rather than left absent — PF9.4 wants the answer readable in
+ * one place, and a profile that says "warning" out loud cannot be misread as
+ * "whatever the rule happens to declare this quarter".
+ *
+ * `warning` and not `blocking-overridable` for E1, though a relation outside the
+ * metamodel is exactly the statement a strict EDGY model must not contain:
+ * nothing in this library implements a blocking level, so the value would claim
+ * an effect that does not exist. When the gesture refusal lands, this is a
+ * two-word change and this file is the only one that moves.
+ */
+const strict = {
+    id: 'edgy.strict',
+    framework: 'edgy',
+    labelKey: 'com.labre.edgy.profile.strict',
+    fallback: 'Strict',
+    rules: {
+        'edgy.non-canonical-link': 'warning',
+        'edgy.overlapping-artefacts': 'warning',
+    },
+};
+export const EDGY_PROFILES = [sketch, strict];

package/dist/relation-resolver.d.ts

@@ -0,0 +1,32 @@
+import { InteractivityExtension } from '@formicoidea/labre-core/std/gfx';
+/**
+ * Turns "a connector was drawn, or one of its ends just moved" into a naming.
+ *
+ * Registered from the FLAG-GATED `EdgyViewExtension`, not from the always-on
+ * render one, and the distinction is `docs/adr/0009`'s: this is a creation
+ * tool. It authors content — it writes a role and a label into the document —
+ * and it only ever fires on an edge the flag-gated toolbox itself stamped
+ * `edgy:relation`. A board drawn while the flag was on keeps every verb it was
+ * given, painted by the always-on renderer and read by the always-on
+ * vocabulary; with the flag off nothing new is named because nothing new is
+ * being armed. Registering it always-on would mean the library kept authoring
+ * EDGY content for a host that switched EDGY off.
+ *
+ * The subscription mechanics are `EstuarineGhostManager`'s, including the part
+ * that matters: the surface is a SIGNAL, null at mount and replaced when the
+ * surface block is.
+ */
+export declare class EdgyRelationResolver extends InteractivityExtension {
+    static key: string;
+    private _subscriptions;
+    private _disposeSurfaceEffect;
+    private _pending;
+    private _candidates;
+    mounted(): void;
+    unmounted(): void;
+    private _forget;
+    private _unsubscribe;
+    private _resubscribe;
+    private _schedule;
+    private _flush;
+}

package/dist/relation-resolver.js

@@ -0,0 +1,101 @@
+import { InteractivityExtension } from '@formicoidea/labre-core/std/gfx';
+import { effect } from '@preact/signals-core';
+import { EDGY_RELATION_DELAY_MS, resolveEdgyRelations } from './relation.js';
+/**
+ * Turns "a connector was drawn, or one of its ends just moved" into a naming.
+ *
+ * Registered from the FLAG-GATED `EdgyViewExtension`, not from the always-on
+ * render one, and the distinction is `docs/adr/0009`'s: this is a creation
+ * tool. It authors content — it writes a role and a label into the document —
+ * and it only ever fires on an edge the flag-gated toolbox itself stamped
+ * `edgy:relation`. A board drawn while the flag was on keeps every verb it was
+ * given, painted by the always-on renderer and read by the always-on
+ * vocabulary; with the flag off nothing new is named because nothing new is
+ * being armed. Registering it always-on would mean the library kept authoring
+ * EDGY content for a host that switched EDGY off.
+ *
+ * The subscription mechanics are `EstuarineGhostManager`'s, including the part
+ * that matters: the surface is a SIGNAL, null at mount and replaced when the
+ * surface block is.
+ */
+export class EdgyRelationResolver extends InteractivityExtension {
+    constructor() {
+        super(...arguments);
+        this._subscriptions = [];
+        this._disposeSurfaceEffect = null;
+        this._pending = null;
+        this._candidates = new Set();
+    }
+    static { this.key = 'edgy-relation-resolver'; }
+    mounted() {
+        this._disposeSurfaceEffect = effect(() => {
+            this._resubscribe(this.gfx.surface$.value);
+        });
+    }
+    unmounted() {
+        this._disposeSurfaceEffect?.();
+        this._disposeSurfaceEffect = null;
+        this._unsubscribe();
+        this._forget();
+        super.unmounted();
+    }
+    _forget() {
+        if (this._pending)
+            clearTimeout(this._pending);
+        this._pending = null;
+        this._candidates.clear();
+    }
+    _unsubscribe() {
+        for (const subscription of this._subscriptions)
+            subscription.unsubscribe();
+        this._subscriptions = [];
+    }
+    _resubscribe(surface) {
+        this._unsubscribe();
+        // Candidates queued against the previous surface are about elements this
+        // one has never heard of.
+        this._forget();
+        if (!surface)
+            return;
+        this._subscriptions.push(surface.elementAdded.subscribe(({ id, local }) => {
+            if (!local)
+                return;
+            this._schedule(id);
+        }));
+        this._subscriptions.push(surface.elementUpdated.subscribe(({ id, props, local }) => {
+            // LOCAL only, the filter `reading.ts` documents at length: `local`
+            // partitions the fleet into one writer and N−1 silent observers with
+            // no leader election. Without it, everyone on a shared board would
+            // name the same relation the moment it synced — the same role and the
+            // same word each time, so nothing would corrupt, but each peer would
+            // get an undo entry for a gesture they did not make.
+            if (!local)
+                return;
+            // Only the two ends can turn an unnamed relation into a sentence.
+            // Every other prop — a drag, a restyle, a label edit — must not even
+            // rearm the timer.
+            if (!props || (!('source' in props) && !('target' in props)))
+                return;
+            this._schedule(id);
+        }));
+    }
+    _schedule(id) {
+        this._candidates.add(id);
+        if (this._pending)
+            clearTimeout(this._pending);
+        this._pending = setTimeout(() => {
+            this._pending = null;
+            this._flush();
+        }, EDGY_RELATION_DELAY_MS);
+    }
+    _flush() {
+        const surface = this.gfx.surface;
+        const candidates = this._candidates;
+        // Whatever happens below, what accumulated is accounted for: a set left
+        // behind would be replayed against a later, unrelated gesture.
+        this._candidates = new Set();
+        if (!surface)
+            return;
+        resolveEdgyRelations(surface, candidates);
+    }
+}

package/dist/relation.d.ts

@@ -0,0 +1,142 @@
+import { ConnectorElementModel } from '@formicoidea/labre-core/model';
+import type { XYWH } from '@formicoidea/labre-core/global/gfx';
+import type { SurfaceBlockModel } from '@formicoidea/labre-core/std/gfx';
+import { type EdgyRoleId } from './roles.js';
+/**
+ * **A relation drawn by hand names itself.**
+ *
+ * Until this module the 24 typed relations of the metamodel were born of the
+ * "EDGY dynamic" template and nowhere else: a user who wanted "this Process
+ * requires that Asset" on their own board had a plain connector, carrying no
+ * role, saying nothing, read by nothing (PO recette of 26/08/2026).
+ *
+ * ## Why ONE menu entry and not twenty-two
+ *
+ * The metamodel's 24 rows are 24 DISTINCT ordered pairs of elements, so the
+ * verb is entirely determined by the pair: there is exactly one thing a link
+ * from a Journey to a Channel can say, and it is "traverses". A palette of
+ * twenty-two verbs would therefore be twenty-two ways of asking the user a
+ * question the metamodel already answers — and twenty-one ways of getting it
+ * wrong. The toolbox arms ONE tool, stamped with the generic parent role
+ * `edgy:relation`, and this resolver reads the pair the user actually attached
+ * and writes the verb.
+ *
+ * ## What it writes, and what it refuses to write
+ *
+ * - **pair in the metamodel** → the verb's role (`EDGY_VERB_ROLE`) and the verb
+ *   as the link's visible label, in the same shape the template lays one down
+ *   (`text` + `labelXYWH` + `labelOffset`). The sentence is now legal, so E1
+ *   says nothing.
+ * - **pair known only the OTHER way round** → the role of the reversed match is
+ *   written anyway, and the edge is NOT flipped. This is deliberate: silently
+ *   turning the arrow round would overrule a gesture the user made on purpose,
+ *   and leaving the edge generic would hide the mistake behind the vaguer "not
+ *   a sentence of the metamodel". Naming it makes E1 report the precise
+ *   sentence — "a channel traverses a journey" — and `docs/adr/0010`'s M3
+ *   (`edge.invert-direction`) is one click away on the contextual toolbar. The
+ *   violation IS the affordance.
+ * - **pair in neither direction** → nothing is written. The edge keeps
+ *   `edgy:relation`, and E1 reports it as a relation the metamodel does not
+ *   declare between these two elements, which is exactly what it is.
+ * - **an end outside the alphabet** — a People node, a base Object, a plain
+ *   sticky, an element of another framework — → nothing is written and nothing
+ *   is said. Same contract as the `relation-endpoints` family: outside the
+ *   alphabet is outside the conversation (PRD principle 8).
+ *
+ * ## Once, and only from the generic towards the verb
+ *
+ * A verb role already written is never rewritten — not by this module, not
+ * ever. Re-resolution is allowed only while the edge still carries the generic
+ * role, which is what makes "drop the end on the wrong element, then move it"
+ * work without the tool fighting the hand. And nothing here ever writes
+ * `edgy:relation` back over a verb: the resolution runs one way.
+ */
+/**
+ * Recompute delay. The connector tool rewrites `target` on every pointer move
+ * of the drag, so resolving on the spot would name the relation after the FIRST
+ * element the cursor passed over — and, the naming being write-once, would then
+ * refuse to name it after the one the user actually dropped it on. Debouncing
+ * means the pair that gets read is the pair that ended up on the board.
+ *
+ * Same value as the validation engine's, and for the same reason: it is the
+ * shortest wait a human does not perceive at the end of a gesture.
+ */
+export declare const EDGY_RELATION_DELAY_MS = 120;
+/** Where the verb sits along the link. The templates' own default. */
+export declare const EDGY_RELATION_LABEL_DISTANCE = 0.5;
+/**
+ * The label BOX for a verb — `x`/`y` are re-centred on the path at the first
+ * layout, but the `w`/`h` are the box, so it has to be sized to the word or the
+ * verb wraps mid-syllable on a two-word relation like "is part of".
+ *
+ * Exported and read by `templates/index.ts` as well: the 24 relations the
+ * template draws and the ones drawn by hand have to look identical, and two
+ * copies of `verb.length * 9 + 24` is one copy too many.
+ */
+export declare function edgyVerbLabelXYWH(verb: string): XYWH;
+/** What the metamodel calls the relation between two elements. */
+export interface EdgyRelationNaming {
+    /** The verb's own role: `edgy:traverses`. */
+    role: EdgyRoleId;
+    /** The verb, which also becomes the link's visible label. */
+    verb: string;
+    /**
+     * Whether the metamodel knows this pair only the OTHER way round. The edge is
+     * named all the same and never flipped — see the note at the top of the file.
+     */
+    reversed: boolean;
+}
+/**
+ * The verb the metamodel gives an ordered pair of element roles, direct match
+ * first, reversed match second, `null` when it knows neither.
+ *
+ * Pure, and exported for the unit spec: it is the whole opinion of this module,
+ * and a function taking two strings is testable without a surface, an editor or
+ * a DI container around it.
+ */
+export declare function edgyRelationNaming(sourceRole: string | undefined, targetRole: string | undefined): EdgyRelationNaming | null;
+/**
+ * Whether this edge is a generic EDGY relation with both ends ATTACHED — the
+ * one state this module acts on.
+ *
+ * `role === EDGY_ROLE.relation` exactly, never `roleIsA`: a verb role
+ * specialises the parent, and treating it as a candidate is precisely how the
+ * resolver would start rewriting its own work. An end released over empty
+ * canvas relates nothing to nothing, so it is not a candidate either — it
+ * becomes one the moment the user drags it onto something.
+ *
+ * A LOCKED edge is left alone, the guard `edge.invert-direction` applies for
+ * the same reason: locking is the user saying "do not touch this", and a
+ * resolver that wrote to one anyway would be the one gesture on this canvas
+ * that ignores it.
+ */
+export declare function isUnnamedEdgyRelation(edge: ConnectorElementModel): boolean;
+/**
+ * The naming this edge has earned from the elements it is attached to, or
+ * `null` when there is nothing to write. Reads only; the writes are below.
+ */
+export declare function edgeRelationNaming(surface: SurfaceBlockModel, edge: ConnectorElementModel): EdgyRelationNaming | null;
+/**
+ * Write the verb onto one edge.
+ *
+ * Through `surface.updateElement` and never through `EdgelessCRUDIdentifier`,
+ * for the reason `edge.invert-direction` spells out at length: `crud`'s wrapper
+ * calls `recordLastProps`, which would make this relation's label geometry the
+ * DEFAULT for every connector drawn afterwards. Naming one relation is a
+ * statement about that relation, never a style preference.
+ */
+export declare function writeEdgyRelationName(surface: SurfaceBlockModel, edge: ConnectorElementModel, naming: EdgyRelationNaming): void;
+/**
+ * Name every edge among `ids` that has earned a name, in ONE undo step.
+ *
+ * The seam, and the only function here that writes. Two phases on purpose: the
+ * namings are decided BEFORE anything is captured, so a flush that finds
+ * nothing to say costs no undo entry at all — an empty capture would turn every
+ * stray connector into a stop on the user's way back through their own history.
+ *
+ * Read-only is checked here rather than trusted: `surface.updateElement`
+ * THROWS on a read-only store, so a resolver that did not ask would turn
+ * opening a shared board in read-only into an exception per connector drawn on
+ * it.
+ */
+export declare function resolveEdgyRelations(surface: SurfaceBlockModel, ids: Iterable<string>): EdgyRelationNaming[];