yarramate 0.7.1 → 0.8.1

package/catalogues/core-enrichment.yaml

@@ -1,15 +1,18 @@
 format: yarramate/question-catalogue/v1
 id: core-enrichment
-version: "0.3"
+version: "0.5"
 profile: yarramate/core@0.1
 presentation:
   title: Core enrichment interview
   description: >-
-    The guided design path: motivation, business, and application waves plus
-    cross-cutting hygiene (technology and implementation follow in a later
-    version). Each question states the decision its answer changes; a
-    question that cannot is deleted, not softened. Adequacy is enforced by
-    linkage depth and attestation, never by reading words.
+    The guided design path: motivation, business, application, technology,
+    and implementation waves plus cross-cutting hygiene. Each question
+    states the decision its answer changes; a question that cannot is
+    deleted, not softened. Adequacy is enforced by linkage depth and
+    attestation, never by reading words. Versioning is additive within a
+    major version: every question records the catalogue version it arrived
+    in (ADR 0063), and a completed interview honestly reopens when the
+    path deepens.
 
 waves:
   - id: motivation
@@ -23,6 +26,16 @@ waves:
     description: >-
       How declared services are realized, performed, and fed with
       information.
+  - id: technology
+    name: Technology
+    description: >-
+      Where the declared applications actually run and what materializes
+      them.
+  - id: implementation
+    name: Implementation
+    description: >-
+      How the planned architecture becomes real: work, deliverables, and
+      the plateaus between here and there.
   - id: hygiene
     name: Model hygiene
     description: Cross-cutting completeness that keeps every wave honest.
@@ -31,6 +44,7 @@ questions:
   # ---- motivation ----------------------------------------------------------
   - id: outcome-missing
     wave: motivation
+    since: "0.1"
     scope: workspace
     trigger:
       - condition: no-subject-of-kind
@@ -50,6 +64,7 @@ questions:
 
   - id: stakeholders-missing
     wave: motivation
+    since: "0.1"
     scope: workspace
     trigger:
       - condition: no-subject-of-kind
@@ -68,6 +83,7 @@ questions:
 
   - id: constraints-missing
     wave: motivation
+    since: "0.1"
     scope: workspace
     trigger:
       - condition: no-subject-of-kind
@@ -86,6 +102,7 @@ questions:
 
   - id: goal-unrealized
     wave: motivation
+    since: "0.1"
     scope: subject
     subjects:
       kinds:
@@ -105,11 +122,14 @@ questions:
     authority: either
     resolution: >-
       Add realization relationships from the fulfilling capability or
-      service, or record the aspirational status in the goal's description.
+      service, record the aspirational status in the goal's description,
+      or retire the goal (status: retired) to record that it no longer
+      steers design.
 
 
   - id: goal-no-driver
     wave: motivation
+    since: "0.3"
     scope: subject
     subjects:
       kinds:
@@ -137,6 +157,7 @@ questions:
 
   - id: driver-influences-nothing
     wave: motivation
+    since: "0.3"
     scope: subject
     subjects:
       kinds:
@@ -158,6 +179,7 @@ questions:
 
   - id: stakeholder-unconcerned
     wave: motivation
+    since: "0.3"
     scope: subject
     subjects:
       kinds:
@@ -180,6 +202,7 @@ questions:
 
   - id: requirement-unrealized
     wave: motivation
+    since: "0.3"
     scope: subject
     subjects:
       kinds:
@@ -198,11 +221,15 @@ questions:
       roadmap.
     authority: either
     resolution: >-
-      Add realization from the fulfilling service, component, or behavior,
-      or record the descoping decision and remove the requirement.
+      Add realization from the fulfilling service, component, or
+      behavior; to descope instead, retire the requirement (status:
+      retired) — retirement preserves the decision on record and closes
+      the question (ADR 0064). Delete only when the history itself is
+      noise.
 
   - id: principle-unapplied
     wave: motivation
+    since: "0.3"
     scope: subject
     subjects:
       kinds:
@@ -225,6 +252,7 @@ questions:
 
   - id: assessment-unlinked
     wave: motivation
+    since: "0.3"
     scope: subject
     subjects:
       kinds:
@@ -243,6 +271,7 @@ questions:
 
   - id: motivation-unattested
     wave: motivation
+    since: "0.3"
     scope: subject
     subjects:
       kinds:
@@ -268,6 +297,7 @@ questions:
   # ---- business ------------------------------------------------------------
   - id: service-consumer-unknown
     wave: business
+    since: "0.1"
     scope: subject
     subjects:
       kinds:
@@ -291,6 +321,7 @@ questions:
 
   - id: owner-missing
     wave: business
