smart-byte: governance, burns, and transfers between clusters #135

Merged

dcharlot merged 2 commits from smart-byte-lifecycle into main 2026-10-01 12:22:03 -04:00

Conversation 0 Commits 2 Files changed 22 +12919 -303

2026-10-01

Transaction Science

smart-byte: governance, burns and transfers between clusters, with vectors ...

smart-byte-state implements cluster_state.md:
- governance: Change and Proposal, electorates, the quorum, the time lock;
- burns: Burn and the retired record;
- exports: ExportStatement and Certificate;
- the import checks.

smart-byte-core: Transition::sign_export and the destination member. The
envelope compares frames within a cluster only.

smart-byte-lockstep: the committing nodes sign each committed frame's export
certificates. The certificates are built from a committing node's report,
never from a node whose state diverged.

state_vectors.json grows to 23 vectors (state-013 to state-023 new,
state-011 extended) and is regenerated in place; v1 is DRAFT. Every new check
has a vector that fails an implementation leaving it out. The README
documents the 14 new error classes, and the regeneration log records the
change.

crosscheck/verify_v1.py implements governance, burns, exports and imports
from the spec text. It reproduces every vector, 117 of them, both plain and
under -O.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

f9fbd5a3af

• View at this point in history

2026-10-01 11:48:44 -04:00

Transaction Science

smart-byte spec: governance, burns, and transfers between clusters ...

cluster_state.md, rewritten. The state gains the cluster's identifier, its
peers, its governance (delay, sequence number, pending changes), and the
retired, exported and imported records.
- Governance proposals change the registry and the peers. Each is
  sequence-numbered, needs approval from floor(2m/3)+1 of its electorate,
  and is time-locked by the cluster's delay.
- A burn retires a byte for good.
- A transition may name a destination cluster. The source's committing nodes
  certify the byte's state as it left. The destination checks the
  certificate and verifies the byte's full history itself.

envelope_wire_format.md: the destination member, covered by the signature
and the history hash. Frames rise within a cluster; a move to another
cluster starts that cluster's count.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

31f5d6bba4

• View at this point in history

2026-10-01 11:10:54 -04:00