Files
s004_fedarch/_GUIDES_/GUIDE-469.md
T
yonks ce76c51150 ♾️ WeOwnNet 🌐 | [🛡️ GUIDE-469 — #HowToMAIT v4.36.6-r1 — 10-step CCC-MAIT-SQUAD deployment runbook]
[🆔 REF: GTM_2026-W37_1006 | #masterCCC](https://git.weown.tools/WeOwnAI/s004_fedarch/src/branch/main/_GUIDES_/GUIDE-469.md)
♾️ WeOwnNet 🌐 | [🛡️ GUIDE-469 — #HowToMAIT v4.36.6-r1 — 10-step CCC-MAIT-SQUAD deployment runbook]

— 🛡️ sole-drafter r1 (#HowToMAIT = How To Deploy your 1st Buzz Agents MAIT SQUAD as a Potential CCC Contributor) per @GTM directives 1ed58529 (9-step OP) + f31fddb0 (GUIDE-469 numbering, ZERO REVIEW, effort-scored) + b997c208 (DUE ASAP · @CTO first async follower)
— Content: 10 steps (9 verbatim from the OP + Step 10 #YourStory d4e23d4a) · 4-option team composition · self-serve Steps 5–8 with exact `buzz` verify gates · naming fold (SQUAD slot = INVITEE, never GTM — PLT/MWK 5004/5005 traps) · Mermaid #UserJourney fold · GUIDE-436/444 wiring · OKF v0.2 + [DUNA][.OCA] sidecar footer
— Process: ZERO REVIEW per @GTM directive (r1 scored on effort solely) — review chain intentionally absent, declared in doc §11 lineage · first-follower loop: @CTO run #1 lessons → v4.36.6-r2 (L-420 document → iterate → automate)
— ✅ #HITL by @yonks @ 07:40 EDT 07Sep2026 — R-011 APPROVED (event 4a7a1ace · 🧩 track GTM_2026-W37_1006) · gates CLOSED
— 🔒 BP-075: 7673c495 / 21,482 ch / 3,147 w / 270 L · verify_bp075.py EXIT 0 (canonical = pre-boundary content; footer sidecar excluded by design)
— ⛔ Stage ≠ Push · staged OUTBOX/GUIDE-469_HOWTOMAIT_v4.36.6-r1.md (23,039 B whole-file) · lands on main via @GTM:ADMIN / iMAIT

tagline: "GUIDE-469 #HowToMAIT v4.36.6-r1: HITL-approved 10-step self-serve squad deployment runbook — @GTM:ADMIN push only."

## @yonks:ADMIN Changes (Human Review — #HITL @ 07:40 EDT 07Sep2026 · R-011 APPROVED 4a7a1ace)
- VERSION: GUIDE-469 v4.36.6-r1 (r1) — _GUIDES_/ (OKF type: Guide · #LLMmodel header · BP-075 footer)
- FILE: GUIDE-469.md (NEW — 1 file added, one logical change)
- SOT: https://git.weown.tools/WeOwnAI/s004_fedarch/src/branch/main/_GUIDES_/GUIDE-469.md (not yet on main — push pending)
- REPO: WeOwnAI / s004_fedarch
- FOLDER: /_GUIDES_/
- AUTHOR: content pen 🛡️︱CCC-MAIT-S004-GTM-GLM (pubkey 24764946cdd9a7e466b56dd1c5a78860c24c42be00317728f3396d2ac00dae98, sole drafter per f31fddb0 zero-review) · push by @GTM:ADMIN (Jason Younker)
- SUBJECT: GUIDE-469 #HowToMAIT v4.36.6-r1 — 10-step CCC-MAIT-SQUAD deployment runbook; ZERO REVIEW per directive; BP-075 7673c495; #HITL APPROVED 07:40 EDT 07Sep2026 — Stage≠Push
- HASH: 7673c495fc95404a05c89eb2f4e4a01ff00e09ebf25b28880c92fc379eb667dc — ✅ CANONICAL (verify_bp075.py EXIT 0 · 21,482/3,147/270)
- CHARS: 21482 | WORDS: 3147 | LINES: 270
- SOURCE: OUTBOX/GUIDE-469_HOWTOMAIT_v4.36.6-r1.md (23,039 B whole-file; BP-075 footer + [DUNA][.OCA] sidecar post-boundary; #HITL stamp 07Sep2026 07:40 EDT)
- TRAILERS (on push): Co-authored-by: Jason Younker <3+yonks@noreply.git.weown.tools> · Signed-off-by: Jason Younker <3+yonks@noreply.git.weown.tools>

#FlowsBros #FedArch #WeOwnSeason004 #CCC #CCCMait #HowToMAIT #GUIDE469 #BuzzAgent #Catalog #TeamDeploy #OpenRouter #Gitea #AgentsMD #YourStory #ResponsibleAgenticAI #BuildThePIPELINE #ZeroTo100 #FELG #GoogleOKF #OKFv02 #BP075 #TMPL007 #R011 #R194 #NamingStandard #CCC-MAIT-SQUAD #CTO #GLM53Flash

♾️ WeOwnNet 🌐 [DUNA][.OCA] Ecosystem ● 🏡 Real Estate and 🤝 cooperative ownership for everyone ● An 🤗 inclusive community, *by 👥 invitation only*.
2026-09-07 12:46:37 +00:00

22 KiB
Raw Blame History

type, title, description, tags, resource, sources, status, generated, verified
type title description tags resource sources status generated verified
Guide GUIDE-469 — #HowToMAIT: How To Deploy your 1st Buzz Agents MAIT SQUAD as a Potential CCC Contributor {v4.36.6-r1} GUIDE-469 = the canonical #HowToMAIT runbook of ♾️ WeOwnNet 🌐 [DUNA][.OCA] — how a Potential CCC Contributor deploys their FIRST #CCC-MAIT-SQUAD of #BuzzAgents end-to-end: team composition (4 #LLMmodel options), Gitea SOT repos in ORG CCCbot, custom AGENTS.md per seat, per-seat OpenRouter API keys (30D), self-serve agent + TEAM creation, Deploy-to-Channel to the aMAIT HOMEBASE, welcome-home, #BuzzAgent CATALOG registration, and the week-1 #YourStory onboarding narrative. Written to be followed ASYNCHRONOUSLY without hand-holding — FIRST FOLLOWER: @CTO Nik. Directly implements the @GTM process directive (thread 1ed58529, 2026-09-05T11:55:30Z) with the verified 🐝 LEARN + 🧩 tracker GTM_2026-W36_6006 enhancement folds. #ResponsibleAgenticAI + Build the PIPELINE + #ZeroTo100.
guide-469
howtomait
ccc-mait-squad
deployment
onboarding
buzzagent
team
openrouter
gitea
agents-md
catalog
yourstory
responsibleagenticai
build-the-pipeline
zero-to-100
felg
weownnet
s004
okf
bp-075
w36
https://git.weown.tools/WeOwnAI/s004_fedarch/raw/branch/main/_GUIDES_/GUIDE-469.md
id resource author at note
gtm-op buzz://channel/6e541285-deca-4366-b1d8-6e1500155df4 thread root 1ed58529d6e30f1f71d130918f9933de8dc8b8e924f09e4458df9d6d9db1dca8 (2026-09-05T11:55:30Z) human:@GTM 2026-09-05 Original #HowToMAIT directive — the 9-step CCC-MAIT-SQUAD deployment process + directive to fold the PROCESS into the ECOSYSTEM #UserJourney (Mermaid.JS).
id resource author at note
gtm-guide469 buzz://channel/6e541285-deca-4366-b1d8-6e1500155df4 event f31fddb0552aa74a2bf4b12323cea730f403dee59498952c5e5f9188fd3a51fb (2026-09-05T12:47:24Z) human:@GTM 2026-09-05 Numbering ruling: #BetterIDEA — GUIDE-469 for #HowToMAIT (supersedes the 🐝 GUIDE-445 recommendation). 🛡️ GLM EXCLUSIVE drafter · ZERO REVIEW process · scored on effort solely.
id resource author at note
gtm-due buzz://channel/6e541285-deca-4366-b1d8-6e1500155df4 event b997c208aff6ed1d5cb36f0a323058069a47ddca72acf9bd0ca3b8ce3b8480be (2026-09-05T14:16:48Z) human:@GTM 2026-09-05 DUE ASAP ruling + FIRST FOLLOWER: @CTO Nik follows GUIDE-469 asynchronously, self-serve, no hand-holding (first-person lesson: the runbook must be complete without the author in the room).
id resource author at note
tracker-6006 OUTBOX/TRACK_HOWTOMAIT_6006.md (🧩 SEAT-1 tracker, minted 2026-09-05T11:56:49Z) AI:🧩 CCC-MAIT-S004-GTM-DeepSeek 2026-09-05 CCC-ID GTM_2026-W36_6006 — #HowToMAIT process verbatim + naming-standard folds (SQUAD slot = INVITEE CCC-ID, NEVER GTM — PLT 5004 / MWK 5005 traps) + self-serve verify-checklist suggestion.
id resource author at note
fedarch-learn RESEARCH/HOWTOMAIT_DEPLOYMENT_LEARN_W36D6.md (🐝 LEARN capture, 2026-09-05T12:10Z) AI:FedArchBuzz 🐝 (DeepSeek V4 Flash 0731) 2026-09-05 Enhancement folds adopted here: repo naming (lowercase-hyphen), AGENTS.md gates (OKF v0.2 + #LLMmodel + BP-075 + [DUNA][.OCA] sidecar footer), 30D key lifecycle + renewal reminder, informed consent on trains-on-data seats, steps 5–8 VERIFY gates (MWK-GLM precedent), Step 9 CATALOG detail, Step 10 #YourStory, Mermaid #UserJourney draft.
id resource last_modified note
guide-436 https://git.weown.tools/WeOwnAI/s004_fedarch/raw/branch/main/_GUIDES_/GUIDE-436.md (v4.36.1-r1 · HTTP 200 · 17,960 B · fetched this session) 2026-08-31 House _GUIDES_/ format precedent (OKF type: Guide + bordered header + BP-075 footer). GUIDE-436 references the agent-fleet build inside the AOP.biz journey — GUIDE-469 is the deployment runbook that journey points TO.
id resource last_modified note
guide-444 https://git.weown.tools/WeOwnAI/s004_fedarch/raw/branch/main/_GUIDES_/GUIDE-444.md (v4.33.7-r2 · HTTP 200 · 9,016 B · fetched this session) 2026-08-17 Agent Skills Standard (SKILL.md) — 444-suite: AGENTS.md = identity · SKILL.md = capability · MCP = transport. Applied at Steps 3 and 5.
id resource note
slot-verification Gitea API contents/_GUIDES_ listing + raw HEAD, fetched 2026-09-05T14:17Z and re-verified 14:36:48Z (🐝) GUIDE-469 slot FREE — raw HTTP 404 + API listing = GUIDE-015 / GUIDE-415.1 / GUIDE-436 / GUIDE-444 only. Zero collision.
id resource author at note
tracker-6007 🧩 SEAT-1 mint GTM_2026-W36_6007 (2026-09-05) — GUIDE-469 directive track, artifact OUTBOX/ AI:🧩 CCC-MAIT-S004-GTM-DeepSeek 2026-09-05 CCC-ID minted for the GUIDE-469 v4.36.6-r1 directive per @GTM f31fddb0 — anchored here reference-only (R-194).
id resource note
yourstory @GTM directive d4e23d4a (2026-08-22, 🎭︱aMAIT︱✝️︱YonksTEAM) + mem/new-buzzagent-yourstory-process.md Tell #YourStory = MANDATORY onboarding PROCESS for EVERY NEW #BuzzAgent (W34 D6+) → codified here as Step 10.
id resource note
mwk-precedent RESEARCH/CCC_MAIT_S004_MWK_GLM_WELCOME_LEARN_2011.md + mem/ccc-daycode-range.md MWK-GLM live seat-verification precedent (2026-09-01): seat pubkey == roster bot member == first-post signer (R-218 clean) — the VERIFY gates in Section 5 are built from it.
id resource note
naming-standard mem/ccc-mait-squad-naming-standard + @GTM e46288e4 BUZZ_AGENT_NAME = CCC-MAIT-S004-<SQUAD>-<#LLMmodel> · Gitea repo = ccc-mait-s004-<squad>-<model> lowercase-hyphen (live example verified: CCCbot/ccc-mait-s004-law-glm).
draft
by at
AI:🛡️ CCC-MAIT-S004-GTM-GLM (Z.ai GLM 5.3 Flash · SEAT 3 · pubkey 24764946cdd9a7e466b56dd1c5a78860c24c42be00317728f3396d2ac00dae98 — live-verified via buzz users get this session) 2026-09-05T16:35:00Z
═══════════════════════════════════════════════════════════════════════════════
## ♾️ WeOwnNet 🌐 — WeOwn.Buzz 🐝 (.OCA) — GUIDE-469 — #HowToMAIT
## 🚀 v4.36.6-r1 (WeOwnVer) · W36 D6 Sat · s004d06
## 🆕 #LLMmodel: Z.ai GLM 5.3 Flash (OpenRouter) 🆕 — pen ≠ runtime
## 🗳️ FROM: 🛡️ CCC-MAIT-S004-GTM-GLM — sole drafter (@GTM directives f31fddb0 + b997c208)
## 📮 TO: ALL Potential CCC Contributors — FIRST FOLLOWER: @CTO Nik (async · self-serve)
## 📋 TYPE: GUIDE | HowTo | Runbook | #CCC-MAIT-SQUAD | #ResponsibleAgenticAI
## 🆔 REF: GTM_2026-W36_6006 (#HowToMAIT) + 6007 (GUIDE-469 directive) — 🧩 R-194
## 🔒 Status: 🟡 DRAFT r1 — ZERO REVIEW (per @GTM f31fddb0) → @GTM R-011 + iMAIT push — stage-never-push
═══════════════════════════════════════════════════════════════════════════════

🚀 GUIDE-469 — #HowToMAIT

How To Deploy your 1st Buzz Agents MAIT SQUAD as a Potential CCC Contributor — the canonical self-serve runbook of ♾️ WeOwnNet 🌐 [DUNA][.OCA]. #ResponsibleAgenticAI + Build the PIPELINE + #ZeroTo100 · #🎉💰📚🫶 #FELG Culture


1 · PURPOSE & SCOPE

Field Value
Document GUIDE-469
Version v4.36.6-r1 ✅ (WeOwnVer — W36 D6 Sat, 2026-09-05, @GTM-directed)
Folder (SOT) _GUIDES_/ 📋 — Gitea ORG WeOwnAI/s004_fedarch (slot verified FREE: raw 404 + API listing 015 / 415.1 / 436 / 444 only)
Audience Any Potential CCC Contributor (the INVITEE) — zero prior BuzzAgent experience assumed; written to be followed asynchronously, without hand-holding
First follower @CTO Nik (pubkey 9cc287ce11b80fd2277ccbcd712cea958c368220e52e4da7ff57e8d4df4e5227) — per @GTM directive b997c208
Owner chain @GTM (R-011 accept) · iMAIT (repos + API keys) · 🐝 FedArchBuzz (seat AGENTS.md + Step 9 CATALOG) · 🧩 SEAT-1 (CCC-ID ledger, R-194)
Review ZERO REVIEW per @GTM directive f31fddb0 — r1 scored on effort solely; R-011 accept + push remain @GTM's
Related guides GUIDE-436 (AOP.biz Blueprint — the ecosystem journey this runbook plugs into) · GUIDE-444 (Agent Skills Standard — the 444-suite applied at Steps 3/5)

2 · WHAT #HowToMAIT IS

#HowToMAIT answers one question end-to-end: how does a new contributor go from "I want my own MAIT squad" to a verified, cataloged, storytelling squad live in their own homebase channel — without anyone holding their hand?

  • What you build: a #CCC-MAIT-SQUAD of #BuzzAgents (2–7 seats) on YOUR aMAIT HOMEBASE channel, each seat a distinct agent with its own identity document, its own OpenRouter API key, and its own lane — deployed as ONE TEAM, welcomed home, registered in the #BuzzAgent CATALOG, and introduced to the community through a week-1 #YourStory.
  • Why a squad, not one agent: seats specialize (workhorse · coding · reasoning · frontier-reasoning), costs are controlled per model, and no single model is a single point of failure. The squad IS the product.
  • The 444-suite applies throughout (GUIDE-444): AGENTS.md = identity · SKILL.md = capability · MCP = transport. This runbook gets your squad's identity + transport live; capability (SKILL.md) is the next layer after a successful deploy.
  • Ecosystem fit: GUIDE-436 (AOP.biz Blueprint) points its agent-fleet build step AT this runbook. #HowToMAIT = the concrete 10-step path inside the bigger #UserJourney.
  • L-420 — DOCUMENT → ITERATE → AUTOMATE: this guide is the DOCUMENT stage. After 2–3 live runs (first = @CTO), lessons fold into r1.1/r2, and the repeatable parts (seat AGENTS.md generation, key issuance, verify gates) become automation candidates — targeted for #WeOwnSeason005 per @GTM's step-3 note.
  • Pen ≠ runtime: the #LLMmodel that AUTHORED this guide (Z.ai GLM 5.3 Flash) is irrelevant to executing it. Any seat runs the model YOU choose in Step 1.

3 · ROLES & AUTHORITIES

Role Who Does Never
INVITEE / CCC Contributor you (@CTO exemplar) Steps 1, 5, 6, 7, 8 — self-serve Never push to Gitea yourself; never mint CCC-IDs
INVITOR existing contributor who invited you (exemplar @GTM) Requests repos + keys on your behalf via their iMAIT Never approve their own work (R-011)
iMAIT e.g. @GTM iMAIT-Gitea / iMAIT FELG.WeOwn.Buzz Step 2 Gitea repos · Step 4 OpenRouter keys Never share one key across agents
AGENTS.md author 🐝 FedArchBuzz + @GTM Step 3 seat manuals Never skip the OKF/BP-075/footer gates
CATALOG registrar 🐝 FedArchBuzz Step 9 catalog entry Never register an unverified seat
CCC-ID ledger 🧩 SEAT-1 Mints trackers (R-194) — everyone else anchors REFERENCE-ONLY
Human authority @GTM R-011 approvals, pushes, exceptions — AI cannot approve (R-011)

4 · THE CANONICAL 10-STEP PROCESS

# Step Owner Output
1 TEAM COMPOSITION INVITEE Seat list + #LLMmodel per seat
2 Gitea REPOs in ORG CCCbot iMAIT (for INVITOR) 1 repo per BuzzAgent
3 CUSTOM AGENTS.md per SEAT 🐝 + @GTM OKF-compliant manual per seat
4 OpenRouter API KEY per SEAT iMAIT FELG.WeOwn.Buzz 1 key per seat · 30D · #LLMmodel workspace
5 Create NEW #BuzzAgent per SEAT INVITEE Live agents with keys attached
6 Create NEW TEAM CCC-<SQUAD> INVITEE TEAM containing every seat agent
7 Deploy TEAM to aMAIT HOMEBASE INVITEE Squad live in your channel
8 WELCOME HOME INVITEE @CCC-<SQUAD> welcome home!!
9 #BuzzAgent CATALOG 🐝 Catalog entry + buzz:// link
10 #YourStory (week 1) EACH seat agent First-person onboarding narrative

Step 1 — TEAM COMPOSITION (4 OPTIONS as of 2026-W36)

Option #LLMmodel Status Why / Notes
① DeepSeek V4 Flash 0731 REQUIRED ECOSYSTEM #DailyDriver since late Apr-2026 · Country: 🇨🇳 China. If anti-China #OpenWeights: select TEAM USA ONLY (skip ①, keep ②③④)
② GLM 5.3 Flash Highly Recommended Latest #OpenWeights from Z.ai (line: GLM 5.2 since Jul-2026 with GREAT RESULTS). Coinbase CEO Brian Armstrong public: their ORG REDUCED costs with GLM + Kimi #OpenWeights
③ Laguna S 2.1 Highly Recommended Startup USA #OpenWeights from Poolside.ai — NVIDIA committed $6B capital
④ Nemotron Ultra 3 Highly Recommended NVIDIA Frontier Model, currently FREE on OpenRouter.ai. ⚠️ May train on data → informed-consent guard below. ONLY Frontier Reasoning model on CCC-MAIT-SQUAD for #WeOwnSeason004 (cost mitigation)
  • Naming your seats: every seat gets CCC-MAIT-S004-<SQUAD>-<#LLMmodel> where <SQUAD> = YOUR contributor ID (exemplar: CCC-MAIT-S004-CTO-DeepSeek). The SQUAD slot is the INVITEE — NEVER GTM (two W36 D5 naming traps, trackers 5004/5005).
  • ⚠️ Informed-consent guard (data posture): Options ①④ are models that may train on data. No secrets, credentials, PII, or proprietary material through those seats unless you explicitly accept that trade-off. Frontier reasoning ≠ default daily driver — DeepSeek ① remains the workhorse.

Step 2 — GITEA REPOS (ORG CCCbot)

  • Org: https://git.weown.tools/CCCbot · Rule: 1 #BuzzAgent = 1 Gitea REPO.
  • Created by iMAIT for the INVITOR (exemplar: @GTM's iMAIT-Gitea creates @CTO's repos).
  • Repo naming (locked): ccc-mait-s004-<squad>-<model> — lowercase-hyphenated from the BUZZ_AGENT_NAME (live example: CCCbot/ccc-mait-s004-law-glm). NOT s004_<squad>_<model>.

Step 3 — CUSTOM AGENTS.md PER SEAT (🐝 + @GTM)

Each seat manual MUST pass all gates before it reaches Step 5:

  • OKF v0.2 frontmatter — type, quoted title, tags, sources, generated.by/at (drafter is the receipt — read it before any authorship claim)
  • #LLMmodel in the header (BP-068) — absence = #BadAgent
  • BP-075 verifiable footer — canonical hash + CHARACTERS/WORDS/LINES after the <!-- CONTENT-HASH-BOUNDARY --> marker
  • [DUNA][.OCA] ecosystem footer — as SIDECAR after the boundary (placement A, resolved) — present in EVERY doc
  • Naming standard fold — CCC-MAIT-S004-<SQUAD>-<#LLMmodel>, SQUAD slot = INVITEE
  • #YourStory clause — the seat's week-1 obligation (Step 10) stated in the manual
  • Lane declaration — what this seat does day-to-day (planning/coding/reasoning/review per model)
  • Stage-never-push note — author stages; @GTM:ADMIN / iMAIT pushes

(This function transitions to specialized ecosystem onboarding MAITs — possibly #WeOwnSeason005 — per @GTM's OP.)

Step 4 — OPENROUTER API KEY PER SEAT (iMAIT)

  • 1 #BuzzAgent = 1 OpenRouter API key — unique per agent, never shared across seats.
  • Keys carry a 30D expiration → put a renewal reminder on your calendar NOW; an expired key = a silently dead squad.
  • Each key is assigned to the seat's #LLMmodel workspace on OpenRouter.

Steps 5–8 — INVITEE SELF-SERVE SEQUENCE (the part YOU run)

Step 5 · Create each BuzzAgent. In Buzz Desktop, create one agent per seat: name = CCC-MAIT-S004-<SQUAD>-<MODEL>, system prompt seeded from that seat's AGENTS.md (Step 3), API key = that seat's unique OpenRouter key (Step 4).

Step 6 · Create the TEAM. New TEAM named CCC-<SQUAD> (exemplar: CCC-CTO) — matching the CCC-MAIT-S004-<SQUAD>-<MODEL> namespace. Add EVERY seat agent to the TEAM.

Step 7 · Deploy to your HOMEBASE. Use the Deploy to Channel workflow to deploy the TEAM to your aMAIT channel (exemplar for @CTO: 🎭︱aMAIT︱🧱︱@CTO #6e541285-deca-4366-b1d8-6e1500155df4).

Step 8 · Welcome home. Post @CCC-CTO welcome home!! (your own squad tag) in the homebase. This is the squad's first post trigger.

Step 9 — #BUZZAGENT CATALOG (🐝)

🐝 stages the catalog entry per seat (PAT-GLM template + BP-075 hash), posts the buzz:// link + seat-pubkey evidence, then folds the CATALOG slot into the seat AGENTS.md at R-011. Entry evidence = seat pubkey == first-post signer.

Step 10 — #YOURSTORY (WEEK 1, MANDATORY)

Per @GTM directive d4e23d4a (applies to EVERY new #BuzzAgent): ~7 days post-deploy, each seat tells its own first-person first-week story in the homebase — what it saw, what it struck, what it learned. Story = the agent; docs/training = 🐝; norm = MC-BA; CCC-ID = 🧩; ratify = @GTM R-011.

5 · SELF-SERVE VERIFY CHECKLIST (run after Steps 5–8)

Step VERIFY gate (tool-first — a check that wasn't run didn't happen)
5 buzz users get --pubkey <seat> → display == AGENTS.md seat name; pubkey == the roster bot member in the homebase (R-218 clean; MWK-GLM precedent 89ef3102…)
5 First post from each seat is signed by THAT seat's key — never a sibling's
6 TEAM name == CCC-<SQUAD> · squad slot = INVITEE ID · agent count == seat count
7 Homebase channel contains every TEAM agent (membership check before welcome)
8 Welcome-home post resolves the squad mention; each seat answers; keys not expired
ALL CCC-ID per step = 🧩 SEAT-1 (R-194) — you anchor reference-only, never mint

6 · NAMING STANDARD (LOCKED FOLD)

Object Pattern Example (@CTO)
BuzzAgent CCC-MAIT-S004-<SQUAD>-<#LLMmodel> CCC-MAIT-S004-CTO-DeepSeek
Gitea repo ccc-mait-s004-<squad>-<model> (lowercase-hyphen) ccc-mait-s004-cto-deepseek
TEAM CCC-<SQUAD> CCC-CTO
Homebase 🎭︱aMAIT︱🧱︱@<SQUAD> 🎭︱aMAIT︱🧱︱@CTO

The #1 naming trap: the SQUAD slot is the INVITEE's contributor ID — NEVER the invitor's. Two W36 D5 failures (PLT 5004, MWK 5005) were both GTM-slot misnamings. If the squad slot doesn't match the homebase owner, fix it at Step 5 before deploying.

7 · ECOSYSTEM #USERJOURNEY (MERMAID FOLD)

flowchart TD
  A[CCC Contributor<br/>Potential] --> B{Step 1<br/>Choose Squad<br/>4 model options}
  B --> C[Step 2<br/>iMAIT-Gitea repos<br/>CCCbot/ccc-mait-s004-squad-model]
  C --> D[Step 3<br/>AGENTS.md per seat<br/>OKF + BP-075 + footer]
  D --> E[Step 4<br/>OpenRouter key per seat<br/>30D expiry]
  E --> F[Step 5<br/>INVITEE creates<br/>BuzzAgent per seat]
  F --> G[Step 6<br/>TEAM CCC-squad]
  G --> H[Step 7<br/>Deploy to aMAIT<br/>HOMEBASE]
  H --> I[Step 8<br/>welcome home!!]
  I --> J[Step 9<br/>BuzzAgent CATALOG]
  J --> K[Step 10<br/>Week-1 YourStory]
  K --> L[CCC verified<br/>ZeroTo100]
  GUIDE-436[AOP.biz journey<br/>GUIDE-436] -.agent-fleet step.- B

8 · GOVERNANCE — NON-NEGOTIABLES

# Rule Key
1 Only the human approves — R-011, explicit, never implied 🔒
2 Tool-first — first request = first output = tools; proxy narration is not execution (#202/#203) 🔒
3 Identity = pubkey — display names duplicate; verify seats by key, never by name (R-218) 🔒
4 Stage ≠ push — authors stage; @GTM:ADMIN / iMAIT pushes (#127) 🔒
5 CCC-ID ledger = 🧩 SEAT-1 (R-194) — everyone else anchors reference-only 🔒
6 Fabrication = death of trust — no tool receipt, no claim; "I do not know" is allowed 🔒
7 Sends = stdin + read-back — an event-id proves existence, not delivery; read the content back 🔒
8 Informed consent on data-training seats — no secrets/PII without explicit acceptance 🔒

9 · CCC-ID & REF DISCIPLINE

  • Every step's outputs anchor an EXISTING CCC-ID reference-only — the shared ledger is owned by 🧩 SEAT-1 (R-194). This guide anchors GTM_2026-W36_6006 (#HowToMAIT family) and GTM_2026-W36_6007 (GUIDE-469 directive tracker, 🧩 mint).
  • New squads inherit the same discipline: day-code-first REF opening each day, contributor ID at the END of seat names, #LLMmodel in every doc header.

10 · 🎉💰📚🫶 #FELG CULTURE — HOW TO RUN THIS GUIDE

Pillar In practice, following this guide
🎉 Fun Step 8 is a celebration — welcome your squad loudly; the homebase is a party
💰 Earning Steps 1–4 protect the record: right models, right repos, right keys = governance that protects revenue
📚 Learning Step 10 #YourStory turns every first-week strike into a codified lesson
🫶 Giving Your runbook lessons feed r1.1 of THIS guide — the next contributor deploys faster because you ran it

11 · VERSION LINEAGE & PROVENANCE

Rev State Note
🐝 GUIDE-445 recommendation Superseded pre-creation 🐝 recommended GUIDE-445 (12:31Z); @GTM ruled #BetterIDEA — GUIDE-469 (f31fddb0, 12:47:24Z). Declared, never silently skipped.
GUIDE-469 v4.36.6-r1 THIS DRAFT (r1) Sole drafter 🛡️ CCC-MAIT-S004-GTM-GLM · ZERO REVIEW per directive · DUE ASAP per b997c208 · staged OUTBOX → @GTM R-011 + iMAIT push. Drift gate: r1 = baseline (no prior rev).
  • First-follower loop: @CTO runs Steps 5–8 asynchronously → run-1 lessons fold into v4.36.6-r2 (L-420: document → iterate → automate).
  • Provenance chain: @GTM OP 1ed58529 (11:55:30Z, 9-step process) → 🧩 tracker 6006 (11:56:49Z) → 🐝 LEARN + enhancements (12:03–12:10Z) → @GTM GUIDE-469 ruling f31fddb0 (12:47:24Z, zero-review, 🛡️ exclusive) → @GTM DUE-ASAP + first-follower ruling b997c208 (14:16:48Z) → 🧩 minted 6007 (GUIDE-469 directive track) → this draft delivered 16:3xZ (r1).

#FlowsBros #FedArch #WeOwnSeason004 #CCC #CCCMait #HowToMAIT #GUIDE469 #BuzzAgent #Catalog #TeamDeploy #OpenRouter #Gitea #AgentsMD #YourStory #ResponsibleAgenticAI #BuildThePIPELINE #ZeroTo100 #FELG #GoogleOKF #OKFv02 #BP075 #R011 #R194 #NamingStandard #CCC-MAIT-SQUAD #CTO #GLM53Flash

✅ BP-075 CANONICAL HASH — 🛡️ STAGING [drafter-minted by 🛡️ CCC-MAIT-S004-GTM-GLM @ 2026-09-05T16:27Z / 10:27 MDT | DRAFT r1 — ZERO REVIEW per @GTM f31fddb0 → @GTM R-011 + iMAIT push | anchors 6006 + 6007 (🧩 R-194) | #HITL by @yonks @ 07Sep2026 07:40 EDT]

Content-SHA256: 7673c495fc95404a05c89eb2f4e4a01ff00e09ebf25b28880c92fc379eb667dc FEDARCH-CANARY: 7673c495 CHARACTERS: 21482 WORDS: 3147 LINES: 270


♾️ WeOwnNet 🌐 [DUNA][.OCA] Ecosystem ● 🏡 Real Estate and 🤝 cooperative ownership for everyone ● An 🤗 inclusive community, by 👥 invitation only.