feat(didi-chat), skill(triage-inbox): relations + tags verbs in the workbench slab; aboutness routing lands as step 5b

didi can now speak the family tree: the workbench slab teaches
organization.relations / organization.relate / organization.tag.add with a
propose-first discipline — relations are judgment calls, so didi invokes
only when the operator stated the relationship themselves, quoting their
phrasing into the edge's description. Both-orgs-must-exist and
peers-not-hierarchies (funds / partners_with) are spelled out.

Triage integration per the plan's Phase 3: the ACTIVE_SKILLS slab gains
step 5b (aboutness routing — parent content on the parent, initiative
content on the child, reference_of pointer across the seam; real-actor
initiatives with no row get minted + related + tagged instead of parked),
and the initiative_hub stream kind sheds its "while parent/child modeling
is unresolved" caveat. SKILL.md updated in the same commit per the
update-both-together rule: the parent-child open decision flips to MODEL
LANDED with the new routing recorded in place.

Verified: workspace tsc clean; service rebuilt and serving.

Refs #55.

Files changed:
- services/workspace/src/chat.ts
- context-v/agent-skills/triage-inbox-w-suggestions/SKILL.md
- changelog/2026-07-27_01_Organizations-Learn-Their-Family-Tree-Parent-Child-Peer-Relations-Plus-Org-Tags.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

@@ -163,3 +163,19 @@ the drive's click literally couldn't reach them. Now opacity-based with
 `:focus-within`, so Tab reveals them too. The drive proving the buttons
 *work* is exactly the rung that caught the button you couldn't Tab to;
 the human walk-through still judges whether the surface is *usable*.
+
+### didi learns the family tree, and triage learns to ask "parent or child?" (#55)
+
+`WORKBENCH_CHAT_VERBS` now carries `organization.relations / relate /
+tag.add` with the relations discipline: **propose by default** — a
+relation is a judgment call, so didi chat_invokes only when the operator
+stated the relationship themselves ("X is an initiative of Y"), quoting
+their phrasing into the edge's `description`. The triage slab gains
+**step 5b (aboutness routing)**: when a destination org has relations or
+the page names an initiative of a parent, ask which entity the content is
+*about* before filing — and an initiative that's a real actor with no row
+yet gets minted, related, and tagged `Initiative` instead of parked. The
+triage SKILL.md's parent-child open decision flips to **MODEL LANDED**,
+and the `initiative_hub` stream kind sheds its "while parent/child
+modeling is unresolved" caveat — it's now only for initiatives that don't
+merit their own org row.

context-v/agent-skills/triage-inbox-w-suggestions/SKILL.md

@@ -389,12 +389,24 @@ attention goes to the hard tail.
       Human Potential Network) — sibling folder
       (`corpus/organizations/<slug>/`?) or something else? Still open;
       captures accumulate pending in the inbox.
-- [ ] **Parent-child organizations** (raised in batch 1, 2026-07-25):
-      urban-institute is the parent org; upmobility-foundation is an
-      initiative of it. Operator ruling: do NOT file content into either
-      until the relationship is modeled. Full write-up + candidate shape:
+- [x] **Parent-child organizations** — MODEL LANDED (2026-07-27): org↔org
+      relations are live (`organization.relate` / `.relations` /
+      `.unrelate` / `.relation.update` — parent/child/peer + kind +
+      free-text description, edges in the `affiliations` table) along with
+      org tags (`organization.tag.add` / `.remove` — Initiative, Program,
+      Fund…). Per
+      [[../../plans/Org-Relations-Parent-Child-Peer-Plus-Org-Tags|the plan]];
+      history in
       [[../../issues/Parent-Child-Nested-Organizations-Not-Modeled|Parent-Child-Nested-Organizations-Not-Modeled]].
-      Affected captures stay pending in the inbox.
+      **Aboutness routing (step 5b):** when a destination org has relations
+      or the page names an initiative/fund/program of a parent, ask which
+      entity the content is *about* before filing — parent content on the
+      parent, initiative content on the child, `reference_of:` pointer
+      across the seam when both want it. An initiative that is a real actor
+      but has no row yet → mint the child, relate it (`rel: parent`,
+      `kind: initiative_of`), tag it `Initiative`, and file there.
+      The parked upmobility/urban-institute captures are the pilot filing
+      (issue's worklist section A).
 - [x] **Person-destined content** (ruled 2026-07-27): individual funders
       keep normal `funders/<slug>/` folders (the funders corpus is the
       funder-to-strategy mapping substrate); DB identity is a **persons**
@@ -414,7 +426,9 @@ A condensed operational form of this skill ships in didi's chat as the
 **ACTIVE_SKILLS slab** in `services/workspace/src/chat.ts` (the Slab-3 spot
 reserved since v0.0.1), teaching the triage verbs
 (`organization.corpus.add`, `resolver.search`, `resolver.apply`,
-`resolver.update_org`, `organization.streams.add`) and the decision
+`resolver.update_org`, `organization.streams.add` — and, since 2026-07-27,
+the relations/tags verbs `organization.relations`, `organization.relate`,
+`organization.tag.add` with the step-5b aboutness routing) and the decision
 sequence above. Honest limit: chat-didi can register, resolve, mint, and
 stream — the *disk* half of a filing (canonical merge, pointer files,
 binary moves) still runs session-side via the scripts above, until a