+    since: "0.1"
     scope: subject
     subjects:
       kinds:
@@ -313,6 +344,7 @@ questions:
 
   - id: actor-unassigned
     wave: business
+    since: "0.1"
     scope: subject
     subjects:
       kinds:
@@ -335,6 +367,7 @@ questions:
 
   - id: information-unaccessed
     wave: business
+    since: "0.1"
     scope: subject
     subjects:
       kinds:
@@ -358,6 +391,7 @@ questions:
 
   - id: no-service-declared
     wave: business
+    since: "0.1"
     scope: workspace
     trigger:
       - condition: no-subject-of-kind
@@ -378,6 +412,7 @@ questions:
 
   - id: service-realizes-no-motivation
     wave: business
+    since: "0.3"
     scope: subject
     subjects:
       kinds:
@@ -405,6 +440,7 @@ questions:
 
   - id: process-untriggered
     wave: business
+    since: "0.3"
     scope: subject
     subjects:
       kinds:
@@ -427,6 +463,7 @@ questions:
 
   - id: business-service-unrealized
     wave: business
+    since: "0.3"
     scope: subject
     subjects:
       kinds:
@@ -460,6 +497,7 @@ questions:
   # ---- application ---------------------------------------------------------
   - id: app-service-unrealized
     wave: application
+    since: "0.3"
     scope: subject
     subjects:
       kinds:
@@ -490,6 +528,7 @@ questions:
 
   - id: component-realizes-nothing
     wave: application
+    since: "0.3"
     scope: subject
     subjects:
       kinds:
@@ -515,6 +554,7 @@ questions:
 
   - id: behavior-unassigned
     wave: application
+    since: "0.3"
     scope: subject
     subjects:
       kinds:
@@ -546,6 +586,7 @@ questions:
 
   - id: event-triggers-nothing
     wave: application
+    since: "0.3"
     scope: subject
     subjects:
       kinds:
@@ -568,6 +609,7 @@ questions:
 
   - id: information-unowned
     wave: application
+    since: "0.3"
     scope: subject
     subjects:
       kinds:
@@ -589,6 +631,7 @@ questions:
 
   - id: planned-design-unattested
     wave: application
+    since: "0.3"
     scope: subject
     subjects:
       kinds:
@@ -612,9 +655,246 @@ questions:
       topic "design-review" (revoke by deleting it when the design
       changes).
 
