Operations.

Registry activation, all six role artifacts, Loader V3 deployment observations, immutable policies, and a recent blockhash are reacquired by the release workspace.

The compiler emits canonical Product, domain, portfolio, and content identities without claiming any account exists onchain.

Realm and Market are optional explicit coordinates; when supplied they must be non-executable, distinct, present at the same finalized floor, and owned by selected Core.

The Found31 workspace independently authenticates runtime Product records, infrastructure profile and immutable Registry/Rent artifacts before constructing unsigned v0 bytes.

The Direct V3 workspace reacquires Hot38, Product runtime width, ProgramSet selection, descriptor, lifecycle, strategy, TransitionVM, AccountProfile, Loader state, and checked release evidence.

The visible legacy registration encoder is intentionally excluded: successor maker-root ownership and production registration artifacts are not frozen.

No browser action is exposed until successor replay roots, action artifacts, and terminal account profiles form one accepted production route.

The production Core→Resolution action is reachable, but no chain-derived operator snapshot currently selects its authority and account frame. The browser will not construct from wire constants alone.

The production action is reachable, but the operator has no current authority-selection snapshot/report builder. A browser constructor would invent authority.

Real-provider 38-account submit and permissionless 18-account reclaim constructors exist in Rust; no browser copy of their ABI is accepted.

The Rust operator checks the Product record digest, runtime-u32 selector, terminal certificate, and current resolution state before construction.

The Rust operator requires the exact terminal and refund preconditions; browser transaction bytes remain unavailable until generated ABI parity lands.

A chain-derived Rust Hot V3 builder exists; a generated browser ABI and production release bundle have not yet crossed the web boundary.

The Series V3 operator owns exact transaction planning, but the browser has no current production release manifest encoder.

The General workspace derives the current candidate and selection lifecycle, action artifacts, exact PDA bumps, lookup table, and packet-safe unsigned transaction.

The General workspace exposes only action artifacts whose current state/lifecycle recipes and child geometry can be fully reacquired and packet-checked.

Close derives the successor terminal coordinate from expected revision plus one and recomputes all canonical state PDAs before unsigned construction.

The Rust operator derives Dealer equity and custody coordinates. Browser construction waits for the finalized production artifact bundle rather than inventing pool state.

The Dealer successor kernel and operator are present; the browser still lacks a generated, release-selected transaction encoder.

Rust successor builders exist; the browser remains unavailable until exact production artifacts and account profile are generated and selected.

The browser workspace that claimed this action encoded the schema-1 DCLTECO1 economic projection, whose only program was banished; the live successor speaks DCLTEMK2/DCLTEPS2 through dclutch-economic-slice-kernel and has no generated browser ABI. Nothing is constructed from a wire no deployed program reads.

Representation conversion was reachable only through the same banished schema-1 projection. Native and represented supplies now live in Claims/Custody state, and no browser encoder for that route has been generated from its owning crate.

The browser authenticates CapabilityV4, ProductBasisV3, independent K/N widths, and exact zero or positive payout. Transaction construction remains Rust-only because SignedDeltaV3 and Custody authority/digests have one canonical operator emitter.