Execution

§ 06

THE RUNTIME MODEL

Four stages. Each one is a binding between something abstract and something that actually exists on-chain. Hover a stage to expand it.

hover, focus or tap a stage — the readout follows

§ 07

A program is not a document about what should happen. Once it is deployed, running it is the happening.

CONCEPTUAL SHAPE OF A RUN

function execute() {
    hook();
    captureFee();
    updateState();
}

CONCEPTUAL UI ONLY — NOT THE DEPLOYED CONTRACT SOURCE

READ THIS AS A DIAGRAM, NOT AS SOURCEthe three lines above name the order of concerns — call the hook, account for the fee, write the state. They are not an extract from the contract, and nothing on this page asserts that these exact functions exist.

“CODE IS NOT THE DESCRIPTION.”“CODE IS THE EVENT.”

FIG. 5 — TRANSFORMATION

CODE

RUNTIME

EXECUTION

STATE

In an ordinary system, a rule is written down and something else carries it out — a job, an operator, a multisig. The gap between the two is where discretion lives, and discretion is where systems drift from their own descriptions.

A Hook removes the gap. The rule and its execution occupy the same transaction. What the code says is what the chain does, in the same block, without an intermediary step in which anyone could choose otherwise.

§ 14

SYSTEM LOG

The experiment, narrating itself. Each line corresponds to something that happened on-chain.

EVENT STREAMREALTIME SUBSCRIBED

NO EVENTS RECORDEDthe stream is quiet. Nothing is simulated in its place.

SEQUENCE — SWAP · HOOK · FEE · BUYBACK · BURN · STATESYNTHETIC STREAM