ship(feature, org-relations): organizations know their family tree — relate, tag, walk, and file by aboutness

The full arc is live: parent/child/peer relations with typed kinds and
free-text context, the first org tag mechanism, the Org Workbench surface
to work both, didi + triage integration, and the pilot untangle that
proved the whole thing on the case that demanded it — which turned out to
be two distinct entities all along (UpMobility Foundation peer/
partners_with Urban Institute, not initiative-of).

First complete run of context-v/loops/Implement-Feature-Loop.md:
init 570d0b6 → tickets #49-#57 all closed (cedf12b, 62ab198, 2e10cdd,
afbfa21, d4371d5, f66116e, 73a508e; pilot disk half in reach-edu
30e0453) → agent drives green → operator walk-through passed, spawning
one fix-ticket (#57, corpus-kind datalist) and the superseding peer
ruling → this closing bracket.

This commit: changelog polished for the reader (pilot beat, What's next,
full files_changed), plan → Shipped with post_ship_note, issue worklist
A-1 + section C checked with the ruling recorded. The
surrealdb-canonical-layer skill snapshot updated in its own repo
(lossless-agent-skills ed8ebd7).

Remaining welds (Truist↔LiftFund, Beacon, Koch edges, USDA, Harvard
chain) untangle lazily at filing pressure, tracked in the issue file.

Files changed:
- changelog/2026-07-27_01_Organizations-Learn-Their-Family-Tree-Parent-Child-Peer-Relations-Plus-Org-Tags.md
- context-v/plans/Org-Relations-Parent-Child-Peer-Plus-Org-Tags.md
- context-v/issues/Parent-Child-Nested-Organizations-Not-Modeled.md

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01RW28dw3kQAKXr2ZNefCukE

Author: mpstaton

changelog/2026-07-27_01_Organizations-Learn-Their-Family-Tree-Parent-Child-Peer-Relations-Plus-Org-Tags.md

@@ -11,14 +11,30 @@ augmented_with:
 files_changed:
   - context-v/plans/Org-Relations-Parent-Child-Peer-Plus-Org-Tags.md
   - context-v/loops/Implement-Feature-Loop.md
+  - context-v/issues/Parent-Child-Nested-Organizations-Not-Modeled.md
+  - context-v/agent-skills/triage-inbox-w-suggestions/SKILL.md
+  - services/record-surrealdb-resolver/src/org-relations.ts
+  - services/record-surrealdb-resolver/src/resolver.ts
+  - services/record-surrealdb-resolver/src/handlers.ts
+  - services/record-surrealdb-resolver/src/domains.ts
+  - services/record-surrealdb-resolver/src/server.ts
+  - services/workspace/src/capabilities.ts
+  - services/workspace/src/chat.ts
+  - apps/org-workbench/src/RelatedOrgs.svelte
+  - apps/org-workbench/src/OrgCard.svelte
+  - apps/org-workbench/src/App.svelte
+  - apps/org-workbench/src/AdditiveList.svelte
+  - apps/org-workbench/src/lib/types.ts
+  - apps/org-workbench/src/lib/org-client.ts
+  - scripts/prove-org-relations.mjs
 ---
 
 # Organizations Learn Their Family Tree
 
-> **Stub note:** this entry is being written *as the work lands*, per the
-> [[../context-v/loops/Implement-Feature-Loop|Implement-Feature-Loop]] (its
-> first run). `## What landed` accumulates a beat per closed ticket; the
-> polish pass happens at ship. Tickets: augment-it #49–#56.
+> Written beat-by-beat *as the work landed* — the first run of the
+> [[../context-v/loops/Implement-Feature-Loop|Implement-Feature-Loop]]
+> (tickets #49–#57, `init(feature, org-relations)` →
+> `ship(feature, org-relations)` in one day, human gate included).
 
 ## Why Care?
 
@@ -191,3 +207,33 @@ across the client's orgs — 19 in reach-edu on first fire (`annual_report`,
 Autocomplete, never enforcement: a non-match creates exactly what the
 operator typed, the same open-vocabulary philosophy as relation kinds.
 Refreshed per card load, so a kind minted on one org suggests on the next.
+
+### The pilot untangle — and the conflation confesses (#56)
+
+The acceptance test was the case that started it all:
+`funders/upmobility-foundation-urban-institute/`. Walking it through the
+live workbench produced the run's best finding: **the weld was never a
+parent and its initiative — it was two distinct entities.** UpMobility
+Foundation (upmobility.org, a nonprofit donor) and Urban Institute's
+*Upward Mobility* initiative (upward-mobility.urban.org) had been fused by
+a host-family match. The operator ruled them **peers** (`partners_with`
+edge), minted `urban-institute` (+`Think-Tank` tag) through the UI, and
+the 17-file sweep split the folder by aboutness: seven UpMobility captures
+into the renamed `funders/upmobility-foundation/`, six Urban files into
+`think-tanks/urban-institute/` (including the three captures parked since
+triage batch 1, now registered as `content_items`), two fetch-blocked
+profiles gated, two mis-packed third parties re-inboxed — and **zero
+`reference_of:` pointers**, because the DB edge itself is the connection.
+reach-edu commit `30e0453`.
+
+The issue's remaining welds (Truist↔LiftFund, Beacon, the Koch
+constellation edges, USDA↔Rural Development, the Harvard chain) untangle
+lazily at filing pressure, now with the tools this ship built.
+
+## What's next
+
+- The rest of the reconciliation worklist, case by case, in triage sessions.
+- Corpus roll-up lenses (child content surfacing on the parent) — deferred
+  until the edges earn it.
+- Multi-hop chains (Project on Workforce ⊂ HKS ⊂ Harvard) render one hop
+  today; walking is click-through.

context-v/issues/Parent-Child-Nested-Organizations-Not-Modeled.md

@@ -7,8 +7,9 @@ authors:
   - Michael Staton
 augmented_with:
   - Claude Code on Claude Fable 5
-semantic_version: 0.0.0.2
+semantic_version: 0.0.1.0
 revisions:
+  - 2026-07-27 — **Model shipped + pilot untangled (0.0.1.0).** Section C fully checked (edges in `affiliations`, six capabilities, workbench surface, triage step 5b); pilot case A-1 done with a superseding ruling — UpMobility Foundation and Urban Institute's Upward Mobility initiative are DISTINCT entities, related peer/`partners_with`, not initiative-of. All three parked captures filed. Remaining: worklist A-2..4 and B, untangled lazily at filing pressure per the standing ruling.
   - 2026-07-25 — Initial draft, written mid-triage-run when the Urban Institute event page (batch 1 item 18) was parked rather than filed into the conflated funder folder.
   - 2026-07-27 — **Reconciliation worklist added (0.0.0.2).** After the DB-slug-is-source-of-truth pass renamed every cleanly-renamable folder, the welded slugs are the last disk↔DB divergence — operator directed: build this in and track it. Full per-case inventory with current state and untangle steps; gh issue opened for the work trail.
 tags:
@@ -100,14 +101,19 @@ pointers across the seam, (4) re-home any parked inbox captures.
 
 ### A. Welded disk folders (4)
 
-- [ ] **`funders/upmobility-foundation-urban-institute/`** — Upward Mobility
-      Foundation (initiative) welded to Urban Institute (parent). Clean
-      `upmobility-foundation` row EXISTS (operator-created); `urban-institute`
-      row does not. Three inbox captures parked on this case (event page,
-      homepage, 2025 impact report). Untangle: mint `urban-institute`
-      (think-tank), edge `upmobility-foundation —initiative_of→
-      urban-institute`, split folder content by aboutness, file the three
-      parked captures. **The pilot case — do this one first.**
+- [x] **`funders/upmobility-foundation-urban-institute/`** — UNTANGLED
+      2026-07-27 (the pilot case, run through the live Org Workbench +
+      operator-confirmed sweep). **Ruling supersedes the original framing:**
+      the weld conflated two DISTINCT entities — UpMobility Foundation
+      (upmobility.org, a nonprofit donor) and Urban Institute's Upward
+      Mobility *initiative* (upward-mobility.urban.org). The operator ruled
+      the relation **peer / `partners_with`**, not initiative_of — the
+      initiative is Urban's, not the foundation's. `urban-institute` minted
+      via the workbench (+`Think-Tank` tag); edge live in `affiliations`;
+      folder split by aboutness (7 files → `funders/upmobility-foundation/`,
+      6 → `think-tanks/urban-institute/` incl. the three parked captures,
+      2 gated, 2 re-inboxed) with NO `reference_of:` pointers — the DB edge
+      carries the connection. reach-edu commit `30e0453`.
 - [ ] **`funders/truist-foundation-liftfund-us/`** — Truist Foundation welded
       to LiftFund (a CDFI grantee/partner, not a sub-org — the edge here is
       `funds`/`partners_with`, not `initiative_of`). Clean `truist-foundation`
