@sdd-method/maintain-cli 0.14.0 → 0.15.1

package/dist/lib/catalogue/canonical-schema.yaml

@@ -7,7 +7,7 @@
 # Emitted by sdd-cli's YAML emitter with no line folding; the three header scalars are quoted for the
 # textual readers downstream. The one deliberate difference from the authored form is schema_status:
 # the authored form says canonical; a projection never does.
-schema_version: "7.0.0"
+schema_version: "7.1.0"
 schema_owner: "sdd-method"
 schema_status: "generated"
 enums:
@@ -645,7 +645,7 @@ enums:
       description: Its change archived on a passing judge, with this repository's work order implementing it.
     - value: observed
       description: Independent evidence from this repository's code matches (a baseline's characterization tests or a reverse snapshot).
-    description: The kind of evidence an assertion is about one revision, in one repository (M-ADR 0230 §4.7, Proposed).
+    description: The kind of evidence an assertion is about one revision, in one repository (M-ADR 0230 §4.7).
   change_status:
     values:
     - value: proposed
@@ -714,14 +714,14 @@ enums:
       description: Observations, scores and findings, about a named revision.
     - value: execution
       description: "The change records and the build itself: changes, work orders, lineage, and the provenance the build or aggregation stamps."
-    description: Where a catalogue's facts, or a column's, are authored (M-ADR 0230 §4.1, Proposed). Each catalogue carries one; a column carries one only where it differs.
+    description: Where a catalogue's facts, or a column's, are authored (M-ADR 0230 §4.1). Each catalogue carries one; a column carries one only where it differs.
   relationship_end_cardinality:
     values:
     - value: exactly-one
     - value: zero-or-one
     - value: one-or-more
     - value: zero-or-more
-    description: "How many entities one end of a relationship holds for one entity at the other end (M-ADR 0230 §4.3, Proposed): a Mermaid ER end marker (|| exactly one, |o or o| zero or one, }| or |{ one or more, }o or o{ zero or more). A TypeQL relationship is zero-or-more at both ends, because the subset admits no participation cardinality; a role's @card is a cardinality invariant (domain_invariants). Replaced entity_relationship_cardinality in schema 6.0.0."
+    description: "How many entities one end of a relationship holds for one entity at the other end (M-ADR 0230 §4.3): a Mermaid ER end marker (|| exactly one, |o or o| zero or one, }| or |{ one or more, }o or o{ zero or more). A TypeQL relationship is zero-or-more at both ends, because the subset admits no participation cardinality; a role's @card is a cardinality invariant (domain_invariants). Replaced entity_relationship_cardinality in schema 6.0.0."
   domain_invariant_kind:
     values:
     - value: unique
@@ -732,7 +732,7 @@ enums:
       description: A bound on how many entities the named relationship relates, stated in the statement.
     - value: rule
       description: Any other rule, stated in the statement.
-    description: The type of a domain invariant (M-ADR 0230 §4.3, Proposed).
+    description: The type of a domain invariant (M-ADR 0230 §4.3).
   revision_state:
     values:
     - value: current
@@ -741,14 +741,14 @@ enums:
       description: An agreed open change states it.
     - value: history
       description: Once published or stated, and no longer current.
-    description: Which view a revision belongs to (M-ADR 0230 §4.7, Proposed).
+    description: Which view a revision belongs to (M-ADR 0230 §4.7).
   change_effect_element_kind:
     values:
     - value: requirement
       description: A requirement, written by a behaviour delta.
     - value: structure
       description: An element of the structural model, written by a structural delta.
-    description: What kind of element a change effect writes (M-ADR 0230 §4.7, Proposed).
+    description: What kind of element a change effect writes (M-ADR 0230 §4.7).
   adr_governs:
     values:
     - value: current
@@ -757,7 +757,7 @@ enums:
       description: "The system as the agreed changes will leave it: the decision applies from its change's archive."
     - value: none
       description: "Neither: proposed, rejected, deprecated, superseded by a decision now in force, or its change withdrawn."
-    description: Which view a decision governs (M-ADR 0230 §4.2, Proposed).
+    description: Which view a decision governs (M-ADR 0230 §4.2).
   contract_revision_state:
     values:
     - value: agreed
@@ -768,7 +768,22 @@ enums:
       description: Applicable, with a sunset.
     - value: retired
       description: "No longer applicable: an archived change's revision the file no longer holds."
-    description: A contract revision's applicability in the published specification (M-ADR 0230 §4.2, Proposed).
+    description: A contract revision's applicability in the published specification (M-ADR 0230 §4.2).
+  ppt_archetype:
+    values:
+    - value: party
+      description: A person or an organisation.
+    - value: place
+      description: A location where things happen or are kept.
+    - value: thing
+      description: An object that is tracked individually.
+    - value: role
+      description: A way a party, place or thing takes part in something.
+    - value: moment-interval
+      description: Something that happens at a moment or over an interval, and is recorded.
+    - value: description
+      description: A catalogue-entry description that many things share.
+    description: An entity's Party-Place-Thing archetype, as the capability spec template classifies it (schema 7.1.0).
 catalogues:
   domains:
     primary_key: id
