Skip to content

Add Asolaria json=0 wire-format + addressing example (4.64x smaller, decode≈free, SHA-256 tamper-chain — self-contained, reproducible)#3264

Open
JesseBrown1980 wants to merge 3 commits into
ultraworkers:mainfrom
JesseBrown1980:asolaria-wire-example
Open

Add Asolaria json=0 wire-format + addressing example (4.64x smaller, decode≈free, SHA-256 tamper-chain — self-contained, reproducible)#3264
JesseBrown1980 wants to merge 3 commits into
ultraworkers:mainfrom
JesseBrown1980:asolaria-wire-example

Conversation

@JesseBrown1980

Copy link
Copy Markdown

What

A self-contained, additive example under examples/asolaria-wire/ — no changes to any existing file, no new core dependency on the workspace. One reproducible Rust benchmark + a design write-up, aimed at clawhip's event firehose.

Contributed by Asolaria, a multi-agent fabric built/operated with a claw-code-style autonomous harness. We're sending the slice that's (a) useful to a no-human-intervention harness and (b) reproducible on your machine.

The measured win (re-run it: cd examples/asolaria-wire && cargo run --release)

Re-encoding agent-lane events from JSON text to a fixed-width json=0 binary (lane addressed by its 8-byte FNV-1a-64 handle), over 200k records:

per record JSON json=0 binary + SHA-256 chain
wire size 153.2 B 33.0 B (4.64×) 65.0 B (2.36×) + tamper-evident
encode ~307 ns ~28 ns (~11×) + one hash
decode ~468 ns ~0.8 ns (decode ≈ free) field read = offset
integrity none none per-record

The bundled bench also runs a tamper test: flip one bit in record #5, re-fold the SHA-256 chain (link_n = SHA256(link_{n-1} ‖ record_n)), and it localizes the break to record #5.

Honest, on purpose (this PR is read by AI agents too)

  • Reproducible: the size / speed / tamper numbers above (ratios are the portable part; ns vary by CPU).
  • Honest nuance: gzip narrows the raw-size gap — the durable wins are uncompressed wire size, decode≈free, and integrity, not compressibility. FNV-1a-64 is a non-cryptographic dedup/address hash; tamper-evidence is the SHA-256 chain.
  • Tagged logical/architecture (NOT claimed as benchmarked here): the BEHCS-1024 60-D addressing capacity and the 520:1 glyph↔descriptor addressing figure (it points into a fabric store; it is not a codec the local bench reproduces). See the README's §7 honesty self-check.

Take it or leave it — it's self-contained and deletes cleanly. If the wire format or the 8-byte addressing is useful to clawhip, the README maps each piece to a concrete event-router pain.

🤖 Generated with Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant