🪠soft3/tok.md

Toktoken frameworkplumb stackvalue layerplumb
cyber plumb soft3 core spec cyber
π 0.02% 405 words · 3 min

tok

the value layer of soft3. three primitives that close the question of what value IS and how it MOVES in cyberspace:

primitive what it is
Coin the fungible token nature
Card the non-fungible token nature
PLUMB the five operations: pay, lock, update, mint, burn

every Sigma in cyberspace is a configuration of Coins held by Cards, mutated through PLUMB. every Robot is realized as a Card. every state change in cyberspace is a sequence of PLUMB operations.

position in soft3

   neurons → Robots
                │
        tok  ───┤        value layer    — this repo
        bbg ────┤        memory layer
        tru ────┤        convergence layer
        radio ──┤        transport layer
        ...     │
            cybergraph

tok sits between the agency of the Robot (what it wants to do) and execution on the cybergraph (what was done). PLUMB programs compile through trident, execute on nox, and prove on zheng.

what makes tok minimal

  • two natures, exactly: Coin (fungible) + Card (non-fungible). no third nature
  • five operations, exactly: pay + lock + update + mint + burn. no sixth operation
  • one composition rule: operations compose into Intents that commit atomically or roll back

accounts, registries, ledgers, balance sheets, contracts, permits, escrows — all derived from Cards holding Coin balances mutated by PLUMB. if a behavior cannot be expressed in PLUMB, it does not belong in the value layer.

conservation

PLUMB preserves four invariants by construction (the zheng proof system rejects any operation sequence that breaks them):

law statement
Sigma conservation every pay has one source and one destination
Token conservation Σ balances = mints − burns per Coin class
Card uniqueness owner_count(id) = 1 always
Atomicity all ops in an Intent commit together or none do

provability replaces enforcement.

see also

  • cyb/robot — the entity that exercises PLUMB
  • latency targets (foculus explanation) — when pays and rewards become final/spendable; tok owns conservation, foculus owns the clocks
  • specs/money-loop (cyber/specs) — network product contract for balance, send, receive, multi-payee reward-after-link
  • soft3 — the stack tok belongs to
  • bbg — where PLUMB-mutated state lives
  • trident — the language tok operations compile from
  • zheng — the proof system that enforces conservation
  • nox — the VM that executes PLUMB

discover all concepts

Folder

Graph