@@ -1220,7 +1235,7 @@ catalogues:
     - name: effective_change
       type: string
       nullable: true
-      description: "From the ADR's **Effective:** line (M-ADR 0230 §4.2, Proposed): the change whose archive makes the decision apply, by its undated name; empty when it applies on acceptance. Added in schema 6.0.0."
+      description: "From the ADR's **Effective:** line (M-ADR 0230 §4.2): the change whose archive makes the decision apply, by its undated name; empty when it applies on acceptance. Added in schema 6.0.0."
     - name: governs
       type: string
       nullable: true
@@ -1503,7 +1518,7 @@ catalogues:
     - name: source
       type: string
       nullable: false
-      description: "capability-tree | product-map | capability-spec | structural-model. As of schema 6.0.0, source: structural-model is emitted for a capability only the structural model holds (M-ADR 0230 §4.3, Proposed)."
+      description: "capability-tree | product-map | capability-spec | structural-model. As of schema 6.0.0, source: structural-model is emitted for a capability only the structural model holds (M-ADR 0230 §4.3)."
       source_of_truth: derived
     - name: runway_classification
       type: string
@@ -1637,7 +1652,7 @@ catalogues:
     - name: source
       type: string
       nullable: false
-      description: "feature-tree | feature-set | capability-spec | feature-spec | feature-grounding | structural-model. As of schema 6.0.0, source: structural-model is emitted for a feature only the structural model holds (M-ADR 0230 §4.3, Proposed). NOTE: feature-tree-group source removed in 1.3.0 — groups are now first-class in feature_groups.csv. As of schema 2.2.0, source: feature-tree is emitted by the canonical builder for rows derived from feature-tree.md bullets. As of schema 2.5.0, source: feature-grounding is emitted for rows derived from `docs/domains/<dom>/design/<capability>/feature-grounding.md` markdown tables (per M-ADR 0143). As of schema 2.7.0, source: capability-spec is emitted by the canonical builder for rows derived from `## Feature Grounding (code-path trace)` tables in `docs/domains/<dom>/product/<capability>.md` capability spec markdown (per M-ADR 0145). Feature-grounding and capability-spec rows are both capability-owned: product_id is empty; capability_id resolves from the file path."
+      description: "feature-tree | feature-set | capability-spec | feature-spec | feature-grounding | structural-model. As of schema 6.0.0, source: structural-model is emitted for a feature only the structural model holds (M-ADR 0230 §4.3). NOTE: feature-tree-group source removed in 1.3.0 — groups are now first-class in feature_groups.csv. As of schema 2.2.0, source: feature-tree is emitted by the canonical builder for rows derived from feature-tree.md bullets. As of schema 2.5.0, source: feature-grounding is emitted for rows derived from `docs/domains/<dom>/design/<capability>/feature-grounding.md` markdown tables (per M-ADR 0143). As of schema 2.7.0, source: capability-spec is emitted by the canonical builder for rows derived from `## Feature Grounding (code-path trace)` tables in `docs/domains/<dom>/product/<capability>.md` capability spec markdown (per M-ADR 0145). Feature-grounding and capability-spec rows are both capability-owned: product_id is empty; capability_id resolves from the file path."
       source_of_truth: derived
     - name: runway
       type: string
@@ -2255,6 +2270,10 @@ catalogues:
       nullable: true
       description: The platform this row belongs to — sdd_id of its platform-root. Stamped by the aggregator per M-ADR 0208 §4.4 (preserve-if-set, fill rule by pull path); left empty by per-SDD builders. Added in 3.7.0.
       source_of_truth: execution
+    - name: ppt_archetype
+      type: string
+      nullable: true
+      description: "The entity's Party-Place-Thing archetype (ppt_archetype). A structure fact: where the SDD has a structural model, the model holds it, and a change states it in its deltas. In an SDD without a model it is read from the capability specs' Entity Classification tables: the first archetype a row's archetype cell names, colour labels and qualifiers aside (Moment alone is moment-interval, PartyRole is role); a cell naming none, an entity no table row resolves to, and two tables disagreeing are reported. Added in schema 7.1.0 (M-ADR 0230)."
     description: "Data-model entity (a structural realisation of a concept inside a domain's data model). Distinct from glossary_items (vocabulary-level) and from domain_models (file-level). Added in schema 2.13.0 per M-ADR 0159. Forward source: `models[].entities[]` in glossary-alignment-manifest.yaml. Reverse source: `EntityName { ... }` declarations inside `erDiagram` fences in `docs/domains/{domain}/architecture/data-model.mermaid.md`. PK uses an entity-aware slug that normalises across UPPER_SNAKE and PascalCase authoring styles."
     foreign_keys:
     - column: domain_id
@@ -2268,6 +2287,7 @@ catalogues:
       nullable: true
     column_enums:
       persistence_kind: enums.persistence_kind
+      ppt_archetype: enums.ppt_archetype
   repo_capability:
     primary_key: id
     source_of_truth: derived
@@ -3933,7 +3953,7 @@ catalogues:
     - name: input_paths
       type: string
       nullable: true
