"A community of builders sharing structured knowledge with the world.
"
That Is the Public Page
It is four short paragraphs, three numbered steps and a button that goes to the registration form. Eighty lines of static markup, no data fetching, no application form. What follows is the same feature described from the code, which is a different and more specific thing.
It Is a Role, Not a Signup
There is no self-serve path into the collective. The CREATOR role arrives exactly one way: an admin mints a registration ticket of type CREATOR, someone registers with that code, and the ticket grants the role along with a label reading Creator. The public page says join the collective. The code says you are invited or you are not. Both are true statements about different parts of the system, and only one of them is enforced.
CREATOR_CODE_PATTERN = ^[A-Z0-9]{4}-[A-Z0-9]{4}-[A-Z0-9]{4}-[A-Z0-9]{4}$
FOLLOWER_CODE_PATTERN = ^[A-Z0-9]+$
Two Codes, One Derived From the Other
A creator code is four groups of four. The moment one is consumed, the system mints a second ticket for that creator's followers, and it names it by concatenating the username in uppercase with the current year. A creator called steph gets STEPH2026 without being asked. The follower ticket inherits the creator ticket's shop discounts, and it hands out two automatic labels built from the same username: one ending in 4Ever and one ending in FanClub.
That naming is a joke that shipped. It is still there, it still fires on every creator activation, and nobody has asked for it to be removed.
What a Follower Ticket Carries
Labels, which are cosmetic and attach to a profile. Shop items, granted outright. And shop item discounts, each stamped with the creator's identifier. That last stamp is the load-bearing one: it is what turns a discount into a commission months later.
How a Commission Is Actually Earned
Follow the chain. A creator issues a code. A follower registers with it, which writes a discount row carrying both the item and the creator. The follower later buys that specific item at that discount. Only then does a commission row get written, at fifty percent of what was actually paid. Not on registration, not on the code being used, not on any other item. One code, one item, one purchase, one row.
Commission rate
50%
Minimum cashout
100 dollars
SC to the dollar
1,000
Follower labels editable
5 max, 2 auto
Payout screens built
0
The Discount Cuts Both Ways
Commission is taken from the discounted price, not the list price. A creator who gives away fifty percent halves their own cut, and a hundred percent code earns them nothing at all. This is arithmetically obvious once stated and it is stated nowhere in the product. A creator setting a generous discount is quietly choosing to be paid less, and finding that out from a dashboard is the wrong way to find it out.
The Dashboard
It appears as a tab on your own profile, only if you hold the role. Three sections: a performance chart with impressions over today, seven days, thirty days or all time; a commissions block with two numbers; and a code manager where you can rename your code and edit up to five follower labels. Renaming the code carries a warning that the old one stops working, because it does.
What Exists Behind the Two Numbers
Commission rows written on qualifying purchases
Balance and history endpoints, creator scoped
Payout request, approve, reject and mark-paid endpoints
Four payout statuses: pending, approved, rejected, paid
Any frontend for requesting a payout
Any deduction from the balance once a payout is marked paid
The monthly payout schedule the home page advertises
The Settlement Gap
The balance is computed as the sum of every commission row ever written for that creator. Marking a payout as paid does not consume, flag or offset a single row. So the balance after a payout is identical to the balance before it, and the only thing preventing an immediate second request is a check for a pending one, which stops applying the moment the first request is approved. The accounting is sound and the settlement half was never built. Nobody has hit this, because there is no interface to hit it with.
A Second Path That Never Fires
A redeem code carries a flag called enableCommission, and the follower-ticket code sets it to true. There is a method to award a commission from a redeem code. Nothing calls it. The commission source enum has two values and one of them is unreachable. It is not broken so much as unfinished in a way that looks finished from the enum.
The Onboarding It Launched With
The collective shipped alongside an onboarding rework, and that rework is not a state machine. There are no step enums anywhere. It is a small config table holding a welcome message, a how-to title and body, and a list of recommended slate ids, resolved from whichever registration ticket you arrived on. The frontend assembles the pages from that config at runtime, adding a Creator Collective page and a Welcome Gift page only when the account holds the role. Three configs are seeded: a default one, a travel one, and one for personal link pages.
"Slatesource is built to be a Porsche that can go up a mountain.
"Steph19th of July 2026
That line is not marketing copy written for this page. It sits in the seeded onboarding how-to body in the database, and it has been there since the onboarding table was created. The wording shifts between configs: the travel config says climb a mountain rather than go up one.
