Programmable State

Axiom Cells

An Axiom Cell is TruthLinked's programmable state unit: isolated bytecode, owned storage, controlled calls, logs, value transfer, and a manifest that declares its execution footprint.

AXIO bytecode256 registers32-byte register valuesManifest enforced

01 What A Cell Owns

A cell owns its bytecode, storage namespace, owner, balance, upgrade state, and manifest metadata. External code cannot mutate a cell by accident; execution enters through a transaction intent and host boundary.

Logic

Compiled Axiom bytecode identified by the AXIO magic.

State

Storage keys accessed through SLOAD, SSTORE, and SDELETE.

Authority

Owner checks use runtime context and access-control opcodes.

Manifest

Declared reads, writes, commutative keys, dynamic specs, and oracle schema IDs.

02 Runtime Surface

Group	Ops
Arithmetic	`ADD`, `SUB`, `MUL`, `DIV`, `MOD`, saturating add/sub.
Storage	`SLOAD`, `SSTORE`, `SDELETE`.
Context	`GET_CALLER`, `GET_OWNER`, `GET_CELL_ID`, `GET_HEIGHT`, `GET_TIMESTAMP`, `GET_VALUE`, calldata helpers.
Output	Return data and event logs.
Cross-cell	Direct and buffered cell calls.
Access control	Owner, caller, equality, non-zero, and gas requirements.
Token ops	Balance, transfer, mint, burn, freeze, thaw host calls.
Accord	Request external data and read finalized response state.

03 Deployment Flow

write source

compile bytecode

generate manifest

deploy cell

call or simulate

runtime enforces boundary

axiom compile ./counter.cell
axiom deploy --from ~/.truthlinked/default.keys --bytecode ./counter.axiom --manifest ./counter.manifest.json
axiom call --from ~/.truthlinked/default.keys --cell <cell_id> --method increment

04 Calls And Simulation

Cell calls carry cell_id, calldata, value, and gas limit. Simulation sends the same shape through a read-only path so builders can inspect behavior before submitting a state-changing transaction.

axiom call --simulate --from ~/.truthlinked/default.keys --cell <cell_id> --method get --gas 500000

05 Upgrade And Immutability

TruthLinked supports deployed cell upgrades through an owner-controlled upgrade path and governance-oriented proposal intents. A cell can also become immutable, after which its upgrade posture changes from movable code to permanent logic.