-      description: "';'-separated paths of the review's other assessed inputs (its `inputs:` list, M-ADR 0230 §4.9, Proposed), beside target_path: a feature's UX evidence, say. Each is read at corpus_ref, so a later edit to any of them makes the score stale, as an edit to the target does. Added in schema 6.0.0."
+      description: "';'-separated paths of the review's other assessed inputs (its `inputs:` list, M-ADR 0230 §4.9), beside target_path: a feature's UX evidence, say. Each is read at corpus_ref, so a later edit to any of them makes the score stale, as an edit to the target does. Added in schema 6.0.0."
     - name: staleness_basis
       type: string
       nullable: false
@@ -4752,7 +4772,7 @@ catalogues:
       nullable: true
       description: The platform SDD the row belongs to (stamped at aggregation).
       source_of_truth: execution
-    description: "Edge: evidence about one revision of a requirement, in one repository that implements it (M-ADR 0230 §4.7, Proposed; replaces requirement_status in schema 6.0.0). Derived, never authored: observed from a baseline's **Observed in:** line, declared-shipped from an archived change's PASS verdict through its work orders' implements lists, each about the revision that change's delta states. An assertion is current while its revision is, and history once a later change moves the requirement, so evidence about one revision is never read as proof of another. An agreed change is not an assertion: it is an intended revision (requirement_revisions) and a change effect (change_effects). Per (revision, repository), the latest assertion wins."
+    description: "Edge: evidence about one revision of a requirement, in one repository that implements it (M-ADR 0230 §4.7; replaces requirement_status in schema 6.0.0). Derived, never authored: observed from a baseline's **Observed in:** line, declared-shipped from an archived change's PASS verdict through its work orders' implements lists, each about the revision that change's delta states. An assertion is current while its revision is, and history once a later change moves the requirement, so evidence about one revision is never read as proof of another. An agreed change is not an assertion: it is an intended revision (requirement_revisions) and a change effect (change_effects). Per (revision, repository), the latest assertion wins."
     natural_key:
     - revision_id
     - repo_id
@@ -4955,7 +4975,7 @@ catalogues:
       nullable: true
       description: The platform SDD the row belongs to (stamped at aggregation).
       source_of_truth: execution
-    description: "An attribute of a domain-model entity, an element of its own (M-ADR 0230 §4.3, Proposed): adding a field to an entity adds an attribute and does not modify the entity. Built from the domain model: a Mermaid ER diagram's attribute lines, or a TypeQL entity's owned attributes. Authored in the structural model (openspec/structure/) where an SDD has one. Added in schema 5.1.0; built from domain models since 6.0.0."
+    description: "An attribute of a domain-model entity, an element of its own (M-ADR 0230 §4.3): adding a field to an entity adds an attribute and does not modify the entity. Built from the domain model: a Mermaid ER diagram's attribute lines, or a TypeQL entity's owned attributes. Authored in the structural model (openspec/structure/) where an SDD has one. Added in schema 5.1.0; built from domain models since 6.0.0."
     natural_key:
     - entity_id
     - name
@@ -5012,7 +5032,7 @@ catalogues:
       nullable: true
       description: The platform SDD the row belongs to (stamped at aggregation).
       source_of_truth: execution
-    description: "A named relationship from one domain-model entity to another, an element of its own (M-ADR 0230 §4.3, Proposed). Built from the domain model: a Mermaid ER diagram's relationship lines, or a TypeQL binary relation, with each end's cardinality and role. Authored in the structural model (openspec/structure/) where an SDD has one. Added in schema 5.1.0; built from domain models since 6.0.0, when one cardinality became two, one per end."
+    description: "A named relationship from one domain-model entity to another, an element of its own (M-ADR 0230 §4.3). Built from the domain model: a Mermaid ER diagram's relationship lines, or a TypeQL binary relation, with each end's cardinality and role. Authored in the structural model (openspec/structure/) where an SDD has one. Added in schema 5.1.0; built from domain models since 6.0.0, when one cardinality became two, one per end."
     natural_key:
     - from_entity_id
     - to_entity_id
@@ -5065,7 +5085,7 @@ catalogues:
       nullable: true
       description: The platform SDD the row belongs to (stamped at aggregation).
       source_of_truth: execution
-    description: "A domain invariant, a typed element of the domain model (M-ADR 0230 §4.3, Proposed): a rule the entity's data always satisfies. It is structure, not intent, wherever it is first written. Built from the domain model's keys: a primary key (PK, or a TypeQL @key) or a unique key (UK) is a unique invariant over its attributes, and a TypeQL role's @card is a cardinality invariant on its relationship. Authored in the structural model (openspec/structure/) where an SDD has one, which can state every kind. Added in schema 5.1.0; built from domain models since 6.0.0."
+    description: "A domain invariant, a typed element of the domain model (M-ADR 0230 §4.3): a rule the entity's data always satisfies. It is structure, not intent, wherever it is first written. Built from the domain model's keys: a primary key (PK, or a TypeQL @key) or a unique key (UK) is a unique invariant over its attributes, and a TypeQL role's @card is a cardinality invariant on its relationship. Authored in the structural model (openspec/structure/) where an SDD has one, which can state every kind. Added in schema 5.1.0; built from domain models since 6.0.0."
     foreign_keys:
     - column: entity_id
       references: entities.id
