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

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

Debt

Needs sign-off

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

  1. A clean playground. rat-stack does real work with packages that stay easy to add and remove.
  2. Agent rules for rat-stack (AGENTS.md). What you may change, which commands to run, and which changes need approval.
  3. Build and run rat-stack (README.md). What is in the repo, how the example works, and how to run it.
  4. Effect + Alchemy peer patterns. Source-grounded patterns from repos on nearby Effect and Alchemy pins.
  5. learn-alchemy. Learn how Alchemy 2 turns an Effect program into a planned Cloudflare deployment.
  6. 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".