Space Organizer

Part 1 — Syllabus

Purpose and Scope

The opt-in, member-open course that authorizes a member to create and run persistent community spaces. It is course-gated commons plumbing (Commons SOP §9): on completion, the member joins the organizer group, which carries the scoped space-creation right and a seat in the Community Organizers space. Open to any member — no Learner Permit, no clock. The course teaches the norms of the role before it grants the role’s power.

(The spaces live in HumHub, the community hub; this course is about organizing them, not about the tool.)

This is a syllabus, not boundary law. The role, its rights, and its gate are the Commons SOP’s (§4, §7A, §9); the conduct standard is the Commons Doctrine’s (§8). Part 2 carries the copy.

What it grants

On passing, an organizer may:

create and own persistent community spaces — the rooms members make for each other, scoped to members (Commons SOP §9);
moderate within the spaces they own;
coordinate in the Community Organizers space.

It does not grant:

application admin of any kind — that is the operator role (Commons SOP §7), provisioned separately by the Lounge Gate 2;
the Opplet Learner Permit, certified standing, the product / Developer working spaces, or any step of the Climb.

Prerequisites

Standing membership only. No Learner Permit. No 72-hour clock — self-paced, take it whenever.

Modules

What this course is — who it’s for, what it grants and what it doesn’t.
The organizer role — creating and owning member spaces; why an organizer is not an operator; hosting vs. owning; what you may and may not create.
Running a space well — moderation and your duty; substance over volume; the life of a space.
Why organize, and getting started — community for its own sake and visibility toward the Climb; your first space.

Delivery and grading

Open Moodle (Lounge), self-paced, no clock, 100% to pass. On graduation, Moodle fires the webhook to n8n-Alpha, which adds the member to the organizer group (Commons SOP §9). Mechanics are the Commons SOP §9’s.

Outcome

An organizer: a member who may create and run persistent community spaces, and who coordinates in the Community Organizers space. Nothing obliges a member to take this course — community life is open to all without it. You can host events and take part in any community space as a participant; this course is only for those who want to run the lasting rooms.

Part 2 — Course Content

Moodle copy-paste. Each lesson is two Moodle pages: a Content page (page contents + a button to advance) and a Question page (the question + answers, each with its jump and score). ✓ marks the correct answer; wrong answers loop back to the same page.

Section 0 — What This Course Is

Lesson 0.1 — Who This Is For, and What It Grants

Content page · “Who This Is For, and What It Grants”

Community life at Opplet is member-run. Any member may host an event; this course is the next step — it lets you create and run a persistent community space of your own: a study group, an interest or working space, a place for the cohort-in-waiting to gather. It’s open to every member — no Learner Permit, no clock.

When you pass, you’ll hold three things: the right to create scoped community spaces, the right to moderate within them, and a seat in the Community Organizers space, where organizers coordinate. What it doesn’t make you: an operator (that’s the application-admin role), a certified member, or a climber. Organizing is its own thing, and it’s complete on its own.

Button: Verify What It Grants → next page

Question page (Multiple choice) · “Verify: What It Grants”

What does passing the Organizer course let a member do?

✓ Create and run persistent community spaces, and moderate within them — open to any member, no Permit needed. — Jump: End of lesson · Score: 1
✗ Hold admin rights across Opplet’s apps. — Jump: this page · Score: 0
✗ Skip Enclave Bootcamp and enter the Range. — Jump: this page · Score: 0

Lesson 0.2 — How This Course Works

Content page · “How This Course Works”

Like the Welcome course, this is a guided read with a short check after each topic, and every answer sits in the text right above it. But this course gates a real responsibility — creating spaces that other members will rely on — so the checks confirm you’ve taken in the norms of the role, not just that you can follow instructions. Read for the duties, not only the permissions.

Button: Verify Course Purpose → next page

Question page (Multiple choice) · “Verify: Course Purpose”

What do the checks in this course confirm?

✓ That you understood the norms of the role before being granted its power. — Jump: End of lesson · Score: 1
✗ Your prior experience running online communities. — Jump: this page · Score: 0
✗ Nothing — passing is automatic on opening the course. — Jump: this page · Score: 0

