--- title: Start a cell — the door is open author: IBEAR Toolkit cohort: IBEAR 49 onward language: en date: 2026-08-21 paths: [stayer, returner, pivoteer, climber] --- # Start a Cell ✌️ **The formula: you two + developers + AI.** - **Product Owner** — owns *what* gets built and *why it matters*. - **Scrum Master** — owns the *rhythm*: the block, the check-ins, the retro. - **Developers** — everyone who answers the announce. In Scrum, "developer" never meant coder — it means *builder*: the one who cooks, designs, negotiates the venue, writes the page. - **AI coworkers** — every seat comes with one. Your AI pair-builds with you: drafts, prototypes, translates, codes what none of you code. Two people open the cell. The announce brings the developers. The AI multiplies all of you. Nobody is the boss — that's the entire org chart. You don't need permission, a budget, or a committee. Two cells are already running (Cohort Connect, the Potluck Kernel). The door is open for the next pair. --- ## The 30-minute start (Day 1) 1. **Find your counterpart.** PO with an itch needs an SM who likes rhythm — or the reverse. Ask one person. That's the click. 2. **Pick your build:** claim one from the menu below — **or invent your own.** Both doors are the same size. 3. **Write the announce** (template at the bottom) and post it where the cohort lives. 4. **Seat the AI:** each of you pastes the toolkit's context pack into your AI coworker — now it knows the method, the calendar, and the cohort's shape, and it works *with* the cell instead of starting cold. "None of us code" stopped being a blocker the day your AI colleague could. Cohort Connect is prototypable in one block this way. 5. **Set your first block:** 1–2 weeks, one small shippable thing. Not the vision — the first slice. That's it. You're a cell. --- ## Door one: the menu — builds ready to claim Each of these is real, scoped, and wanted. Claim one by announcing it. | Build | First slice (one block) | Feeds | |-------|------------------------|-------| | **Festival potluck run** | Run the nearest festival as a full experiment: inverted hosting, non-player roles, visible table list | Potluck Kernel | | **Skills & needs map** | One shared sheet: 38 rows — what I know, what I need, what I can lend | Cohort Connect | | **IBEAR 50 landing crew** | Airport pickups + first-week buddy roster for next year's arrivals, tested on what this cohort wished it had | The program itself | | **Arrival guide, verified** | Take the toolkit's visa/bank/housing checklist and verify every line against what actually happened to the 38 of you — fix what's wrong | The toolkit | | **Golf+** | Design the non-player roles for the next golf day and measure: did the group grow? | Potluck Kernel | | **Panel capture pipeline** | Every guest talk becomes one credited page within 48 hours — you saw the July panel page; be the ones who make it automatic | The wiki | | **Alumni match** | Pair each path group (recruiting, home-market, portfolio, offer) with one alum willing to answer — one intro each, not a mentoring program | The network | | **The ledger experiment** | Test whether a visible "who brought what" list is enough to keep the potluck from becoming a buffet — the Hansa question | Potluck Kernel | ## Door two: invent your own The menu is a starting line, not a fence. The best cell is the one built around a problem *you* actually feel. If nothing above itches, hunt your own: - **What annoyed you this week?** The thing you worked around instead of fixing — that's a build. - **What did you just rebuild that a classmate had already figured out?** Anything solved twice in one cohort wants a shared version. - **What does your country's cohort do that the others don't have?** The Korean study rotation, the Japanese senpai intro, the Indonesian arisan pool — every culture in this room ships a social technology the rest have never seen. Port one. - **What will IBEAR 50 hit that nobody warned you about?** You are the only people alive who know. Build the warning. - **What would you build if it didn't have to be useful?** Some of the best bridges start as jokes. The cohort band, the cookbook, the documentary — if two of you want it, it qualifies. An invented build follows the same three rules and gets the same trade: blocks, open pages, your name on it, and the same hand-over path if it proves out. **Nobody needs to approve your idea. The announce *is* the approval.** --- ## Why "developer" is the easiest door in Not ready to run a cell? Join one. The developer seat is the most underrated role here, and for many people in this cohort it's the *right* first move: **The work speaks, so you don't have to.** PO and SM are talking roles — pitching, coordinating, unblocking. Developer is a *making* role. You contribute a checklist, a prototype, a venue booked, a dish cooked, a page drafted — and the artifact carries your point. In a room where many of us think faster than we can say it in English, that's not a small thing: **a built thing has no accent.** The quiet classmate who ships something every block ends up with more standing than the loudest voice in the meeting — the FAQ already told you volume isn't belonging; this is where that becomes an advantage. **Smallest commitment, same credit.** One small real thing per block. That's the whole job. Your name goes on the page like everyone else's — the wiki credits builders, not talkers. **Your AI closes the language gap while you work.** Draft in your own language, let your AI coworker carry it into English, refine together. You're contributing at full intelligence instead of at second-language speed — the same context-arbitrage move the toolkit teaches for class, applied to building. **It's the apprenticeship.** Roles rotate. Developer this block is how you watch a PO and an SM work from the inside — so next block, when you announce your own cell, you've already seen the method run. Every PO in this cohort's future was a developer first. ### How developers sign up No form, no platform — three ways in, pick the one that fits you: 1. **Reply to the announce** where it was posted. One line: "I'm in — I can bring [the thing]." Done. 2. **Join quietly.** Message the PO directly — or email jlcortes@gmail.com and we'll connect you. Not everyone wants to raise a hand in the group chat, and the developer door exists precisely for you. Joining privately is a first-class path, not a side entrance. 3. **Just bring something.** Show up to the cell's next check-in with a contribution in hand. In a potluck, arriving with a dish *is* the signup. **The record:** each cell's wiki page lists its people — first names, roles, and what each brought, updated when the block ships. **The page is the roster.** No app to join, nothing to log into; if your name is on the page, you're on the team, and the next cohort will read it there. --- ## The rules (there are only three) 1. **Ship in blocks.** 1–2 weeks, something real at the end of each — built, tested, or learned. A cell that hasn't shipped in two blocks isn't a cell; it's a group chat. 2. **Build in the open.** One page here per block: what you tried, what happened, what's next. Credited to you. That page is how the next cohort inherits your work instead of restarting it. 3. **Rotate if you grow.** At 4–5 people, roles rotate each block. Nobody is the boss for long — that's the feature. --- ## What you get This is the honest trade. You get: - **A real product story** — "we identified a problem, formed a team, shipped in blocks, and here's the page trail" is a better interview answer than anything in a case book. - **Your name on it, permanently.** Every page is credited. The wiki doesn't forget. - **The hand-over:** what gets proven here is packaged for **IBEAR Connect**. If the program adopts it, your build becomes part of the institution — with your names in the commit history. Cohorts for the next decade use the thing you made in a two-week block. The alumni network runs on exactly one currency: *people remember who built things.* --- ## The announce (copy, fill, post) ``` WHAT: [the build — from the menu or your own] WHY: [one line — who hurts without it] CELL: [name] (PO) + [name] (SM) + developers (room for 1-3 — builders, not just coders) FIRST BLOCK: [start date] → [end date], shipping [the first slice] IF YOU'RE IN: reply here, or DM [PO's name] to join quietly ``` Post it. Start the block. Write the page. ✌️ **Claimed a build or shipped a block?** Email jlcortes@gmail.com — your page goes up, credited, same week.