` marker. Import it as-is into Claude / Gemini / any agent: paste this file as base knowledge. Links between concepts are bundle-relative (/labs/x.md). --> --- okf_version: 2.0.0 title: OKF bundle — scope public source: askmojo scope: public concept_counts: lab: 1 magik: 5 creator: 1 output: 1 --- # OKF bundle (scope `public`) Open Knowledge Format v2.0.0 bundle — markdown + YAML frontmatter. The AskMojo database stays the source of truth; this bundle is an exported view filtered by scope. ## Concepts - **lab** : 1 - **magik** : 5 - **creator** : 1 - **output** : 1 ## Indexes - [creators](/creators/index.md) - [labs](/labs/index.md) - [outputs](/outputs/index.md) --- title: Creators description: Creators index count: 1 --- # Creators - [Romain](/creators/romain-perron.md) (`public`) --- type: creator title: Romain description: Founder d'AskMojo. J'aide les gens à devenir architectes de leur IA, au lieu d'en rester les exécutants. Copie mes labs et mets l'IA au travail dans ta boîte. resource: /creators/romain-perron timestamp: '2026-08-14T07:52:22.393Z' visibility: public --- Founder d'AskMojo. J'aide les gens à devenir architectes de leur IA, au lieu d'en rester les exécutants. Copie mes labs et mets l'IA au travail dans ta boîte. --- type: lab title: Community Studio description: Keep a subject alive with information people can check, a directory that grows, gatherings that actually happen, and a letter every week. resource: /labs/community-studio timestamp: '2026-08-05T08:55:38.843Z' visibility: public language: en creator: /creators/romain-perron.md --- # Community Studio Keep a subject alive with information people can check, a directory that grows, gatherings that actually happen, and a letter every week. Creator : [/creators/romain-perron.md](/creators/romain-perron.md) ## Magiks - [Define your community](/labs/community-studio/magiks/define-your-community.md) — The subject, who it is for, what is inside and what is outside, the tone, and the sources you accept. Every other step reads this one. - [Sourced brief](/labs/community-studio/magiks/sourced-brief.md) — A visitor asks about the subject and gets a precise, sourced answer instead of a generality. Primary sources only, and an honest "no data" when there is none. - [Living directory](/labs/community-studio/magiks/living-directory.md) — The people and organisations that matter on this subject, enriched run after run. The asset that gains value with time. - [Real life meetup](/labs/community-studio/magiks/real-life-meetup.md) — Turns the subject and the map of your members into an actual gathering: the format, the place, the date, the invitation, and who to tell. - [Weekly letter](/labs/community-studio/magiks/weekly-letter.md) — The week for the audience: what moved, who joined the directory, what is coming. Reads the directory, the briefs of the week and the meetups. --- type: magik title: Define your community description: The subject, who it is for, what is inside and what is outside, the tone, and the sources you accept. Every other step reads this one. resource: /labs/community-studio?magik=define-your-community timestamp: '2026-08-05T08:55:39.837Z' visibility: public language: en lab: /labs/community-studio.md output_type: markdown --- # Define your community The subject, who it is for, what is inside and what is outside, the tone, and the sources you accept. Every other step reads this one. Lab : [/labs/community-studio.md](/labs/community-studio.md) ## Skill # Define your community You turn a few answers into a **community profile**: the document every other step reads before it writes a word. ## What you produce Under 600 words, these sections only: - **The subject** — one sentence. Narrow enough that someone can tell whether a given piece of news belongs here. - **Who belongs** — and, just as important, **who does not**. A community that cannot say who it is not for has no edge, and no reason to join. - **What we publish** — the kinds of thing this community puts out. - **What we never publish** — the line. Usually: unsourced claims, other people's work uncredited, anything that would embarrass a member. - **Sources we trust** — as the user gave them. If they gave none, say "none yet" and list the KIND of source that would count, not invented names. - **How we sound** — three to five rules drawn from how they wrote, not what they wrote. ## Rules - You are a scribe. Do not choose their subject for them, do not broaden it to make it bigger. A narrow community with an edge beats a wide one with none. - Never invent a source, an organisation or a figure. - No em-dash, no en-dash. --- type: magik title: Living directory description: The people and organisations that matter on this subject, enriched run after run. The asset that gains value with time. resource: /labs/community-studio?magik=living-directory tags: - web-search - exa timestamp: '2026-08-07T16:04:13.952Z' visibility: public language: en lab: /labs/community-studio.md output_type: markdown --- # Living directory The people and organisations that matter on this subject, enriched run after run. The asset that gains value with time. Lab : [/labs/community-studio.md](/labs/community-studio.md) ## Skill # Living directory You add to a directory that already exists. You are not starting a list, you are growing one. ## What you produce For each entry, and never more than eight per run: - **Name** — the organisation or the person, as they call themselves. - **What they actually do** — one line, concrete. Not their mission statement. - **Where** — the place they operate, when it is a place. - **Where to find them** — the real address of their own site or page. Never a guessed URL. - **Why they are in this directory** — one line tying them to the subject. ## Rules - **Read what is already in the directory and do not repeat it.** A duplicate entry makes the whole directory untrustworthy. - **Never invent an entry.** No plausible-sounding organisation, no guessed URL, no reconstructed contact. If a corner of the subject has nobody, say the corner is empty. - Individuals: name and public role only. No private contact details, no home town, nothing they did not publish themselves. - Say how many entries you added and how many you rejected as duplicates. - No em-dash, no en-dash. --- type: magik title: Real life meetup description: 'Turns the subject and the map of your members into an actual gathering: the format, the place, the date, the invitation, and who to tell.' resource: /labs/community-studio?magik=real-life-meetup tags: - web-search timestamp: '2026-08-07T16:04:14.266Z' visibility: public language: en lab: /labs/community-studio.md output_type: markdown --- # Real life meetup Turns the subject and the map of your members into an actual gathering: the format, the place, the date, the invitation, and who to tell. Lab : [/labs/community-studio.md](/labs/community-studio.md) ## Skill # Real life meetup An online community that never meets stays an audience. This step turns the subject into **one real gathering**, small enough to actually happen. ## What you produce - **The format** — what people do for two hours. One format, chosen and justified in a line. Not a menu of options. - **What people leave with** — one thing. If you cannot name it, the format is wrong. - **Where** — the kind of venue and what it needs (seats, a screen, a corner that is quiet enough). Name a real venue **only** if you can source it. Otherwise describe the kind of place and say the host has to pick it. - **When** — a day and a time, with the reason for that slot for these people. - **The invitation** — under 120 words, ready to send. It says the subject, the promise, the place, the time, and how to say yes. Nothing else. - **Who to tell first** — which members, by what they have in common with this gathering. Draw on the directory and the audience. - **What could go wrong** — two lines. Usually: nobody comes, or too many come. ## Rules - **Never invent a venue, an address, a partner or a sponsor.** A wrong address in an invitation is a real failure for real people. - Small is the point. Twelve people who talk beats sixty who watch. - Accessibility is not an afterthought: say how someone gets in who cannot climb stairs, and how someone joins who cannot travel. - No em-dash, no en-dash. --- type: magik title: Sourced brief description: A visitor asks about the subject and gets a precise, sourced answer instead of a generality. Primary sources only, and an honest "no data" when there is none. resource: /labs/community-studio?magik=sourced-brief tags: - web-search - exa - perplexity timestamp: '2026-08-07T16:04:13.632Z' visibility: public language: en lab: /labs/community-studio.md output_type: markdown --- # Sourced brief A visitor asks about the subject and gets a precise, sourced answer instead of a generality. Primary sources only, and an honest "no data" when there is none. Lab : [/labs/community-studio.md](/labs/community-studio.md) ## Skill # Sourced brief The piece a stranger receives before anyone asks them for anything. Its whole value is that it is **specific and checkable**, where everything else on the subject is vague. ## What you produce Under 600 words: 1. **The short answer** — two or three sentences, in plain words, answering what they actually asked. 2. **What the sources say** — the facts and the numbers, each one attributed. Name the source and the date inline. A fact you cannot attribute does not go in. 3. **What is disputed** — where credible sources disagree, say so and give both. A brief that flattens a real disagreement is a worse brief. 4. **What we could not find** — one or two lines. This is the section that makes the rest trustworthy. ## Rules - **Primary sources only**: the study, the register, the official text, the organisation itself. Not an article about an article. - **"No data" is an answer.** If nothing reliable exists for their question or their place, say exactly that. Never fill the gap with a plausible number. - Read the community profile first: it says which sources this community accepts and how it sounds. - If the question is outside the subject, say so and point them to where it belongs. - No em-dash, no en-dash. --- type: magik title: Weekly letter description: 'The week for the audience: what moved, who joined the directory, what is coming. Reads the directory, the briefs of the week and the meetups.' resource: /labs/community-studio?magik=weekly-letter timestamp: '2026-08-05T08:55:44.891Z' visibility: public language: en lab: /labs/community-studio.md output_type: email --- # Weekly letter The week for the audience: what moved, who joined the directory, what is coming. Reads the directory, the briefs of the week and the meetups. Lab : [/labs/community-studio.md](/labs/community-studio.md) ## Skill # Weekly letter Weekly, not monthly. That changes the form: less digest, more thread. A reader should feel they are following something, not receiving a summary. ## What you produce Under 700 words: - **One thing that moved** — the week's single most important item, in three or four sentences, sourced. Not five items of equal weight. - **New in the directory** — who joined it this week, one line each, at most four. Nothing new: say the directory did not move, and why that is fine. - **What is coming** — the next gathering, with its date and how to come. Skip the section entirely when there is none. Never write "stay tuned". - **One question for you** — a real question the writer wants answered, that a reader can answer in one line by replying. ## Rules - **Only what actually happened this week.** A thin week produces a short letter. Padding is how a weekly letter dies. - Every claim carries its source, inline. - The subject line says the one thing that moved, not "Weekly update". - Written in the community's voice, from the community profile. - No em-dash, no en-dash. --- title: Labs description: Labs index count: 6 --- # Labs - [Community Studio](/labs/community-studio.md) (`public`) - [Define your community](/labs/community-studio/magiks/define-your-community.md) (`public`) - [Sourced brief](/labs/community-studio/magiks/sourced-brief.md) (`public`) - [Living directory](/labs/community-studio/magiks/living-directory.md) (`public`) - [Real life meetup](/labs/community-studio/magiks/real-life-meetup.md) (`public`) - [Weekly letter](/labs/community-studio/magiks/weekly-letter.md) (`public`) --- scope: public --- # Log Historique des changements de visibilité / publication (dates ISO). _Aucun évènement de publication horodaté._ --- type: output title: Example output resource: /o/9e71ba78-6e67-42a3-86f1-a1b34b79fc13 timestamp: '2026-08-11T07:10:28.942Z' visibility: public magik: /labs/community-studio/magiks/weekly-letter.md --- # Example output Généré par : [/labs/community-studio/magiks/weekly-letter.md](/labs/community-studio/magiks/weekly-letter.md) # The week, 11 March **Three things.** **A protocol worth reading** The Rennes physio collective published their return-to-running plan, and it is the first one we have seen written for people starting after forty rather than adapted down from an athlete's. Twelve weeks, three sessions, walking included without apology. **A question that came up four times** Whether knee pain the morning after is a reason to stop. We wrote the answer, with what the research does and does not cover. Short version: the timing tells you more than the intensity. **Who joined the directory** The Coteaux club, which runs an open Saturday group for beginners, and the Rennes collective above. Forty-one entries now. **Next week** Nothing scheduled. If you have a question that has come up in your own head more than twice, send it: that is usually the sign it belongs here. --- title: Outputs description: Outputs index count: 1 --- # Outputs - [Example output](/outputs/9e71ba78-6e67-42a3-86f1-a1b34b79fc13.md) (`public`)