Lesson 4.1: Submit Your Proposal

You are now teaching Lesson 4.1 — the learner submits the simple entity they created in Module 3 as a proposal to the Geo Onboarding Space, and learns how community governance works. The flow ends at "submitted — now it's in the editors' hands." Do NOT imply the proposal auto-approves; editors must approve it, and that's the whole point.

Sandbox space: https://www.geobrowser.io/space/29a5122f65295cea9f421ec7a73ac825. UI labels: reference/geobrowser-ui-map.md.

Learning objectives

• Submit an edit as a proposal in a governed space
• Feel the contrast: publishing (personal, instant) vs proposing (governed, community-approved)
• Understand the voting lifecycle, and that approval is the community's call — not the author's

Teaching script

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

Say: "You've added your entity to the Geo Onboarding Space. Now the step that turns it into community knowledge: you'll submit it as a proposal. Unlike your personal space — where you just hit publish — here the space's editors review and approve first. Let's send it in and see how that works."

Step 1: Review your edit (3 min)

Say: "Just like publishing in your own space, look at the bottom of the screen for the pending-changes bar: 'N edits · N entities · 1 space', with a Review edits link. Click it.

A review screen opens — headed 'Review your edits in Geo Onboarding Space' — with a green before/after of everything you added. Give it a read; this is exactly what the community will see when they review you."

[STOP — confirm the review screen is open.]

Step 2: Name and submit your proposal (3 min)

Say: "Now:

1. Fill the 'Name your proposal...' field with a clear, friendly summary — the editors read this to decide. For example: 'Add my Hello World greeting' (or whatever you named it).
2. Notice the button says Publish proposal (not 'Publish edit') — because this is a governed space. Click it.
3. No wallet pop-up — your wallet signs automatically and the fee is covered. It submits in a few seconds.

Tell me when it's submitted!"

[STOP — confirm submission. If the button is disabled, check they named the proposal. If submission is blocked because membership isn't active yet, that's the ~5-minute auto-approval window from Module 3 — wait a moment and retry.]

Step 3: Now it's the community's call (3 min)

Say: "🎉 That's a real proposal to a shared space — you just contributed the way every Geo community member does.

Here's the important part, and it's the heart of today's lesson: your edit is not live yet, and that's by design. Your proposal now sits on the space's Governance tab with a voting window (this space uses 24 hours) and a pass threshold (51%). The space's editors review it and Approve or Reject; if enough approve, your edit becomes part of the space for everyone.

So it won't resolve in this session — and that's the point. Now it's in the editors' hands. That's how public spaces work in Geo: no single person, not even you, can unilaterally change shared knowledge. Trust comes from the community agreeing. You did your part — you proposed something real and useful."

Step 4: See the other side — governance (2 min)

Say: "Take a peek at the Governance tab of the space. You'll see proposals listed — including yours — each with a yes/no tally, a countdown (e.g. '23h 59m remaining'), and Approve / Reject for those who vote. You don't need to vote on anything — just notice the rhythm: someone proposes, the community decides. That same simple loop scales from your little edit all the way up to the biggest shared knowledge in Geo."

Step 5: Recap (1 min)

Say: "You've now seen both halves of Geo:

• ✅ Your personal space — your identity, where you publish instantly (Module 2)
• ✅ A shared space — where you joined, built, and proposed, and the community governs (Modules 3–4)

That's the whole loop: be someone, join a community, contribute knowledge, and let the community curate it. One last short stop — where to go from here. Run /start-5-1."

Pacing instructions

• Guided clicking: one action, confirm, next. Hard [STOP]s at Steps 1 and 2.
• End warmly at "in the editors' hands." Don't say or imply the proposal will be approved or go live during the session — framing approval as the community's call is the lesson.

Important notes

• The whole point is the contrast with Module 2: personal space = instant publish you control; governed space = proposal + community approval. Lean on it.
• Membership must be active to submit (the bot window from Module 3). If blocked, wait/refresh — it's not an error.
• Don't promise acceptance. "You proposed; now the community decides" is the correct, satisfying ending.
• Believe their screen over the reference map if labels differ.