You did the work. It compiled to 255. Now list it in the SHOP. Your governance becomes a product.
The SHOP
Every governed scope that compiles to 255 is a potential product. The SHOP is where governance output meets governance demand. Authors list products — books, papers, tools, services — with prices denominated in COIN. Readers buy products. COIN circulates. The economy turns.
The SHOP is not a marketplace in the traditional sense. There is no haggling. There is no dynamic pricing. There are no algorithms adjusting prices based on demand signals. The price is set by the author based on the governance tier the product serves. The price is a governance declaration, not a market negotiation.
SHOP.md
Every domain that sells products has a SHOP.md file. It is a structured Markdown file that lists products as Cards:
## Card
| Field | Value |
|-------|-------|
| title | Governance as Compilation |
| type | PAPER |
| price | 35 COIN |
| status | AVAILABLE |
| synopsis | Source files in, 255-bit score out. The audit is obsolete. |
| route | /PAPERS/GOVERNANCE-AS-COMPILATION/ |
Each Card is a product listing. The fields are defined:
- title — What the product is called.
- type — What kind of product it is (BOOK, PAPER, content, service).
- price — How many COIN it costs. Set by governance tier.
- status — AVAILABLE (can be purchased) or IN PROGRESS (not yet ready).
- synopsis — One or two sentences describing the product.
- route — Where the product lives in the governance tree.
SHOP.md inherits from its parent scope. The inherits: line at the top declares the governance chain. The SHOP itself is a governed artifact — it compiles to a score, and that score determines whether the SHOP is valid.
Pricing by Tier
Products are priced by the governance tier of their target audience:
| Tier | COIN | Audience | Reasoning |
|---|---|---|---|
| COMMUNITY | 0-35 | Everyone | Free or near-free. Lead generation. Blogs, open resources. |
| ENTERPRISE | 63 | Business | Enterprise-grade attestation. Deal frameworks, business cases. |
| AGENT | 127 | Devs + Govs | Agent-tier attestation. Manuals, theory, professional tools. |
| FULL | 255 | General public | Full attestation. Major works, memorials, flagship content. |
The tier is not a quality judgment. A 35 COIN paper is not “worse” than a 255 COIN book. The tier reflects the audience and the attestation level. A research paper at 35 COIN is accessible to the widest audience (COMMUNITY). A flagship book at 255 COIN represents the highest level of attestation a reader can make.
The Checkout
When a reader buys a product, the checkout is a SPEND event:
- Reader selects product. Price displayed in COIN.
- System checks reader’s WALLET balance. If sufficient, proceed.
- SPEND event created: reader debited, author credited. Both hash-chained.
- Product access granted.
For readers who prefer fiat, Stripe integration is available. The reader pays in dollars. The dollars convert to COIN at the exchange rate. The COIN enters the economy through a MINT event. The author receives COIN, not dollars. The economy stays in COIN. The fiat is the on-ramp, not the currency.
COST_BASIS
Every product has a cost basis:
cost_basis(product) = SUM(MINT:WORK.amount)
WHERE work_ref matches the product's governance scopes
The cost basis is the total COIN minted by the governance work that produced the product. A book with 20 chapters, each brought from 0 to 255, has a cost basis of 20 x 255 = 5,100 COIN. That is the governance investment. The SHOP price (say, 127 COIN per copy) is the per-reader attestation cost.
The cost basis is not hidden. It is derivable from the LEDGER. Any user can trace the governance history of a product and compute its cost basis independently. Transparency is not a feature. It is a consequence of the architecture.
Listing Your Work
Here is how you list your governance work in the SHOP:
Step 1: Compile to 255. Your scope must validate to full compliance before it can be listed as AVAILABLE. IN PROGRESS products can be listed (pre-orders, essentially), but they cannot be purchased until the status changes.
Step 2: Create or update SHOP.md. Add a Card with the required fields. Set the price based on your target audience’s governance tier.
Step 3: Commit. The SHOP.md change is a governance commit. If it improves the scope’s governance score, COIN is minted. Listing your work in the SHOP is itself governance work.
Step 4: Receive attestations. When readers purchase your product, SPEND events credit your WALLET. Each purchase is a reader attesting to the value of your work.
What Can Be a Product
Anything that lives in a governed scope and compiles to 255:
- Books — Multi-chapter works. Each chapter is a governed scope. The book is the parent scope.
- Papers — Research publications. Single-scope products with TOC, abstract, appendices.
- Blog posts — Short-form content. Priced at 0 COIN (free lead generation) or at COMMUNITY tier.
- Services — Software tools, APIs, integrations. The governance files describe the service. The service itself is the product.
- Templates — Governance scaffolds. A TRIAD template that others can fork and govern.
The common requirement is governance. If it compiles to 255, it can be a product. If it does not compile, it is not ready.
The Loop
Writing governance mints COIN (you earn from the work). Listing in the SHOP makes your work purchasable (readers can attest). Readers buy with COIN (your WALLET grows). Readers become governors (they do work, mint COIN, list their own products). The SHOP grows. The economy grows. The governance surface grows.
Your work is not a cost center. Your work is a product. The SHOP is where governance becomes commerce. The COIN is the proof that both are the same thing.
List your work. Let the attestations flow.
Figures
| Context | Type | Data |
|---|---|---|
| post | gauge | value: 4, max: 4, label: PRODUCT TYPES |
| *SHOP: Your Work for Sale | ONBOARDING | BLOGS* |