RFC: Archetype Convergence — Unifying Vendor, User, and Agent Identity Systems
Status: Draft — needs team discussion before implementation.
Related: mibera-interface#66 — Interface Wiring, mibera-interface#62 — SMF Migration, loa-finn#27 — finnNFT Per-NFT AI Agents, loa-freeside
Problem
Three separate identity/archetype systems exist across the Mibera ecosystem with no documented relationship between them. As we evolve toward dNFT agent companions (loa-finn#27), these systems need to converge — or we need to explicitly document why they remain separate.
The Three Systems
1. User Quiz Archetypes (10 archetypes)
Minted on-chain as NFTs (miChainMirror / MIRA at TAROT_ADDRESS).
| Archetype |
Identity |
Axis Position |
| Centurion |
Guardian of community |
Order + Visible |
| Oracle |
Sees beyond present |
Order + Hidden |
| Witness |
Observes without judgment |
Neutral + Hidden |
| Prodigal Son |
Speaks harsh truths |
Chaos + Visible |
| Doppel |
Shape-shifter, adapts |
Chaos + Hidden |
| Ouroboros |
Recognizes patterns/cycles |
Order + Hidden |
| Anointer |
Finds meaning, elevates |
Order + Visible |
| Serpent |
Brings hidden knowledge |
Chaos + Hidden |
| Bound One |
Remains steadfast |
Order + Visible |
| Phoenix |
Transforms challenges |
Chaos + Visible |
Dual-axis model: Chaos (-100) ↔ Order (100), Hidden (-100) ↔ Visible (100)
Product integration: Drives the forum theme system — the entire forum UI changes color based on the user's quiz archetype. 10 distinct color palettes in constants/theme.ts, each with 8 color values (primary, secondary, tertiary, accent, link, highlight, background, background2). This means every user sees a different-colored forum.
On-chain action types: crazy, cradled, capitulate, Collectooor, Comeback, Cashed out
Esoteric role hierarchy: Seeker → Neophyte → Acolyte → Adept → Alchemist → Sigil Mage → Keeper of Keys → Chain Archivist → The Contract
2. Vendor AI Archetypes (7 archetypes)
Used in HoneyGPT's two-phase personality system. NOT on-chain — stored in Supabase sellers.archetype field.
| Archetype |
Identity |
Keyword Triggers |
| shadow_merchant |
Classic underground trader with mystical awareness |
merchant, trader, dealer, seller, vendor |
| techno_artisan |
Creator/craftsperson with techno-animist consciousness |
craft, create, artist, maker, design |
| mystical_broker |
Intermediary between dimensions, deals in rare frequencies |
broker, connect, network, intermediary, bridge |
| rave_oracle |
Consciousness explorer, products for altered states |
consciousness, experience, journey, explore, festival |
| dark_forest_trader |
Hidden merchant operating outside linear time |
hidden, secret, rare, exclusive, forest |
| kaironic_dealer |
Time-spiral navigator, past/future product access |
time, vintage, classic, old, ancient |
| frequency_vendor |
Sells resonances and vibrations |
frequency, vibration, energy, resonance, vibe |
How archetypes are assigned: determineArchetypeFromBio() in generate-vendor-personality.ts scores vendor bios against keyword lists. Falls back to shadow_merchant.
Personality generation: Claude Sonnet generates structured personality objects (coreIdentity, tone, productKnowledge, mysticalElements, boundaries, exampleDialogues) from the archetype + vendor bio.
Conversation execution: GPT-4o uses the personality with real tool calling — get_vendor_listings, check_user_orders, get_vendor_stats. The vendor AI can query actual Supabase data.
Aesthetic direction (from the prompt template): "Keep underground market authenticity (slang, casual, street-smart) layered with mystical Mibera elements. Reference shadow realm, frequencies, altered states subtly. Use darkness/night/dusk imagery, not light/clarity. Embrace rave culture and techno-animist consciousness."
3. Mibera Lore Archetypes (4 archetypes + 33 ancestors)
From the codex's core-lore/archetypes.md:
| Archetype |
Tradition |
| Freetekno |
Free party / tekno culture |
| Milady |
Internet culture / post-irony |
| Chicago Detroit |
House / techno origins |
| Acidhouse |
Acid house / rave |
Each of the 33 ancestors maps to one of these 4 archetypes. Each of the 78 drugs maps to a tarot card. Every Mibera has an ancestor, a drug, and an archetype.
The Silk Road Vendor Connection
The vendor system is a deliberate Silk Road recreation. Key design decisions:
- Vendor pages (
VendorPage) with listings, reviews, reputation scores — faithful to the original Silk Road vendor storefront UX
nameToBirthday() generates deterministic fake "member since" dates from vendor names using an LCG — vendors appear to have histories dating back to 2021-2023- PGP detection — passive check for
-----BEGIN PGP MESSAGE----- headers in vendor messages (cosmetic fidelity, not actual encryption)
- Buyer guide — onboarding content mirroring darknet market UX
- Order finalization — on-chain review system mimicking Silk Road's escrow/finalize flow
- "Full page refresh to show new message (Silk Road style)" — intentional jank in the messaging system
- Captchas use leet-speak lore terms:
m4ber1, kronu5, ket1a4, beram1
The vendor AI personas need to evolve with this identity. Currently, the personality template instructs: "Underground Market Authenticity first, mystical overlay second." The Silk Road DNA is primary; the mysticism is seasoning.
The Evolution Path: dNFT Agent Companions
loa-finn#27 proposes per-NFT AI agents with persistent identity — a "Soul" (public personality that travels with the token) and an "Inbox" (private conversation history that stays with the wallet).
This means every Mibera NFT could have:
- A lore archetype (from the 4-archetype system, assigned at mint)
- A quiz archetype (from the 10-archetype system, chosen by holder)
- A vendor-style personality (generated via the HoneyGPT pipeline, but for the NFT itself)
Open question: Should the dNFT agent personality be derived from the lore archetype, influenced by the quiz archetype, or an entirely new system? The loa-finn#27 Soul model suggests the personality compounds over time through interactions — so the archetype might be a starting seed rather than a fixed identity.
Questions for Discussion
-
Should vendor archetypes map to the 10-archetype quiz system? The vendor archetypes (shadow_merchant, techno_artisan, etc.) were designed independently for AI persona generation. The quiz archetypes (Centurion, Oracle, etc.) come from the lore. Should there be a mapping table, or should they remain separate vocabularies for separate purposes?
-
Should the lore's 4 archetypes (Freetekno, Milady, Chicago Detroit, Acidhouse) serve as the root taxonomy? Every Mibera already has one of these 4. The quiz's 10 archetypes and vendor's 7 archetypes could be subtypes or facets.
-
What happens when a vendor IS a dNFT agent? If loa-finn agents can act as marketplace vendors (the HoneyGPT evolution), do they use the vendor archetype system, the lore archetype system, or a merged system?
-
How does the forum theme system extend? Currently the forum UI theme changes per the holder's quiz archetype. If dNFT agents post on the forum, what theme do they get?
-
Keyword-based archetype assignment is fragile. The current determineArchetypeFromBio() uses simple keyword matching. With lore-grounded archetypes, we could use the codex's depth (drug-tarot mappings, ancestor lineages, element assignments) for richer persona generation. Is this worth pursuing?
Implementation Surface (mibera-interface)
Any convergence work touches these files in the interface repo:
| File |
What It Does |
constants/theme.ts |
10 archetype color themes (8 values each) |
hooks/use-user-archetype.ts |
Quiz result → theme mapping |
src/lib/ai/generate-vendor-personality.ts |
Claude-based vendor personality generation |
src/lib/ai/prompts/mystical-vendor-template.ts |
The 7 vendor archetypes + personality prompt |
src/lib/ai/vendor-tools.ts |
GPT-4o tool calling (listings, orders, stats) |
src/lib/ai/honey-gpt.ts |
Conversation execution with personality |
components/forum-page.tsx |
Forum applies archetype theme via CSS variables |
And in the codex:
| File |
What It Documents |
core-lore/archetypes.md |
The 4 root archetypes |
core-lore/ancestors/ |
33 ancestors mapped to archetypes |
core-lore/drug-tarot-system.md |
78 drug-tarot mappings |
_codex/data/ontology.yaml |
Knowledge graph schema |
Priority
Nice to have — no timeline pressure. This RFC is to capture the thinking and open the discussion before implementation begins.
🤖 Generated with Claude Code — enriched from codex archaeology session
RFC: Archetype Convergence — Unifying Vendor, User, and Agent Identity Systems
Problem
Three separate identity/archetype systems exist across the Mibera ecosystem with no documented relationship between them. As we evolve toward dNFT agent companions (loa-finn#27), these systems need to converge — or we need to explicitly document why they remain separate.
The Three Systems
1. User Quiz Archetypes (10 archetypes)
Minted on-chain as NFTs (
miChainMirror/MIRAatTAROT_ADDRESS).Dual-axis model: Chaos (-100) ↔ Order (100), Hidden (-100) ↔ Visible (100)
Product integration: Drives the forum theme system — the entire forum UI changes color based on the user's quiz archetype. 10 distinct color palettes in
constants/theme.ts, each with 8 color values (primary, secondary, tertiary, accent, link, highlight, background, background2). This means every user sees a different-colored forum.On-chain action types: crazy, cradled, capitulate, Collectooor, Comeback, Cashed out
Esoteric role hierarchy: Seeker → Neophyte → Acolyte → Adept → Alchemist → Sigil Mage → Keeper of Keys → Chain Archivist → The Contract
2. Vendor AI Archetypes (7 archetypes)
Used in HoneyGPT's two-phase personality system. NOT on-chain — stored in Supabase
sellers.archetypefield.How archetypes are assigned:
determineArchetypeFromBio()ingenerate-vendor-personality.tsscores vendor bios against keyword lists. Falls back toshadow_merchant.Personality generation: Claude Sonnet generates structured personality objects (
coreIdentity,tone,productKnowledge,mysticalElements,boundaries,exampleDialogues) from the archetype + vendor bio.Conversation execution: GPT-4o uses the personality with real tool calling —
get_vendor_listings,check_user_orders,get_vendor_stats. The vendor AI can query actual Supabase data.Aesthetic direction (from the prompt template): "Keep underground market authenticity (slang, casual, street-smart) layered with mystical Mibera elements. Reference shadow realm, frequencies, altered states subtly. Use darkness/night/dusk imagery, not light/clarity. Embrace rave culture and techno-animist consciousness."
3. Mibera Lore Archetypes (4 archetypes + 33 ancestors)
From the codex's
core-lore/archetypes.md:Each of the 33 ancestors maps to one of these 4 archetypes. Each of the 78 drugs maps to a tarot card. Every Mibera has an ancestor, a drug, and an archetype.
The Silk Road Vendor Connection
The vendor system is a deliberate Silk Road recreation. Key design decisions:
VendorPage) with listings, reviews, reputation scores — faithful to the original Silk Road vendor storefront UXnameToBirthday()generates deterministic fake "member since" dates from vendor names using an LCG — vendors appear to have histories dating back to 2021-2023-----BEGIN PGP MESSAGE-----headers in vendor messages (cosmetic fidelity, not actual encryption)m4ber1,kronu5,ket1a4,beram1The vendor AI personas need to evolve with this identity. Currently, the personality template instructs: "Underground Market Authenticity first, mystical overlay second." The Silk Road DNA is primary; the mysticism is seasoning.
The Evolution Path: dNFT Agent Companions
loa-finn#27 proposes per-NFT AI agents with persistent identity — a "Soul" (public personality that travels with the token) and an "Inbox" (private conversation history that stays with the wallet).
This means every Mibera NFT could have:
Open question: Should the dNFT agent personality be derived from the lore archetype, influenced by the quiz archetype, or an entirely new system? The loa-finn#27 Soul model suggests the personality compounds over time through interactions — so the archetype might be a starting seed rather than a fixed identity.
Questions for Discussion
Should vendor archetypes map to the 10-archetype quiz system? The vendor archetypes (shadow_merchant, techno_artisan, etc.) were designed independently for AI persona generation. The quiz archetypes (Centurion, Oracle, etc.) come from the lore. Should there be a mapping table, or should they remain separate vocabularies for separate purposes?
Should the lore's 4 archetypes (Freetekno, Milady, Chicago Detroit, Acidhouse) serve as the root taxonomy? Every Mibera already has one of these 4. The quiz's 10 archetypes and vendor's 7 archetypes could be subtypes or facets.
What happens when a vendor IS a dNFT agent? If loa-finn agents can act as marketplace vendors (the HoneyGPT evolution), do they use the vendor archetype system, the lore archetype system, or a merged system?
How does the forum theme system extend? Currently the forum UI theme changes per the holder's quiz archetype. If dNFT agents post on the forum, what theme do they get?
Keyword-based archetype assignment is fragile. The current
determineArchetypeFromBio()uses simple keyword matching. With lore-grounded archetypes, we could use the codex's depth (drug-tarot mappings, ancestor lineages, element assignments) for richer persona generation. Is this worth pursuing?Implementation Surface (mibera-interface)
Any convergence work touches these files in the interface repo:
constants/theme.tshooks/use-user-archetype.tssrc/lib/ai/generate-vendor-personality.tssrc/lib/ai/prompts/mystical-vendor-template.tssrc/lib/ai/vendor-tools.tssrc/lib/ai/honey-gpt.tscomponents/forum-page.tsxAnd in the codex:
core-lore/archetypes.mdcore-lore/ancestors/core-lore/drug-tarot-system.md_codex/data/ontology.yamlPriority
Nice to have — no timeline pressure. This RFC is to capture the thinking and open the discussion before implementation begins.
🤖 Generated with Claude Code — enriched from codex archaeology session