+  # ---- technology ----------------------------------------------------------
+  - id: component-unhosted
+    wave: technology
+    since: "0.4"
+    scope: subject
+    subjects:
+      kinds:
+        - yarramate/core@0.1#applicationComponent
+      kindMatching: exact
+      statuses:
+        - planned
+        - current
+    trigger:
+      - condition: missing-linkage
+        kinds:
+          - yarramate/core@0.1#serving
+          - yarramate/core@0.1#assignment
+        direction: incoming
+        counterpartKinds:
+          - yarramate/core@0.1#node
+          - yarramate/core@0.1#device
+          - yarramate/core@0.1#systemSoftware
+          - yarramate/core@0.1#technologyService
+    question: >-
+      Where does {subject.name} run?
+    materiality: >-
+      The hosting boundary decides latency, failure domain, scaling
+      model, and data residency; a component with no declared runtime is
+      deployed by whoever gets there first. Matching is exact by intent:
+      profile-derived module kinds inherit their deployable parent's
+      hosting rather than answering separately.
+    authority: either
+    resolution: >-
+      Add the node, device, or system software that hosts it with a
+      serving or assignment relationship into the component.
+
+  - id: node-serves-nothing
+    wave: technology
+    since: "0.4"
+    scope: subject
+    subjects:
+      kinds:
+        - yarramate/core@0.1#node
+        - yarramate/core@0.1#device
+        - yarramate/core@0.1#systemSoftware
+    trigger:
+      - condition: missing-relationship
+        kinds:
+          - yarramate/core@0.1#serving
+          - yarramate/core@0.1#assignment
+        direction: outgoing
+    question: >-
+      What does {subject.name} host or serve?
+    materiality: >-
+      Declared infrastructure that serves nothing is either cost without
+      purpose or missing the links that justify it; both change the
+      deployment budget.
+    authority: either
+    resolution: >-
+      Add serving or assignment relationships to the applications and
+      behavior it hosts, or remove it.
+
+  - id: technology-service-unrealized
+    wave: technology
+    since: "0.4"
+    scope: subject
+    subjects:
+      kinds:
+        - yarramate/core@0.1#technologyService
+      statuses:
+        - planned
+        - current
+    trigger:
+      - condition: missing-linkage
+        kinds:
+          - yarramate/core@0.1#realization
+        direction: incoming
+        counterpartKinds:
+          - yarramate/core@0.1#node
+          - yarramate/core@0.1#systemSoftware
+          - yarramate/core@0.1#technologyFunction
+          - yarramate/core@0.1#technologyProcess
+    question: >-
+      What provides {subject.name}?
+    materiality: >-
+      A technology service with no realizing node or behavior is a
+      dependency assumed rather than provided; outages and upgrades have
+      no owner in the model.
+    authority: either
+    resolution: >-
+      Add realization from the node, system software, or technology
+      behavior that provides the service.
+
+  - id: artifact-unassigned
+    wave: technology
+    since: "0.4"
+    scope: subject
+    subjects:
+      kinds:
+        - yarramate/core@0.1#artifact
+      kindMatching: exact
+    trigger:
+      - condition: missing-relationship
+        kinds:
+          - yarramate/core@0.1#assignment
+          - yarramate/core@0.1#realization
+        direction: any
+    question: >-
+      What deploys {subject.name}, and what does it materialize?
+    materiality: >-
+      An artifact with no deployment target and nothing it realizes is a
+      build output the architecture cannot place; release engineering
+      starts from exactly these links.
+    authority: either
+    resolution: >-
+      Assign the artifact to the node that deploys it and add realization
+      to the component or data it materializes.
+
+  # ---- implementation ------------------------------------------------------
+  - id: workpackage-delivers-nothing
+    wave: implementation
+    since: "0.4"
+    scope: subject
+    subjects:
+      kinds:
+        - yarramate/core@0.1#workPackage
+    trigger:
+      - condition: missing-relationship
+        kinds:
+          - yarramate/core@0.1#realization
+          - yarramate/core@0.1#aggregation
+        direction: outgoing
+    question: >-
+      What does {subject.name} produce?
+    materiality: >-
+      Work with no deliverable cannot be accepted or declared done; the
+      deliverable link is what makes progress reviewable rather than
+      reported.
+    authority: either
+    resolution: >-
+      Add realization from the work package to its deliverables.
+
+  - id: workpackage-unassigned
+    wave: implementation
+    since: "0.4"
+    scope: subject
+    subjects:
+      kinds:
+        - yarramate/core@0.1#workPackage
+    trigger:
+      - condition: missing-linkage
+        kinds:
+          - yarramate/core@0.1#assignment
+        direction: incoming
+        counterpartKinds:
+          - yarramate/core@0.1#businessActor
+          - yarramate/core@0.1#businessRole
+    question: >-
+      Who is committed to {subject.name}?
+    materiality: >-
+      An unassigned work package is a plan without capacity; commitment
+      is the difference between a roadmap and a wish list.
+    authority: human
+    resolution: >-
+      Add assignment from the actor or role that owns the work.
+
+  - id: deliverable-realizes-nothing
+    wave: implementation
+    since: "0.4"
+    scope: subject
+    subjects:
+      kinds:
+        - yarramate/core@0.1#deliverable
+      kindMatching: exact
+    trigger:
+      - condition: missing-relationship
+        kinds:
+          - yarramate/core@0.1#realization
+        direction: outgoing
+    question: >-
+      What does {subject.name} make real?
+    materiality: >-
+      A deliverable that realizes no architecture element is effort
+      disconnected from the design; its acceptance criteria cannot be
+      stated architecturally.
+    authority: either
+    resolution: >-
+      Add realization from the deliverable to the plateau, requirement,
+      or element it brings into being.
+
+  - id: plateau-aggregates-nothing
+    wave: implementation
+    since: "0.4"
+    scope: subject
+    subjects:
+      kinds:
+        - yarramate/core@0.1#plateau
+    trigger:
+      - condition: missing-relationship
+        kinds:
+          - yarramate/core@0.1#aggregation
+          - yarramate/core@0.1#composition
+        direction: outgoing
+    question: >-
+      Which architecture does {subject.name} stabilize?
+    materiality: >-
+      A plateau that aggregates nothing describes no state anyone can
+      stand on; migration planning needs to know what is stable when.
+    authority: either
+    resolution: >-
+      Aggregate the elements that are current during this plateau, or use
+      architecture states instead and remove it.
+
+  - id: gap-unaddressed
+    wave: implementation
+    since: "0.4"
+    scope: subject
+    subjects:
+      kinds:
+        - yarramate/core@0.1#gap
+    trigger:
+      - condition: missing-relationship
+        kinds:
+          - yarramate/core@0.1#association
+          - yarramate/core@0.1#realization
+        direction: any
+    question: >-
+      What closes {subject.name}?
+    materiality: >-
+      A named gap nothing addresses is a known risk with no plan; either
+      work closes it or the acceptance of it should be on record.
+    authority: human
+    resolution: >-
+      Associate the gap with the plateaus it separates and the
+      deliverable that closes it, or record the decision to accept it.
+
   # ---- hygiene -------------------------------------------------------------
   - id: concept-isolated
     wave: hygiene
