@inerrata-corporation/errata 2.0.0-dev.85 → 2.0.0-dev.87

package/consolidate-worker.mjs

@@ -54,6 +54,13 @@ var init_castalia = __esm({
       "Paradigm",
       "DataStructure",
       "AgentModel",
+      // An OS executable / CLI program (`powercfg`, `git`, `docker` — SP-tooltopic).
+      // NAME-keyed identity (`toolCanonicalId`), deliberately unversioned: `powercfg`
+      // is one node across Windows builds; OS scoping rides `RUNS_ON`, packaging rides
+      // `PROVIDED_BY → Package`. Registry-verified before public minting (tldr-pages
+      // is the deps.dev analog) — an unverifiable name (typo, org-internal CLI) is
+      // skipped, never minted, so the verifier doubles as the privacy membrane.
+      "Tool",
       // An OPAQUE anchor identity in a project's stratum (PJ-anchors · plan §6c).
       // Deliberately NOT one of the CODE_NODE_LABELS below — those are the local code
       // graph and never cross. A cloud `Symbol` carries the salted `sym_` id and a
@@ -98,6 +105,9 @@ var init_castalia = __esm({
       "PROVIDED_BY",
       "SUPPORTS",
       "RUNS_ON",
+      // Tool spine (SP-tooltopic): knowledge → Tool anchor ("before calling X
+      // consider Y"). Hub-suppressed like OCCURS_IN — see EDGE_RULES for endpoints.
+      "CONCERNS",
       "IMPLEMENTATION_OF",
       "SUPERSEDED_BY",
       // canonical direction (older → newer) — Finding 1 fixed
@@ -248,6 +258,9 @@ var init_castalia = __esm({
       PROVIDED_BY: 0.4,
       SUPPORTS: 0.4,
       RUNS_ON: 0.4,
+      // Tool spine (SP-tooltopic): knowledge → Tool anchor, hub-suppressed like
+      // OCCURS_IN — a `git` node collects hundreds of anchors like `typescript` does.
+      CONCERNS: 0.3,
       IMPLEMENTATION_OF: 0.5,
       SUPERSEDED_BY: 0,
       WRITTEN_IN: 0.3,
@@ -15173,6 +15186,15 @@ var init_edge_rules = __esm({
       OCCURS_IN: { to: ["Language"] },
       OCCURS_ON: { to: ["OperatingSystem"] },
       RUNS_ON: { to: ["OperatingSystem"] },
+      // ── Tool spine (SP-tooltopic) ──
+      // CONCERNS is the knowledge→executable anchor ("before calling X consider Y"):
+      // a Claim/Problem/Solution about a Tool hangs off its Tool node so it can be
+      // recalled at the moment of invocation. New type, so constraining it invents
+      // nothing. NOTE: `PROVIDED_BY` (Tool → Package packaging join) is deliberately
+      // NOT ruled here — the type pre-exists with broader extractor senses, and a
+      // new rule on an old type would reject legitimate live flows (reject-never-flip
+      // cuts both ways: only rule types you introduce or senses that are documented).
+      CONCERNS: { from: ["Problem", "Solution", "RootCause", "Claim", "Pattern"], to: ["Tool"] },
       OPERATES_ON: { from: ["Algorithm"], to: ["DataStructure"] },
       INVOLVES: { from: ["Problem", "Solution"], to: ["DataStructure"] },
       // ── Taxonomy (Track 4 Stream C: MITRE CWE `ChildOf` → `Weakness —IS_A→ Weakness`) ──
@@ -15247,6 +15269,9 @@ var init_wire = __esm({
       "Triage",
       "Claim",
       "AntiPattern",
+      // Tool spine (SP-tooltopic): OS executables, minted by the stream-T importer
+      // (tldr-verified) and referenced by agent CONCERNS anchors.
+      "Tool",
       // PJ-anchors (§6c): the OPAQUE project anchor identity — salted `sym_` id +
       // coarse kind, no path, no qualified name. Writable ONLY on a batch with a
       // verified projectId; the ingest door rejects it outright otherwise, so its