Section 1 — The Organizer Role

Lesson 1.1 — What an Organizer Is

Content page · “What an Organizer Is”

An organizer creates and stewards persistent community spaces. You name a space, give it a purpose, bring people in, keep it healthy, and retire it when it’s done. You are the host of a room, not a manager of the platform. Most of what “Opplet is full of learning” means runs on organizers — the study groups, the demos, the working spaces are theirs, not handed down from above.

Button: Verify The Role → next page

Question page (Multiple choice) · “Verify: The Role”

An organizer is:

✓ Someone who creates and stewards community spaces — the host of a room, not a manager of the platform. — Jump: End of lesson · Score: 1
✗ A platform administrator with rights over all of Opplet. — Jump: this page · Score: 0
✗ A paid staff role you apply for. — Jump: this page · Score: 0

Lesson 1.2 — An Organizer Is Not an Operator

Content page · “An Organizer Is Not an Operator”

Two roles are easy to confuse; keep them apart. An operator holds admin or power-user rights across one or more apps (HumHub, Moodle, and the rest) — application-layer authority, provisioned by the Lounge Gate 2 (Commons SOP §7). An organizer holds rights scoped to the spaces they own — you create and moderate your own spaces, and nothing beyond them. Creating a space never gives you app admin. Different rooms, different keys.

Button: Verify Organizer vs Operator → next page

Question page (Multiple choice) · “Verify: Organizer vs Operator”

What separates an organizer from an operator?

✓ An organizer’s rights are scoped to the spaces they own; an operator holds admin across one or more apps. — Jump: End of lesson · Score: 1
✗ Nothing — they are two names for the same role. — Jump: this page · Score: 0
✗ An organizer holds platform root; an operator does not. — Jump: this page · Score: 0

Lesson 1.3 — Hosting vs. Owning

Content page · “Hosting vs. Owning”

There are two ways to run activity, and only one needs this course:

Host an event — ephemeral: a talk, study group, or demo on Jitsi, surfaced on the member calendar. Open to any member; no course required.
Own a space — persistent: a room that lives on, that you create and steward. This is what the Organizer credential grants.

So anyone can run a one-off; organizers run the lasting places.

Button: Verify Hosting vs Owning → next page

Question page (Multiple choice) · “Verify: Hosting vs Owning”

Which one needs the Organizer course?

✓ Owning a persistent space. Hosting a one-off event is open to any member. — Jump: End of lesson · Score: 1
✗ Hosting a one-off event; owning a space is open to all. — Jump: this page · Score: 0
✗ Both need the course. — Jump: this page · Score: 0

Lesson 1.4 — What You May and May Not Create

Content page · “What You May and May Not Create”

Your space-creation right is scoped on purpose. You may create member community spaces — the rooms members make for each other, kept to members. You may not create:

the chartered scaffold (Town Square, Job Seekers, Base Camp) — those exist by the Commons SOP, not by members;
the product / Developer working spaces — those are mandated by the Tech Board and gated to certified members;
public or platform-level spaces.

You build community rooms, not the building’s structure.

Button: Verify What You Can Create → next page

Question page (Multiple choice) · “Verify: What You Can Create”

Which may an organizer create?

✓ Member community spaces — not the chartered scaffold, the product spaces, or public/platform spaces. — Jump: End of lesson · Score: 1
✗ Anything, including Town Square and the product working spaces. — Jump: this page · Score: 0
✗ Public, platform-wide spaces open to guests. — Jump: this page · Score: 0

Section 2 — Running a Space Well

Lesson 2.1 — Moderation Is Your Duty

Content page · “Moderation Is Your Duty”

When you own a space, you keep it healthy. You moderate within it: hold members to the Commons’ conduct standard — civil, honest, open — and handle the routine exceptions yourself. You act under your callsign, and your actions are logged like everyone’s (Pillar 4): observation is truth. What’s beyond your authority you escalate up the operator ladder (Commons SOP §6). You don’t have to carry what isn’t yours — but you can’t ignore it either.

Button: Verify Your Duty → next page

Question page (Multiple choice) · “Verify: Your Duty”

As a space owner, what is your moderation duty?

