Batteries

Free Battery Factory is the workshop. Each battery is a bounded component that stores, runs, exposes, or checks part of a software boundary.

Shipped Batteries

Battery	Role
`batpak`	Core battery pack format and embedded event substrate.
`syncbat`	Sync-first runtime contracts and dispatch surfaces.
`netbat`	Server and network boundary surfaces for explicit IO.
`hostbat`	Host contract projection: client manifest, H-interface fingerprints, subscription descriptors.
`bvisor`	Boundary supervisor: runs a declared workload under a fail-closed boundary contract with real Linux (landlock/seccomp/cgroups) and Wasm (wasmi/WASI) confinement backends.
`batpak-macros`	Derive macro support for the core substrate.
`batpak-bench-support`	Shared benchmark support for workspace surfaces.

Support Crates

batpak-macros-support, tools/integrity, and tools/xtask are factory machinery. They support the batteries, but they are not application batteries themselves.

Reserved Names

The following names are reserved vocabulary only. They are not shipped products unless a future release adds crates, tests, traceability, and conformance surfaces for them:

wirebat
filebat
testbat
benchbat
viewbat
guardbat
shipbat

Usage Rhythm

Need local event truth? Use batpak.

Need sync-first runtime behavior? Use syncbat.

Need explicit network wiring? Use netbat.

Need the live host contract as data? Use hostbat and prove it with cargo test -p hostbat.

Need to run a declared workload under a confined boundary? Use bvisor.

Need conformance or release checks? Use just inspect, just verify, and just seal.

A non-Rust generated-client surface is intentionally out of scope for the pre-1.0 Rust-first line and deferred post-1.0.