@@ -142,23 +148,27 @@ pointers across the seam, (4) re-home any parked inbox captures.
 
 ### C. The build (what "model lands" means)
 
-- [ ] Ratify the edge shape: a typed `org_relations` RELATE edge
-      (`kind: initiative_of | fund_of | program_of | agency_of | chapter_of |
-      funds | partners_with`), queryable both directions.
-- [ ] Capabilities: `organization.relate` (+ list/remove) on the wire, so
-      edges never need direct writes.
-- [ ] Surface: entity card shows parent/children; corpus lenses can roll a
-      child's content up to the parent.
-- [ ] Triage integration: the skill's aboutness routing gains a "parent or
-      child?" step once edges exist; the four welded folders above get
-      untangled as the acceptance test.
+- [x] ~~Ratify the edge shape~~ — SHIPPED 2026-07-27, with one deliberate
+      deviation from the candidate shape: org→org edges live in the
+      existing **`affiliations`** table (`edge_type: 'org_org'`,
+      `rel: 'child_of' | 'peer'`, open-vocabulary `kind`, free-text
+      `description`, `client_access`), not a new `org_relations` table.
+      Per [[../plans/Org-Relations-Parent-Child-Peer-Plus-Org-Tags]].
+- [x] ~~Capabilities~~ — `organization.relate / relations / unrelate /
+      relation.update` + `organization.tag.add / tag.remove` live; proof
+      script `scripts/prove-org-relations.mjs` 22/22 green.
+- [x] ~~Surface~~ — Org Workbench card shows Part of / Contains / Peers
+      with click-through navigation + a Tags row. (Corpus roll-up lenses
+      deliberately deferred — named out-of-scope in the plan.)
+- [x] ~~Triage integration~~ — aboutness routing landed as step 5b in the
+      triage skill + didi's slabs; pilot untangle done (worklist A-1 above).
 
 ## Parked pending this issue
 
-- `inbox/2026-06-10_apprenticeship-industry-driven-made-to-scale.md` (Urban
-  Institute event; batch 1 #18)
-- `inbox/2026-06-10_driving-impact-by-equipping-changemakers-with-evidence-and-s.md`
-  (Urban Institute homepage; batch 2)
+~~All three parked captures filed 2026-07-27~~ (event page, homepage, AND
+the 2025 impact report) → `think-tanks/urban-institute/`, registered via
+`organization.corpus.add`, reach-edu commit `30e0453`. Nothing remains
+parked on this issue.
 
 ## See also
 

context-v/plans/Org-Relations-Parent-Child-Peer-Plus-Org-Tags.md

@@ -7,9 +7,12 @@ authors:
   - Michael Staton
 augmented_with:
   - Claude Code on Claude Fable 5
-semantic_version: 0.0.0.2
+semantic_version: 0.0.1.0
+date_first_published: 2026-07-27
 issue_reference: "[[../issues/Parent-Child-Nested-Organizations-Not-Modeled]]"
+post_ship_note: "Executed same day as authored, first run of [[../loops/Implement-Feature-Loop]] (tickets #49–#57, init 570d0b6 → ship). Proof script caught two real relation.update bugs; the browser drive caught a keyboard-unreachable affordance; the human gate added #57 (corpus-kind datalist) and a superseding pilot ruling — UpMobility Foundation and Urban Institute are DISTINCT entities, peer/partners_with, so the pilot needed no reference_of pointers at all."
 revisions:
+  - "2026-07-27 — v0.0.1.0 — Shipped. All four phases landed; pilot untangled with the peer ruling; #56 worklist tracked in the issue file."
   - "2026-07-27 — v0.0.0.2 — status → Implementing at loop start ([[../loops/Implement-Feature-Loop]] first run). Superseded by reality: `tag.suggest` / `tag.apply` verbs already exist (capabilities.ts:240-241, domains.ts) — §1.4's 'add a thin tags.vocab' is unnecessary; the UI datalist rides `tag.suggest`, and the org tag handlers reuse `ensureTagInVocab` + `toDashed` from domains.ts. (`tag.apply` itself is source_usages-scoped, not reusable for orgs.)"
 tags:
   - Plan
@@ -18,7 +21,7 @@ tags:
   - Canonical-Layer
   - Org-Workbench
   - Data-Modeling
-status: Implementing
+status: Shipped
 ---
 
 # Org Relations (parent/child/peer) + Org Tags