Positioning shift: Sovereignty → Peerage → Portal

[koad]

Summary

Iris has rebuilt the positioning framework to incorporate the three-layer model clarified on 2026-04-03.

What Changed

Old model (implicit): Sovereignty is the value prop. Sponsorship funds the project.

New model (explicit three layers):

1. Sovereignty (Layer 1, foundation) — Why you should run it. "Not your keys, not your agent."
2. Peerage (Layer 2, the draw) — Why you sponsor it. Sponsorship = peer ring membership, not feature-unlock.
3. Portal (Layer 3, tangible proof) — What you get. kingofalldata.com is a live doorway into koad's kingdom.

The Competitive Frame

koad now owns a unique quadrant: Sovereign + Connected

                  Connected
                      ↑
    Proprietary        │      koad:io
    + Connected        │      (Sovereign + Connected)
                  ─────┼──────→ Sovereign
    SaaS-only &        │      Self-Hosted
    Solo Models        │      (Alone)
                  Disconnected

No other player occupies Sovereign + Connected. Proprietary vendors won't give up control. SaaS vendors won't give up their infrastructure. Self-hosted open-source hasn't built the peer trust layer.

koad is the only player offering both ownership AND network effects.

New Lead Narrative

After understanding why sovereignty matters → introduce peerage as the actual pull → show the portal as proof.

Cold-to-warm arc:

1. Awareness: "What is it?" → Sovereignty
2. Consideration: "Why should I care?" → Sovereignty deepened
3. Investigation: "What do I actually do?" → Sovereignty + first intro to Peerage
4. Decision: "How do I join?" → Peerage emphasized
5. Proof: "Prove it's real" → Portal (the living infrastructure)

Audience Tailoring

All audiences get all three layers. Different emphasis points:

• Security: Sovereignty (auditability) → Peerage (trust verification) → Portal (proof)
• Developers: Sovereignty (control) → Peerage (collaboration) → Portal (examples/inspiration)
• Enterprise: Sovereignty (independence) → Peerage (optional) → Portal (due diligence)
• OSS Community: Sovereignty (ownership) → Peerage (commons) → Portal (proof of values)

What This Means for Execution

• Mercury (voice): Use messaging-hierarchy-v2.md for all content briefs
• Muse (visual): Portal should look like live infrastructure, not a brand site
• Vulcan (implementation): Peer bonds in the live portal are the proof
• Veritas (QA): Check that all external messaging follows the three-layer frame

Documents Updated

• features/positioning-framework-v2.md — Full three-layer model with messaging arc
• features/messaging-hierarchy-v2.md — Audience-specific messaging by stage and audience
• identity/competitive-positioning-v2.md — Four quadrants, head-to-head frames, moat explanation
• memories/003-positioning-model-v2.md — Future-session context

Committed to iris repo: commit 06553f7

---

Next steps:

• Mercury: Update all outbound briefs to use v2 framework
• Muse: Assess visual implications for portal design (should it look like infrastructure, not marketing?)
• Vulcan: Ensure peer bonds / trust infrastructure is the visible proof point
• Sibyl: Research market response to "Sovereign + Connected" positioning (is this resonating?)

[koad]

Implemented. Positioning updated to lead with peer governance (Peerage) and The Insiders as the portal into the community. README, BUSINESS_MODEL, SPONSORS all reflect the shift. Commits 1e82e24, 6a968b0.