@@ -5111,7 +5131,7 @@ catalogues:
       nullable: true
       description: The platform SDD the row belongs to (stamped at aggregation).
       source_of_truth: execution
-    description: "One row per distinct text of a requirement (M-ADR 0230 §4.7, Proposed; schema 6.0.0). Derived from the behaviour store: the living spec's text is current; an agreed open change's ADDED or MODIFIED block is intended; an archived change's block the living spec no longer holds is history. A revision is identified by its digest, so the same text is one revision wherever it appears."
+    description: "One row per distinct text of a requirement (M-ADR 0230 §4.7; schema 6.0.0). Derived from the behaviour store: the living spec's text is current; an agreed open change's ADDED or MODIFIED block is intended; an archived change's block the living spec no longer holds is history. A revision is identified by its digest, so the same text is one revision wherever it appears."
     foreign_keys:
     - column: requirement_id
       references: requirements.id
@@ -5160,7 +5180,7 @@ catalogues:
       type: string
       nullable: true
       description: The platform SDD the row belongs to (stamped at aggregation).
-    description: "One row per element a change writes (M-ADR 0230 §4.7, Proposed; schema 6.0.0): a requirement from its behaviour deltas, a structural element from its structural deltas (an archived change's from its effect record, structure/applied.yaml). Base and target are the revisions it moves the element between; a requirement's are revision ids (<requirement>@<12 hex digits of its digest>), catalogued in requirement_revisions except the target of a change not yet agreed; a structural element's are sha256 digests."
+    description: "One row per element a change writes (M-ADR 0230 §4.7; schema 6.0.0): a requirement from its behaviour deltas, a structural element from its structural deltas (an archived change's from its effect record, structure/applied.yaml). Base and target are the revisions it moves the element between; a requirement's are revision ids (<requirement>@<12 hex digits of its digest>), catalogued in requirement_revisions except the target of a change not yet agreed; a structural element's are sha256 digests."
     natural_key:
     - change_id
     - element_kind
@@ -5196,7 +5216,7 @@ catalogues:
     - name: sunset_date
       type: string
       nullable: true
-      description: "For a deprecated revision, the date it is retired. Not yet populated: the builder does not yet read a version's sunset date (BASELINE.md's optional sunset_date)."
+      description: "For a deprecated revision, the date it is retired: the sunset an archived change's agreement record states for the version (contracts[].deprecates.sunset, agreement-record schema 1.3.0). Empty for a version deprecated only in BASELINE.md, whose sunset is not read."
     - name: change_id
       type: string
       nullable: true
@@ -5212,7 +5232,7 @@ catalogues:
       nullable: true
       description: The platform SDD the row belongs to (stamped at aggregation).
       source_of_truth: execution
-    description: A contract version's content revisions, each identified by its content digest (M-ADR 0230 §4.2, Proposed; schema 6.0.0). The contract file's current content is active (deprecated where the contract is); a revision an agreed open change pins as the one it agrees (agreement record 1.2.0, contracts[].agrees) is agreed; one an archived change agreed that the file no longer holds is retired. A compatible amendment is a new revision at the same path, so an agreed revision and the active one coexist, both checked. Active is a claim about the published specification, not about deployment.
+    description: A contract version's content revisions, each identified by its content digest (M-ADR 0230 §4.2; schema 6.0.0). The contract file's current content is active (deprecated where the contract is); a revision an agreed open change pins as the one it agrees (agreement record 1.2.0, contracts[].agrees) is agreed; one an archived change agreed that the file no longer holds is retired. A compatible amendment is a new revision at the same path, so an agreed revision and the active one coexist, both checked. Active is a claim about the published specification, not about deployment.
     foreign_keys:
     - column: contract_id
       references: contracts.id

package/dist/lib/catalogue/retired-catalogues.js

