@unified-product-graph/core 0.31.0 → 0.32.0

package/dist/index.cjs

@@ -775,7 +775,7 @@ var UPG_DOMAINS = [
     id: "workspace",
     label: "Workspace",
     description: "Spatial thinking spaces for arranging entities, debating decisions, and committing to the graph. Workspaces are transient canvases that sit alongside all other domains, letting you compose and explore relationships before they become permanent graph structure. A framework exercise is a structured workspace: one run of a framework (MoSCoW, RICE, Kano, \u2026) applied to a chosen set of entities, with each entity's result recorded on the exercise-to-entity edge rather than the entity itself. A composition is the durable other half: a named, published view assembled from a canvas, with a stable slug people link to and a revision history, whose frozen arrangement holds pointers rather than copied content.",
-    types: ["workspace", "framework_exercise", "composition"]
+    types: ["workspace", "framework_exercise", "composition", "capture"]
   },
   {
     id: "foundations",
@@ -1263,7 +1263,10 @@ var UPG_ENTITY_META = [
   // ── Workspace ──
   { name: "workspace", type_id: "ent_328", maturity: "proposed", since: "0.2.0" },
   { name: "framework_exercise", type_id: "ent_350", maturity: "proposed", since: "0.8.4" },
-  { name: "composition", type_id: "ent_361", maturity: "proposed", since: "0.31.0" }
+  { name: "composition", type_id: "ent_361", maturity: "proposed", since: "0.31.0" },
+  // A dated, hashed rendition of a node that is already in the graph. Enters
+  // `proposed` per the maturity rubric (precedent: composition 0.31.0).
+  { name: "capture", type_id: "ent_362", maturity: "proposed", since: "0.32.0" }
 ];
 var DEFERRED_PROPOSED_BY_CONTRACT = {
   // user_story (UPG-571) and experiment_run (UPG-664) graduated to stable in
@@ -1551,6 +1554,24 @@ var UPG_EDGE_CATALOG = {
   // the catalog's singular-source/target grammar (polymorphic targets
   // would be a separate catalog-mechanic change).
   competitive_analysis_dimensioned_by_classification_axis: { forward_verb: "dimensioned_by", reverse_verb: "dimensions", classification: "hierarchy", source_type: "competitive_analysis", target_type: "classification_axis" },
+  // A product's own classification axes (0.32.0). Before this the only parent a
+  // classification_axis could have was a competitive_analysis, so a taxonomy the
+  // product uses on its OWN entities — the grouped-label case, one named group
+  // over a set of values — had to hang off a competitive analysis it has nothing
+  // to do with, or float parentless.
+  //
+  // Hierarchy, so the axis has a home in get_tree, on the same honest verb the
+  // competitive_analysis edge already uses; and it earns its
+  // UPG_VALID_CHILDREN.product pair the same way product_defines_configuration_axis
+  // did at 0.30.0 — axes are few per product, and visibility of a mechanism
+  // matters more than the tree cost.
+  //
+  // This is what makes one level of label grouping expressible with NO new label
+  // surface: the group is the axis, the labels are its values, and carrying one
+  // is node_classified_as_classification_value, all of it stable since 0.4.0.
+  // Ungrouped freeform labels stay in `tags`. The line between them: if the
+  // group has a name a person would filter by, it is an axis; otherwise a tag.
+  product_dimensioned_by_classification_axis: { forward_verb: "dimensioned_by", reverse_verb: "dimensions", classification: "hierarchy", source_type: "product", target_type: "classification_axis" },
   classification_axis_includes_classification_value: { forward_verb: "includes", reverse_verb: "value_of", classification: "hierarchy", source_type: "classification_axis", target_type: "classification_value" },
   // 0.10.2: also dual-registered as a cross-edge (UPG_CROSS_EDGE_TYPES) so a
   // competitor can be classified directly against a `registry/{classification_value}`
@@ -1790,10 +1811,20 @@ var UPG_EDGE_CATALOG = {
   // iterations; a cycle contains its cooldown), mirroring team_contains_team.
   planning_cycle_contains_planning_cycle: { forward_verb: "contains", reverse_verb: "belongs_to", classification: "hierarchy", source_type: "planning_cycle", target_type: "planning_cycle" },
   // E3: scheduling work into a cycle is a deliberate authoring act, not a
-  // containment nesting — user_story keeps its feature/epic parent and is merely
-  // referenced by the cycle. deliberate_only so the generic-inference chokepoints
-  // never auto-materialise it.
-  planning_cycle_schedules_user_story: { forward_verb: "schedules", reverse_verb: "scheduled_in", classification: "semantic", source_type: "planning_cycle", target_type: "user_story", deliberate_only: true },
+  // containment nesting — the work item keeps its feature/epic parent and is
+  // merely referenced by the cycle. deliberate_only so the generic-inference
+  // chokepoints never auto-materialise it.
+  //
+  // WIDENED AT 0.32.0, renamed from planning_cycle_schedules_user_story. The
+  // story-only endpoint could not hold a real tracker import: the adapters
+  // default an unrecognised issue to `task`, so the type a cycle most needed to
+  // schedule was the one type it could not reach. Endpoint-polymorphic over the
+  // work-item set {feature, epic, user_story, task, bug} by the same
+  // construction as work_item_blocks_work_item in the same 0.20.0 batch — the
+  // `work_item` token names the intended semantic domain, the endpoint is the
+  // `node` wildcard. Three typed edges were the alternative and would have
+  // re-opened a decision this vocabulary already took for the same entity set.
+  planning_cycle_schedules_work_item: { forward_verb: "schedules", reverse_verb: "scheduled_in", classification: "semantic", source_type: "planning_cycle", target_type: "node", deliberate_only: true },
   // E2: the OKR cycle-scoping anchor. objective -> planning_cycle. planning_cycle
   // is portfolio_shared, so this passes the cross-scope gate and ships as
   // PROVISIONAL (allowed cross-product with a write-time warning, self-maintaining,
@@ -2918,6 +2949,16 @@ var UPG_EDGE_CATALOG = {
   // NOT cross_product_eligible: a portfolio-level composition spanning several
   // product graphs is conceivable but unevidenced. Same YAGNI call as above.
   composition_focuses_node: { forward_verb: "focuses", reverse_verb: "focused_in", classification: "cross-domain", source_type: "composition", target_type: "node" },
+  // What a capture is a picture OF (0.32.0). Polymorphic because anything in the
+  // graph can be rendered — a surface, a screen, a report, a canvas — and being
+  // captured carries no structural role, so the endpoint collapses to the
+  // wildcard rather than enumerating a list that would never finish.
+  //
+  // This edge is also where the preservation-is-not-permission rule lands for
+  // renditions: a consumer renders the captures the GRAPH says exist, never the
+  // ones some tool's opaque bag still remembers. A capture that was deleted is a
+  // node that was deleted, and the spec needs no second deletion vocabulary.
+  capture_renders_node: { forward_verb: "renders", reverse_verb: "rendered_by", classification: "cross-domain", source_type: "capture", target_type: "node" },
   // ── P14 edges (replacing foreign-key properties) ─────────────────────────
   feature_addresses_job: { forward_verb: "addresses", reverse_verb: "addressed_by", classification: "cross-domain", source_type: "feature", target_type: "job" },
   feature_drives_key_result: { forward_verb: "drives", reverse_verb: "driven_by", classification: "cross-domain", source_type: "feature", target_type: "key_result" },
@@ -3034,6 +3075,23 @@ var UPG_EDGE_CATALOG = {
   node_owned_by_stakeholder: { forward_verb: "owned_by", reverse_verb: "owns", classification: "cross-domain", source_type: "node", target_type: "stakeholder" },
   node_owned_by_department: { forward_verb: "owned_by", reverse_verb: "owns", classification: "cross-domain", source_type: "node", target_type: "department", cross_product_eligible: true },
   node_owned_by_person: { forward_verb: "owned_by", reverse_verb: "owns", classification: "cross-domain", source_type: "node", target_type: "person" },
+  // ── Cross-domain: Assignment (0.32.0) ───────────────────────────────────────
+  // Assignment is NOT ownership, and 0.12.0 ruled otherwise. That ruling routed
+  // task.assignee and bug.assignee into node_owned_by_person, and it is
+  // superseded here rather than quietly widened, because the two differ in a way
+  // the field measures.
+  //
+  // ASSIGNMENT HAS A TIME INTERVAL AND OWNERSHIP DOES NOT. A shipped ops plane
+  // models assignment as a claim carrying claimed-at, released-at and a partial
+  // unique index enforcing one live claim; nothing in the spec gives ownership
+  // that shape. And a real 184-item board ran with 157 items (85%) unassigned
+  // while every one of them was owned in the ordinary sense. One edge meaning
+  // both cannot express "owned by the team, assigned to nobody", which is the
+  // modal state of a working board.
+  //
+  // Not cross_product_eligible, matching node_owned_by_person: an assignee is a
+  // person in this graph's own roster.
+  node_assigned_to_person: { forward_verb: "assigned_to", reverse_verb: "assigned", classification: "cross-domain", source_type: "node", target_type: "person" },
   // ── Cross-domain: Architecture (DDD) ─────────────────────────────────────────
   // Service, domain_event, domain_entity, aggregate, read_model, api_contract,
   // value_object, command, and data_model are DDD building blocks that all
@@ -3978,7 +4036,18 @@ var UPG_POLYMORPHIC_EDGE_KEYS = [
   // onto a canvas or shown in a published view, and neither carries a
   // structural role, so both collapse polymorphic rather than enumerating.
   "workspace_arranges_node",
-  "composition_focuses_node"
+  "composition_focuses_node",
+  // Universal assignment (0.32.0): who is working on this, as distinct from who
+  // owns it. Wildcard source for the same reason node_owned_by_person has one.
+  "node_assigned_to_person",
+  // Capture subject (0.32.0): anything in the graph can be rendered, and being
+  // rendered carries no structural role.
+  "capture_renders_node",
+  // Cadence scheduling (0.32.0, widened from planning_cycle_schedules_user_story):
+  // endpoint-polymorphic over the work-item set {feature, epic, user_story, task,
+  // bug}. The `work_item` key token names the intended semantic domain; the
+  // endpoint is the `node` wildcard.
+  "planning_cycle_schedules_work_item"
 ];
 var _POLY_KEY_SET = new Set(UPG_POLYMORPHIC_EDGE_KEYS);
 function isPolymorphicEdge(key) {
@@ -4173,6 +4242,11 @@ var UPG_VALID_CHILDREN = {
     // the product renders. Few per product, and top-level because an axis is a
     // product-wide fact rather than a child of any one feature or surface.
     "configuration_axis",
+    // Classification (0.32.0): the product's own taxonomies — the grouped-label
+    // case, one named group over a set of values. Same reasoning as the
+    // configuration axis above, and until now the only parent a
+    // classification_axis could have was a competitive_analysis.
+    "classification_axis",
     // Engineering
     "bounded_context",
     "code_repository",
@@ -4457,7 +4531,7 @@ var UPG_VALID_CHILDREN = {
   // contains iterations; a cycle contains its cooldown) via
   // planning_cycle_contains_planning_cycle. It does NOT contain user_story as a
   // child: scheduling work into a cycle is the semantic, deliberate-only
-  // planning_cycle_schedules_user_story edge, so a story keeps its feature/epic
+  // planning_cycle_schedules_work_item edge, so the item keeps its feature/epic
   // containment parent and is merely referenced by the cycle.
   planning_cycle: ["planning_cycle"],
   // ── Engineering hierarchy ───────────────────────────────────────────────────
@@ -4803,7 +4877,12 @@ var UPG_CONTAINMENT_FREE_TYPES = /* @__PURE__ */ new Set([
   // part of the product, it is a lens onto one. This is also what keeps the
   // type to two edges rather than three: no provenance edge is minted (that is
   // `workspace_produced_node`, reused) and no parent edge is needed.
-  "composition"
+  "composition",
+  // A capture has no structural parent for the same reason: it anchors to what
+  // it RENDERS, via `capture_renders_node`. Giving it a product parent would
+  // claim a capture is part of the product rather than a picture of one, and
+  // would mint a containment edge whose only job is to satisfy the hierarchy.
+  "capture"
 ]);
 function isContainmentFreeType(entityType) {
   return UPG_CONTAINMENT_FREE_TYPES.has(entityType);
@@ -6909,7 +6988,8 @@ var WORK_ITEM_TEMPLATE = {
   initial_phase: "todo",
   terminal_phases: ["done", "cancelled"],
   phases: [
-    { id: "todo", status_category: "unstarted", label: "To Do", description: "Identified but not yet started.", transitions_to: ["in_progress", "cancelled"] },
+    { id: "backlog", status_category: "backlog", label: "Backlog", description: "Accepted or set aside deliberately: real work, not scheduled. Distinct from `todo`, which is committed and merely not started.", transitions_to: ["todo", "in_progress", "cancelled"] },
+    { id: "todo", status_category: "unstarted", label: "To Do", description: "Identified but not yet started.", transitions_to: ["in_progress", "backlog", "cancelled"] },
     { id: "in_progress", status_category: "started", label: "In Progress", description: "Actively being worked on.", transitions_to: ["in_review", "todo", "cancelled"] },
     { id: "in_review", status_category: "started", label: "In Review", description: "Work completed, awaiting review or acceptance.", transitions_to: ["done", "in_progress", "cancelled"] },
     { id: "done", status_category: "completed", label: "Done", description: "Completed and accepted.", transitions_to: [] },
@@ -7540,7 +7620,11 @@ var UPG_LIFECYCLE_FREE_TYPES = /* @__PURE__ */ new Set([
   //    from experiment_runs (which have lifecycles); hypothesis_evidence was
   //    lifecycle-free here but is deprecated at v0.4.0 ──────────────────────────────────────
   "evidence",
-  "learning"
+  "learning",
+  // ── Workspace (1 of 4): a capture is a fact about a moment, not a workflow.
+  //    It is taken, and from then on it either still matches its subject or it
+  //    does not — which is what `content_hash` answers, not a phase. ─────────
+  "capture"
 ]);
 function isLifecycleFreeType(entityType) {
   return UPG_LIFECYCLE_FREE_TYPES.has(entityType);
@@ -8444,6 +8528,46 @@ function getDeprecatedTypes() {
   return deprecated;
 }
 var UPG_PROPERTY_MIGRATIONS = {
+  "0.32.0": [
+    // C3 — archive becomes a base-node axis. WorkspaceProperties.archived /
+    // archived_at shipped the orthogonal-archive idea for exactly one type;
+    // field data showed it is general (a tracker held 559 archived-completed
+    // items beside 18 live-completed ones), so the pair moves to UPGBaseNode
+    // and the workspace properties are @deprecated. Lift, not drop: the value
+    // is real and its new home means the same thing.
+    {
+      kind: "lift_property_to_top_level",
+      type: "workspace",
+      from_property: "archived",
+      to: "archived",
+      reason: "0.32.0: archive generalised from WorkspaceProperties to UPGBaseNode.archived. Same fact, wider home; the workspace property is @deprecated."
+    },
+    {
+      kind: "lift_property_to_top_level",
+      type: "workspace",
+      from_property: "archived_at",
+      to: "archived_at",
+      reason: "0.32.0: pairs with the archived lift above. UPGBaseNode.archived_at is the canonical home."
+    },
+    // C4 — the duplicate label surfaces. TaskProperties.labels and
+    // BugProperties.labels were declared "applied uniformly across work item
+    // types" and duplicated base-node `tags` with no consumer anywhere. Three
+    // label surfaces (base tags, per-type tags, per-type labels) is two too
+    // many; grouped labels are classification_axis + classification_value, and
+    // ungrouped ones are `tags`.
+    {
+      kind: "drop_props",
+      type: "task",
+      drop_props: ["labels"],
+      reason: "0.32.0: TaskProperties.labels duplicated base-node `tags` and had no consumers. Freeform labels live in `tags`; grouped labels are classification_axis + node_classified_as_classification_value."
+    },
+    {
+      kind: "drop_props",
+      type: "bug",
+      drop_props: ["labels"],
+      reason: "0.32.0: BugProperties.labels duplicated base-node `tags` and had no consumers. Same resolution as task."
+    }
+  ],
   // ── v0.21.0: UPG-690 D.1 — collapse residual *_status shadows into status ────
   //
   // Six `*_status` enum properties that re-encode their entity's own lifecycle
@@ -9579,6 +9703,48 @@ function getSplitMigrations(fromVersion, toVersion) {
   return result;
 }
 var UPG_SCALAR_TO_EDGE_MIGRATIONS = {
+  "0.32.0": [
+    // C2 — assignment gets its own edge, superseding the 0.12.0 rules that
+    // routed task/bug `assignee` into node_owned_by_person.
+    //
+    // WHY THIS IS A REVERSAL AND NOT A GAP-FILL. 0.12.0 ruled that an assignee
+    // is an owner. Assignment has a time interval and an exclusivity that
+    // ownership does not, and a real board ran 85% unassigned while every item
+    // was owned — a state one edge cannot express.
+    //
+    // WHY EXISTING EDGES ARE NOT REWRITTEN. A node_owned_by_person edge on a
+    // task is indistinguishable by inspection from a genuine ownership edge, so
+    // a blanket rename would silently reclassify real facts. Measured population
+    // across every graph in the originating workspace was ~zero, which makes the
+    // cost of leaving them nil and the cost of guessing a wrong fact.
+    //
+    // user_story is included here and was MISSING from 0.12.0 entirely, though
+    // it has carried `assignee` since 0.20.0.
+    {
+      from_type: "task",
+      scalar_property: "assignee",
+      target_type: "person",
+      edge_type: "node_assigned_to_person",
+      drop_scalar: false,
+      reason: 'P14 actor: the assignee is a first-class person ("every task assigned to this person"). Assignment is not ownership: it has an interval and an exclusivity that ownership lacks, so it links node_assigned_to_person, superseding the 0.12.0 node_owned_by_person rule. Display string kept.'
+    },
+    {
+      from_type: "bug",
+      scalar_property: "assignee",
+      target_type: "person",
+      edge_type: "node_assigned_to_person",
+      drop_scalar: false,
+      reason: "P14 actor: same as task. Supersedes the 0.12.0 node_owned_by_person rule. Display string kept."
+    },
+    {
+      from_type: "user_story",
+      scalar_property: "assignee",
+      target_type: "person",
+      edge_type: "node_assigned_to_person",
+      drop_scalar: false,
+      reason: "P14 actor: user_story has carried `assignee` since 0.20.0 and had no promotion rule at all; an asymmetry with task and bug that this closes. Display string kept."
+    }
+  ],
   "0.12.0": [
     // ── Bucket A1 — orphan scalars (no edge existed): add edge + migrate + drop ──
     {
@@ -9989,22 +10155,12 @@ var UPG_SCALAR_TO_EDGE_MIGRATIONS = {
       drop_scalar: false,
       reason: "P14 actor: the release owner is a first-class person; link node_owned_by_person. Display string kept."
     },
-    {
-      from_type: "task",
-      scalar_property: "assignee",
-      target_type: "person",
-      edge_type: "node_owned_by_person",
-      drop_scalar: false,
-      reason: 'P14 actor: the assignee is a first-class person ("every task assigned to this person"); link node_owned_by_person. Display string kept.'
-    },
-    {
-      from_type: "bug",
-      scalar_property: "assignee",
-      target_type: "person",
-      edge_type: "node_owned_by_person",
-      drop_scalar: false,
-      reason: "P14 actor: the assignee is a first-class person; link node_owned_by_person. Display string kept."
-    },
+    // NOTE (0.32.0): the task/bug `assignee` rules that lived here are SUPERSEDED
+    // by the '0.32.0' block below, which routes them to node_assigned_to_person.
+    // They are removed rather than left to double-run: two rules over one scalar
+    // would mint the person once and link it twice, under two verbs that now mean
+    // different things. Graphs promoted before 0.32.0 keep the ownership edges
+    // they were given — see the 0.32.0 block for why those are not rewritten.
     {
       from_type: "roadmap",
       scalar_property: "owner",
@@ -10100,6 +10256,14 @@ function getScalarToEdgeMigrations(fromVersion, toVersion) {
   return result;
 }
 var UPG_EDGE_MIGRATIONS = {
+  "0.32.0": [
+    // C5 — the cadence scheduling edge widens from user_story to the work-item
+    // set. No requires_target_type: the destination's target_type is the `node`
+    // wildcard, and endpoint guards are checked against the catalog's declared
+    // type rather than the concrete instance (same reasoning as the 0.22.0
+    // workspace_produced_node rename below). Gate only on the unwidened source.
+    { kind: "rename", from: "planning_cycle_schedules_user_story", to: "planning_cycle_schedules_work_item", requires_source_type: "planning_cycle", reason: "0.32.0: a cycle could only schedule a user_story, while tracker imports produce `task` by default; the type a cadence most needed to hold was the one it could not reach. Widened to the polymorphic work-item endpoint; no flip, source unchanged. Measured live population of the old type at release: zero (no .upg in the repo or the dogfood graph carried it), so this rename is a vocabulary change, not a data migration." }
+  ],
   // (target version TBD at release ceremony — pencilled at 0.22.0, the next
   // breaking slot after 0.21.0 per the docket; adjust the key if Wave 4
   // claims it first.) WS3 commit-provenance collapse (2026-07-05, ratified):
@@ -11653,9 +11817,9 @@ var UPG_PROPERTY_SCHEMA = {
     priority: { type: "string", enum: ["urgent", "high", "medium", "low", "none"], description: "Urgency relative to other work. Independent of `bug_severity` (a critical bug can have low priority if rare)." },
     assignee: { type: "string", description: "Assigned person. Promote to a `node_owned_by_person` edge if ownership must be queryable." },
     due_date: { type: "string", description: "ISO date due. Often tied to a release gate or SLA." },
-    labels: { type: "string[]", description: "Free-form classification tags. Applied uniformly across work item types." },
+    labels: { type: "string[]", description: "Free-form classification tags. @deprecated since 0.32.0. Use base-node `tags` for ungrouped labels, and `classification_axis` + `classification_value` + `node_classified_as_classification_value` when the labels belong to a named group. This field duplicated `tags` and had no consumers; three parallel label surfaces (base `tags`, per-type `tags`, per-type `labels`) were two too many. `UPG_PROPERTY_MIGRATIONS['0.32.0']` drops it." },
     workflow_state: { type: "string", description: 'The source tool\'s raw custom workflow state, verbatim and opaque (e.g. "In Review", "QA", "Needs Triage"). Non-canonical and never reasoned over: it exists to round-trip an import losslessly. Map it onto a canonical bucket with `workflow_state_category`; canonical `status` stays the sole reasoning axis.' },
-    workflow_state_category: { type: "string", description: 'Canonical bucket the raw `workflow_state` maps onto for reasoning (a source "In Review" and "QA" might both map to a verification phase). Optional companion to `workflow_state`: it lets a graph reason over an imported custom workflow without promoting the raw label to `status`.' }
+    workflow_state_category: { type: "string", enum: ["triage", "backlog", "unstarted", "started", "completed", "cancelled"], description: 'Canonical bucket the raw `workflow_state` maps onto for reasoning: a source "In Review" and a source "QA" may both map to a verification phase. Optional companion to `workflow_state`; canonical `status` remains the sole reasoning axis.', notes: "It exists so a graph can reason over an imported custom workflow WITHOUT promoting the source's raw label to `status`. The raw label keeps its own field and stays verbatim; this one says what that label means in the six-bucket vocabulary every major tracker converges on. NARROWED FROM `string` AT 0.32.0. The field exists to carry exactly the vocabulary, and typing it as an open string meant nothing enforced the one thing it was for; an importer could write any word here and no consumer would know it had. A graph carrying a free string now fails to type-check rather than failing to be understood." }
   },
   // BuildArtifactProperties: Build artifact.
   build_artifact: {
@@ -11686,6 +11850,16 @@ var UPG_PROPERTY_SCHEMA = {
     allocated: { type: "number", description: "Capacity already allocated to work" },
     available: { type: "number", description: "Remaining unallocated capacity" }
   },
+  // CaptureProperties: Capture: a dated, hashed rendition of something already in the graph.
+  capture: {
+    capture_uri: { type: "string", description: "Where the bytes are. `https://` for hosted, `file://` or a relative path for local. Required: a capture with no location renders nothing." },
+    content_hash: { type: "string", description: "Content hash of the bytes. The regeneration signal; see the type's `@remarks` for why mtime and size are not." },
+    hash_algorithm: { type: "string", enum: ["sha256", "sha1", "md5"], description: "Hash algorithm. Absent means `sha256`." },
+    captured_at: { type: "string", description: "ISO timestamp the capture was taken." },
+    media_type: { type: "string", description: 'IANA media type of the bytes. @example "image/png"' },
+    fidelity: { type: "string", enum: ["exact", "approximate", "not_applicable"], description: "How faithfully this rendition represents its subject. `approximate` covers a capture taken in a stand-in state or at the wrong viewport." },
+    capture_status: { type: "string", enum: ["captured", "blocked", "skipped"], description: "Whether the capture succeeded.", notes: "A `blocked` capture is a real record rather than a missing one: it says the subject exists and could not be rendered, which is what stops the next run rediscovering the same obstacle. `skipped` is the deliberate exclusion." }
+  },
   // CeremonyProperties: Ceremony entity.
   ceremony: {
     ceremony_type: { type: "string", enum: ["standup", "planning", "review", "retro", "sync", "demo", "other"], description: "Kind of recurring meeting" },
@@ -11889,7 +12063,9 @@ var UPG_PROPERTY_SCHEMA = {
     members: { type: "object[]", description: "The frozen member arrangement, captured at publish. Layout and pointers only, never resolved content." },
     rev: { type: "number", description: "Monotonic revision, bumped on each republish of the same slug.", notes: "A published revision is a fact about the composition, user-visible as a new print from the same plate, so it is serialised. Worth distinguishing from a store's concurrency token, which shares the name in some backends but is a fact about the table rather than about the thing, and is not spec data." },
     published_at: { type: "string", description: "ISO timestamp of the most recent publish or republish." },
-    published_by: { type: "string", description: "Publisher handle or email. Display scalar, same posture as `WorkspaceProperties.owner`." }
+    published_by: { type: "string", description: "Publisher handle or email. Display scalar, same posture as `WorkspaceProperties.owner`." },
+    member_query: { type: "object", description: "When present, membership is DERIVED: members are produced by running this query rather than authored by placement.", notes: "This is the portable statement of what the composition shows. `CompositionMember.href` remains the publishing tool's own resolved route and stays opaque to everyone else; a member may carry both, and then the href is a fast path while the query is the meaning. A consumer that cannot parse the href can still render the layer, which is the whole reason the declaration is here rather than in a tool-namespaced bag key. A composition with no `member_query` is authored, which is what every composition written before 0.32.0 is." },
+    presentation: { type: "object", description: "Advisory rendering intent for the composition as a whole. A consumer may ignore it entirely and still be conformant." }
   },
   // ConfigurationAxisProperties: A named dimension along which the product's composition differs.
   configuration_axis: {
@@ -12346,7 +12522,7 @@ var UPG_PROPERTY_SCHEMA = {
     start_date: { type: "string", description: "ISO date work begins" },
     target_date: { type: "string", description: "ISO date work completes" },
     workflow_state: { type: "string", description: 'The source tool\'s raw custom workflow state, verbatim and opaque (e.g. "In Review", "QA", "Needs Triage"). Non-canonical and never reasoned over: it exists to round-trip an import losslessly. Map it onto a canonical bucket with `workflow_state_category`; canonical `status` stays the sole reasoning axis.' },
-    workflow_state_category: { type: "string", description: 'Canonical bucket the raw `workflow_state` maps onto for reasoning (a source "In Review" and "QA" might both map to a verification phase). Optional companion to `workflow_state`: it lets a graph reason over an imported custom workflow without promoting the raw label to `status`.' }
+    workflow_state_category: { type: "string", enum: ["triage", "backlog", "unstarted", "started", "completed", "cancelled"], description: 'Canonical bucket the raw `workflow_state` maps onto for reasoning: a source "In Review" and a source "QA" may both map to a verification phase. Optional companion to `workflow_state`; canonical `status` remains the sole reasoning axis.', notes: "It exists so a graph can reason over an imported custom workflow WITHOUT promoting the source's raw label to `status`. The raw label keeps its own field and stays verbatim; this one says what that label means in the six-bucket vocabulary every major tracker converges on. NARROWED FROM `string` AT 0.32.0. The field exists to carry exactly the vocabulary, and typing it as an open string meant nothing enforced the one thing it was for; an importer could write any word here and no consumer would know it had. A graph carrying a free string now fails to type-check rather than failing to be understood." }
   },
   // ErrorBudgetProperties: Error budget.
   error_budget: {
@@ -12530,7 +12706,7 @@ var UPG_PROPERTY_SCHEMA = {
     target_date: { type: "string", description: "ISO date work completes" },
     health: { type: "string", enum: ["on_track", "at_risk", "off_track"], description: "Delivery health" },
     workflow_state: { type: "string", description: 'The source tool\'s raw custom workflow state, verbatim and opaque (e.g. "In Review", "QA", "Needs Triage"). Non-canonical and never reasoned over: it exists to round-trip an import losslessly. Map it onto a canonical bucket with `workflow_state_category`; canonical `status` stays the sole reasoning axis.' },
-    workflow_state_category: { type: "string", description: 'Canonical bucket the raw `workflow_state` maps onto for reasoning (a source "In Review" and "QA" might both map to a verification phase). Optional companion to `workflow_state`: it lets a graph reason over an imported custom workflow without promoting the raw label to `status`.' }
+    workflow_state_category: { type: "string", enum: ["triage", "backlog", "unstarted", "started", "completed", "cancelled"], description: 'Canonical bucket the raw `workflow_state` maps onto for reasoning: a source "In Review" and a source "QA" may both map to a verification phase. Optional companion to `workflow_state`; canonical `status` remains the sole reasoning axis.', notes: "It exists so a graph can reason over an imported custom workflow WITHOUT promoting the source's raw label to `status`. The raw label keeps its own field and stays verbatim; this one says what that label means in the six-bucket vocabulary every major tracker converges on. NARROWED FROM `string` AT 0.32.0. The field exists to carry exactly the vocabulary, and typing it as an open string meant nothing enforced the one thing it was for; an importer could write any word here and no consumer would know it had. A graph carrying a free string now fails to type-check rather than failing to be understood." }
   },
   // FeatureAreaProperties: A structural grouping of related features within a product.
   feature_area: {
@@ -13526,7 +13702,8 @@ var UPG_PROPERTY_SCHEMA = {
     url: { type: "string", description: "Where the product lives. Marketing site, app store URL, etc.", modifier: "volatile" },
     logo_url: { type: "string", description: "Logo or icon URL. Used to render product cards and lists.", modifier: "volatile" },
     launched_at: { type: "string", description: "When the product became generally available (ISO 8601)" },
-    described_configuration: { type: "string", description: 'The product configuration this graph describes, named in plain language. A label for readers: nothing reads it to gate, filter, or alter how a tool interprets the graph. @example "Enterprise plan, split-navigation flag on"', notes: "A product's composition often differs by feature flag, plan tier, permission level or beta programme: surfaces appear, disappear, or are replaced by different surfaces with different occupants. A graph that models one of those without saying which is qualified by a condition nobody wrote down, and every fact in it inherits that silence. It makes no claim about which configuration most customers are on. Where a product genuinely ships several and the differences matter, declare a `configuration_axis` instead and let each fact say which values it holds under." }
+    described_configuration: { type: "string", description: 'The product configuration this graph describes, named in plain language. A label for readers: nothing reads it to gate, filter, or alter how a tool interprets the graph. @example "Enterprise plan, split-navigation flag on"', notes: "A product's composition often differs by feature flag, plan tier, permission level or beta programme: surfaces appear, disappear, or are replaced by different surfaces with different occupants. A graph that models one of those without saying which is qualified by a condition nobody wrote down, and every fact in it inherits that silence. It makes no claim about which configuration most customers are on. Where a product genuinely ships several and the differences matter, declare a `configuration_axis` instead and let each fact say which values it holds under." },
+    key_prefix: { type: "string", description: 'Prefix for keys minted onto this product\'s nodes (e.g. `"LTN"`, giving `LTN-1`, `LTN-2`, \u2026). A product with no prefix mints no keys. @example "LTN"', notes: 'Pairs with `UPGBaseNode.key`, which holds the minted value. The prefix sits on the product because the key\'s uniqueness scope is the product, across entity types; the namespace a tracker calls a "team". Only the prefix is serialised: the next number is `max(existing) + 1`, derived from the graph, because a counter is a fact about a store rather than about the product.' }
   },
   // ProductAreaProperties: ProductArea entity.
   product_area: {
@@ -14126,9 +14303,9 @@ var UPG_PROPERTY_SCHEMA = {
     effort: { type: "string", description: 'Effort estimate (e.g. "2h", "1d", "3 points"). Use a consistent unit within your team.' },
     priority: { type: "string", enum: ["urgent", "high", "medium", "low", "none"], description: "Relative importance against other tasks" },
     due_date: { type: "string", description: "ISO date due. Typically bounded by the containing story's due date." },
-    labels: { type: "string[]", description: "Free-form classification tags. Applied uniformly across work item types." },
+    labels: { type: "string[]", description: "Free-form classification tags. @deprecated since 0.32.0. Use base-node `tags` for ungrouped labels, and `classification_axis` + `classification_value` + `node_classified_as_classification_value` when the labels belong to a named group. This field duplicated `tags` and had no consumers; three parallel label surfaces (base `tags`, per-type `tags`, per-type `labels`) were two too many. `UPG_PROPERTY_MIGRATIONS['0.32.0']` drops it." },
     workflow_state: { type: "string", description: 'The source tool\'s raw custom workflow state, verbatim and opaque (e.g. "In Review", "QA", "Needs Triage"). Non-canonical and never reasoned over: it exists to round-trip an import losslessly. Map it onto a canonical bucket with `workflow_state_category`; canonical `status` stays the sole reasoning axis.' },
-    workflow_state_category: { type: "string", description: 'Canonical bucket the raw `workflow_state` maps onto for reasoning (a source "In Review" and "QA" might both map to a verification phase). Optional companion to `workflow_state`: it lets a graph reason over an imported custom workflow without promoting the raw label to `status`.' }
+    workflow_state_category: { type: "string", enum: ["triage", "backlog", "unstarted", "started", "completed", "cancelled"], description: 'Canonical bucket the raw `workflow_state` maps onto for reasoning: a source "In Review" and a source "QA" may both map to a verification phase. Optional companion to `workflow_state`; canonical `status` remains the sole reasoning axis.', notes: "It exists so a graph can reason over an imported custom workflow WITHOUT promoting the source's raw label to `status`. The raw label keeps its own field and stays verbatim; this one says what that label means in the six-bucket vocabulary every major tracker converges on. NARROWED FROM `string` AT 0.32.0. The field exists to carry exactly the vocabulary, and typing it as an open string meant nothing enforced the one thing it was for; an importer could write any word here and no consumer would know it had. A graph carrying a free string now fails to type-check rather than failing to be understood." }
   },
   // TeamProperties: Team entity.
   team: {
@@ -14350,7 +14527,7 @@ var UPG_PROPERTY_SCHEMA = {
     priority: { type: "string", enum: ["urgent", "high", "medium", "low", "none"], description: "Relative importance against other stories. Lifted onto user_story (0.20.0) so the story is a first-class plannable unit alongside task, matching Jira/Linear where the story/issue is the estimated-and-assigned atom." },
     due_date: { type: "string", description: "ISO date due. Typically bounded by the release or planning_cycle the story is scheduled into." },
     workflow_state: { type: "string", description: 'The source tool\'s raw custom workflow state, verbatim and opaque (e.g. "In Review", "QA", "Needs Triage"). Non-canonical and never reasoned over: it exists to round-trip an import losslessly. Map it onto a canonical bucket with `workflow_state_category`; canonical `status` stays the sole reasoning axis.' },
-    workflow_state_category: { type: "string", description: 'Canonical bucket the raw `workflow_state` maps onto for reasoning (a source "In Review" and "QA" might both map to a verification phase). Optional companion to `workflow_state`: it lets a graph reason over an imported custom workflow without promoting the raw label to `status`.' }
+    workflow_state_category: { type: "string", enum: ["triage", "backlog", "unstarted", "started", "completed", "cancelled"], description: 'Canonical bucket the raw `workflow_state` maps onto for reasoning: a source "In Review" and a source "QA" may both map to a verification phase. Optional companion to `workflow_state`; canonical `status` remains the sole reasoning axis.', notes: "It exists so a graph can reason over an imported custom workflow WITHOUT promoting the source's raw label to `status`. The raw label keeps its own field and stays verbatim; this one says what that label means in the six-bucket vocabulary every major tracker converges on. NARROWED FROM `string` AT 0.32.0. The field exists to carry exactly the vocabulary, and typing it as an open string meant nothing enforced the one thing it was for; an importer could write any word here and no consumer would know it had. A graph carrying a free string now fails to type-check rather than failing to be understood." }
   },
   // ValueObjectProperties: DDD value object.
   value_object: {
@@ -14465,8 +14642,8 @@ var UPG_PROPERTY_SCHEMA = {
     workspace_purpose: { type: "string", enum: ["discovery", "planning", "retrospective", "design", "research", "strategy", "general"], description: "What the workspace is for. Drives template suggestions and surfaces in workspace browsers.", notes: "`discovery` is persona, job and opportunity exploration. `planning` covers roadmap and decision sessions. `retrospective` is reflection on shipped work. `design` is experience or UI exploration. `research` organises study data and synthesis. `strategy` is high-level direction setting. `general` is the catch-all." },
     owner: { type: "string", description: "Workspace owner (handle or email). Display label; canonical owner is `team_owns_workspace` or `persona_owns_workspace`." },
     member_count: { type: "number", description: "Snapshot count. `team_works_in_workspace` edges are the source of truth.", modifier: "derived" },
-    archived: { type: "boolean", description: "Archived. Archived workspaces remain queryable but hidden from default views." },
-    archived_at: { type: "string", description: "ISO timestamp archived. Pairs with `archived === true`." },
+    archived: { type: "boolean", description: "Archived. Archived workspaces remain queryable but hidden from default views. @deprecated since 0.32.0. Use `UPGBaseNode.archived`, which generalises this pair to every entity type. Field data showed the archived/status split is not a workspace peculiarity: a tracker held 559 archived-completed items beside 18 live-completed ones, and one status field has nowhere to put the difference. `UPG_PROPERTY_MIGRATIONS['0.32.0']` lifts this value to the top level." },
+    archived_at: { type: "string", description: "ISO timestamp archived. Pairs with `archived === true`. @deprecated since 0.32.0. Use `UPGBaseNode.archived_at`. Lifted by `UPG_PROPERTY_MIGRATIONS['0.32.0']`." },
     icon: { type: "string", description: "Display icon (emoji or icon name)" },
     retention: { type: "string", enum: ["transient", "durable"], description: "Retention intent. Absent means `transient`.", notes: "A workspace is a free-form thinking space and is transient by default, so the spec makes both intents EXPRESSIBLE and takes no position on which reaches the file. Whether to write a transient canvas at all is a tool decision, and the recommended posture is not to: a scratch canvas nobody named has no business in a shared, git-tracked graph, where it lands in everyone's diff. Writing only `durable` workspaces is what keeps a canonical graph entity comfortable with a transient-by-default object." },
     canvas: { type: "object", description: "Opaque canvas furniture: the parts of a canvas with no graph referent. Preserved verbatim on round-trip and never interpreted. Tool extension keys are namespaced `<tool>:<key>` with a colon, and no consumer interprets a key it does not own.", notes: "The cut here is UPG principle P14 applied literally. Anything that is a REFERENCE TO A GRAPH NODE is an edge, which is why placed entities ride `workspace_arranges_node` and not this bag: a node id held as a scalar inside a blob is a foreign key in disguise, and a deleted node would leave a stale reference nothing can detect. Anything that is pure UI chrome with no graph referent stays here, because minting `annotation` and `frame` entity types would add catalog surface that is meaningless to every consumer outside the tool that drew it. WHY THE COLON, and why the rule is in the summary rather than buried here. An underscore key is indistinguishable from an ordinary property name, so a migration that targets namespaced keys cannot match it and no validator can detect one that should have been namespaced. That undetectability is why enforcement lives in the type and the documentation instead of in a check: a check would report clean on a bag full of underscore keys, which is worse than no check. Two conventions were already coexisting when this was ruled (`entopo_views` in a live writer, `entopo:view_blocks` in the contract test certifying preservation), which is how a cheap rule becomes a migration. PRESERVATION IS NOT PERMISSION TO RENDER. Preserving every byte says nothing about meaning: a field-measured canvas carried `excluded: true` tombstones, and a consumer that preserved them faithfully while rendering every entry showed the user images they had deleted." }
@@ -21870,6 +22047,7 @@ var ENTITY_EMOJI = {
   competitor_signal: "\u{1F4E1}",
   compliance_framework: "\u{1F3DF}\uFE0F",
   compliance_requirement: "\u26F2",
+  capture: "\u{1F4F8}",
   composition: "\u{1F5BC}\uFE0F",
   constraint: "\u{1F512}",
   contact: "\u{1F4C7}",
@@ -25249,9 +25427,9 @@ var PRODUCT_SPEC_GUIDE = {
     },
     {
       name: "Planning Cadence",
-      description: "The cadence axis. Create a planning_cycle (a sprint, iteration, quarter, or PI), nest finer cycles inside a coarse one, schedule the stories that flow through it, and scope the objectives the cycle serves. Scheduling and scoping are deliberate links, not containment: a story keeps its feature/epic parent.",
-      entity_types: ["planning_cycle", "user_story", "objective"],
-      edge_chain: ["planning_cycle_contains_planning_cycle", "planning_cycle_schedules_user_story", "objective_scoped_to_planning_cycle"]
+      description: "The cadence axis. Create a planning_cycle (a sprint, iteration, quarter, or PI), nest finer cycles inside a coarse one, schedule the work that flows through it (a task, story, epic, feature or bug), and scope the objectives the cycle serves. Scheduling and scoping are deliberate links, not containment: the scheduled item keeps its feature/epic parent.",
+      entity_types: ["planning_cycle", "task", "user_story", "objective"],
+      edge_chain: ["planning_cycle_contains_planning_cycle", "planning_cycle_schedules_work_item", "objective_scoped_to_planning_cycle"]
     }
   ],
   required_bridges: [
@@ -25948,7 +26126,7 @@ var PORTFOLIO_GUIDE = {
 var WORKSPACE_GUIDE = {
   domain_id: "workspace",
   anchor_entity: "workspace",
-  creation_sequence: ["workspace", "framework_exercise", "composition"],
+  creation_sequence: ["workspace", "framework_exercise", "composition", "capture"],
   patterns: [
     {
       name: "Canvas to published view",
@@ -28562,7 +28740,7 @@ var UPG_ANTI_PATTERNS = [
   {
     id: "planning-cycle-without-scheduled-work",
     name: "Planning cycle with no scheduled work",
-    description: "A planning_cycle exists but neither schedules any user_story nor contains a finer sub-cycle. An empty cadence box is a date range with nothing flowing through it: a sprint or iteration nobody planned work into, or a coarse period that was never broken down.",
+    description: "A planning_cycle exists but neither schedules any work item nor contains a finer sub-cycle. An empty cadence box is a date range with nothing flowing through it: a sprint or iteration nobody planned work into, or a coarse period that was never broken down.",
     structured_condition: {
       operator: "and",
       checks: [
@@ -28571,8 +28749,8 @@ var UPG_ANTI_PATTERNS = [
           check: {
             type: "relationship",
             source_type: "planning_cycle",
-            edge_type: "planning_cycle_schedules_user_story",
-            target_type: "user_story",
+            edge_type: "planning_cycle_schedules_work_item",
+            target_type: "node",
             comparison: "not_exists"
           }
         },
@@ -28588,10 +28766,16 @@ var UPG_ANTI_PATTERNS = [
       ]
     },
     why_it_matters: "A cadence layer only earns its keep when work is planned through it. An interval with no scheduled stories and no nested cycles adds ceremony without telling anyone what the period is for.",
-    remediation: "Schedule the stories the cycle will carry via `planning_cycle_schedules_user_story`, or break a coarse period into finer cycles via `planning_cycle_contains_planning_cycle`. If neither applies, the interval is not yet a real cadence box.",
+    remediation: "Schedule the work the cycle will carry via `planning_cycle_schedules_work_item`, or break a coarse period into finer cycles via `planning_cycle_contains_planning_cycle`. If neither applies, the interval is not yet a real cadence box.",
     stages: ["build", "beta", "launch", "growth", "mature"],
     severity: "low",
     since: "0.20.0"
+    // RETARGETED at 0.32.0 from planning_cycle_schedules_user_story. Left
+    // unchanged it would have become a false-positive generator the moment
+    // cycles could hold tasks: a cycle full of scheduled tasks and no stories
+    // would have reported as empty. Labeled fixtures cover the near-miss this
+    // is most likely to get wrong — a coarse `period` cycle that legitimately
+    // holds only sub-cycles and schedules nothing directly.
   },
   // ── Market intelligence layer ───────────────────────────────────────────
   {
@@ -30717,7 +30901,7 @@ var UPG_REGIONS = [
       "roadmap_item_references_feature",
       "feature_request_voted_on_by_feedback_vote",
       "planning_cycle_contains_planning_cycle",
-      "planning_cycle_schedules_user_story"
+      "planning_cycle_schedules_work_item"
     ],
     boundary_edges: [
       {
@@ -32645,9 +32829,12 @@ var NODE_KEY_ORDER = [
   "title",
   "slug",
   "aliases",
+  "key",
   "description",
   "tags",
   "status",
+  "archived",
+  "archived_at",
   "lifecycle_status",
   "source_id",
   "source_type",
@@ -32937,7 +33124,7 @@ function checkHeaderSealText(text) {
 }
 
 // src/index.ts
-var UPG_VERSION = "0.31.0";
+var UPG_VERSION = "0.32.0";
 var UPG_FORMAT_VERSION = "0.4.0";
 var MARKDOWN_FORMAT_VERSION = "0.1";
 var UPG_TYPES = getTypes();