+    since: "0.1"
     scope: subject
     subjects:
       kinds:
@@ -640,6 +920,7 @@ questions:
 
   - id: concept-undescribed
     wave: hygiene
+    since: "0.1"
     scope: subject
     subjects:
       kinds:
@@ -663,6 +944,7 @@ questions:
 
   - id: status-missing
     wave: hygiene
+    since: "0.1"
     scope: subject
     subjects:
       kinds:
@@ -685,6 +967,7 @@ questions:
 
   - id: states-undefined
     wave: hygiene
+    since: "0.1"
     scope: workspace
     trigger:
       - condition: no-state-defined

package/dist/apply-command.js

@@ -123,7 +123,24 @@ const itemMap = (source, collection, id) => {
 };
 // The indent item fields sit at, read off the item's own first field.
 const fieldIndentOf = (source, map) => indentAt(source, nodeRange(map.items[0].key)[0]);
+// A flow-style item (`- { id: x, ... }`) cannot take block field lines;
+// splicing them after it corrupts the sequence (Codex dogfood finding,
+// 2026-08-01). The whole item is rewritten as a block mapping with the
+// mutation applied — churn confined to the item being edited.
+const rewriteFlowItem = (source, map, mutate) => {
+    const mutated = mutate(map.toJSON());
+    const [start, valueEnd] = nodeRange(map);
+    const fieldIndent = indentAt(source, start);
+    const rendered = reindent(stringify(mutated, { lineWidth: 0 }).trimEnd(), fieldIndent);
+    return splice(source, start, valueEnd, rendered);
+};
 const setScalarField = (source, map, key, value) => {
+    if (map.flow) {
+        return rewriteFlowItem(source, map, (fields) => ({
+            ...fields,
+            [key]: value,
+        }));
+    }
     const indent = fieldIndentOf(source, map);
     const rendered = reindent(valueText(value), indent + 2);
     const pair = pairFor(map, key);
@@ -134,6 +151,15 @@ const setScalarField = (source, map, key, value) => {
     return splice(source, start, valueEnd, rendered);
 };
 const appendListField = (source, map, key, additions) => {
+    if (map.flow) {
+        return rewriteFlowItem(source, map, (fields) => ({
+            ...fields,
+            [key]: [
+                ...(fields[key] ?? []),
+                ...additions,
+            ],
+        }));
+    }
     const indent = fieldIndentOf(source, map);
     const pair = pairFor(map, key);
     if (pair === undefined) {
@@ -163,11 +189,19 @@ const appendListField = (source, map, key, additions) => {
     return splice(source, start, valueEnd, `\n${sequenceEntries(merged, indent + 2)}`);
 };
 // Retraction (#115): delete the field's whole entry, from the start of its
-// key line through the end of its value's last line.
+// key line through the end of its value's last line. A flow item is
+// rewritten instead — line-based deletion there would take the whole item
+// with it.
 const removeField = (source, map, key) => {
     const pair = pairFor(map, key);
     if (pair === undefined)
         return undefined;
+    if (map.flow) {
+        return rewriteFlowItem(source, map, (fields) => {
+            const { [key]: _removed, ...rest } = fields;
+            return rest;
+        });
+    }
     const start = lineStartOf(source, nodeRange(pair.key)[0]);
     const valueEnd = pair.value === null || pair.value === undefined
         ? nodeRange(pair.key)[2]

package/dist/design-command.js

@@ -33,6 +33,7 @@ const selectStep = (report, subjectFilter) => {
                     question: question.question,
                     materiality: question.materiality,
                     resolution: question.resolution,
+                    ...(question.since === undefined ? {} : { since: question.since }),
                 };
             }
             const subjects = subjectFilter === undefined
@@ -49,6 +50,7 @@ const selectStep = (report, subjectFilter) => {
                 question: first.question,
                 materiality: question.materiality,
                 resolution: question.resolution,
+                ...(question.since === undefined ? {} : { since: question.since }),
                 subject: {
                     id: first.id,
                     ...(first.name === undefined ? {} : { name: first.name }),

package/dist/interrogate-command.d.ts

@@ -44,6 +44,7 @@ export interface CatalogueQuestion {
     readonly materiality: string;
     readonly resolution: string;
     readonly authority: 'human' | 'agent' | 'either';
+    readonly since?: string;
 }
 export interface QuestionCatalogue {
     readonly format: 'yarramate/question-catalogue/v1';
@@ -74,6 +75,7 @@ interface ReportQuestion {
     readonly question: string;
     readonly materiality: string;
     readonly resolution: string;
+    readonly since?: string;
     readonly subjects?: readonly OpenSubject[];
 }
 export interface InterrogationReport {

package/dist/interrogate-command.js

@@ -12,12 +12,6 @@ const indexGraph = (graph) => {
     const stateSubjects = new Set(graph.claims
         .filter(({ predicate }) => predicate === 'yarramate/state/type')
         .map(({ subject }) => subject));
-    // Architecture states carry concept subjects in the graph but are not
-    // enrichment targets; the catalogue interrogates the model, not the
-    // planning overlay.
-    const concepts = new Set(graph.subjects
-        .filter(({ id, type }) => type === 'concept' && !stateSubjects.has(id))
-        .map(({ id }) => id));
     const claimsBySubject = new Map();
     const kindOf = new Map();
     const nameOf = new Map();
@@ -50,6 +44,16 @@ const indexGraph = (graph) => {
             }
         }
     }
+    // Architecture states carry concept subjects in the graph but are not
+    // enrichment targets; the catalogue interrogates the model, not the
+    // planning overlay. Retired concepts are excluded for the same reason
+    // (ADR 0064): retirement is the recorded decision that a subject left
+    // the design conversation, so no question stays open against it.
+    const concepts = new Set(graph.subjects
+        .filter(({ id, type }) => type === 'concept' &&
+        !stateSubjects.has(id) &&
+        statusOf.get(id) !== 'retired')
+        .map(({ id }) => id));
     return {
         concepts,
         claimsBySubject,
@@ -175,6 +179,7 @@ export function evaluateCatalogue(catalogue, graph, profileContext) {
                 question: question.question.trim(),
                 materiality: question.materiality.trim(),
                 resolution: question.resolution.trim(),
+                ...(question.since === undefined ? {} : { since: question.since }),
             };
             if (question.scope === 'workspace') {
                 const isOpen = question.trigger.every((condition) => conditionHolds(index, condition, undefined, profileContext));
@@ -253,12 +258,13 @@ export function renderInterrogationReport(report) {
                 lines.push(`  closed ${question.id}`);
                 continue;
             }
+            const sinceMarker = question.since === undefined ? '' : ` [since ${question.since}]`;
             if (question.subjects === undefined) {
-                lines.push(`  OPEN   ${question.id} — ${question.question}`);
+                lines.push(`  OPEN   ${question.id}${sinceMarker} — ${question.question}`);
                 lines.push(`         why: ${question.materiality}`);
                 continue;
             }
-            lines.push(`  OPEN   ${question.id} (${question.subjects.length} ${question.subjects.length === 1 ? 'subject' : 'subjects'})`);
+            lines.push(`  OPEN   ${question.id}${sinceMarker} (${question.subjects.length} ${question.subjects.length === 1 ? 'subject' : 'subjects'})`);
             for (const subject of question.subjects) {
                 lines.push(`         ask: "${subject.question}" [authority: ${question.authority}]`);
             }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "yarramate",
-  "version": "0.7.1",
+  "version": "0.8.1",
   "description": "Tool-neutral semantic architecture engine and guided methodology",
   "license": "MIT",
   "repository": {

package/schema/yarramate-design-step.schema.json

@@ -147,6 +147,9 @@
                 "type": "string",
                 "minLength": 1
               }
+            },
+            "since": {
+              "type": "string"
             }
           }
         }

package/schema/yarramate-interrogation-report.schema.json

@@ -68,6 +68,7 @@
         "question": { "type": "string", "minLength": 1 },
         "materiality": { "type": "string", "minLength": 1 },
         "resolution": { "type": "string", "minLength": 1 },
+        "since": { "type": "string" },
         "subjects": {
           "type": "array",
           "minItems": 1,

package/schema/yarramate-question-catalogue.schema.json

@@ -392,6 +392,11 @@
         "resolution": {
           "description": "Guidance for how an accepted answer should land as native authoring (which claim, relationship, or state to add).",
           "$ref": "#/$defs/nonEmptyText"
+        },
+        "since": {
+          "description": "The catalogue version this question first appeared in. Lets consumers distinguish 'the catalogue deepened' from 'the model regressed' when a completed interview reopens (ADR 0063).",
+          "type": "string",
+          "pattern": "^[0-9]+\\.[0-9]+$"
         }
       },
       "allOf": [