Plugins, built in.

First-party plugins, built into the database and the theme — not bolted on top.

1. 01

   The Council

   Shipped

   Proposals, votes, dissent log. For governance-driven communities — co-ops, DAOs, parent committees, employee-owned shops. Roles gate who can propose, who can vote, and who can read the dissent log. The whole shape of how the community runs, built into the forum.

2. 02

   Chronicle

   Coming Q3

   Campaign log for roleplay groups and session-based communities. Session archives, character roster, recurring NPC index. The DM's notebook, made shareable. Pairs with the Chronicle layout.

3. 03

   Library

   Coming Q3

   Book-shelf layout for writing circles and reading groups. Reading challenges, shelf art, per-book threads. Each "book" is a long-running discussion with structure the platform understands.

4. 04

   Atelier

   Coming Q3

   Critique queues for art and writing communities. Crit cards (structured response forms), work-in-progress threads, queue management for who's reviewing what. Anti-spray feedback, built in.

5. 05

   The Workshop

   Coming Q4

   Build logs for maker and homestead communities. Materials shelf, before-and-after threads, project state (planning / in-progress / shipped). Less Pinterest, more shop notebook.

6. 06

   Paid Membership

   V4.2

   Stripe Connect, gated categories, subscription-linked roles. Members pay you, you pay us a percentage. The whole loop runs inside the forum — no external memberships site, no second auth.

1. 01Each suite ships a manifest declaring every face up front — no implicit surfaces appearing after install.
2. 02At boot, the loader registers the suite with the runtime; downstream code reads from one source of truth.
3. 03Per-suite data lives in ext_<id>_* tables. Cross-suite reads are forbidden — integrations happen through the event bus.
4. 04Toggling a suite off hides its faces but preserves its data. Re-enable later and the state is intact.
5. 05Suites inherit the theme tokens automatically — no per-plugin colour configuration, no off-brand UI.

• First-party only today

  No third-party marketplace. The trade-off is depth: every suite shares the database, auth, and theme — none of which is true of OAuth-bolted plugins. An open SDK is on the V4.3+ horizon; not promised, not denied.

• Suite data isn't fungible

  You can't migrate from The Council to a generic-poll suite without losing the dissent-log structure. Suites are deep, which means committing to their shape.

• Some suites are Maker-tier-locked

  The Council ships free on Hobby+. Paid Membership and Atelier require Maker (the tier × suite matrix lives on /pricing). You don't pay for shape you don't use.