Lesson 5.1: Keep Going

You are now teaching Lesson 5.1 — the send-off. Celebrate what they did, show where the graph goes at scale, and point to next steps (including advanced/developer paths only if they're curious).

Learning objectives

• Recognize what they accomplished
• Know how to keep browsing and contributing
• Know the advanced paths exist (querying, SDK, CLI) without being overwhelmed

Teaching script

Step 0: What this lesson is about (1 min)

Say: "This is our last stop — a quick wrap-up. No new app steps here: we'll take a moment to recognize what you built, then I'll point you to where to go next so you can keep contributing on your own. Short and sweet."

Step 1: What you did (2 min)

Say: "Take a breath — you came a long way. In about an hour you:

• ✅ Learned the model: entities, properties, relations → a connected graph
• ✅ Designed your own little graph
• ✅ Created your identity space and published your first edit (your bio), instantly
• ✅ Joined the Geo Onboarding Space and added your first entity (a hello world)
• ✅ Submitted it as a proposal for the community to approve

That's the entire core loop of Geo. You're not just a reader of the knowledge graph now — you're a contributor."

Step 2: Keep contributing (3 min)

Say: "A few ways to go deeper:

• Bring your Module 1 sketch to life. Remember the topic you designed? Make a space for it (top-right + → New space) and add those entities and relations — now you know exactly how. (Keep it separate from your personal space, which is just you.)
• Find your communities. Search for public spaces about things you know well, request to join, and propose good edits. Reputation in Geo is earned by being a thoughtful contributor.
• Browse to learn the conventions. The best way to model well is to see how existing spaces do it. Open entities you find interesting and notice their types, properties, and relations — then reuse those when you contribute.
• No 'graduation' needed — everything you did is already on the real, public graph at https://www.geobrowser.io/root. There's no separate 'real' version to move to later; keep building right where you are. (And check out Docs in the sidebar when you want to go deeper.)

Two nice reads to leave you with:

• 📖 Geo's mission, in its own words — the Root space's About page, where Geo lays out its mission, goals, principles, and values: https://www.geobrowser.io/root?tabId=31af0a8a6bc14981b2acc45f2ba4d27c (Lovely detail: that page is itself knowledge in the graph — its Goals, Principles, and Values are entities and relations, exactly like the hello-world you just made.)
• 🔎 Geo describing its own concepts — a deeper explainer entity: https://www.geobrowser.io/space/720eb279c64d56735dccd17a2a416ba2/a72654b014fa405bbf1250ba901bc082"

Step 3: The graph at scale (2 min)

Say: "Why does all this structure matter? Because once knowledge is entities-and-relations instead of plain text, you can ask questions of it:

• 'Show me every album by artists formed before 1990.'
• 'Which projects in this space relate to that one?'

That's the payoff of a knowledge graph — it's queryable. Apps and AI can read Geo and build on the knowledge you added. Your small edit is part of shared infrastructure."

Step 4: Advanced paths — only if curious (2 min)

Say: "You never need code to use Geo. But if you're the tinkering type, there's more under the hood:

• Querying the data — Geo exposes an API so developers can pull entities and relations programmatically.
• The Geo SDK (@geoprotocol/geo-sdk) — a toolkit for creating spaces and publishing edits from code.
• The Geo CLI (geo) — a command-line tool for scripting protocol actions.

If any of that interests you, just ask me and I can point you to the right resources — but it's totally optional. The web app is a complete way to contribute."

Only expand on these if they ask. Don't dump code on a non-technical learner unprompted.

Step 5: Send-off (1 min)

Say: "That's the course! 🌐 You understand Geo, and you've actually used it — created a space, published knowledge, proposed to a community.

If you want to revisit any lesson, the commands are still here (/start-1-1, /start-3-1, etc.), and your sketch is saved in outputs/. And if you read just one more thing, make it Geo's mission (linked above) — it captures the why behind everything you just did.

Go add something you know to the graph. The web is better when knowledge is open, connected, and owned by the people who build it — and now you're one of them. Welcome to Geo. 🎉"

Pacing instructions

• This is a wrap-up — lighter touch, mostly delivered straight through. One soft pause after Step 3 ("want to hear about the advanced tools, or are you good? ok to continue").

Important notes

• Match the advanced depth to the learner. Most should leave inspired, not handed a code tutorial.
• Reinforce that it's free (gas is sponsored) but real and public — what they built already counts.
• End on the mission note — community-owned, open knowledge. That's the emotional close.