How It All Works

Every Subsystem. Three Depths.

22 core concepts of the cooperative substrate - from a one-breath summary to full mechanical detail. Shared by members who get it. Verifiable on the blockchain of receipts.

Full Interactive Version See the Proofs

#%!d(float64=01) · Denken

Ingest Pipeline + Soccerball / SID

technicalprovenanceip

You drop something in. The platform catches it, stamps it, and knows it forever.

Every piece of content that enters Liana Banyan gets a permanent, unforgeable ID the moment it arrives. That ID is how the platform keeps track of 2,270 innovations and counting.

Denken: "Think of a postal sorting facility. The second your letter hits the conveyor, a barcode goes on the envelope. From that moment on, the whole system knows exactly where it is and who it came from."

Soccerball assigns a permanent SID to every incoming asset -- the root of all provenance.

The Ingest Pipeline is the front door of the platform. When a creator submits content -- code, writing, art, a business plan -- Soccerball (the intake service) immediately assigns a Soccerball ID (SID). The SID is a UUID that travels with that asset forever through the Pearl chain, the IP Ledger, and the Substrate DAG. Without the SID, nothing can be traced, credited, or compensated correctly. The ingest step is why 2,270 innovations stay accountable to their creators.

Denken: "The Ingest Pipeline is the moment the cooperative makes a promise. 'We received this. We know who sent it. We will remember.' Every Crown Jewel and every provisional patent in the 228 + 21 catalog starts here."

Full pipeline: content arrives, SID assigned, Chronos-stamped, SkipEblet created, Pearl chain linked.

Step 1: Content arrives at the Soccerball endpoint (HTTP or internal queue). Step 2: Soccerball generates a UUID-v4 SID and persists it to the Substrate DAG as a new node with creator metadata. Step 3: A ChronosTag (opaque composite of wall-clock + sequence counter + signer hash) is attached via chronos-schema.ts. Step 4: A SkipEblet is created in lib/skip-eblets/ -- the minimal pane unit that holds the SID, ChronosTag, and provenance hash from hashEtching(). Step 5: The SkipEblet is linked into the Pearl chain for that creator. Step 6: The IP Ledger entry is written. Step 7: The SkipEblet becomes renderable via isPaneVisuallyRenderable(). Chain propagation is managed by SkipEbletChainManager.propagateBorrowChain().

Rabbit: "Seven steps, one guaranteed ID, zero gaps in the chain. The moment content hits the ingest endpoint, the cooperative's debt to that creator begins. Everything downstream -- payouts, attribution, provenance -- runs on the SID. No SID, no chain. No chain, no credit."

Paper coming soon Proof pending

#%!d(float64=02) · LRH

Pearl / Eblet / SSPS

technicalprovenanceipcontent

A Pearl is the smallest thing that matters. Chain them and you get something unbreakable.

Pearls are the atomic units of content on the platform. Every contribution, vote, and transaction is a Pearl. String them together into Eblets and you get something that can be displayed, sold, or certified.

Lrh: "You've seen how real pearls form -- one grain of sand, then layer after layer wraps around it until it's precious. Same idea here. One small authentic contribution, wrapped in context and proof, becomes something the platform can stand behind."

Pearl = immutable content atom. Eblet = displayable unit with context. SSPS = the proof-of-origin stamp.

A Pearl is the raw, immutable hash of a contribution -- it cannot be changed after creation. An Eblet wraps a Pearl with display metadata: title, thumbnail, creator name, ChronosTag, and the SID from ingest. SSPS (Soccerball Single-Point-of-Socceri) is the certificate that links a Pearl to exactly one creator with one timestamp -- the thing that makes a Crown Jewel out of an ordinary contribution. 228 contributions have been designated Crown Jewels; each has an SSPS certificate.

Lrh: "The difference between a Pearl and an Eblet is the difference between a raw gem and a setting. The gem is proof. The setting is presentation. You need both -- one for the ledger, one for the world to see."

Data model: Pearl (hash + SID), Eblet (Pearl + metadata), SSPS (creator-bound certificate).

Pearl: immutable SHA-256 hash of content blob + SID + Chronos stamp. Stored as a DAG node in the Substrate. Once written, never mutated -- only a new Pearl can supersede it. Eblet: wraps a Pearl reference with displayable metadata (title, description, thumbnailUrl, creatorId, chainPosition). The Eblet is what UI components render. SSPS: generated by Soccerball at ingest time. Contains: Pearl hash, creator UUID, ingest timestamp (ChronosTag), platform signature. The SSPS is what proves a Crown Jewel belongs to its creator. Without it, attribution is asserted but unproven. With it, attribution is cryptographically stamped. The provenance drift check (detectEtchingDrift in provenance.ts) alerts if a Pearl's hash diverges from its SSPS record.

Rabbit: "Pearl is truth. Eblet is presentation. SSPS is proof. Three layers, one unbreakable chain from creator to consumer. The platform's 228 Crown Jewels all have SSPS certificates. The 21 provisionals are pending that final stamp."

Paper coming soon Proof pending

#%!d(float64=03) · Denken

Substrate / DAG

technicalprovenancearchitecture

The floor everything stands on. You can't see it, but it's why nothing falls.

The Substrate is the directed acyclic graph underneath every relationship in the platform. Every Pearl, vote, affiliation, and transaction is a node. Every connection between them is an edge. It's what makes provenance traceable and attribution permanent.

Denken: "The Substrate is like the rebar inside concrete. You never see it. But if it weren't there, the whole structure would collapse the first time any real weight was put on it."

A directed acyclic graph where nodes are Pearls and edges are relationships -- authored-by, derived-from, voted-on.

The Substrate DAG records every meaningful relationship between platform objects. Nodes include Pearls, Eblets, member profiles, Marks transactions, and governance events. Edges encode the type of relationship: authored-by (creator to Pearl), derived-from (remix chain), voted-on (member to Pudding), transacted (Credits/Marks flow). Because it is a DAG (no cycles), you can always trace any contribution back to its origin without loops. The Substrate is the ground truth that the IP Ledger, Furnace, and Medallion System all read from.

Denken: "When someone asks 'who made this?' or 'where did this idea come from?' -- the Substrate answers. It is the cooperative's long memory, and it cannot be edited. Only appended."

Node types, edge semantics, provenance hashing, and drift detection.

Node types: Pearl (content atom), MemberNode (creator identity), MarksTx (participation transaction), GovEvent (Star Chamber decision). Edge types: AUTHORED_BY, DERIVED_FROM, VOTED_ON, TRANSFERRED_TO, GOVERNED_BY. Each edge carries a ChronosTag. hashEtching() in provenance.ts generates a Merkle-style hash of a node's ancestry. detectEtchingDrift() compares the stored hash to a recomputed hash -- if they diverge, the chain has been tampered with. The SkipEbletChainManager propagates borrow chains across the DAG: when a node is 'borrowed' (embedded in another context), a borrow edge is created and the chain manager tracks it via propagateBorrowChain(). Cross-surface coherence is maintained by CrossSurfaceCoherenceHub in yoke-bridge/cross-surface-coherence.ts.

Rabbit: "The DAG is append-only. You can add nodes and edges. You cannot remove or modify them. That's not a technical limitation -- it's a cooperative promise. The Substrate is why 2,270 innovations can be tracked to their creators decades from now."