@@ -7,7 +7,7 @@ import { rm, stat } from "node:fs/promises";
 import { join } from "node:path";
 /** name -> why it went, and what replaced it. */
 export const RETIRED_CATALOGUES = new Map([
-    ["requirement_status", "retired in catalogue schema 6.0.0: evidence about one revision of a requirement is requirement_assertions (M-ADR 0230 §4.7, Proposed)"],
+    ["requirement_status", "retired in catalogue schema 6.0.0: evidence about one revision of a requirement is requirement_assertions (M-ADR 0230 §4.7)"],
 ]);
 /** Remove each retired catalogue's file from `dir`. Returns the file names removed. */
 export async function removeRetiredCatalogues(dir, findings, label) {

package/dist/lib/catalogue/rubric-coverage-map.yaml

@@ -954,7 +954,7 @@ coverage:
   entity_attributes:
     kind: entity
     scoring: scored-at-source
-    instrument: an element of the structural model (M-ADR 0230, Proposed); scored with its domain model by rubrics/domain-architecture-rubric.md
+    instrument: an element of the structural model (M-ADR 0230); scored with its domain model by rubrics/domain-architecture-rubric.md
     relationships:
       entity_id:
         class: membership
@@ -962,7 +962,7 @@ coverage:
   entity_relationships:
     kind: entity
     scoring: scored-at-source
-    instrument: an element of the structural model (M-ADR 0230, Proposed); scored with its domain model by rubrics/domain-architecture-rubric.md
+    instrument: an element of the structural model (M-ADR 0230); scored with its domain model by rubrics/domain-architecture-rubric.md
     relationships:
       from_entity_id:
         class: membership
@@ -973,7 +973,7 @@ coverage:
   domain_invariants:
     kind: entity
     scoring: scored-at-source
-    instrument: an element of the structural model (M-ADR 0230, Proposed); scored with its domain model by rubrics/domain-architecture-rubric.md
+    instrument: an element of the structural model (M-ADR 0230); scored with its domain model by rubrics/domain-architecture-rubric.md
     relationships:
       entity_id:
         class: membership
@@ -1039,3 +1039,7 @@ coverage:
     kind: enum
     scoring: not-applicable
     reason: closed vocabulary, not an artefact
+  ppt_archetype:
+    kind: enum
+    scoring: not-applicable
+    reason: closed vocabulary, not an artefact

package/dist/lib/catalogue/staleness-verdicts.js

@@ -40,7 +40,7 @@
 //   none — already reported by scores-coverage as unknown currency; not
 //       re-reported here.
 //
-// ASSESSED INPUTS (M-ADR 0230 §4.9, Proposed): a review that names its other inputs (`input_paths`) is read with
+// ASSESSED INPUTS (M-ADR 0230 §4.9): a review that names its other inputs (`input_paths`) is read with
 //   each of them, once its target is current. An input that moved stales the score, with the input named. So does an
 //   input gone from HEAD, and one the corpus did not hold at the anchor: unlike a missing target, the score can still
 //   be re-reviewed against its target, and a review cannot have read an input that was not there, so both prescribe a
@@ -171,7 +171,7 @@ export async function runStalenessVerdicts(session, options) {
         };
     }
     const asStr = (v) => v === null || v === undefined ? "" : String(v).trim();
