centram / economy

Personal Intelligence Economy Design record

Rights precede markets. Proof should precede reward.

CEN is the credit a Centram node spends and earns. The design says a reward settles against a signed usage proof tied to a licensed asset version, and that what crosses the chain is a commitment — never the asset. Running a node does not pay. Storage volume, prompt count, uptime and raw event count are not compensable on their own.

What exists today · CEN

Local credit ledgerin the daemon
Burn / mint / balancesimplemented
Dynamic pricingimplemented
Chain with peers on itnone
Centinel settlementnot built
Fiat exchangenone
Public distributionnone
Proof-gated rewardnot yet true

Read off the tree and the audit backlog, not off the design document.

Where the design and the code disagree Unproven

The reward is currently self-validated.

A genome reward is minted on acceptance, and acceptance is decided by the receiving node alone against its own local fitness baseline. No quorum, no independent-receiver condition.

Why that matters, in numbers

The reward for an accepted genome is 0.2 CEN. The cost of sharing one is 0.1 CEN. Reward exceeds cost, and the only party who decides whether the reward is earned is the party receiving it. Two colluding nodes can therefore mint indefinitely while producing nothing anyone else benefits from.

This is recorded as T2 in the project’s audit backlog, with the fix stated two ways: add an N-independent-receiver or quorum condition to the acceptance mint, or set the reward no higher than the share cost. Neither has been done.

Until one of them is, “proof precedes reward” is a design intent, not a property of the system. The source is the audit backlog, and it outranks this page.

What crosses, and what never does Designed

Commitments rise. Assets do not.

The load-bearing decision in the record, and the one thing here that is not negotiable once built.

On-chain · commitments only Not built

  • asset
  • offer
  • license
  • reserve
  • settle
  • revoke

The line raw data never crosses

Off-chain · your device Runs locally

  • memory
  • prompts
  • training snapshot
  • weight delta
  • demand
  • purpose text

The upper band is dashed because none of those six slots has ever been written: there is no Centram chain with peers on it.

The canonical transaction

Nine steps, from making an asset to auditing the receipt.

Step 01 runs today. The other eight have never run, and step 08 is where the code parts company with the design.

  1. 01 A node creates an asset and evaluates it against its own baseline. Device Implemented
  2. 02 The registry marks an immutable version ACTIVE_ECONOMIC. Chain Designed
  3. 03 A second node publishes demand, or asks for the capability directly. Device Designed
  4. 04 The gateway returns a signed offer and a revocable license proposal. Chain Designed
  5. 05 Both Core policies approve scope, purpose, duration and price. Chain Designed
  6. 06 Centinel reserves CEN in escrow. Chain Designed
  7. 07 A sandbox executes the capability without exposing raw memory. Device Designed
  8. 08 A verifier signs the usage proof; settlement splits the revenue. This is the step the code does not gate on proof — see above. Chain Unproven
  9. 09 Both nodes audit the receipt and watch revocation state. Chain Designed

Five rules that decide what is possible

Constraints first, because they are what a token cannot be allowed to buy.

01 Holds today

The OS never depends on the token

Boot, login, local memory, local inference, local learning, export, delete and recovery all work with no CEN and no chain. A token holder cannot gain operational power over your machine. The single-node product is token-free by construction, and the structural audit cleared it.

02 Designed

Rights precede markets

An asset cannot enter economic state until owner, provenance, consent, version, evaluation, license compatibility, deletion, revocation and bounded execution are all proven.

03 Designed

Only rights are exchanged

Raw memory, a person, an identity or a secret cannot be listed. The standard transaction is a revocable license to one operation, purpose, recipient and duration.

04 Designed

Stake does not buy authority

Stake and slashing protect service integrity. They cannot change Core policy, reach memory, or hand a large holder control over anyone’s personal intelligence.

05 Designed

Economic actions fail closed

A chain outage, reorganisation, fee spike or ambiguous finality enters a degraded state. New settlement pauses; local and safety operations carry on.

Considered and rejected

What a design refuses says more than what it promises.

Each of these was written down and turned down.

Reward all captured data
It pays for surveillance, duplicate data, secret capture and Sybil spam instead of measured capability.
Make CEN required to boot, or to run local AI
A chain, a market or a token holder would gain operational power over user-owned memory and over whether the machine runs at all.
Put intelligence assets directly on-chain
Permanence and public replication cannot coexist with deletion, revocation and local sovereignty.
Let smart contracts authorise execution
Economic validity is not operating-system authority. Only Centram Core issues a scoped capability grant.

The result the rest of this page depends on

The value of any of this rests on collective learning being worth something measurable. At 1.1B parameters over five seeds, the project’s own experiment did not show that: the bridge from a loss-space win to a held-out task win did not hold. The audit backlog is explicit that if that bridge never closes, the token layer adds no product value at all.

The papers page carries the same measurement against the paper it belongs to. Nothing here is a shipped feature, an offer, or investment material.

Get told when it ships

One address, kept to send release news and nothing else. Unsubscribe by asking.