I build infrastructure for AI-native workflows where state, provenance, replay, and human control matter. My background runs through mortgage origination, bookkeeping operations, retail field technology, SMB systems, and now Rust/TypeScript software infrastructure. That weird bridge is the point: I build tools for the messy seam where software has to explain what happened, who approved it, what changed, and why anyone should trust it.
Currently building with The Free Battery Factory, a software systems lab focused on audit-grade event history, adaptive workflow surfaces, deterministic replay, release-gated packages, and evidence-bearing runtime boundaries.
- Personal site: heyoub.dev - Eassa Ayoub, AI workflow infrastructure and systems builder
- Systems lab: freebatteryfactory.com - The Free Battery Factory
- batpak docs: batpak overview - append-only event history, receipts, replay, and proof surfaces
- LiteShip docs: LiteShip overview - adaptive projection for CSS, GPU, ARIA, AI manifests, and runtime surfaces
| Project | What it is | Why it exists |
|---|---|---|
| batpak | Rust crate family plus TypeScript SDK for append-only event history, typed payloads, hash-chained ancestry, receipts, deterministic replay, projections, and network/host boundaries. | To make AI and workflow systems answer: what did the system know, when, and why? |
| LiteShip / CZAP | TypeScript adaptive projection framework that turns continuous signals into named states, then casts those states to CSS, GPU, ARIA, AI-readable manifests, TypeScript unions, and runtime outputs. | To stop UI, accessibility, automation, and agent-facing state from drifting into five different half-truths. |
| heyoub.dev | Personal site and dogfood surface for LiteShip/CZAP. | The site should not merely describe the system. It should run on the system. |
What does Eassa Ayoub do?
I build Rust and TypeScript infrastructure for AI workflow systems that need declared state, provenance, deterministic replay, release gates, human-in-the-loop controls, and inspectable evidence.
What is batpak?
batpak is an embedded, sync-first append-only journal for tamper-evident event history. It focuses on typed events, receipts, hash-chain ancestry, deterministic replay, projections, and explicit host/network boundaries.
What is LiteShip/CZAP?
LiteShip, powered by the CZAP engine, is an adaptive projection framework. It lets a workflow or web surface define a small number of trustworthy states, then project those states consistently across CSS, GPU, ARIA, AI manifests, TypeScript, and runtime outputs.
What problems am I best suited for?
Mortgage/fintech AI, document workflows, compliance traceability, AI workflow infrastructure, SMB systems, borrower intake, operator dashboards, provenance, release gates, and trust boundaries.
Rust, TypeScript, Effect, Astro, React, Vite, Vitest, Playwright, Node.js, pnpm, Cargo, event sourcing, append-only journals, canonical encoding, receipts, hash chains, deterministic replay, projections, release gates, package publishing, CI, property tests, fault testing, mutation testing, semver checks, and operator-readable docs.
Before building software systems, I worked inside the systems software usually forgets: mortgage pipelines, borrower communication, document collection, compliance-sensitive workflows, bookkeeping operations, SMB tooling, retail hardware, low-voltage installs, and field tech handoffs.
That is the lens: build software that respects the operator, preserves evidence, and does not hide its state in a fog machine.
- Site: heyoub.dev
- Email: hello@heyoub.dev
- Lab: The Free Battery Factory
- GitHub org: freebatteryfactory