Model parent/child organization relationships — org_relations edges, organization.relate capability, welded-slug reconciliation

[mpstaton]

The canonical layer has no way to express that one organization is an initiative, fund, program, agency, or chapter of another. The first inbox-triage co-pilot run (2026-07-25) hit this repeatedly, and the DB-slug reconciliation pass (2026-07-27) reduced the residue to exactly the cases this models: four welded disk folders, the hosted-fund shape, the Koch/Stand Together constellation, the USDA/DOL agency chains, and the Harvard academic chain.

Work context (full inventory, per-case untangle steps, and the build definition):
https://github.com/lossless-group/augment-it/blob/rebuild/turbo-rsbuild/context-v/issues/Parent-Child-Nested-Organizations-Not-Modeled.md

The build, in brief:

• Typed org_relations RELATE edge in SurrealDB (initiative_of | fund_of | program_of | agency_of | chapter_of | funds | partners_with), queryable both directions
• organization.relate (+ list/remove) capabilities on the NATS wire
• Entity-card and corpus-lens surfaces for parent/children and roll-up
• Triage-skill integration (aboutness routing gains a parent-or-child step)
• Acceptance test: untangle the four welded folders, starting with upmobility-foundation ↔ urban-institute (three inbox captures are parked on that case)

🤖 Generated with Claude Code