OMNI saysCOMMIT — append a block to the per-user chain; equivalent to PUBLISH (v3.2).
COMMIT (v3.2, ledger tier) appends an immutable block to the user's chain — the molecular equivalent of PUBLISH. Per R8, every version must COMMIT a block: "there is no such thing as an unrecorded version." The block schema is fixed: (n, version, ts, prev_hash, instance_h, delta_h, meta_sig, hash). COMMIT is how change becomes permanent and auditable; skipping it breaks forensics and rollback.
Power-ups you unlock
Append a block to the per-user chain
≡ PUBLISH, ledger tier
Every version COMMITs a block (R8)
No unrecorded versions
The Silent Failure attacks — common mistakes
Shipping a version without committing (violates R8)
Mutating a committed block
Skipping fields in the fixed schema
Boss battleList the fixed block schema fields COMMIT writes.
Example code
<!doctype html><html><head><meta charset="utf-8"></head>
<body style="background:#06040d;color:#b388ff;font-family:monospace;padding:20px"><pre>commit: block (n, version, ts, prev_hash,
instance_h, delta_h, meta_sig, hash)
every version commits (R8) → no unrecorded versions</pre></body></html>