com.freebatteryfactory/docs

List the Free Battery Factory products whose documentation is hosted here, each with a one-line blurb, current docs version, and canonical URLs. Presence here means the docs are published, not that th…

Full-text search across the product documentation. Returns the best-matching pages with title, description, canonical URL, matched section headings, and a snippet. Omit `product` to search every produ…

Fetch a single documentation page as Markdown, given a product id and a page slug (both come from list_products / search_docs results, or a doc URL like /liteship/overview). Returns the title, descrip…

Return a link to the complete, source-linked agent reference (llms-full.txt) for a product — its entire prose, API surface, and examples in one document. This file is large, so it is returned as a res…

Describe the adaptive dimensions of this site's pages: each named layout regime, the states it can occupy, and the signal and thresholds it is carved from. These are the same boundary definitions that…

The structural map: what the pieces are and how they fit. This doc explains the system on its own — the ADRs record why each choice was made, but you shouldn't need them to unde…

How LiteShip sits inside an Astro site: where the document host ends and the CZAP runtime begins. Imports stay on @czap/; export names like czapMiddleware() stay literal.

How to think with LiteShip when building visually rich Astro websites. The CZAP engine evaluates boundaries, casts styles, and keeps the working deck trim; you still install and…

The monorepo ships a native audit lane that extends the existing build, typecheck, coverage, benchmark, and runtime-seam feedback loops.

How to author with LiteShip: the CZAP engine's rigging surface, shipped as @czap/ packages.

Part of LiteShip: the CZAP engine's capsule and scene assembly. Vocabulary: GLOSSARY.md.

This file is the shortest route to the right document.

From pnpm add in your Astro project to a boundary changing state as you drag the window edge, in about five minutes. Two concepts get you there: Boundary.make and satelliteAttrs…

Vocabulary for prose across this repository. Technical identifiers (Boundary, @czap/core, czapMiddleware, --czap-, host-wired, CLI czap, ...) stay exactly as shipped; this file…

LiteShip runs inside the host application's security boundary: the host's CSP, the host's Trusted Types policy, the host's runtime endpoints. This page is the minimum host check…

This document maps the main @czap/ compartments in the repo: the hull sections you import from.

