Skip to main content

Community operators

The operator catalogue is the framework's type system, so it can't be edited on a whim — an operator that quietly changes meaning would break every result that depends on it. But it also can't be frozen, or the framework stops growing. Community operators resolve that with a staking-vote process: the catalogue grows by a procedure everyone can see, not by fiat.

The lifecycle​

1 · Propose

Anyone submits a candidate operator — into a shared staging area or their own tenant.

2 · Open the vote

The author opens a vote window on the proposal.

3 · Stake

Voters stake a credit envelope for or against — and the stake is locked for the window, so a vote costs something to cast.

4 · Resolve

At close, the stakes are tallied and every stake is refunded — voting has skin in the game without being a fee.

Promotion is a human gate​

Passing the vote doesn't silently rewrite the canonical registry. Promotion into the framework's official catalogue is a separate, human-reviewed gate — the community's staking vote is a strong signal, but a person stands between an accepted proposal and the type system every result relies on. Until then, a proposed operator is exactly what the hypothesis stamp says a generated equation is: a candidate, not accepted physics.

Why stake-to-vote​

Locking a stake to vote — and refunding it at resolution — is a deliberate design. It makes a vote cost attention without costing money: you can't spam approval for free, but you're not charged for participating honestly. Combined with the human promotion gate, it lets the catalogue grow from the community while keeping the bar for canonical high — the same balance of openness and rigour the rest of the framework strikes.

  • Operators — the catalogue this process grows.
  • Equation study — the hypothesis stamp a proposal wears until promoted.
  • The economy — the credits a stake is made in.