-    // input_paths (schema 6.0.0, M-ADR 0230 §4.9, Proposed): a catalogue built before it has no such column, and its
+    // input_paths (schema 6.0.0, M-ADR 0230 §4.9): a catalogue built before it has no such column, and its
     // scores are read as naming no other input.
     const query = (inputs) => `SELECT rubric_id, target_ref, target_path, corpus_ref, scored_at, staleness_basis, ${inputs}
      FROM "quality_scores"
@@ -191,7 +191,7 @@ export async function runStalenessVerdicts(session, options) {
         const rubricId = asStr(rubricIdRaw);
         const targetRef = asStr(targetRefRaw);
         const basis = asStr(basisRaw);
-        // The review's other assessed inputs (M-ADR 0230 §4.9, Proposed): read with the target, so an edit to any of
+        // The review's other assessed inputs (M-ADR 0230 §4.9): read with the target, so an edit to any of
         // them makes the score stale as an edit to the target does.
         const inputs = asStr(inputPathsRaw).split(";").map((x) => x.trim()).filter((x) => x !== "");
         // Counted for BOTH bases, before the branch. The first cut of this counter

package/dist/lib/structure/catalogue.js

@@ -1,13 +1,15 @@
-// The catalogue from the structural model, and the model a built catalogue implies (M-ADR 0230 §4.3, §5.3,
-// Proposed). Where an SDD has a model, it is the record of structure, so every structure catalogue is built from it whole:
+// The catalogue from the structural model, and the model a built catalogue implies (M-ADR 0230 §4.3, §5.3).
+// Where an SDD has a model, it is the record of structure, so every structure catalogue is built from it whole:
 //   a row per element of the current view, with the model's structure columns;
 //   its other columns (every class but structure: derived, declaration, evidence, intent, execution) from the
 //   source-built row with the same id;
 //   for an element only the model holds, the derived columns the model itself settles (MODEL_DERIVED).
 // What the sources hold and the model does not, and a structure column where they disagree, is reported once per
-// catalogue. The model wins: either finding means the sources moved outside a change. Pure: no file is read or written.
+// catalogue. The model wins: either finding means the sources moved outside a change. A source row that states an
+// element as an agreed open change adds or modifies it is that change's intended element, not a disagreement: it is
+// listed apart, and catalogued once the change archives. Pure: no file is read or written.
 import { stringify } from "yaml";
-import { FORMAT_VERSION } from "./model.js";
+import { elementKey, FORMAT_VERSION } from "./model.js";
 import { STRUCTURE } from "./view.js";
 /** The view each generated file renders, for a derived path column of an element only the model holds. */
 export const VIEW_PATHS = {
@@ -44,8 +46,10 @@ function sample(ids) {
 /**
  * Replace every structure catalogue's rows with the view's. Rows of other catalogues are returned as they are. Source
  * rows sharing an id are merged first, later values filling earlier gaps, as the keyed-table dedupe would.
+ * `intended` holds the elements agreed open changes add or modify (intendedWrites); a source row agreeing with one is
+ * pushed to `intendedOut` as `<key> (<change>)` instead of being reported.
  */
-export function overlayModel(schema, view, rows, findings) {
+export function overlayModel(schema, view, rows, findings, intended = new Map(), intendedOut = []) {
     const out = new Map(rows);
     for (const cat of schema.catalogues) {
         if (cat.sourceOfTruth !== STRUCTURE)
@@ -66,6 +70,20 @@ export function overlayModel(schema, view, rows, findings) {
         const elements = view.get(cat.name) ?? new Map();
         const built = [];
         const differ = [];
+        const disagree = (from, e) => structural.filter((c) => cell(from[c]) !== "" && cell(from[c]) !== cell(e.columns[c]));
+        // The source row states the element as an agreed open change does; one stating it otherwise is reported as such.
+        const differIntended = [];
+        const asIntended = (id, from) => {
+            const w = intended.get(elementKey(cat.name, id));
+            if (w === undefined)
+                return false;
+            const cols = disagree(from, w.element);
+            if (cols.length > 0)
+                differIntended.push(`${id} (${cols.join(", ")}; ${w.change})`);
+            else
+                intendedOut.push(`${elementKey(cat.name, id)} (${w.change})`);
+            return true;
+        };
         for (const e of elements.values()) {
             const from = source.get(e.id);
             const row = {};
@@ -73,8 +91,8 @@ export function overlayModel(schema, view, rows, findings) {
                 for (const [k, v] of Object.entries(from))
                     if (!structural.includes(k))
                         row[k] = v;
-                const cols = structural.filter((c) => cell(from[c]) !== "" && cell(from[c]) !== cell(e.columns[c]));
-                if (cols.length > 0)
+                const cols = disagree(from, e);
+                if (cols.length > 0 && !asIntended(e.id, from))
                     differ.push(`${e.id} (${cols.join(", ")})`);
             }
             else {
@@ -85,12 +103,15 @@ export function overlayModel(schema, view, rows, findings) {
                 row[c] = e.columns[c];
             built.push(row);
         }
-        const missing = [...source.keys()].filter((id) => id !== "" && !elements.has(id)).sort();
+        const missing = [...source.keys()].filter((id) => id !== "" && !elements.has(id) && !asIntended(id, source.get(id))).sort();
         if (missing.length > 0) {
-            findings.add("divergence", `${cat.name}: the sources hold ${missing.length} row(s) the structural model does not (${sample(missing)}); the model is the record of structure, so they are not catalogued. Add them through a change's structural deltas, or remove them from the sources (M-ADR 0230 §4.3, Proposed)`, "warn", `catalogue:${cat.name}`);
+            findings.add("divergence", `${cat.name}: the sources hold ${missing.length} row(s) the structural model does not (${sample(missing)}); the model is the record of structure, so they are not catalogued. Add them through a change's structural deltas, or remove them from the sources (M-ADR 0230 §4.3)`, "warn", `catalogue:${cat.name}`);
+        }
+        if (differIntended.length > 0) {
+            findings.add("divergence", `${cat.name}: ${differIntended.length} source row(s) state an element an agreed open change adds or modifies, and disagree with it: ${sample(differIntended.sort())}. The change's delta is what archives; bring the source into line with it, or the delta with the source (M-ADR 0230 §4.3, §4.7)`, "warn", `catalogue:${cat.name}`);
         }
         if (differ.length > 0) {
-            findings.add("divergence", `${cat.name}: ${differ.length} element(s) where the sources and the structural model disagree, catalogued as the model states them: ${sample(differ.sort())}. A source that is a generated view is rendered again; any other is brought into line through a change (M-ADR 0230 §4.3, Proposed)`, "warn", `catalogue:${cat.name}`);
+            findings.add("divergence", `${cat.name}: ${differ.length} element(s) where the sources and the structural model disagree, catalogued as the model states them: ${sample(differ.sort())}. A source that is a generated view is rendered again; any other is brought into line through a change (M-ADR 0230 §4.3)`, "warn", `catalogue:${cat.name}`);
         }
         out.set(cat.name, built);
     }

package/dist/lib/structure/compose.js

@@ -1,4 +1,4 @@
-// Views over the structural model, and how changes compose (M-ADR 0230 §4.5, §4.7, Proposed).
+// Views over the structural model, and how changes compose (M-ADR 0230 §4.5, §4.7).
 //   current       the model as published
 //   at a change   current with that change's deltas and those of its dependency closure, dependencies first
 //   intended      current with every agreed change's deltas

package/dist/lib/structure/effects.js

@@ -1,4 +1,4 @@
-// A change's structural effect, and the effect record an archive leaves (M-ADR 0230 §4.6, §4.7, Proposed). Pure reads,
+// A change's structural effect, and the effect record an archive leaves (M-ADR 0230 §4.6, §4.7). Pure reads,
 // so the catalogue builder and the verify-only CLI can carry them; writing the record is apply.ts's.
 import { parseDocument } from "yaml";
 import { elementKey, revision } from "./model.js";