LiteShip is constraint-based adaptive rendering — a multimedia-native UI compiler/runtime (not a component library). It quantizes continuous signals (viewport, scroll, motion pr…

Verified against the 0.9 completion campaign (2026-07-13, v0.10.0 tree). See STATUS.md for live counts, gate totals, coverage numbers, and current telemetry watch items.

This file is the tacit knowledge for working on LiteShip: the laws we learned by breaking things, abstracted so they outlive any one version. No public training data covers this…

Last updated: 2026-07-13 (v0.10.0 tree; the completion cut landed the semantic-truth pass — see below).

This tree is generated from TSDoc on the @czap/ packages: the compartments that implement the CZAP engine (Content-Zoned Adaptive Projection). LiteShip is the product name; impo…

Complete source-linked reference for LiteShip.

Free Battery Factory builds small sync-first batteries for software boundaries.

batpak is a sync-first embedded event substrate for recording, linking, replaying, verifying, and projecting local application truth.

This file is narrative ordnance: short, human-readable rules for the current substrate.

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

A terminal is a named boundary where a battery accepts, denies, emits, or observes work.

An event records a domain fact at a coordinate.

Receipts are structured evidence of outcomes.

A circuit is a bounded route through which work, state, or evidence moves.

Replay reconstructs state from events.

The log is the source of truth. A projection is a cached interpretation.

batpak owns a local truth boundary per journal: one Store, one datadir, one exclusive writer. That scopes source truth to a single append-only journal; it does not mean distribu…

Conformance is the factory contract made executable.

Claude Code auto-loads this file. The authoritative, tool-agnostic operating doctrine for this repository lives in AGENTS.md (shared with Codex and other agent tools). It is imp…

One screen to find the right door. batpak's reading surface is the README plus twelve numbered guides; pick the path that matches your intent — nobody is required to read all of…

batpak is an embedded, sync-first event store for Rust: an append-only, hash-chained journal with typed events, verifiable receipts, deterministic replay, and derived projection…

This is a living document. It is re-audited every time a line item lands: knock an item, re-read its section, promote/demote what the change revealed. Items are owner-gated — no…

Complete source-linked reference for batpak.

Code generation that can prove what it made, and a test harness that tries to break it.

The compiler. A complete request goes in; one sealed expansion comes out, or one diagnostic that says exactly why not.

The taste tester. It has no loyalty to the baker, no opinion about the recipe, and it records everything.

A proc-macro crate may export nothing but macros, so this one is small on purpose: token conversion, span custody, one call into the compiler, diagnostic placement, emission. It…

This home makes a collection's maximum cardinality part of its Rust type and keeps every field behind the constructors that establish that cardinality.

A plan is written before anything exists. A rendering is what a renderer actually produced. This home is where the two meet, and it does not ask the renderer whether it obeyed.

The codec kind: one declared shape in, the Rust that writes its canonical bytes and reads them back out.

Most of this compiler knows nothing about what it is generating. This home is the bounded first-party adapter: it targets the public macroonz-harness constructor surface and the…

A request that fails any step is refused whole, and this is the value that says why.

An expansion is the point at which one request's plan, proof, and explanation become one result that may release generated material.

Anything this compiler produces can be held to account, and this is where it answers.

The one place in this crate that names a compiler's own token type.

Thirty-two bytes that say which thing this is, and a transcript that says why.

What you are generating, declared once, in your own crate.

Generated material must account for how it was derived from authored material. An origin trail records that derivation as a directed walk from producing nodes toward produced no…

A plan is the complete output set of one request, named before a token of the target language has been written.

A plan names what should exist before any target syntax does. A rendering records what a renderer actually produced.

A request is what you hand this compiler, and an expansion is what comes back. This home owns the consumer-declared door and the complete walk from captured meaning to a sealed…

Some output cannot be written where a declaration stands.

A declaration expands where it stands, while some of its generated material belongs only in a test or benchmark target. Compiling that material in the declaring crate as well as…

What a producer hands the compiler, and what a renderer hands back.

A wall-clock number on its own is a rumor.

This home turns one caller-declared source into a typed elapsed reading. It owns the boundary discipline around that source and no theory of what time means to the caller. Nothi…

A seed pack carries inputs worth keeping from one search into a later one.

Some harness facts are authored rather than observed.

A test nobody wrote down is a test nobody can count.

Adversity you schedule, not adversity the harness invents.

This home turns stable rustc source coverage into a bounded search signal while leaving Macroonz's existing corpus, generation, reporting, reduction, and replay owners in charge…

The generation road turns a declared search into deterministic inputs and an honest account of every case it reached. The reduction road turns one recorded failure into a smalle…

An address is blake3::derivekey over a preimage, under a context assembled from one stem, the minting home's DomainTag, and the position that tag carries. Separation is by deriv…

This home treats a schedule as declared input and judges command-order concurrency without running threads or reading a clock.

The engine that damages a subject on purpose, to find out whether anybody would have noticed. Say it like mutater crossed with interpreter, because that is what it is — the inst…

The network home composes deterministic simulation with addressed transcript custody behind one public road.

Most of the harness judges a subject against laws its owner declared. This home exists for the claims where that is not enough: where the only thing available to check an answer…

The schedule inside one operation is an input.

A check answers one question about one input. A property states a law over a population, a relation, a wiring, or a history and turns a counterexample into typed evidence.

A trial executes once and then it is gone. The report preserves which trial ran, the revisions and invocation it stood on, where it was written, and what became of its attempt.…

The runner is the harness's execution engine. It receives the complete authored world, a declared selection over that world, and one invocation, then returns a report without di…

One declaration binds two inseparable outputs: a stamped benchmark table and a typed report reader. They travel through one carrier and one generated-support pin because either…

This home projects declared interleaving explorations into ordinary Rust at the declaration site.

A proc host converts tokens and preserves compiler spans, while each descriptor child owns the grammar and rendering for its projection. This home owns the orchestration between…

One declaration in; one module out, delivered as deferred cargo the consumer's test target invokes.

A direct network declaration becomes the harness builders its declaration site compiles.

One declaration, two synchronization worlds.

This home answers how one authored trial declaration becomes a harness trial-table payload without letting the author claim producer or consumption-target facts.

The descriptor adapter emits ordinary Rust expressions that reach the harness through public constructors, readers, closed-choice arms, stamp clauses, and operation roads. This…

This private home owns the checked join, duplicate-consumption prevention, destination coherence, and the complete support assembly. It depends on cargo and does not render or d…

This private home owns declared and deferred cargo, their proved parentage, promotion, and the complete axis set. It reads exact material from closed deliveries and does not ass…

This private home owns the exported shell, its plan-keyed name, rendering, and delivery. It depends on verified assembly and lower cargo but neither proves nor assembles cargo.

This home owns the normalized declaration the compiler receives, the bounded builders that make it, literal capture, text lexing, source coordinates, and canonical captured iden…

This home owns the bounded token tree a renderer writes, its pure composers, its canonical identity bytes, and its human-readable source projection.

This private child owns the facts an authored benchmark row states and the identity derived from those facts.

This private child owns the work a benchmark callable may record and the judgment an owner may make over the measured and planted-worse curves.

A human admits a finding, and the run that produced it has to outlive the admission.

Mutation pressure needs a stable vocabulary for the generic kinds of damage it can attribute without inventing subject meaning.

Some harness values look alike while carrying authority that must never substitute for one another.

The input-generation owner turns a declared search into deterministic structured inputs and a complete accounting of every case it reaches.

The reduction owner searches for a smaller input that still produces the fingerprint carried by one refused trial report.

The typed reading and custody of pressure imported from an external mutation backend.

Discovery is the private noun home for owner mutation policy, producer discovery, policy admission, executable evaluation surfaces, selections, resolved mutations, and evaluatio…

Interpretation owns production and evaluation call types and bindings, observations, evaluation pairs and their standing, mutation witnesses, no-mutation results and parity, int…

The scope, budget, and inspectable plan vocabulary an evidence road uses before it spends anything.

This home owns the semantic vocabulary and invariant nucleus for turning observed openings into reviewable proposals and for the explicit human-admission operation over a review…

Rewrite owns structural mutation descriptors, their refusal-ordered guards, declared descriptor rosters, audit candidates, admission posture, and the artifact-mutation seed voca…

Specimen owns exact compiled pressure over one separately materialized, production-shaped selected projection.

The verdict report carries the four verdict-chain evidence axes: materialization, activation, execution, and outcome, alongside its baseline and scoped equivalence.

Deterministic message passing is a declared value.

A transcript binds source-specific material and delivery lineage to one content address.

This home compares a caller-reported compiler observation with behavior the caller declared independently.

This home maps rendered Rust through a foreign parser and compares the resulting syntax with a caller-authored declaration.

This home writes a published preimage grammar from typed caller arguments and derives the identity that grammar names.

This home reads golden vectors written from a specification and compares one producer result with the exact bytes stated for that input.

Complete source-linked reference for Macroonz.