NIMOS / ENGINES / ASTE
← THE BUILD SYSTEMASTE
THE SAFETY NET
Automation, State & Testing
The automation, state and test layer that makes 'it works' a measured sentence.
DRAWN BY THE HOUSE
One mark per engine, on one grid, in one hand.
10
TOOLS
PROJECT
WIRE
USED
THIS BUILD
The test runner is present and the release gates run through it.
THE PROOF LEDGER →WHAT
What it is
Ten tools: Zustand, Jotai, XState, Immer, zod-to-json-schema, Playwright, Cypress, ESLint, Prettier and MSW.
WHY
Why it exists
Nothing ships without the verification corridor. Gates are cheaper than incidents, and deterministic state is cheaper than a bug you cannot reproduce.
HOW
How it runs
npm into projects; Playwright drives the corridor; mocks stay truthful to the real API; lint and format are part of the release, not a suggestion.
WHEN
When it runs
Statechart work, release gates, staging mocks, lint/format hooks and end-to-end tests.
WHO
Who owns it
CEO owns the gate; Research watches the testing ecosystem; Build writes suites and stores; Data keeps pass/fail and flake history; Ops blocks red builds.
TOOLS
The registry
The engine manifest is the source of truth. These are its entries, including the ones that are not used on this build — the proof ledger says which is which.
zustand
npmExtremely lightweight state stores minimizing component re-renders.
jotai
npmAtomic state management for multi-layered designs.
xstate
npmFormally structured state models for intricate view states.
immer
npmStructural state handling via immutable copy updates.
zod-to-json-schema
npmValidation boundaries → structural configuration templates.
playwright
npmComplete automated view-interaction validation suites.
cypress
npmFunctional user-behavior testing for interface paths.
eslint
npmStandardized structural balance auditing.
prettier
npmCode-style unification across teams.
msw
npmMock service workers simulating API networks during local staging.
10 registry entries. The proof ledger on the Gantry page says which of them this build actually used.
RUN
Run it
ENGCTL / THE ENGINE FLOOR
$ engctl show aste$ engctl awaken aste$ engctl install aste --dir ./site`engctl` is the registry control surface. `awaken` checks wiring before it activates a cell; `install` writes the parts into a project.
PROOF
On this build
The test runner is present and the release gates run through it.
N/A and PARTIAL are stated, not hidden. The ledger is generated from this project, not from a template.
LIMITS
What this does not claim
USED for the test runner; the engine has more tools than this site's proof ledger exercises.
The engine is the how. The brief is the start.