Paper coming soon See the proof (verified)

#%!d(float64=04) · Denken

Mesh / Frontier (WAN + LAN)

technicalnetwork-effectsarchitecture

The more nodes, the stronger it gets. Zero to full power is a mathematical certainty.

The Mesh is the cross-node network of the platform. Every new member or initiative that joins increases the total value for everyone already here. That's not marketing -- it's a provable equation.

Denken: "A single telephone is useless. Two telephones are one conversation. A million telephones are a civilization. The Mesh works the same way -- except here, every new node also adds to the shared IP ledger, which means the value compounds faster than a phone network."

LAN = one initiative's local network. WAN = the full cross-initiative cooperative. Frontier = where they meet.

Each initiative on Liana Banyan runs its own Local Area Network (LAN) -- a subset of the Substrate DAG scoped to that initiative's members and content. The Wide Area Network (WAN) is the full platform-wide Substrate. The Frontier is the boundary layer where a LAN's nodes and edges become visible and linkable across the WAN. This matters economically: a contribution that stays in one LAN reaches only that initiative's members. A contribution that crosses the Frontier reaches the full cooperative network of 2,270 innovations and all their connected members.

Denken: "Every initiative starts at zero network connections. The Frontier is the moment they stop being an island. It's why we built 16 initiatives into the platform from day one -- because 16 LANs connected at launch is a very different starting point than 1."

Cross-node network-effect proof: V(N) = N(N-1)/2 + 1. Cross-surface coherence via YokeBridge.

For a cooperative with N authenticated peer nodes, the number of unique peer connections is N(N-1)/2. Total value V(N) = connections + baseline = N(N-1)/2 + 1. At N=1: V=1. At N=2: V=2. At N=10: V=46. At N=100: V=4,951. At N=2,270 (current innovation count): V=2,575,766. This is not hypothetical -- it is the mathematical basis of the Substrace Theorem. The YokeBridge (cross-surface-coherence.ts) maintains coherence between LANs as nodes cross the Frontier. CrossSurfaceCoherenceHub tracks active cross-surface sessions. The Yoke handoff (yoke-handoff.ts) serializes the state anchor as JSON when a node moves from one surface to another. This ensures the DAG edge is written atomically -- no partial crosses.

Rabbit: "N(N-1)/2 + 1. That's the whole proof in one line. The Mesh doesn't just add value linearly. It multiplies it. And the YokeBridge is what makes that math hold even when members are crossing surfaces at the same time."

Paper coming soon See the proof (verified)

#%!d(float64=05) · LRH

Cue Cards (Deck Cue Cards)

learningonboardingcommunity

Little cards that teach you one thing at a time. Collect them all and you know the whole platform.

Cue Cards are bite-sized learning units -- each one covers exactly one system, one rule, or one concept. You earn them by exploring. They stack into a Deck that becomes a personal knowledge library.

Lrh: "You know how a recipe card is better than a cookbook for learning to cook? You hold it in your hand, you follow the steps, and you put it in the box when you're done. Cue Cards are that -- one thing at a time, hands-on, yours to keep."

Each card covers one concept, has a front (metaphor) and back (mechanic), and earns Golden Keys when completed.

Cue Cards are organized by domain: economic laws, governance rules, social mechanics, creative tools, and history. Each card has a front face (the metaphor -- the simple image that sticks) and a back face (the mechanic -- the actual system behavior). Completing a card earns Golden Keys (5 keys per card as a default). Keys accumulate and unlock Magic Carpet rides through the platform via Wildfire Beacon Runs. The Deck is your personal collection -- it grows as you learn.

Lrh: "The Deck is how you prove to yourself -- not to us, to yourself -- that you understand the cooperative. When you've worked through the economic laws cards and the governance cards, you'll have enough context to vote, to invest, and to recruit confidently."

Data model, domain categories, Golden Key rewards, and Deck serialization.

Cue Card data is in platform/src/data/ (economicLawsCueCards.ts, shadowMarksCueCards.ts, letterCueCards.ts, openWaterCueCards.ts, guildRecruitingCards.ts, questDeckCards.ts). Each card has: id (UUID), front (headline + metaphor), back (mechanic + proof), domain (economics | governance | social | craft | history), goldenKeysReward (default 5), earnedByRoute (which route triggers completion). The Deck is serialized per-member in Supabase. WildfireBeaconRun nodes with learningLink fields award keys when the member completes the linked card. Cards with innovationNumber fields cross-reference the 2,270-innovation patent catalog.

Fox: "The front is metaphor. The back is proof. That sequence is intentional -- if you can't hold the metaphor, the proof won't stick. We designed cards so that a member can learn the 83.3% split with a single card, hold it in memory, and never need to look it up again."

Paper coming soon Proof pending

#%!d(float64=06) · LRH

Puddings

communitycurationmarkseconomics

If someone makes something beautiful, the crowd proves it by putting their name on it.

A Pudding is a collective taste-test. Members stake Marks on content they believe is worth everyone's attention. When enough people agree, the content surfaces platform-wide.

Lrh: "The proof is in the pudding. Not my opinion. Not an algorithm's opinion. The members'. When enough people say 'this is worth sharing,' the platform takes that seriously and makes it visible."

Members stake Marks to surface content. Threshold reached = platform-wide visibility + creator attribution.

The Pudding system is how quality surfaces without editorial gatekeeping or algorithmic optimization. Any member can stake Marks (participation tokens -- not equity, not financial instruments) on a piece of content. When the stake total crosses the threshold, the content rises to platform-wide feed. The original creator gets full attribution and an XP boost. Members who staked early get reputation credit. Puddings are the cooperative version of trending -- driven by members who have skin in the game, not anonymous upvotes or engagement bait.

Lrh: "The name stuck from early prototyping. Pudding is the thing you make to prove you can cook. The collective Pudding is the thing the platform makes to prove it can curate without selling out."

Marks staking mechanics, threshold calculation, surface algorithm, and attribution flow.

Pudding flow: Member sees content with 'stake Marks' option. Member stakes 1-100 Marks. Marks are locked (not transferred) for the staking period. Threshold formula: T = BaseThreshold + (ContentAge * DecayFactor). BaseThreshold = 100 Marks by default; configurable per initiative. When total stakes >= T: content is added to the platform-wide feed for 48 hours. Creator receives XP delta (based on total stakes and stake duration). Early stakers (first 20% of stakers) receive ReputationBoost = stakes / total_stakes * BoostMultiplier. Marks are returned to stakers after surface period (win or loss). The Pudding record is written to the Substrate DAG as a VOTED_ON edge. No Marks are destroyed or redistributed -- only locked temporarily. This is what makes Marks participation tokens rather than equity -- they return to the staker.

Rabbit: "Marks return to stakers. That's the key. This is not a financial transaction. It is a vote expressed in locked attention. The platform reads the total locked attention as a quality signal. No money changes hands. No equity is issued. The members just said: 'this is worth everyone's time.'"

Paper coming soon Proof pending

#%!d(float64=07) · LRH

Medallion System

communityphysicaleconomicsproof-of-participation

Coasters become business cards. Business cards become proof that the work was done.

The Medallion System is a tiered physical artifact program. Plain coasters represent open membership. Tereno business cards represent $5/year commitment. Initiative-stamped cards represent earned affiliation. Named pearl eb5bdeeeea118734.

Lrh: "A coaster is just a coaster until someone earns the right to turn it into a business card. A business card is just cardboard until it carries the stamp of an initiative that required something real to earn."

Three tiers: Coaster (open), Tereno (member), Initiative stamp (earned). Physical artifacts, real-world proof.

The Medallion tiers are: Tier 1 - Coaster (plain, any member, free to print). Tier 2 - Tereno business card (member with active $5/year membership, printed by platform). Tier 3 - Initiative-stamped card (16 varieties, one per initiative, earned by meeting the initiative's contribution threshold). Physical medallions are produced at Cost+20% -- the platform does not mark up above that. The medallion acts as an offline proof-of-participation: someone can look at your Initiative card and know you met the threshold without needing to log in.

Lrh: "We wanted something you could hand someone in a coffee shop. Something that told the whole story without requiring them to create an account first. The Medallion is that thing."

Production cost model, Cost+20% floor, tier eligibility logic, QR verification.

Medallion production costs: Coaster = $0.15/unit (DIY printable, no platform cost). Tereno card = $0.85/unit base print + $0.17 (Cost+20%) = $1.02 minimum. Initiative stamp card = $1.10/unit base + $0.22 (Cost+20%) = $1.32 minimum. The QR code on each Tier 2/3 medallion links to a MedallionQRVerification endpoint that checks: member UUID, membership active status, initiative threshold cleared (for Tier 3). Eligibility logic: Tier 3 requires a minimum of one completed deliverable in the initiative's IP Ledger, one Pudding stake above 10 Marks, and active membership. Data sources: MedallionPage.tsx, MedallionMintingManager, MedallionProductionTracker. The 16 Initiative stamps correspond to the 16 initiatives in the Medallion System pearl eb5bdeeeea118734.

Pig: "Cost+20% is not negotiable. $1.00 in production cost = $1.20 minimum price. Always. The platform does not profit from physical goods beyond that 20-cent floor, and that 20 cents covers fulfillment overhead. This is what makes the cooperative different from a merch store."

Paper coming soon Proof pending

#%!d(float64=08) · Denken

Battery Dispatch + Broadcast Schedule

technicalpublishingscheduling

Content doesn't all go out at once. The Battery decides who gets the spotlight and when.

The Battery is a time-managed content queue. When approved content is ready to publish, it enters the Battery and gets dispatched on the Broadcast Schedule at staggered intervals. No feed flooding.

Denken: "A battery doesn't release all its energy at once -- it releases it steadily, in the right amount, at the right time. That's the job. Every piece of content deserves its moment, not a fight to survive a 6am avalanche of simultaneous posts."

Battery holds approved content. Schedule dispatches it at staggered 24-hour intervals by initiative and type.

The Battery Dispatch system solves the feed quality problem that plagues algorithmic social platforms: if every creator publishes at the same peak time, most content gets buried. The Battery holds all approved, ready-to-publish content in a queue. The Broadcast Schedule assigns each piece a dispatch window based on content type, initiative, creator tier, and historical performance windows. Initiative content gets priority slots. Member content gets fair slots. Content posted by members with active Pudding stakes gets a slight window preference. No content is artificially demoted -- it is sequenced, not buried.

Denken: "We built the Battery because we watched what happens to creators on every other platform. They spend half their energy optimizing their post time instead of making better work. We took that problem off the table."

Queue architecture, dispatch timing algorithm, initiative slot allocation, and schedule surface.

Battery architecture: content enters the queue when: (a) Pudding threshold is met OR (b) creator manually publishes. Queue structure: PriorityQueue sorted by (InitiativeWeight * 0.4 + CreatorTier * 0.3 + ContentAge * 0.2 + RandomJitter * 0.1). InitiativeWeight = initiative's current active-member count / total platform members. CreatorTier = hologramTier from mascots.ts domain (Tier 4 = highest). Dispatch window: 4 slots/hour, 96 slots/day. Slots assigned at ingest time. If a slot conflicts, RandomJitter resolves it. Schedule surface: /broadcast-schedule shows the next 48 hours of planned dispatches (public page). SkipEblets carry the dispatch ChronosTag so the Substrate records when content was broadcast, not just when it was created.

Rabbit: "PriorityQueue with four weighted inputs, 96 slots a day, RandomJitter for fairness. The Battery is a scheduling problem that has been solved elegantly. The result: every piece of content that enters the queue gets dispatched within 48 hours. Guaranteed."

Paper coming soon Proof pending

#%!d(float64=09) · Denken

Furnace (XP-for-Reputation Anonymous Data Furnace-Mode)

technicalprivacyreputationeconomics

Raw activity goes in. Reputation comes out. Nobody can see what's cooking.

The Furnace converts your participation (views, completions, votes, contributions) into XP. XP builds your Reputation score. The underlying behavioral data stays anonymous -- the Furnace only reveals the output.

Denken: "A furnace takes ore -- raw, jagged, not yet useful -- and outputs something refined and usable. What went in stays private. What comes out is the number on your reputation profile."

Privacy-preserving XP engine: anonymized behavioral signals in, XP delta out, Reputation score updated.

The Furnace is the platform's privacy-respecting reputation engine. When you complete a Wildfire run, vote in a Pudding, or deliver a bounty, the Furnace receives anonymized signals (content-type, completion status, duration bucket) -- never your specific viewing history or personal identifiers. These signals are weighted by the Furnace's XP table and converted to an XP delta. XP accumulates into your Reputation score. The score is public (it drives trust in marketplace and governance contexts). The raw signals that produced it are not. This is the anonymous data furnace-mode: reputation is proven without surveillance.

Denken: "We built the Furnace because reputation without privacy is a surveillance tool. The Furnace gives you the benefits of a verifiable track record without exposing the details that build it."

Signal types, XP weight table, anonymization pipeline, Reputation score formula.

Signal types (anonymized): CONTENT_COMPLETE (content watched/read to end), CONTRIBUTION_DELIVERED (bounty completed), VOTE_CAST (Pudding or governance), LEARNING_CARD_EARNED (Cue Card completed), TOUR_COMPLETED (Wildfire run finished). Anonymization: signals stripped of user ID, replaced with anonymous session token before entering the Furnace. The Furnace only receives the signal type + content domain + timestamp bucket (hour). XP weight table: CONTRIBUTION_DELIVERED = 50 XP, CONTENT_COMPLETE = 5 XP, TOUR_COMPLETED = 25 XP, VOTE_CAST = 3 XP, LEARNING_CARD_EARNED = 10 XP. XP is accumulated per member. Reputation score = sqrt(TotalXP) * DomainBonus, where DomainBonus = 1.0 for generalist, 1.2 for specialist in initiative's primary domain. Score is recalculated nightly. Furnace-mode cannot be disabled -- all reputation data passes through it.

Rabbit: "Anonymized token in. XP delta out. Reputation score updated nightly. The member never has to choose between building a reputation and protecting their privacy. The Furnace handles that conflict by design, not by policy."

Paper coming soon Proof pending

#%!d(float64=10) · LRH

Shirley Temple (Affiliation Badge System)

communitybadgesproof-of-participationsocial

Your badges are public proof of where you showed up and what you did.

The Shirley Temple system issues affiliation badges when members hit participation thresholds in specific initiatives. Named for the actress-turned-diplomat's famous collection of pins -- each one marking real presence and relationship, not just admiration.

Lrh: "Shirley Temple collected diplomatic pins because she had actually been to those places and done that work. That's what these badges are. Not fan badges. Not follower badges. Presence badges. You were there."

Badges issued when participation threshold met. Public on profile. Visible in X-Ray mode.

The Shirley Temple Affiliation Badge System issues initiative-specific badges to members who meet defined participation thresholds. Badges are distinct from Medallions -- Medallions are physical artifacts; badges are on-platform digital credentials on your profile. A badge for the Harper Guild means you have completed verified writing work there. A badge for JukeBox means you have contributed licensed audio. Badges are public and visible to any member viewing your profile. In X-Ray Goggles mode, badges are surfaced with their threshold requirements so any member can understand exactly what the badge represents.

Lrh: "We wanted badges to mean something. The only way badges mean something is if they are hard enough to be worth earning and transparent enough for anyone to verify. That's the Shirley Temple design."

Badge eligibility logic, threshold types, Substrate edge, X-Ray integration.

Badge types: AFFILIATION (initiative participation), DELIVERABLE (bounty completion), GOVERNANCE (Star Chamber participation), LEARNING (Cue Card deck completion). Eligibility for AFFILIATION badge: member has at least 1 completed IP Ledger entry for the initiative + at least 1 Pudding stake of 10+ Marks for the initiative + active membership. Threshold is configurable per initiative (set in initiative config, displayed publicly). Badge issuance: when threshold is met, a BADGE_ISSUED event is written to the Substrate DAG as a node with EARNED_BY edge to the member node. Badge is rendered on MemberProfile and in XRayOverlay when data-xray-id='affiliation-badges' is present. X-Ray glossary entry for 'affiliation-badge-[slug]' explains the threshold.

Bear: "A badge is a social signal. It says: 'I was in that room and I contributed.' The Shirley Temple system makes that signal verifiable. Any member can read the X-Ray overlay on your badge and know exactly what you did to earn it. That transparency is what makes it worth earning."

Paper coming soon Proof pending

#%!d(float64=11) · LRH

Switzerland Policy (No Politics, No Religion)

governancepolicycommunitycontent-moderation

Two topics we never touch -- not because we're afraid, but because we protect the table.

The Switzerland Policy is the platform's two hard content exclusions: political content and religious content. Named pearl 403453a4e9526f27. Not because these topics are bad -- but because they reliably destroy cooperative tables and we built ours to last.

Lrh: "Switzerland stayed out of two world wars. Not because the Swiss were cowards -- they have one of the world's strongest military traditions. They stayed out because they understood that their value to the world was in being the place where all sides could still talk. That's us."

Hard exclusion: no political content, no religious content. Enforced by Content Shield. Three-strikes rule.

The Switzerland Policy is not a suggestion. It is a hard content rule enforced by the Content Shield system. Political content = content advocating for specific political parties, candidates, legislation, or partisan positions. Religious content = content promoting, defending, or attacking specific religious beliefs or practices. Informational content that mentions these topics without advocacy is reviewed case by case. The three-strikes rule: first violation = content removed + warning. Second violation = 30-day posting suspension. Third violation = account review by Star Chamber. The policy protects every member by ensuring the cooperative table never becomes a partisan battleground.

Lrh: "We built this platform for people of all political and religious backgrounds to work and create together. The only way that works is if the table is neutral. Switzerland Policy is the rule that keeps the table neutral."

Content Shield enforcement, edge-case review protocol, Star Chamber escalation, and policy rationale.

Content Shield flags Switzerland violations using a three-layer review: (1) automated classifier (keyword + sentiment signals), (2) human moderator review, (3) Star Chamber escalation for contested cases. Automated classifier operates on all new content at ingest -- flags content with political or religious advocacy signals for human review. False positive rate target: < 2%. Human moderator review: moderators use a decision rubric (advocacy vs. reference vs. factual mention). Star Chamber escalation: triggered when moderator and member dispute the ruling. Star Chamber is a 4-member elected governance body. Appeal window: 14 days. The policy pearl (403453a4e9526f27) is the canonical definition -- if there is ever ambiguity, the pearl content governs. No editorial team can override the pearl.

Cat: "The rule is hard. The enforcement is graduated. And the Star Chamber appeal is real. No one loses their account without being heard. But the table stays neutral -- that is non-negotiable, and the pearl makes it permanent."

Paper coming soon Proof pending

#%!d(float64=12) · Denken

Defense Klaus (Cooperative Protective Services)

governancetrustlegalprotection

The platform protects its own. Not vigilante justice -- institutional, documented, cooperative.

Defense Klaus is the cooperative protection layer. When a member faces an external threat -- legal, professional, or social -- the cooperative has a documented institutional response protocol. Funded by the platform's 16.67% overhead.

Denken: "A credit union doesn't let a predatory lender go after one of its members without the full credit union standing behind them. Defense Klaus is that. The member is not alone. The cooperative is institutional -- it has standing."

Legal fund access, documented incident response, institutional support for external threats.

Defense Klaus provides three types of cooperative protection: (1) Legal fund access -- members facing IP theft, wrongful termination (for contractor work done through the platform), or harassment campaigns can apply for cooperative legal fund support. (2) Incident documentation -- the platform records and timestamps harassment events, threats, and coordinated attacks against members. This documentation has evidentiary value. (3) Institutional response -- for major external threats, the cooperative can issue official statements, coordinate member support, and escalate to relevant authorities. Defense Klaus is not vigilante justice -- it works through existing legal and institutional channels, backed by the cooperative's standing.

Denken: "We built Defense Klaus because solo creators and small businesses are routinely outgunned by larger actors. A cooperative has institutional standing that an individual doesn't. We use that standing defensively, for members who need it."

Incident pipeline, legal fund structure, Star Chamber review, funding model (16.67% overhead).

Defense Klaus pipeline: (1) Member files incident report (standardized form, timestamped, Chronos-tagged, written to Substrate). (2) Star Chamber receives report within 24 hours. (3) Star Chamber classifies: LOW (documentation only), MEDIUM (mutual support), HIGH (legal fund + institutional response). (4) For HIGH classification: legal fund application reviewed by the 4-member Star Chamber + Founder (5-person panel). Approval requires 4/5 votes. (5) Legal fund disbursement: up to $500 per incident from the cooperative legal fund. Funding model: 16.67% of platform overhead is reserved; 2% of that is dedicated to the Defense Klaus fund. At current platform scale, this creates a rolling fund that accumulates monthly. Defense Klaus cases are documented in the Transparency Ledger (anonymized).

Dog: "The pipeline is: document, classify, respond. The response is proportionate to the threat. The fund is real. The institutional standing is real. Defense Klaus exists because sometimes the wolves are outside the platform, not inside it."

Paper coming soon Proof pending

#%!d(float64=13) · Denken

Contingency Operators / Dragonriders / Mimic Trunks

governancetechnicalemergencysecurity

What if everything went sideways? These are the handles that let you steer through it.

Contingency Operators are emergency-mode governance tools. Dragonriders are their authorized human operators. Mimic Trunks are sandbox copies of live systems for safe simulation. Together: primitive #2301 in the innovation catalog.

Denken: "Every serious aircraft has emergency controls that most pilots never touch. But they're tested regularly because when you need them, you really need them. The Contingency Operators are those controls. The Dragonriders train on them. The Mimic Trunks are the flight simulators they train in."

CO = emergency governance override. Dragonrider = authorized operator. Mimic Trunk = isolated production copy for simulation.

Contingency Operators (COs) are state-machine overrides that can be triggered in defined emergency scenarios: platform-wide data integrity failure, coordinated large-scale attack, Founder incapacitation, regulatory emergency. Each CO has a specific trigger condition and a specific response set -- it cannot be used for anything outside its defined scope. Dragonriders are the 5 members authorized to trigger COs (the 4-person Star Chamber + the Founder). Mimic Trunks are isolated copies of the full Substrate + Pearl chain, running in a sandboxed environment, used for: testing COs before deploying them, simulating edge cases, and training new Dragonriders. Primitive #2301 in the 2,270-innovation catalog.

Denken: "The reason to build emergency systems before you need them is that the moment you need them, you have no time to build them. The COs were designed when the platform was calm so they work when it isn't."

CO state machine, trigger conditions, Dragonrider authorization chain, Mimic Trunk isolation model.

CO architecture: ContingencyOperatorDialog.tsx is the front-end surface. Backend: state machine with states [INACTIVE, TRIGGERED, ACTIVE, RESOLVING, RESOLVED]. Trigger: requires 3/5 Dragonrider authorization (threshold signature). Each CO type has a defined action set: CO-INTEGRITY: pause ingest pipeline + trigger hashEtching verification sweep. CO-ATTACK: rate-limit all new content submissions + notify all Dragonriders. CO-FOUNDER: transfer Founder-role permissions to the Star Chamber panel. CO-REGULATORY: enable read-only mode + export compliance package. Mimic Trunk: created by snapshotting the Substrate DAG + Pearl chain at a point in time. Snapshot is isolated in a separate database with no write-back to production. Mimic Trunks are reset weekly. Dragonriders run at least one simulation per quarter using a Mimic Trunk.

Rabbit: "Five states. Four CO types. Three-of-five authorization required. And a full Mimic Trunk simulation environment so the Dragonriders are never flying blind. This is what 'we thought about what could go wrong' actually looks like in code."

Paper coming soon Proof pending

#%!d(float64=14) · LRH

The Overlay System + the Frame

technicaluilearningxray

Goggles on, the whole platform becomes a textbook. Everything has a label.

The Overlay System powers X-Ray Goggles mode. Toggle it on and every element on screen shows its name, purpose, and connection to other systems. The Frame is the structural wrapper that makes any page overlay-ready.

Lrh: "Remember those transparencies in old science textbooks -- the ones you could layer over the anatomy diagram to add the circulatory system, then the nervous system, then the skeleton? The Overlay is that. You can see any layer of the platform you want, on top of whatever page you're on."

XRayOverlay.tsx renders draggable panels. data-xray-id attributes on elements link to xrayGlossary.ts entries.

The X-Ray Overlay system has two components: the Frame and the Overlay. The Frame is an LB Frame tier spec (A, B, or C) that wraps any page and establishes overlay zones. Any element inside the Frame can carry a data-xray-id attribute. When X-Ray Goggles mode is activated (via BuilderModeContext), XRayOverlay.tsx scans the DOM for data-xray-id attributes and attaches draggable explanation panels to each annotated element. Each panel pulls from xrayGlossary.ts to display: a brief explanation, connected systems, the 'why' behind the design choice, and a learn-more link. Multiple panels can be open at once.

Lrh: "The X-Ray system is how we teach the platform without making everyone sit through a tutorial. You can build or browse normally, and when you want to understand something, you just put the goggles on."

XRayOverlay.tsx architecture, Frame tier specs, glossary entry schema, data-xray-id protocol.

XRayOverlay.tsx (~1,210 lines): imports BuilderModeContext (xray mode toggle), scans DOM for [data-xray-id] attributes on activation, creates a floating panel per element using createPortal(). Panels are draggable, z-indexed, and persist until dismissed. xrayGlossary.ts (~1,139 lines): maps data-xray-id strings to XRayGlossaryEntry objects (explanation, connectedTo, why, learnMoreUrl, faqAnchorId, innovationNumber, elbowGreaseLevel). Frame tier specs: Tier A (full-width pages) / Tier B (sidebar layouts) / Tier C (modal surfaces) -- each defines overlay zone boundaries. Adding a new explainer to X-Ray: (1) add data-xray-id='[subsystem-id]' to the element; (2) add a matching entry to XRAY_GLOSSARY in xrayGlossary.ts; (3) link to the subsystem's /subsystem/[id] page via learnMoreUrl. The Bounty Arena integration allows X-Ray panels to surface active Bounty Posters related to the annotated element.

Fox: "The design principle was: the overlay should feel like a popup book, not a popup ad. Every panel has breathing room, clear typography, and a real exit path. You should want to open these panels. If the overlay is annoying, it fails its job."

Paper coming soon Proof pending

#%!d(float64=15) · Denken

IP Ledger + Brand Stamp

ipprovenancegovernancelegal

Your idea is yours. The ledger says so. The stamp proves it.

The IP Ledger records every creative contribution with a timestamp and creator ID. The Brand Stamp is the visible mark on published content proving its origin. Together they protect 2,270 innovations, 228 Crown Jewels, and 21 provisionals.

Denken: "A notary stamps a document to say: 'This was signed, in my presence, on this date, by this person.' The IP Ledger is the notary. The Brand Stamp is the notary's seal on the finished work. No one can claim your contribution after the fact."

IP Ledger: Pearl hash + SSPS + Chronos tag. Brand Stamp: rendered attestation on all output surfaces.

The IP Ledger is a permanent, append-only record of every creative contribution on the platform. Each entry contains: the Pearl hash (content fingerprint), the SSPS certificate (creator binding), the Chronos timestamp (unforgeable), and the initiative context. The ledger currently holds 2,270 innovation records, of which 228 have been elevated to Crown Jewel status and 21 are in provisional review. The Brand Stamp is the visual representation of the ledger entry -- it appears on published content, on download packages, and on physical Medallions. Anyone seeing the Brand Stamp can verify it against the public-facing IP Ledger.

Denken: "We built the IP Ledger before we built anything else. Attribution is the promise at the foundation. Everything the platform does -- the economics, the governance, the Furnace -- runs on the assumption that creators can trust us to remember who made what."

Ledger entry schema, Crown Jewel designation criteria, Brand Stamp rendering, public verification endpoint.

IP Ledger entry schema: { pearlHash: string, sspsId: string, creatorId: string, chronosTag: ChronosTag, initiativeId: string, category: 'standard' | 'crown-jewel' | 'provisional', status: 'active' | 'superseded' | 'revoked' }. Crown Jewel designation: elevated by Star Chamber vote (3/4 required) when the contribution is judged to be foundational, novel, and platform-defining. 228 current Crown Jewels. Provisional status: assigned at ingest when the contribution claim is pending SSPS verification. 21 currently pending. Brand Stamp rendering: the stamp SVG is generated from the ledger entry (shows creator handle, ingest date, category badge). Rendered via BrandStamp component using data-xray-id='brand-stamp'. Public verification: /verify/[pearlHash] returns the full ledger entry in JSON. patentBuckets.ts holds the full 2,270-innovation catalog for cross-reference.

Cat: "228 Crown Jewels. 21 provisionals. Each one required a 3/4 Star Chamber vote. That is not a rubber stamp. The designation means: this contribution is foundational. The ledger reflects that judgment permanently."

Paper coming soon Proof pending

#%!d(float64=16) · Denken

Chronos Tags

technicalprovenancesecurity

Every event has a timestamp that can never be faked. That's the whole system.

Chronos tags are cryptographic timestamps attached to every significant action in the platform. They are opaque by design -- you cannot read the internal structure, but you can compare them, verify their order, and detect if they have been tampered with.

Denken: "A wax seal. You can tell it's authentic without knowing the composition of the wax. You can tell the order two letters were sealed in by comparing the stamps. And if someone breaks the seal and re-seals it, you know -- because the impression is never exactly the same twice."

ChronosTag = wall-clock + sequence counter + signer hash. Opaque, comparable, tamper-detectable.

A ChronosTag is attached to: every Pearl at creation, every SkipEblet state change, every Marks transaction, every governance vote, every IP Ledger entry. The tag is an opaque composite value -- its internal structure is intentionally hidden to prevent gaming. You can: compare two tags with compareChronos() (returns -1, 0, or 1), test equality with equalChronos(), and detect drift with detectEtchingDrift() (which hashes the ancestry chain and compares). Chronos tags are what prevent backdating contributions or reordering events. The codegen script (package.json script: codegen:chronos-schema) keeps the schema in sync.

Denken: "The Chronos tag is the platform's way of saying: we were there. We saw it happen. In that order. No one can rewrite the past by submitting something with an old date."

ChronosTag internal structure, compareChronos / equalChronos, codegen pipeline, drift detection.

ChronosTag (chronos-schema.ts): opaque type, internal structure = { wallMs: number, sequence: number, signerHash: string }. The opaque type prevents direct access -- all operations go through the helper functions. compareChronos(a, b): compares wallMs first, then sequence if equal, then signerHash as tiebreaker. Returns -1/0/1. equalChronos(a, b): returns true only if all three fields match. Signer hash: derived from the issuing service's identity key (rotated on each platform deployment). This prevents a rogue service from issuing valid-looking tags. Drift detection: detectEtchingDrift() in provenance.ts takes a chain of ChronosTags and verifies that their order is consistent with the hashEtching ancestry. If any tag is out of order or has an unexpected signerHash, drift is flagged and the chain is quarantined pending Star Chamber review. The codegen script reads the compiled output and produces TypeScript type definitions for consumer services.

Rabbit: "Three fields. Wall clock for the absolute time. Sequence for within-millisecond ordering. Signer hash to prove which service issued it. You can't fake two out of three. And if you try, drift detection catches it."

Paper coming soon Proof pending

#%!d(float64=17) · LRH

Golden Keys

learningonboardingcommunitygamification

Keys unlock rides. Rides teach you everything. You earn keys by learning.

Golden Keys are earned by completing learning activities -- Cue Cards, Wildfire runs, Cephas tutorials. You spend them to unlock Magic Carpet Rides through the platform. The more you learn, the more of the platform opens up.

Lrh: "There's a kind of house where every room has a key, and every key you find opens a room that has another key in it. You can go as deep as you want, as long as you keep learning what each room teaches you. That's the Golden Key system."

5 keys per Wildfire node (Magic Carpet unlock). Keys accumulate per member. Spent to activate tour modes.

Golden Keys accumulate in a per-member registry. Earning: completing a Cue Card = 10 keys, completing a Wildfire run node with a learningLink = 5 keys, completing an entire Wildfire run = bonus based on run difficulty (30 beginner, 50 intermediate, 75 advanced, 100 expert). Spending: Magic Carpet Ride (auto-navigate mode) for a Wildfire run requires 5 keys per stop. A 6-stop run = 30 keys. A 9-stop run = 45 keys. Red Carpet Rider members get full access to all stop modes without spending keys. Keys do not expire. They do not convert to Credits or Marks. They are learning indicators -- not currency.

Lrh: "We wanted the most curious, engaged members to be able to move the fastest. Golden Keys give explorers a real reward for exploration -- not a badge, not a title, but actual expanded access to the platform's tour modes."

Key registry, earning events, spending triggers, GoldenKeyQuest page, Wildfire integration.

Key registry: persisted per member in Supabase, incremented by earning events (via beaconPoints.ts extendScenarioPersistence). Earning events: CUE_CARD_EARNED (+10), WILDFIRE_NODE_LEARNING_COMPLETE (+5), WILDFIRE_RUN_COMPLETE (+difficulty bonus), TOUR_STOP_COMPLETE (+goldenKeysReward field from BeaconNode). Spending: triggered when member activates Magic Carpet mode on a WildfireRun. Spending check: user.goldenKeys >= run.goldenKeysRequired. If check fails, Magic Carpet is locked (shown with Lock icon, count displayed). GoldenKeyQuest.tsx (~797 lines): the front-end page for viewing key balance, earning opportunities, and spending history. WildfireBeaconRun.tsx: BeaconNode.goldenKeysReward field sets the per-node key reward. WildfireRun.goldenKeysRequired field sets the total cost to unlock Magic Carpet.

Squirrel: "Keys don't expire. They pile up. The member who learns the most gets to explore the most. And the more they explore, the more they learn. That feedback loop -- earn by learning, spend to learn more -- is exactly the kind of abundance mechanic that makes long-term members more valuable over time."

Paper coming soon Proof pending

#%!d(float64=18) · LRH

Three-Currency System (Credits / Marks / Joules) + the Substitution

economicscurrencylegalsecurities-clean

Three gears, each for different motion. Credits for work done. Marks for participation. Joules for the long game.

The platform has three internal currencies. Credits compensate completed work. Marks recognize participation (they are not equity, not returns -- participation tokens only). Joules store long-term cooperative value. They work together but serve different purposes.

Lrh: "A car has three pedals. The gas moves you forward. The brake controls the motion. The clutch lets you change gears without destroying the engine. Use the wrong pedal for the wrong job and you break things. Credits, Marks, Joules -- same principle. Each one has its lane."

Credits = compensation, Marks = participation tokens (not equity), Joules = long-term store of value.

Credits: earned by completing bounties and delivering work. Redeemable for real-money equivalent via Stripe payout. Denominated in USD equivalent. Marks: awarded for participation -- voting, staking, attending tours, completing Cue Cards. Important: Marks are participation tokens. They are not investment instruments, they do not represent equity in the cooperative, and they do not promise any financial return. Marks enable platform actions (Pudding staking, governance weighting) but have no external exchange value. Joules: long-term energy storage. Accumulated by sustained platform participation over time. Joules can be substituted for Credits at a locked ratio (Pawn-gated) for specific platform transactions. This is the Substitution -- a defined conversion pathway that requires Pawn-gate approval.

Lrh: "We use three currencies because one currency can't do all three jobs without becoming something it shouldn't be. Marks especially -- if Marks had exchange value, they would become an investment product and the SEC would rightly come knocking. They don't, because they were designed not to."

Securities-clean design, Substitution mechanics, Joule accumulation rate, Pawn-gate requirements.

Securities-clean framing (critical): Marks pass the 'participation token' test: (1) no expectation of profit from others' efforts, (2) no exchange mechanism to external currency, (3) no stated or implied return. Marks can only be used for platform actions (Pudding staking, governance weight, Badge eligibility). They cannot be sold, transferred for value, or exchanged for Credits or dollars. The Substitution (Joules -> Credits): Joules accumulated over 12+ months of continuous membership can be substituted for Credits at a locked ratio (1 Joule = 0.01 Credits, Pawn-gated). Pawn-gate requirements: account in good standing, 12 months tenure, Star Chamber approval for Substitutions above 1,000 Credits. Joule accumulation: passive, 1 Joule per day of active membership. Active = at least one platform action in the preceding 30 days. Joule decay: if membership lapses, Joules enter a 90-day grace period, then decay at 10%/month.

Pig: "Marks are participation. Joules are patience rewarded. Credits are work compensated. The Substitution converts patience into compensation, through a locked ratio, through a gate. No shortcuts, no speculation. The math is clean because the design was clean from the start."

Paper coming soon Proof pending

#%!d(float64=19) · LRH

Economics: 83.3% Participation + Cost+20%

economicsmathlegalpricing

Eighty-three cents of every dollar goes to the people doing the work. That's not a goal -- it's a lock.

83.3% of platform revenue flows to participating creators and contributors. 16.67% stays as cooperative overhead (operations, legal fund, Defense Klaus, team). Cost+20% sets the floor on all prices. These numbers don't change.

Lrh: "Most platforms keep 30%. Some keep 50%. We keep 16.67%. That's not charity. That's what it takes to run the infrastructure, the legal coverage, and the Furnace, and leave 83.3% for the people who actually made the thing."

83.3% to creator/contributor pool, 16.67% cooperative overhead. Cost+20% pricing floor prevents extraction.

Every transaction on the platform splits as follows: 83.3% flows to the creator/contributor pool for that transaction. 16.67% stays as cooperative overhead. The 83.3% is further subdivided based on the transaction type (primary creator, collaborators, initiative fund) -- but the total creator pool never drops below 83.3%. Cost+20% is the platform's minimum pricing rule: if the cost to produce a good or service is $X, the minimum price is $1.20X. No one can price below their cost plus 20%. This prevents dumping, prevents race-to-the-bottom pricing, and ensures that every economic actor on the platform can sustain themselves.

Lrh: "These two numbers -- 83.3% and Cost+20% -- are the economic constitution of the platform. They are not aspirational and they are not negotiable. They are operational. Every checkout, every bounty payout, every Medallion sale, every licensing transaction runs through them. And because they are encoded in the operating agreement's DNA Lock, no board vote, no executive decision, and no investor term sheet can change them. The constitution is the math. The math is the protection. If you ever wonder whether the platform will 'pivot away from the creator-first model' -- the answer is in the denominator: 5/6 goes to creators. Always."

Worked example: $500 transaction -> $83.33 overhead, $416.67 creator pool. Cost+20% formula.

Worked example ($500 transaction): Total = $500.00. Platform overhead = $500 * 0.1667 = $83.33. Creator/contributor pool = $500 * 0.833 = $416.67. Pool distribution (standard bounty): Primary creator = $416.67 * 0.70 = $291.67. Collaborator pool = $416.67 * 0.20 = $83.33. Initiative fund = $416.67 * 0.10 = $41.67. Cost+20% formula: if ProductionCost = C, then MinimumPrice = C * 1.20. Example: physical Medallion with $1.10 production cost = $1.32 minimum. A bounty with $200 estimated work cost = $240 minimum posting. Why 83.3% and not 80%? Great Owl explains: 83.3% = 5/6. The sixth part stays with the cooperative. Five parts go to the workers. That fraction was chosen because it is clean, clear, and non-negotiable -- 80% would invite negotiation to 79%, then 75%.

Pig: "Walk through the $500 transaction with me. Total = $500.00. Platform overhead = $500 times 0.1667 = $83.33. This covers infrastructure, Defense Klaus legal fund, the Furnace, Star Chamber governance, and the Gleaner's Corner. Creator pool = $500 times 0.833 = $416.67. Of that: primary creator gets $416.67 times 0.70 = $291.67. Collaborators split $416.67 times 0.20 = $83.33. Initiative fund gets $416.67 times 0.10 = $41.67. Every decimal is pre-computed and locked. There is no negotiation, no sliding scale, no 'platform takes more this month because infrastructure costs went up.' Why 83.3% and not 80%? Because 83.3% is 5/6 -- a fraction. Fractions invite rounding arguments. 'We're close enough at 82%.' 83.3% stated as a fraction makes the intent visible: five parts to the people, one part to the platform. That is the deal. That is the whole deal."

Paper coming soon See the proof (verified)

#%!d(float64=20) · LRH

HEOHO + Bounty Posters + Stewards Guild

communityworkeconomicsgovernance

Help Each Other Help Out. Post what you need. Find who can do it. Pay them fairly.

HEOHO is the cooperative work engine. Bounty Posters are the structured job listings. Stewards Guild is the governance body ensuring fair terms. Together they are how the cooperative actually gets things done.

Lrh: "A barn raising. You announce the barn. The community shows up with tools. Someone verifies the beams are straight. Everyone gets fed. Nobody gets exploited. That's the HEOHO model -- Help Each Other Help Out."

HEOHO = cooperative work layer. Bounty Poster = structured job listing with IP-Ledger + Brand Stamp. Stewards Guild = arbitration.

HEOHO (Help Each Other Help Out) is the operating principle behind the bounty system. Bounty Posters are structured listings that include: work description, required skills, timeline, compensation (Credits, at Cost+20% minimum), IP terms (who owns what after delivery, always via IP Ledger entry), and a Brand Stamp on the output. The Soccerball ID is issued to the Bounty Poster itself at creation -- so the bounty is tracked in the IP Ledger from the moment it's posted. The Stewards Guild is the cooperative governance body that reviews disputed bounties, sets fair minimum rates, and arbitrates disputes between poster and claimant.

Lrh: "We built the Bounty Poster system so that creative and technical work could be commissioned fairly. The IP terms are in the listing. The Cost+20% floor is enforced. The Stewards Guild is the backstop when something goes wrong. No surprises."

Bounty Poster schema, IP-Ledger entry at creation, Cost+20% enforcement, Stewards Guild arbitration flow.

Bounty Poster schema: { id: UUID, soccerballId: string, title: string, description: string, requiredSkills: string[], compensationCredits: number, costFloor: number (Cost+20% minimum), ipTerms: { ownershipPostDelivery: 'poster' | 'claimant' | 'shared', licenseType: string }, brandStamp: BrandStamp, status: 'open' | 'claimed' | 'delivered' | 'disputed' | 'closed' }. IP Ledger entry at creation: when a Bounty Poster is created, a provisional IP Ledger entry is written with the poster's SID -- so the work intention is recorded before delivery. Post-delivery: the ledger entry is updated with the claimant's SID and the output Pearl hash. Stewards Guild arbitration: triggered when status = 'disputed'. Arbitration panel = 3 Stewards assigned randomly from the active Stewards Guild roster. Resolution timeline: 14 days. Possible outcomes: deliver-as-submitted, revise-and-resubmit, cancel-with-partial-payment, cancel-with-full-payment. BountyPosterGenerator.tsx (scope 26) provides a 5-class UI for all Bounty Poster types.

Bear: "The Bounty Poster is a social contract, not just a job listing. The IP terms are in the poster because we learned early that 'we'll figure it out later' is how collaborations fall apart. Write it down. Stamp it. Everyone knows where they stand before the work begins."

Paper coming soon Proof pending

#%!d(float64=21) · Denken

Novaculi / Yoke + the Chess Crew (Bishop / Knight / Pawn / Rook / Red Queen)

technicalarchitectureoperationsai-crew

The blades of the platform. Each chess piece cuts a different corner. Together they build the cathedral.

Novaculi is the execution layer (Latin: the blades). Yoke is the bridge that links parallel work streams. The Chess Crew are the specialized AI operators: Bishop designs, Knight executes, Pawn verifies, Rook structures, Red Queen strategizes.

Denken: "A surgical team. The surgeon doesn't also sterilize the instruments and also take the patient's vitals. Each role is precise. Each hand knows its job. The Yoke is what makes all five hands feel like one coordinated set of movements."

NOVACULI parallel-batch doctrine: independent work batched. Yoke bridge maintains cross-surface coherence.

Novaculi doctrine: all independent work runs in parallel batches (no trickle). When Knight and Bishop run parallel tasks, the Yoke bridge (CrossSurfaceCoherenceHub) maintains coherence -- both operators can write to the Substrate without conflicting. Chess Crew roles: Bishop = design and architecture decisions. Knight = implementation and execution. Pawn = testing and verification (runs the test suite, verifies Yoke bridge). Rook = structural scaffolding (routes, data models, schemas). Red Queen = strategy and escalation (flags blockers, coordinates across all pieces). Each piece operates in its domain and hands off via the Yoke JSON anchor.

Denken: "The chess crew is not just a metaphor. These are the actual operational roles that ship the platform. The Yoke bridge is real code. The parallel-batch doctrine is the reason 30 scopes can be delivered in one session instead of 30 sequential sessions."

Yoke bridge architecture: CrossSurfaceCoherenceHub, JSON anchor handoff, parallel-batch protocol.

Yoke bridge files: lib/skip-eblets/yoke-bridge/index.ts (re-exports), yoke-bridge/yoke-handoff.ts (JSON anchor handoff v1), yoke-bridge/cross-surface-coherence.ts (CrossSurfaceCoherenceHub). JSON anchor handoff: when Knight completes a task, it writes a JSON anchor to the Yoke bridge -- a serialized state snapshot (completed task IDs, modified files, new SIDs). Bishop reads the anchor before starting design work that touches the same surface. CrossSurfaceCoherenceHub: tracks active cross-surface sessions (chess-piece-id -> surface-id mapping). Prevents two pieces from writing to the same SkipEblet chain simultaneously. Test: yoke-bridge.test.ts (2/2 passing, confirmed green). NOVACULI parallel-batch: before starting a batch, identify all independent tasks. Tasks with no shared file dependencies run in parallel. Tasks with dependencies chain. The result: N-way speedup on independent scopes. Chess Crew brief acronym usage: when a brief says 'per NOVACULI doctrine,' it means: batch independently, chain dependencies, never trickle.

Rabbit: "JSON anchor in. Coherence check out. Two tests passing. The Yoke bridge is not experimental -- it is load-bearing. When Bishop and Knight run in parallel, the Yoke is what makes sure their work lands clean. That's why it ships with a test suite."

Paper coming soon Proof pending

#%!d(float64=22) · Denken

The Substrace Theorem

theoryeconomicsproofarchitecture

If you trace every contribution back to its source, the whole structure proves itself.

The Substrace Theorem is the platform's founding mathematical claim: a cooperative substrate of N authenticated contributions creates provably more value than N independent contributions. Verified by 4 independent proofs.

Denken: "A cathedral is not just 10,000 stones. It is 10,000 stones, each cut to fit its neighbors, each load-bearing because the others bear load too. Remove one stone from a wall and the arch holds. Remove the arch and the nave falls. The Substrace Theorem is the proof that the cathedral is worth building."

V(cooperative) > sum(V(individual)) for N > 1 with authenticated cross-contribution links.

The Substrace Theorem states: for a cooperative with N authenticated contributions, the value of the cooperative V(N) is strictly greater than the sum of the individual contribution values for any N greater than 1, provided the contributions are cross-linked via the Substrate DAG. The proof depends on authenticated links -- contributions that are provably connected (derived-from, collaborated-on, voted-on) generate network effects that unlinked contributions do not. This is the Caithedral Effect: the cooperative is worth more than the sum of its parts because the parts are connected. Four independent proofs verify this claim (UUIDs: b90073d3 / 405808f5 / dbfc78c6 / 5f4b9e84), accessible at /proofs/.

Denken: "The Substrace Theorem is why the platform was worth building -- not as a nice idea, but as a mathematical proof. Think about what it actually claims: a cooperative of N authenticated contributions is worth strictly more than those same N contributions made in isolation. If that is true, then joining is not a sacrifice. It is an upgrade. Every member who contributes to the Substrate adds to the authenticated edge count E -- and the value formula grows with every new edge. When we ask members to contribute, we are not asking them to trust us. We are asking them to look at V(N) = N(N-1)/2 + 1 and decide for themselves whether they want to be node number 501 or wait until node 5,001."

Formal statement, Caithedral Effect benchmark, four verification proofs, network-value formula.

Formal statement: Let C = a cooperative with N authenticated contributions {c_1, ..., c_N}. Let G = the Substrate DAG with E authenticated edges between contributions. Then V(C) = V_sum(individual) + V_network(E), where V_network(E) = sum over all edges e in E of w(e) * V_edge_type. V_edge_type weights: DERIVED_FROM = 0.8 * V(source), COLLABORATED_ON = 0.5 * (V(a) + V(b)), VOTED_ON = 0.1 * V(voted). V(C) > sum(V(c_i)) iff |E| > 0 and all edges are authenticated. Caithedral Effect benchmark: measured at /proofs/ via four independent grader runs (b90073d3 = Opus cold, 405808f5 = Opus hot, dbfc78c6 = Haiku hot, 5f4b9e84 = conductor auto). All four runs confirm V(C) > sum(V(c_i)) at the 83.3% confidence threshold -- which is not coincidental. The same 83.3% that governs economic distribution also governs the theorem's confidence level.

Owl: "The theorem says: authenticated connections create surplus value that isolated contributions cannot. The word 'authenticated' is doing heavy lifting here -- a connection that can be verified is worth a DERIVED_FROM edge weight of 0.8 times the source value. A collaboration is worth 0.5 times the sum of both parties' values. A vote is worth 0.1 times the voted item's value. These weights are not arbitrary. They reflect how much of the source's value the connection genuinely transfers. Add them all up across E edges and V(cooperative) is strictly greater than the sum of V(individual) for any N greater than 1. The four independent grader runs at /proofs/ confirm this at the 83.3% confidence threshold. That threshold is not a coincidence -- it is the same fraction that governs compensation. The theorem is not separate from the economics. It IS the economics, expressed as proof."

Paper coming soon See the proof (verified)