services/workspace/src/chat.ts

@@ -129,6 +129,22 @@ VERB RECOGNITION SHORTCUTS:
 - "/crawl-team <org-slug>" → chat_invoke organization.crawl with target "team".
 - A bare "/crawl-links" / "/crawl-streams" / "/crawl-team" (no argument), or "this org" / "this organization", targets the focused organization from context when one is present — chat_invoke directly with its org_slug. No focused org and no argument → ask.
 - Natural phrasings ("crawl for relevant pulse streams for X", "find X's team members") map to the same targets — chat_invoke when the org is unambiguous, chat_propose otherwise.
+
+ORG RELATIONS + TAGS (per context-v/plans/Org-Relations-Parent-Child-Peer-Plus-Org-Tags.md):
+
+organization.relations — Read one org's family tree: parents / children / peers, each with kind + description.
+  args: { org_slug: string, client: string }
+
+organization.relate — Connect two EXISTING orgs. rel is relative to org_slug: "parent" = other_slug is the parent. kind is an open vocabulary (initiative_of, fund_of, program_of, agency_of, chapter_of, funds, partners_with); description carries the human context worth keeping.
+  args: { org_slug: string, other_slug: string, rel: "parent" | "child" | "peer", kind?: string, description?: string, client: string }
+
+organization.tag.add — Tag an org for what it IS (Initiative, Program, Fund, Funder, Think-Tank…). Train-Case by convention.
+  args: { org_slug: string, tag: string, client: string }
+
+RELATIONS DISCIPLINE:
+- Relations are judgment calls — chat_propose by default; chat_invoke only when the operator stated the relationship themselves ("X is an initiative of Y" → relate X→parent Y, kind initiative_of, and quote their phrasing into description).
+- Both orgs must already exist — if one is missing, propose creating it first (resolver.search before ever proposing a mint).
+- Not every pairing is a hierarchy: funders/grantees and partners are rel "peer" with kind "funds" / "partners_with".
 `;
 
 // Slab 3 — active skills. First resident (2026-07-25): the condensed
@@ -154,7 +170,7 @@ resolver.apply — Mint a new organization row (action "create"). Long-form full
 resolver.update_org — Enrich names right after ANY one-string create: complete_name (full formal name), conventional_name (what humans call it), aliases[] (greedy: acronyms, smushed forms, former names). Also renames slugs (old slug auto-preserved as alias).
   args: { org_slug: string, new_slug?: string, complete_name?: string, conventional_name?: string, aliases?: string[], client: string }
 
-organization.streams.add — Register a rolling page as a pulse stream on an org. Kinds: "topic_stream" (topic/issues hub), "blog_index" (blog/news index), "initiative_hub" (a named initiative's hub page — also the lightweight answer for initiative-shaped pages while parent/child org modeling is unresolved).
+organization.streams.add — Register a rolling page as a pulse stream on an org. Kinds: "topic_stream" (topic/issues hub), "blog_index" (blog/news index), "initiative_hub" (a named initiative's hub page — still right when the initiative does NOT merit its own org row; when it does, mint the child and relate it instead).
   args: { org_slug: string, url: string, kind: string, name: string, client: string }
 
 TRIAGE DECISION SEQUENCE (per item):
@@ -163,6 +179,7 @@ TRIAGE DECISION SEQUENCE (per item):
 3. Rolling index page (topic hub / blog index / initiative hub) on a tracked org? → organization.streams.add, not corpus content. A one-time capture of a page that keeps pulsing is worthless.
 4. Fetch-blocked capture (403/CAPTCHA/paywall)? → gated, not discarded: the URL is still wanted. Discard is only for genuinely worthless content (404 bodies, nav-only pages, consent boilerplate).
 5. Destination: org-attributable content → the org (search first, mint via resolver.apply if truly absent, enrich names immediately); topical content → an existing domain via source.add (resolve the slug against "Existing corpora" — never fabricate); tool homepages / content marketing → the tools topic; a profile page on an identity-link site (Candid, Cause IQ, Charity Navigator, GrantForward…) → the org it profiles.
+5b. Parent or child? When the destination org has relations (organization.relations) or the page names an initiative/fund/program of a parent, ask which entity the content is ABOUT before filing: parent-org content files on the parent, initiative content on the child. Both plausibly claim it → file by aboutness and tell the operator a reference_of pointer belongs across the seam (disk side, triage session). Initiative with no org row yet → propose minting the child + organization.relate (rel "parent", kind initiative_of) instead of filing onto the parent's streams when the initiative is a real actor.
 6. Org role buckets on disk (funders / gov-entities / think-tanks / associations-networks / academic-institutions / data-services) and the disk half of a filing (canonical file moves, reference_of pointer files, binary siblings) are handled by operator-side sessions, not chat — register the DB side here and tell the operator the file placement runs in the triage session.
 
 TRIAGE DISCIPLINE: