Architecture · Alignment Notes

The Kinship Graph Workflow — Canon Gaps

The Kinship Graph Workflow is published as-is; its vocabulary predates current canon. These were the gaps to close. Closed, later the same day: the Kinship Graph Architecture v1.1 replaces the workflow and resolves every item below. This page stays as the record of the revision brief.

← The Kidunaverse — home Surfaces Orchestration Foundation Protocol Organizations Actions Roles Sentinel Legal Institutions Integrations
Publish honestly, align deliberately: the workflow stays untouched until its next revision; this list is the revision's brief.

The thirteen gaps

  1. "User" (~84 uses) — canon is member, never user.
  2. "Market" (~38 uses) — canon is Forum; "market" survives only as internal mechanics vocabulary.
  3. "Elector" — now Envoy (trades pass/fail tokens in Forums; votes and acts for members in alliances and organizations under their instruction).
  4. No Relationship node — canon makes the dyadic relationship a first-class node (exactly two members, information-bearing, per-Organization: the same two people relate differently in different Organizations).
  5. No Community — the first rung of the social ladder (3+ members; replaces "Guild") is missing entirely; the progression is Community → Alliance → Organization.
  6. No Project node — a major primitive within Organizations (a collection of resources, agents, and information with a purpose; Studio's organizing principle).
  7. No Ecosystem node — no server/ecosystem layer and no kap://eco.domain.net naming.
  8. "NFT" — canon: a registry and clear relationships; NFTs are not required.
  9. Agent taxonomy — generic "Agents" and "bots" instead of the five canonical types: Allies, Actors, Sentinels, Envoys, Operators. No Sentinel appears at all.
  10. "DUNA" as the public word — member-facing canon is Organization (other jurisdictions may pass similar laws under other names).
  11. "Levels" — must reconcile with the four access levels (public / private / secret / personal) and the no-holdings-recognition rule.
  12. No Field / Scene / Portal layer — acceptable for a graph document, but the node set should match what the Field must represent (the eight major nodes).
  13. Institution shape — canon: a special case of Alliance, KYB'd through the duna's registered agent; the workflow predates this.

Aligned and worth keeping

Apache AGE as the graph engine (matches the implementation decision) · wallets · Kinship Codes · lineage · the DUNA as the legal wrapper at the center — the doc's central insight, "three worlds, one graph," is exactly the architecture.

Recorded 2026-07-13 against the v5.5 canon delta.