# Kidunaverse cofounder skill — canon delta · 2026-07-13 (evening) · Kinship Graph Architecture v1.0

**Apply via Settings. Wins with the earlier 2026-07-13 delta until the fold lands.**

## The operating graph has a spec of record

**Kinship Graph Architecture v1.0** replaces the Kinship Graph Workflow (all thirteen canon gaps closed). Status: build specification for the **August 10, 2026 initial release**. Published under Architecture on the team site; PDF and figures in the kit.

## Decisions now canon (the fifteen, condensed)

1. Graph organized around **Members, Allies, Organizations, Actions**; Projects, Relationships, Communities, Alliances, Forums, Wisdom, Institutions, Records first-class supporting.
2. **Member everywhere** — visitor/guest/builder/founder/catalyst/luminary are states or Organization-scoped roles, never alternate nouns.
3. **Network identity ≠ legal Organization membership** — the schema records exact membership status; the product still says Member.
4. **Every Action resolves to exactly one organization_id.** Kinship Duna default only for an allowlisted class of network/guest Actions, recorded `context_defaulted=true`; defaulting never creates membership or authority.
5. **DUNA is a legal-form adapter, not the ontology.** `Organization` is the system object; WV DUNA is the first LegalForm/LegalRegistration adapter.
6. **Forum replaces Market.** Several Forums per Organization; the one-DUNA-one-Market `BECAME` edge is gone.
7. **Two agent families, typed kinds.** Exactly one Ally per Member; every non-Ally agent is an Actor. Sentinel, Envoy, Operator, registrar, intake, research are typed Actor kinds. (Reconciles the five-canonical-types vocabulary: five remain the member-facing words; structurally Ally + typed Actors.) Queue consumers are services, not social agents.
8. **Actions are a subgraph**: ActionDefinition · ActionRequest · AuthorizationDecision · Command · ActionRun · ExternalOperation · Record.
9. **One deterministic boundary: the Graph Command Service.** Models propose; the service resolves, authorizes, validates, commits, starts external operations, appends Records.
10. **Projects and work in the launch core** — engagements, work items, deliverables, milestones, agreements, split rules, invoices, credentials.
11. **Agent configuration named**: Inform/Wisdom · Instruct/Stance · Empower/Connection · Enable/Automation · Impart/Skill. A **Wisdom Drop** is a permissioned namespace of Items and vector chunks.
12. **The graph is not an accounting ledger.** Amounts/balances live in an immutable double-entry PostgreSQL ledger; rails stay authoritative for settlement; the graph links to it.
13. **The graph is authoritative current state** — typed graph state, command/record tables, ledger references, and a transactional outbox commit in ONE PostgreSQL transaction; no uncontrolled dual writes; protected decisions never read a stale projection.
14. **Launch as a modular monolith** (Postgres + Apache AGE + pgvector, one Graph Command Service, isolated workers); split only at measured boundaries.
15. **Full ontology now; risky economics by policy/feature gate.** Architecture readiness is not legal authorization.

## Data hygiene rule

Current graph state vs Records (evidence) vs telemetry are different things; only state and durable member-relevant Records enter the operating graph.

## Status

Recorded 2026-07-13 evening. The Workflow and its gap list remain published as history.