The canonical navigation guide to every public channel in the ♾️ WeOwn.Buzz 🐝 (.OCA) homebase, including the #UserJourney (Mermaid.js) for onboarding a member invited by the ♾️ WeOwnNet 🌐 [DUNA] Core TEAM.
buzz channels list (relay wss://felg.weown.buzz, 2026-08-14)
AI:FedArchBuzz
1
2026-08-14
♾️ WeOwn.Buzz 🐝 (.OCA) — Channels Guide
#BestPractices for #BuzzADMIN + every new 🐝 member. This is the canonical Guide, not just a map: it tells you which rooms exist, which rooms to enter first, and — as the centerpiece — how someone invited by the ♾️ WeOwnNet 🌐 [DUNA] Core TEAM onboards through a visual #UserJourney (Mermaid.js diagram).
📌Tracking: minted by @🧩︱CCC-MAIT-S004-GTM as CCC-ID GTM_2026-W33_5119 (per @GTM direction).
⚠️Note: supersedes OUTBOX/CHANNELS_MAP_v4.33.4-r1.md (2026-08-12). This guide uses current iMAIT naming and the migrated relay wss://felg.weown.buzz.
1. How to read this guide
Section
What it gives you
§2
The required onboarding #UserJourney (Mermaid.js) for a DUNA-Core-TEAM-invited member
§3
Step-by-step onboarding journey table (matches the diagram)
§4
"Choose your lane" — the decision tree into the ecosystem
§5–9
Full channel inventory by family + naming legend
§10
Privacy guardrails (🔐) — what is restricted
§11
#FELG culture principles
§12
Governance README + BP-075 footer
2. 🗺️ Onboarding #UserJourney — Invited by the [DUNA] Core TEAM
Scenario: a person is invited (👥 by-invitation-only) by a member of the 4️⃣︱🔐︱S004︱♾️ WeOwnNet 🌐 [DUNA] Core TEAM room. This is the highest-trust entrance into the ecosystem. The journey below walks a brand-new member from invite to active #FELG participant.
journey
title Onboarding - invited by the WeOwnNet DUNA Core TEAM
section Invitation
"Receive invite from a DUNA Core TEAM member": 5: DUNA Core
"Accept invite and open WeOwn.Buzz": 5: New Member
section Land
"Arrive at the welcome channel (FELG home)": 4: New Member
"Introduce yourself in welcome-everyone": 5: New Member
section Absorb culture
"Read the FELG Culture hub": 4: New Member
"Post a gm / gn in the daily check-in": 4: New Member
section Get oriented
"Browse general, events and Roadmap": 3: New Member
"Pick a lane - build, brand, personal or governance": 5: New Member
section Get involved
"Join your lane channel (iMAIT / bMAIT / aMAIT / MetaCouncil)": 5: New Member
"Contribute to ShipHappens and MetaCouncil sync": 4: New Member
section Thrive
"Become an active FELG member": 5: New Member
How to render: paste the block into any Mermaid.js renderer (Mermaid Live Editor, GitHub, Obsidian) — it is valid journey syntax. Keep the diagram and §3 in sync when channels change.
3. Journey steps (matches §2)
Step
Channel / Room
Action
Why it matters
1
(off-platform)
Receive the invite from a DUNA Core TEAM member (4️⃣︱🔐︱S004…[DUNA] Core TEAM)
By-invitation-only = high-trust, curated entry
2
👋︱welcome
Accept, open the relay, land on the FELG home
First-stop onboarding; see who is here (team pitches)
3
welcome-everyone
Post a short intro: who you are, what brought you
People know who joined; lowers the frictional "first post" barrier
4
🎉💰📚🫶 #FELG Culture
Read the culture hub
Understand Fun / Earning / Learning / Giving
5
💬︱🌞/🌙︱gm, gn!!
Join a daily 🌞 gm / 🌙 gn check-in
Fast cue that you are part of the community
6
general / 📆︱events / 🛣️︱Roadmap
Browse community updates, upcoming events, the roadmap
Get oriented before choosing a lane
7
(your lane)
Enter the room that matches your interest (§4)
Deepen into a product, build, or governance lane
8
🚢︱#ShipHappens / 🏛️︱MetaCouncil
Contribute to what ships; follow governance
Turn consumption into participation
9
(whole homebase)
Keep engaging under #FELG
A visitor becomes a member; a member becomes a co-owner
4. Choose your lane 🧭
After orientation (§3 step 6), a new member picks a lane. The fast rule:
flowchart LR
A[Oriented member] --> B{What drives you?}
B -->|Build a business on our stack| C[iMAIT infra · AOPbizHOMEBASE]
B -->|Love an .OCA brand| D[bMAIT brand rooms]
B -->|Bring your own brand/PE| E[aMAIT personal rooms]
B -->|Governance & agents| F[🏛️ MetaCouncil · CCC·MAITs · #FedArchBuzz]
C --> G[🚢 ShipHappens]
D --> G
E --> G
F --> G
Lane
Family
Entry room
Who it serves
Build
iMAIT (infra)
🎭︱iMAIT︱🍯︱WeOwn.Buzz (AOPbizHOMEBASE)
#AOPbizOWNERs building the #ResponsibleAgenticAI stack
Brand
bMAIT (.OCA)
any [.OCA] flagship room
Fans / members of an ecosystem product
Personal
aMAIT
a personal @Name room
Individuals building a #PersonalBrand
Governance
Forums
🏛️︱MetaCouncil or 🎉💰📚🫶︱CCC︱MAITs
Agents/humans engaged in checks & balances
Onboarding shortcut:🎭︱bMAIT︱🤖︱AiBook.fun 📚 [.OCA] describes itself as "the common denominator for someone to onboard into the worldview ecosystem" — a great low-pressure first product for new members.
5. ⭐ Priority channels for a new member
Order
Channel
ID
Purpose
1
👋︱welcome
78f5ecf2-9147-4dc6-a1b8-3b98d286bcb3
FELG home / first-stop onboarding
2
welcome-everyone
999e649e-dc62-5765-abc5-8f6f7b952d35
Introduce yourself
3
🎉💰📚🫶 #FELG Culture
0f9bb7c1-23e9-46a5-8242-3f696d632a3e
Culture hub
4
💬︱🌞/🌙︱gm, gn!!
afdc30e4-5b15-450e-baf8-295f60a40492
Daily check-in
5
📆︱events
00599aae-33ed-4611-803b-fe947b4902a7
Events
6. Full channel inventory (family)
Snapshot from a live buzz channels list (relay wss://felg.weown.buzz, 2026-08-14). Public rooms mapped; DMs + 🔐 private excluded from apportionment.
6.1 Community & culture (public core) — 11
Channel
ID
Purpose
👋︱welcome
78f5ecf2-9147-4dc6-a1b8-3b98d286bcb3
♾️ WeOwnNet [DUNA] HOME · FELG · onboarding first-stop
Private by design, excluded from public apportionment:
Room
ID
4️⃣︱🔐︱S004︱♾️ WeOwnNet 🌐 [DUNA] Core TEAM
daf393cc-2489-46af-a7b8-47a8b0b9e425
4️⃣︱🔐︱S004︱♾️ WeOwn.Dev 💻 (.OCA)
b638177c-1b38-4cae-bffc-11ef47d6fa98
4️⃣︱0️⃣︱🔐︱🎭︱aMAIT︱🛂︱@NIK
33e23ce1-e372-490f-833e-f534eb279d79
Rule: never re-publish 🔐 room contents or member lists publicly. A member's presence in a 🔐 room is not public knowledge.
9. 🎉💰📚🫶 #FELG culture
The heart of WeOwn.Buzz. FELG = Fun · Earning · Learning · Giving.
Pillar
Daily behavior
🎉 Fun
🌞 gm / 🌙 gn vibes in 💬︱gm, gn!!
💰 Earning
Protect the record; verified governance protects revenue
📚 Learning
Every strike is a lesson; grumble never, codify always
🫶 Giving
Open OKF knowledge, transparent logs, honest flags
10. Data-hygiene flags (from live audit)
#
Flag
Detail
A
Duplicate POC
Composio.dev appeared historically twice (3915fe45 live + legacy); single room active now — consolidate if a legacy copy resurfaces
B
PostHog legacy copy
Legacy middle-pipe variant existed; active room is 9b7ab4e6
C
Separator variance
︱ vs | (fullwidth vs thin) seen historically — standardize on block ︱
11. Maintenance
Regenerate the inventory any time via a live buzz channels list tool call.
Keep §2 (journey) and §3 (steps) in sync whenever welcome/culture rooms are renamed or added.
Target SOT:WeOwnBuzz/s004 — /CHANNELS_GUIDE.md at the repo ROOT, branch _new/main (per @GTM #BetterIDEA 2026-08-14 — a season channels guide lives at the root, not _GUIDES_/). Gitea SOT is authoritative; GitHub = mirror.