@unified-product-graph/core 0.39.0 → 0.41.0

package/dist/index.d.cts

@@ -6387,6 +6387,76 @@ declare const UPG_EDGE_CATALOG: {
         target_type: string;
         deliberate_only: true;
     };
+    project_contains_epic: {
+        forward_verb: string;
+        reverse_verb: string;
+        classification: "hierarchy";
+        source_type: string;
+        target_type: string;
+    };
+    project_contains_feature: {
+        forward_verb: string;
+        reverse_verb: string;
+        classification: "hierarchy";
+        source_type: string;
+        target_type: string;
+    };
+    project_contains_user_story: {
+        forward_verb: string;
+        reverse_verb: string;
+        classification: "hierarchy";
+        source_type: string;
+        target_type: string;
+    };
+    project_contains_task: {
+        forward_verb: string;
+        reverse_verb: string;
+        classification: "hierarchy";
+        source_type: string;
+        target_type: string;
+    };
+    project_contains_bug: {
+        forward_verb: string;
+        reverse_verb: string;
+        classification: "hierarchy";
+        source_type: string;
+        target_type: string;
+    };
+    project_advances_key_result: {
+        forward_verb: string;
+        reverse_verb: string;
+        classification: "cross-domain";
+        source_type: string;
+        target_type: string;
+    };
+    project_drives_outcome: {
+        forward_verb: string;
+        reverse_verb: string;
+        classification: "cross-domain";
+        source_type: string;
+        target_type: string;
+    };
+    project_assumes_assumption: {
+        forward_verb: string;
+        reverse_verb: string;
+        classification: "cross-domain";
+        source_type: string;
+        target_type: string;
+    };
+    constraint_constrains_project: {
+        forward_verb: string;
+        reverse_verb: string;
+        classification: "cross-domain";
+        source_type: string;
+        target_type: string;
+    };
+    strategic_theme_pursues_project: {
+        forward_verb: string;
+        reverse_verb: string;
+        classification: "cross-domain";
+        source_type: string;
+        target_type: string;
+    };
     milestone_gates_release: {
         forward_verb: string;
         reverse_verb: string;
@@ -11636,6 +11706,29 @@ declare function rotateSlug<T extends Pick<UPGBaseNode, 'slug' | 'aliases'>>(nod
  *                      the containment guardrail (persona↔job↔need decompositions,
  *                      product-local reasoning) that must stay in-graph.
  *
+ * WILDCARD ENDPOINTS, STATED PLAINLY (0.41.0, field report `7aaa2f7e`). The
+ * mechanism is described on `isCrossCapable` below, but its consequence was
+ * never written down where a reader looks for it, so a reporter reasonably
+ * read a `decision_*_node` edge's absent scope as unfinished work and proposed
+ * declaring it `provisional`. It cannot be declared: scope is DERIVED, never
+ * authored. And `node` is not a type, so it can never be `portfolio_shared`
+ * and never carries the gate on its own. Therefore:
+ *
+ *   **An edge with a `node` wildcard endpoint is `resident` unless its OTHER,
+ *   concrete endpoint is a portfolio-shared type, or the edge type is curated
+ *   into `UPG_CROSS_EDGE_TYPES` by name.**
+ *
+ * That is why `node_owned_by_team` is cross-capable (team is shared) while
+ * `decision_influences_node`, `decision_produces_node`,
+ * `decision_constrained_by_node` and `risk_threatens_node` are resident:
+ * `decision` and `risk` are not in the shared tier. Only three wildcard edges
+ * are cross-capable today, all of them curated BY NAME.
+ *
+ * Widening one is a two-option decision and BOTH amend a ratified list, which
+ * is why it is not a spec-writer's call: curate the edge type by name, or
+ * promote the concrete endpoint type into the portfolio-shared tier, which
+ * moves every other edge touching that type at the same time.
+ *
  * The gate (`isCrossCapable`) is DERIVED from `EntityTypeMeta.portfolio_shared`, so
  * the guardrail is self-maintaining: a new persona/job/need internal edge is
  * auto-rejected with no list to touch. The gate LOGIC itself never changes the
@@ -27035,7 +27128,7 @@ declare function checkHeaderSealText(text: string): UPGHeaderSealReport;
  * it stamps the `upg_version` field of every `.upg` file written by the SDK.
  * The `check:version-lockstep` gate enforces this at release time.
  */
-declare const UPG_VERSION: "0.39.0";
+declare const UPG_VERSION: "0.41.0";
 /**
  * The `.upg` JSON document format version. Written to the `upg_version` field.
  * Evolves independently from `UPG_VERSION` (the catalogue version).

package/dist/index.d.ts

@@ -6387,6 +6387,76 @@ declare const UPG_EDGE_CATALOG: {
         target_type: string;
         deliberate_only: true;
     };
+    project_contains_epic: {
+        forward_verb: string;
+        reverse_verb: string;
+        classification: "hierarchy";
+        source_type: string;
+        target_type: string;
+    };
+    project_contains_feature: {
+        forward_verb: string;
+        reverse_verb: string;
+        classification: "hierarchy";
+        source_type: string;
+        target_type: string;
+    };
+    project_contains_user_story: {
+        forward_verb: string;
+        reverse_verb: string;
+        classification: "hierarchy";
+        source_type: string;
+        target_type: string;
+    };
+    project_contains_task: {
+        forward_verb: string;
+        reverse_verb: string;
+        classification: "hierarchy";
+        source_type: string;
+        target_type: string;
+    };
+    project_contains_bug: {
+        forward_verb: string;
+        reverse_verb: string;
+        classification: "hierarchy";
+        source_type: string;
+        target_type: string;
+    };
+    project_advances_key_result: {
+        forward_verb: string;
+        reverse_verb: string;
+        classification: "cross-domain";
+        source_type: string;
+        target_type: string;
+    };
+    project_drives_outcome: {
+        forward_verb: string;
+        reverse_verb: string;
+        classification: "cross-domain";
+        source_type: string;
+        target_type: string;
+    };
+    project_assumes_assumption: {
+        forward_verb: string;
+        reverse_verb: string;
+        classification: "cross-domain";
+        source_type: string;
+        target_type: string;
+    };
+    constraint_constrains_project: {
+        forward_verb: string;
+        reverse_verb: string;
+        classification: "cross-domain";
+        source_type: string;
+        target_type: string;
+    };
+    strategic_theme_pursues_project: {
+        forward_verb: string;
+        reverse_verb: string;
+        classification: "cross-domain";
+        source_type: string;
+        target_type: string;
+    };
     milestone_gates_release: {
         forward_verb: string;
         reverse_verb: string;
@@ -11636,6 +11706,29 @@ declare function rotateSlug<T extends Pick<UPGBaseNode, 'slug' | 'aliases'>>(nod
  *                      the containment guardrail (persona↔job↔need decompositions,
  *                      product-local reasoning) that must stay in-graph.
  *
+ * WILDCARD ENDPOINTS, STATED PLAINLY (0.41.0, field report `7aaa2f7e`). The
+ * mechanism is described on `isCrossCapable` below, but its consequence was
+ * never written down where a reader looks for it, so a reporter reasonably
+ * read a `decision_*_node` edge's absent scope as unfinished work and proposed
+ * declaring it `provisional`. It cannot be declared: scope is DERIVED, never
+ * authored. And `node` is not a type, so it can never be `portfolio_shared`
+ * and never carries the gate on its own. Therefore:
+ *
+ *   **An edge with a `node` wildcard endpoint is `resident` unless its OTHER,
+ *   concrete endpoint is a portfolio-shared type, or the edge type is curated
+ *   into `UPG_CROSS_EDGE_TYPES` by name.**
+ *
+ * That is why `node_owned_by_team` is cross-capable (team is shared) while
+ * `decision_influences_node`, `decision_produces_node`,
+ * `decision_constrained_by_node` and `risk_threatens_node` are resident:
+ * `decision` and `risk` are not in the shared tier. Only three wildcard edges
+ * are cross-capable today, all of them curated BY NAME.
+ *
+ * Widening one is a two-option decision and BOTH amend a ratified list, which
+ * is why it is not a spec-writer's call: curate the edge type by name, or
+ * promote the concrete endpoint type into the portfolio-shared tier, which
+ * moves every other edge touching that type at the same time.
+ *
  * The gate (`isCrossCapable`) is DERIVED from `EntityTypeMeta.portfolio_shared`, so
  * the guardrail is self-maintaining: a new persona/job/need internal edge is
  * auto-rejected with no list to touch. The gate LOGIC itself never changes the
@@ -27035,7 +27128,7 @@ declare function checkHeaderSealText(text: string): UPGHeaderSealReport;
  * it stamps the `upg_version` field of every `.upg` file written by the SDK.
  * The `check:version-lockstep` gate enforces this at release time.
  */
-declare const UPG_VERSION: "0.39.0";
+declare const UPG_VERSION: "0.41.0";
 /**
  * The `.upg` JSON document format version. Written to the `upg_version` field.
  * Evolves independently from `UPG_VERSION` (the catalogue version).

package/dist/index.js

@@ -2735,6 +2735,93 @@ var UPG_EDGE_CATALOG = {
   // arbitrary work. deliberate_only because project membership is authored,
   // never inferred from co-occurrence.
   project_delivers_work_item: { forward_verb: "delivers", reverse_verb: "delivered_by", classification: "semantic", source_type: "project", target_type: "node", deliberate_only: true },
+  // ── project as a first-class home for work (0.41.0, Captain-ratified) ──────
+  //
+  // Teams model in Linear, where an Initiative holds Projects and a Project
+  // holds Issues; UPG must express that natively or every sync leaves a reader
+  // guessing which node is which. `project_implements_initiative` already
+  // carries the upper relation (read from the project's side). These five carry
+  // the lower one, and the set is exactly what the Linear issue-type map
+  // produces: an issue becomes a feature, bug, task, user_story or epic.
+  //
+  // WHY THESE ARE CONTAINMENT AND `project_delivers_work_item` IS NOT.
+  // 0.33.0 widened `project_delivers_epic` into the polymorphic
+  // `project_delivers_work_item` and ruled, correctly, that it could not be a
+  // `contains` verb: containment obliges a `UPG_VALID_CHILDREN` pair keyed by
+  // CONCRETE type names, which a wildcard endpoint can never supply. That
+  // argument forecloses containment for the wildcard; it does not foreclose
+  // containment for concrete pairs, which is what these are. So this is not a
+  // reversal of that ruling — it is the half the wildcard could not reach.
+  //
+  // A KNOWN SHADOW PAIR, ACCEPTED DELIBERATELY (Captain, 2026-09-04). Both an
+  // authored `project_contains_task` and a `project_delivers_work_item` can
+  // name the same pair. That duplication is real and is taken on purpose, to
+  // avoid a migration on live `project_delivers_work_item` instances. The
+  // precedence is stated so it is never ambiguous: CONTAINMENT IS THE PARENT
+  // AXIS AND WINS; the polymorphic edge stays the reference for targets outside
+  // the concrete set. If a real graph is ever observed holding both for one
+  // pair, that is the signal to retire the polymorphic edge for these five
+  // types and migrate — the option deliberately not taken here.
+  project_contains_epic: { forward_verb: "contains", reverse_verb: "belongs_to", classification: "hierarchy", source_type: "project", target_type: "epic" },
+  project_contains_feature: { forward_verb: "contains", reverse_verb: "belongs_to", classification: "hierarchy", source_type: "project", target_type: "feature" },
+  project_contains_user_story: { forward_verb: "contains", reverse_verb: "belongs_to", classification: "hierarchy", source_type: "project", target_type: "user_story" },
+  project_contains_task: { forward_verb: "contains", reverse_verb: "belongs_to", classification: "hierarchy", source_type: "project", target_type: "task" },
+  project_contains_bug: { forward_verb: "contains", reverse_verb: "belongs_to", classification: "hierarchy", source_type: "project", target_type: "bug" },
+  // ── project's strategic reach (0.41.0) ────────────────────────────────────
+  //
+  // The parity half. `initiative` and `project` are two granularities of the
+  // same idea, and teams pick one: Linear-shaped teams put the dated, owned,
+  // key-result-linked bet in a PROJECT, while the standard's `initiative`
+  // carried all the strategic reach and `project` reached milestone,
+  // deliverable and a wildcard. A team choosing the honest name for its
+  // granularity should not lose its connection to strategy.
+  //
+  // Mirrors of initiative's edges on the FORWARD verbs, so a reader moving
+  // between the two granularities is never re-learning the vocabulary. The
+  // mirror is deliberately not total, and the two places it stops are both
+  // correct rather than sloppy:
+  //
+  //   REVERSE VERBS. `strategic_theme_pursues_initiative` reverses to
+  //   `pursued_under`, which reads as membership in a theme's programme.
+  //   `strategic_theme_pursues_project` reverses to `pursued_by`, because a
+  //   project is the vehicle doing the pursuing, not a subdivision of the
+  //   theme. Same forward verb, different relationship on the way back.
+  //
+  //   CLASSIFICATION. Initiative's five are causal / cross-domain / hierarchy
+  //   / semantic; all five of these are `cross-domain`. That is domain
+  //   arithmetic, not inconsistency: `initiative` sits in `strategy` alongside
+  //   its targets, so a `cross-domain` classification there would be T1.7
+  //   same-domain debt, while `project` is `program_mgmt` and every target
+  //   here is `strategy`, so `cross-domain` is the measured truth and adds
+  //   nothing to that debt.
+  //
+  // CROSS-PRODUCT SCOPE, ruled deliberately (2026-09-04, raised by Troi during
+  // the 0.41.0 editorial pass). Three of initiative's carry
+  // `cross_product_eligible: true` and none of these do, which looks at first
+  // like reinstating at the portfolio seam the reach this change removes
+  // elsewhere. It is not: `key_result`, `outcome` and `strategic_theme` are
+  // all `portfolio_shared`, so these edges already resolve `provisional` and
+  // ARE authorable across graphs today, with a warning, not rejected. The
+  // difference is curated (hard-allow, silent) versus provisional (allowed,
+  // warned). Left provisional on purpose: the curated set is a ratified
+  // snapshot that grows on measured need, and no field evidence yet shows
+  // anyone authoring these across graphs. Promote to curated when it appears,
+  // which is a one-flag change per edge.
+  //
+  // Deliberately NOT mirrored: `initiative_enters_market_segment`,
+  // `_realises_value_proposition`, `_unlocks_revenue_stream` and
+  // `_raises_strategic_question`. A delivery-scoped project does not enter a
+  // market or unlock a revenue stream; that reach belongs to the coarser level,
+  // and copying it down would make the two types synonyms rather than
+  // granularities. `capability` needs no edge either: a project reaches it
+  // through the features it now contains (`capability_implemented_by_feature`),
+  // and `decision` already reaches a project through the polymorphic
+  // `decision_influences_node`.
+  project_advances_key_result: { forward_verb: "advances", reverse_verb: "advanced_by", classification: "cross-domain", source_type: "project", target_type: "key_result" },
+  project_drives_outcome: { forward_verb: "drives", reverse_verb: "driven_by", classification: "cross-domain", source_type: "project", target_type: "outcome" },
+  project_assumes_assumption: { forward_verb: "assumes", reverse_verb: "assumed_by", classification: "cross-domain", source_type: "project", target_type: "assumption" },
+  constraint_constrains_project: { forward_verb: "constrains", reverse_verb: "constrained_by", classification: "cross-domain", source_type: "constraint", target_type: "project" },
+  strategic_theme_pursues_project: { forward_verb: "pursues", reverse_verb: "pursued_by", classification: "cross-domain", source_type: "strategic_theme", target_type: "project" },
   milestone_gates_release: { forward_verb: "gates", reverse_verb: "gated_by", classification: "cross-domain", source_type: "milestone", target_type: "release" },
   milestone_triggers_release: { forward_verb: "triggers", reverse_verb: "triggered_by", classification: "cross-domain", source_type: "milestone", target_type: "release" },
   deliverable_ships_feature: { forward_verb: "ships", reverse_verb: "shipped_by", classification: "cross-domain", source_type: "deliverable", target_type: "feature" },
@@ -7727,7 +7814,7 @@ var UPG_VALID_CHILDREN = {
   subscription: ["invoice"],
   // ── Program Management hierarchy ─────────────────────────────────────────────
   program: ["project", "risk_register", "change_request", "resource_allocation", "status_report"],
-  project: ["milestone", "deliverable"],
+  project: ["milestone", "deliverable", "epic", "feature", "user_story", "task", "bug"],
   risk_register: ["risk"],
   // ── Accessibility hierarchy ──────────────────────────────────────────────────
   a11y_standard: ["a11y_guideline", "a11y_audit", "a11y_annotation"],
@@ -33894,7 +33981,7 @@ function checkHeaderSealText(text) {
 }
 
 // src/index.ts
-var UPG_VERSION = "0.39.0";
+var UPG_VERSION = "0.41.0";
 var UPG_FORMAT_VERSION = "0.4.0";
 var MARKDOWN_FORMAT_VERSION = "0.1";
 var UPG_TYPES = getTypes();