BROADSIDECHAIN 4663 / FORK CONTROL SURFACE
07 / MECHANISM & LIMITS

HOW THE VOLLEY WORKS.

Published control paths are executed against one target inside an isolated chain-state copy. Each call produces a before/after diff; the state copy is then discarded.

EXECUTION SEQUENCEFOUR DETERMINISTIC PHASES
01
FORK CHAIN 4663

Copy state at one stated block.

eth_blockNumber
02
RESOLVE ROLE HOLDERS

Load thirteen published EOA addresses.

registry.roles()
03
EXECUTE + OBSERVE

Call each function and read five target fields.

state.diff()
04
DISCARD THE FORK

Keep only the reproducible report.

fork.dispose()
HARD LIMITSWHAT THE INTERFACE DOES NOT CLAIM
01

SIMULATION ≠ PREDICTION

The roles exist and are published. This interface makes no statement about anyone's intent to use them.

02

A FORK IS A SLICE

Role holders can change. Each report is valid only for the exact block printed on it.

03

GUN FIVE MOVES NO TARGET STATE

The current implementation does not enforce oraclePaused internally. The volley records no observed target-state movement.

04

CHAIN CONDITIONS

L2BEAT: not even Stage 0. Exit window: None. Sequencer failure: “No mechanism”. Critical upgrade path: EOA, no delay.