package/dist/lib/structure/intended.js

@@ -0,0 +1,199 @@
+// What an open change adds, for the references its own content makes (M-ADR 0230 §4.7, §4.11 proof 3).
+// A reference made by an open change resolves against the current view plus that change's additions: the elements its
+// structural deltas ADD, those of the changes in its depends_on closure, and the contracts its agreement record agrees
+// as new files. A reference made by anything else resolves against the current view only, so a current reference that
+// resolves only against an addition is still refused.
+// What ties content to a change is never the reference being resolved:
+//   a model element                        the change's own delta (validateDeltas, viewAt)
+//   a source-built row with a change_id    that change
+//   a contract row                         the change whose record agrees its file as new
+//   a row naming such a contract           that change
+//   a row built from the change's files    that change (its spec_path lies in openspec/changes/<change>/, as a
+//                                          requirement the change ADDS does)
+// Pure but for reading agreement records.
+import { readdir, readFile } from "node:fs/promises";
+import { join } from "node:path";
+import { parseDocument } from "yaml";
+import { closure } from "./compose.js";
+import { elementKey, loadChangeStructure } from "./model.js";
+export const CONTRACTS = "contracts";
+const LIFECYCLES = ["proposed", "agreed", "withdrawn", "superseded"];
+/** The change's agreement record (docs/agreements/<change>.yaml): its status, or `unrecorded`, and its new contract files. */
+export async function readAgreement(repo, change) {
+    let text;
+    try {
+        text = await readFile(join(repo, "docs", "agreements", `${change}.yaml`), "utf8");
+    }
+    catch {
+        return { status: "unrecorded", newContracts: [] };
+    }
+    let record;
+    try {
+        record = parseDocument(text).toJS()?.agreement_record;
+    }
+    catch {
+        return { status: "unrecorded", newContracts: [] };
+    }
+    const status = LIFECYCLES.find((s) => s === String(record?.["status"] ?? "")) ?? "unrecorded";
+    const newContracts = [];
+    const entries = Array.isArray(record?.["contracts"]) ? record["contracts"] : [];
+    for (const raw of entries) {
+        if (raw === null || typeof raw !== "object")
+            continue;
+        const e = raw;
+        if (e["amended_by_this_change"] !== true)
+            continue;
+        const files = Array.isArray(e["files"]) ? e["files"].map(String) : e["file"] !== undefined ? [String(e["file"])] : [];
+        // agreement-record schema 1.2.0 and later: a file the change relies on carries relies_on, so an agreed file
+        // without one is new (1.3.0 states it). An entry with no agrees predates the digests and says nothing either way.
+        const digest = (field, f) => {
+            const v = e[field];
+            return v !== null && typeof v === "object" ? String(v[f] ?? "") : String(v ?? "");
+        };
+        for (const f of files)
+            if (digest("agrees", f) !== "" && digest("relies_on", f) === "")
+                newContracts.push(`${String(e["repo"] ?? "")}/${f}`);
+    }
+    return { status, newContracts };
+}
+/** The open changes (openspec/changes/<change>, not archive/), with their agreement records. */
+export async function loadOpenChanges(repo, problems) {
+    let names;
+    try {
+        names = (await readdir(join(repo, "openspec", "changes"), { withFileTypes: true }))
+            .filter((e) => e.isDirectory() && e.name !== "archive")
+            .map((e) => e.name)
+            .sort();
+    }
+    catch {
+        names = [];
+    }
+    const open = new Map();
+    const newContracts = new Map();
+    for (const name of names) {
+        const agreement = await readAgreement(repo, name);
+        open.set(name, { structure: await loadChangeStructure(repo, name, problems), status: agreement.status });
+        newContracts.set(name, agreement.newContracts);
+    }
+    return { open, newContracts };
+}
+const cell = (v) => (v === null || v === undefined ? "" : String(v));
+/**
+ * Each open change's additions, and the change that adds each. A contract is identified by its built row: the row
+ * whose spec_path is `<repo>/<file>` as the record names it. A new contract with no built row adds nothing, and a
+ * reference to it stays unresolved.
+ */
+export class Additions {
+    open;
+    own = new Map();
+    adder = new Map();
+    constructor(open, newContracts, contractRows) {
+        this.open = open;
+        const idByPath = new Map();
+        for (const r of contractRows)
+            if (cell(r["spec_path"]) !== "")
+                idByPath.set(cell(r["spec_path"]), cell(r["id"]));
+        for (const [name, oc] of open) {
+            const keys = new Set();
+            for (const d of oc.structure.deltas)
+                for (const e of d.added)
+                    keys.add(elementKey(e.catalogue, e.id));
+            for (const p of newContracts.get(name) ?? []) {
+                const id = idByPath.get(p);
+                if (id !== undefined && id !== "")
+                    keys.add(elementKey(CONTRACTS, id));
+            }
+            this.own.set(name, keys);
+            for (const k of keys)
+                if (!this.adder.has(k))
+                    this.adder.set(k, name);
+        }
+    }
+    /** The open change that adds the element or contract, if one does. */
+    addedBy(catalogue, id) {
+        return this.adder.get(elementKey(catalogue, id));
+    }
+    /** Whether the element or contract is the change's own addition or one of its dependency closure's. */
+    within(change, catalogue, id) {
+        const key = elementKey(catalogue, id);
+        return closure(change, this.open).some((c) => this.own.get(c)?.has(key) ?? false);
+    }
+    /** The contracts the given changes add. */
+    contracts(changes) {
+        const out = new Set();
+        for (const c of changes)
+            for (const k of this.own.get(c) ?? [])
+                if (k.startsWith(`${CONTRACTS}/`))
+                    out.add(k.slice(CONTRACTS.length + 1));
+        return out;
+    }
+    /** The open changes a source-built row belongs to: its change_id, the change whose files it is built from, or a new contract it is or names. */
+    ownersOf(schema, catalogue, row, sddId) {
+        const out = new Set();
+        const changeId = cell(row["change_id"]);
+        if (changeId !== "") {
+            const name = changeId.startsWith(`${sddId}::`) ? changeId.slice(sddId.length + 2) : changeId;
+            if (this.open.has(name))
+                out.add(name);
+        }
+        const from = /^openspec\/changes\/([^/]+)\//.exec(cell(row["spec_path"]))?.[1];
+        if (from !== undefined && this.open.has(from))
+            out.add(from);
+        const contractOwner = (id) => {
+            const by = this.adder.get(elementKey(CONTRACTS, id));
+            if (by !== undefined)
+                out.add(by);
+        };
+        const cat = schema.catalogues.find((c) => c.name === catalogue);
+        if (catalogue === CONTRACTS && cat)
+            contractOwner(cell(row[cat.primaryKey]));
+        for (const fk of cat?.foreignKeys ?? [])
+            if (fk.references === `${CONTRACTS}.id` && cell(row[fk.column]) !== "")
+                contractOwner(cell(row[fk.column]));
+        return [...out].sort();
+    }
+}
+/**
+ * Sort a build's dangling references: a row an open change owns, naming that change's addition, resolves in that
+ * change's view. Every other stays dangling, including a row nothing ties to the change that adds its target.
+ */
+export function splitDangling(schema, rowsByCatalogue, failures, additions, sddId) {
+    const intended = [];
+    const dangling = [];
+    const index = new Map();
+    const rowOf = (catalogue, pk) => {
+        let byPk = index.get(catalogue);
+        if (!byPk) {
+            const key = schema.catalogues.find((c) => c.name === catalogue)?.primaryKey ?? "id";
+            byPk = new Map((rowsByCatalogue.get(catalogue) ?? []).map((r) => [cell(r[key]), r]));
+            index.set(catalogue, byPk);
+        }
+        return byPk.get(pk);
+    };
+    for (const f of failures) {
+        const [target, column] = f.target.split(".");
+        const targetPk = schema.catalogues.find((c) => c.name === target)?.primaryKey;
+        const row = rowOf(f.catalogue, f.referencingRow);
+        const owner = f.value === "" || column !== targetPk || row === undefined
+            ? undefined
+            : additions.ownersOf(schema, f.catalogue, row, sddId).find((c) => additions.within(c, target, f.value));
+        if (owner !== undefined)
+            intended.push({ failure: f, change: owner });
+        else {
+            const by = f.value === "" ? undefined : additions.addedBy(target, f.value);
+            dangling.push(by === undefined ? { failure: f } : { failure: f, addedBy: by });
+        }
+    }
+    return { intended, dangling };
+}
+/** Element key -> the agreed change that adds or modifies it, and the element as that change states it. */
+export function intendedWrites(open, agreed) {
+    const out = new Map();
+    for (const c of agreed) {
+        for (const d of open.get(c)?.structure.deltas ?? [])
+            for (const e of [...d.added, ...d.modified])
+                out.set(elementKey(e.catalogue, e.id), { change: c, element: e });
+    }
+    return out;
+}
+//# sourceMappingURL=intended.js.map

package/dist/lib/structure/model.js

@@ -1,4 +1,4 @@
-// The structural model and a change's structural deltas (M-ADR 0230 §4.3, §4.4, Proposed). Pure reads, so the
+// The structural model and a change's structural deltas (M-ADR 0230 §4.3, §4.4). Pure reads, so the
 // verify-only CLI can carry them. The format is docs/method/methods/guides/structural-model-format.md:
 //   openspec/structure/<partition>.yaml                    the model, one file per partition
 //   openspec/changes/<change>/structure/<partition>.yaml   a change's delta for that partition

package/dist/lib/structure/render.js

@@ -1,4 +1,4 @@
-// The generated views of the structural model (M-ADR 0230 §4.3, Proposed): projections, never edited. Each file is
+// The generated views of the structural model (M-ADR 0230 §4.3): projections, never edited. Each file is
 // rendered from the current view alone, in id order, so the same model renders the same bytes. Its first line names
 // the generator and the digest of the body below it, which tells three states apart:
 //   missing      the file is absent