Vision
acidnet is amenoacidsā working estate: the apps he runs, the records of what he runs and pays for, and the stack they are built on, in one repository.
It grew out of rat-stack. rat-stackās own vision, at the commit acidnet started from, is joelhooks/rat-stack VISION.md at b8df5c2. acidnet keeps its stack, its fence50, and its reference code, and writes its own purpose here, as rat-stack asks of every project that grows out of it.
Scope35: everything amenoacids builds and operates himself. That includes apps run from Amp threads and orbs, the infrastructure they deploy, and the registers that describe them.
Audience: amenoacids and the agents that work for him. This is solo work. Nobody else depends on it, and a bad deploy is cheap to roll back.
What lives here
- Apps in
apps/*.session-reviewandstewardrun from Amp threads: they plan and journal, and a person approves before anything changes. - Shared packages in
packages/*. rat-stackās packages stay as the floor. acidnetās own additions arejournal,workspace, andusage. - Registers in
registers/: what acidnet runs (machines) and what it pays for (subscriptions), filled only from evidence. - Evals in
scripts/evalandresults/: whether a steering payload changes how a model behaves.
One repository, so shared code is shared, not copied. A package used by two apps lives in packages/, never as a vendored copy that drifts.
How changes land
- The local gate is the check. Lefthook runs
pnpm checkandpnpm testbefore every commit, and the VCS policy blocks every hook bypass. GitHub Actions runs only when started by hand. - Agents do the work and report it. The owner reviews outcomes, not chores.
- Speed beats ceremony when the blast radius is small. Ask before anything that cannot be undone: deleting data, destroying infrastructure, or spending money.
Debt
- Code folded in from elsewhere may sit outside the strict lint and Effect diagnostics for a while.
AGENTS.mdlists each such path, and the list only shrinks. - New code takes the rat-stack path from the start: a contract, a job-shaped port, an adapter outside core, and an observable outcome.
Needs sign-off
- Turning GitHub Actions back on for push or pull requests, or adding paid compute
- Weakening the local gate or the bypass fence
- Deleting a register entry, a journal, or any recorded evidence
- Destroying or replacing deployed infrastructure
Amendment policy
amenoacids amends this document. Agents may propose changes with evidence.
Last changed 2026-11-11 in 3cbaef0. Source on GitHub. Change log.
Linked from
- A clean playground. rat-stack does real work with packages that stay easy to add and remove.
- Agent rules for rat-stack (AGENTS.md). What you may change, which commands to run, and which changes need approval.
- Build and run rat-stack (README.md). What is in the repo, how the example works, and how to run it.
- Effect + Alchemy peer patterns. Source-grounded patterns from repos on nearby Effect and Alchemy pins.
- learn-alchemy. Learn how Alchemy 2 turns an Effect program into a planned Cloudflare deployment.
- uncomplect. Find responsibilities that a rat-stack design combines, separate them into capabilities, cartridges, machines, features, and clients, and enforce that separation through types and checks. Use when asked to simplify, review, or replace a design, "what would Rich Hickey do", "optimize for deletion", or "define this error out of existence".