General semantic-Product-ID OpenBatch — 2026-09-08

This is an accepted owned-local-validator observation. It is a host/runtime source-split diagnostic, not a checked release or devnet claim. It records one completed OpenBatch against the preserved a7 ledger and no later General act.

Inputs and provenance

The host source was exported from the committed tree and built on hbox through swarm-build; it was not built from the shared dirty worktree. The runtime is the sealed a7 artifact cohort above. These are intentionally named separately: this result does not establish a single-source release.

The repaired identity boundary

The authenticated Product graph carries two different values:

• the finalized Product-record digest, which authenticates the Registry coordinate; and
• the Product body's semantic product_id, which AccountProfile projects into identity::SELECTION_PRODUCT and GeneralBatchOpeningV1 commits.

Before ebcc5a17e, the host fed the record digest into the OpenBatch occurrence and Batch PDA derivation. The runtime read the semantic Product ID, so it refused the proposed occurrence with 0x4004 before the accelerator call. The commit keeps product_record for record-bound General actions and passes product_id only to the OpenBatch occurrence; its loopback session uses the same semantic ID for the primary Batch state PDA. The focused Rust control uses deliberately distinct record (0x94…) and Product (0x43…) identities and proves the occurrence differs. It passed:

cargo test -p dclutch-operator \
  general_hot_v3::tests::open_request_derives_the_slot_independent_batch_occurrence \
  -- --exact --test-threads=1
# 1 passed

Both cargo check -p dclutch-operator --locked and cargo check -p dclutch-local-successor-bootstrap --locked passed at the committed host source.

Capability seal and route construction

The preceding real seal remains part of the accepted frame:

The bootstrap and exact frozen LUT runs are separate, recorded transactions; the final route was re-emitted with the signed request digest and exact table. No account list was hand-assembled.

Accepted execution and read-back

The final preflight had simulatedError: null; submission then landed:

The plan recorded the primary state as vacant before execution, at logical coordinate 5 with bump 255. The read-back is the poststate, rather than an inference from the send.

Immutable hbox artifacts

All paths below are immutable files on the preserved ledger directory.

Controlled limit

This evidence stops after OpenBatch. It neither runs nor claims PlaceOrder, CancelOrder, CloseBatch, or any exit. The preserved Trading artifact is known to exhaust its compute budget on the exact nonzero PlaceOrder ProgramTest path before accelerator invocation; the reported profile reaches admitted-cpi-index at a 57,110-byte heap total and then reaches the 1,400,000 CU ceiling. The next host campaign must use the fresh Trading artifact after the funded-seal join repair and must derive its maker signed-order terms and actual Claims/Custody children from chain facts. The a7 ledger remains preserved as the OpenBatch evidence source.