✓ Hold your space to the conduct standard, handle routine exceptions, and escalate what’s beyond you — under callsign, logged. — Jump: End of lesson · Score: 1
✗ Nothing — moderation is entirely automated. — Jump: this page · Score: 0
✗ Police the whole platform, not just your space. — Jump: this page · Score: 0

Lesson 2.2 — Substance, Not Volume

Content page · “Substance, Not Volume”

This is the one norm to take to heart. Organizing earns you visibility, and a genuinely useful contribution can even become a Climb exemplar (Section 3). That tempts people to manufacture activity — run ten thin sessions, spin up empty spaces — to look busy. It doesn’t work, and it isn’t what’s wanted. The community values substance: one study group that actually helps people beats ten that don’t. Operators vouch for work that mattered, not for a tally. Create a space because there’s a real need, steward it because people use it, and don’t litter the commons with dead rooms.

Button: Verify The Norm → next page

Question page (Multiple choice) · “Verify: The Norm”

Does running many thin sessions advance you?

✓ No — substance counts, not volume; one contribution that helps people beats a large tally. — Jump: End of lesson · Score: 1
✗ Yes — the more sessions you run, the higher you rank. — Jump: this page · Score: 0
✗ Yes — empty spaces still count toward your record. — Jump: this page · Score: 0

Lesson 2.3 — The Life of a Space

Content page · “The Life of a Space”

Community spaces are born and retired by members — that’s the freedom of the member-organized tier (Commons SOP §7A). With it comes a duty: create with a clear purpose, keep the space active while it serves one, and archive it when it’s done. A dormant space isn’t a monument; it’s clutter that makes the commons harder to navigate. Retiring a finished space is good organizing, not failure.

Button: Verify The Lifecycle → next page

Question page (Multiple choice) · “Verify: The Lifecycle”

What do you do with a space whose purpose is finished?

✓ Archive or retire it — don’t leave dead rooms cluttering the commons. — Jump: End of lesson · Score: 1
✗ Leave it open forever as a record of your work. — Jump: this page · Score: 0
✗ Hand it to an operator, who must keep it running. — Jump: this page · Score: 0

Section 3 — Why Organize, and Getting Started

Lesson 3.1 — Two Reasons to Organize

Content page · “Two Reasons to Organize”

People organize for two reasons, and both are valid:

For the community itself. Building places where members learn and meet is a complete, respected way to take part. Many organizers never climb, and that is a full life in the Commons.
For visibility toward the Climb. Organizing puts your real work in front of the operators who recruit. For a Permit-holder waiting on a cohort window, it’s the productive answer to the wait — it’s how your work gets seen and nominated (WiseNxt SOP §3). But — as in Lesson 2.2 — it earns visibility, not a seat: only a wanted, durable improvement becomes an exemplar, judged at the same bar as any other work.

Organize because it’s useful; the visibility follows.

Button: Verify Why Organize → next page

Question page (Multiple choice) · “Verify: Why Organize”

Organizing toward the Climb gives you:

✓ Visibility — your work gets seen and nominated; only substantial, wanted work becomes an exemplar, never a guaranteed seat. — Jump: End of lesson · Score: 1
✗ A reserved seat in the next Range cohort. — Jump: this page · Score: 0
✗ Automatic certified standing. — Jump: this page · Score: 0

Lesson 3.2 — Your First Space

Content page · “Your First Space”

When you pass, you’ll land in the Community Organizers space — your back-office, where organizers coordinate, hand off recurring programs, and surface their work. To start a space: create it (a community space, scoped to members), give it a clear name and purpose, set who can join, and seed it with a first session or post so it opens with life in it. Keep it healthy, and retire it when it’s served its purpose. That’s the whole job.

Button: Complete the Organizer Course → next page

Question page (Multiple choice) · “Verify: Getting Started”

Where do organizers coordinate, and how should a new space open?

✓ In the Community Organizers space; open a new space with a clear purpose and some seeded activity. — Jump: End of lesson · Score: 1
✗ Anywhere on the platform; an empty space is fine to leave. — Jump: this page · Score: 0
✗ In the product working spaces, after earning the Permit. — Jump: this page · Score: 0

END OF DOCUMENT