2026-02-23-YOUR-FIRST-255

Your First 255

You just signed up. You have 500 COIN. Here is how to make your first scope compile to 255.

The Number

255 is not a grade. It is not a percentage. It is not a score on a curve. 255 is the maximum value of an 8-bit unsigned integer — the state in which all eight governance dimensions are satisfied simultaneously. When your scope scores 255, it has compiled. When it scores less than 255, it has not.

Think of it as a compiler. Your code either compiles or it does not. There is no “mostly compiles.” There is no “compiles with warnings we can ignore.” 255 is compiled. Everything else is not.

The Three Files

Every governed scope starts with three files. We call them the TRIAD:

CANON.md — Your declaration. It contains exactly one thing: your axiom. The axiom is the single assertion from which everything else derives. “This scope publishes research papers.” “This scope governs the frontend.” “This scope is a memorial.” One sentence. The axiom is the seed.

VOCAB.md — Your language. It defines the terms you use. If you use a word that is not in VOCAB.md, it is undefined — a type error. VOCAB.md forces precision. You cannot govern what you cannot name.

README.md — Your interface. It tells the world what your scope does, how to use it, and what it exposes. README.md is the contract between your scope and everyone else.

Create these three files. Commit. Run magic validate. Your score will jump from 0 to approximately 35. That is the COMMUNITY tier — the minimum viable governance. You exist. You have declared yourself. The compiler sees you.

Climbing

35 is not 255. You have seven more dimensions to satisfy. Here is the path:

Add COVERAGE.md. Answer eight questions about your scope: What does it declare? What evidence exists? What is its history? Who uses it? What does it practice? How is it structured? What has it learned? What language does it use? Each answered question lights up a dimension. Each lit dimension adds bits to your score.

Add LEARNING.md. Record what you discovered while governing. Patterns, insights, corrections, and EVOLUTION signals — epoch transitions that mark when your scope changed direction. LEARNING.md is the scope’s memory: accumulated intelligence plus governance history in one file.

Add ROADMAP.md. Declare where your scope is going. What is the next milestone? What is unresolved? ROADMAP.md is the forward-looking complement to LEARNING.md’s backward-looking record.

Fill in references. Link to your parent scope. Link to your peers. Cite your sources. References are the lateral connections that prove your scope does not exist in isolation.

Each addition is a commit. Each commit computes a gradient — the difference between your old score and your new score. Each positive gradient mints COIN.

The Gradient

This is the part that surprises new users. You do not just reach 255 and then get rewarded. You get rewarded at every step.

Going from 0 to 35? That is 35 COIN minted to your WALLET. Going from 35 to 127? That is 92 COIN minted. Going from 127 to 224? That is 97 COIN minted. Going from 224 to 255? That is 31 COIN minted.

Total: 255 COIN. Exactly the maximum score. The governance work invested in a scope is valued at exactly the score it achieves. Not more. Not less.

The gradient is the key. Only improvement mints. Staying at 255 mints zero — there is nothing to improve. Going backward costs COIN through DEBIT:DRIFT. The economic signal is immediate: build up governance, earn COIN. Tear it down, lose COIN.

Your First Day

Here is what your first day looks like:

  1. Create a scope directory.
  2. Write CANON.md with one axiom.
  3. Write VOCAB.md with your key terms.
  4. Write README.md describing what the scope does.
  5. Commit. Run magic validate. Score: ~35. MINT:WORK: ~35 COIN.
  6. Add COVERAGE.md. Answer the eight questions.
  7. Commit. Run magic validate. Score: ~127. MINT:WORK: ~92 COIN.
  8. Add LEARNING.md and ROADMAP.md.
  9. Commit. Run magic validate. Score: ~224. MINT:WORK: ~97 COIN.
  10. Final pass — verify references, complete vocabulary, check structure.
  11. Commit. Run magic validate. Score: 255. MINT:WORK: ~31 COIN.

You started the day with 500 COIN from signup. You end the day with 500 + 255 = 755 COIN. You have a fully governed scope. You have a WALLET with a balance. You have a LEDGER record proving every gradient.

Your first 255. The compiler says yes.

Figures

Context Type Data
post pipeline steps: Write CANON → Write VOCAB → Write README → Validate → 255
*Your First 255 ONBOARDING BLOGS*