honest framework

Start here,
React developer.

The framework concepts map directly to what you already know. The reading order below is chosen for React developers: start with what will feel most familiar, end with what will feel most liberating.

Recommended reading order

01
Why should I care?
The bugs that disappear. The bugs that remain. The benchmark numbers, run yourself.
 02
DATAOS
You know useState and useEffect. This eliminates both. The DOM is the state. There is nothing to synchronize.
 03
honest-observe
One event log for browser and server, joined by request ID. What Redux DevTools tried to be, but for your whole stack.
 04
honest-type
You know Zod. This is runtime classification without the schema object — the type IS the Set.
 05
honest-features
You know LaunchDarkly. This runs in your process, costs nothing, and toggles without a redeploy.
 06
honest-persist
You know Prisma migrations. This replaces the file chain with a schema diff. No V001, V002, V003.

Also in the framework

honest-test
Exhaustive enumeration from finite vocabularies. Not sampled — every valid input, every time.
honest-check
Static verification from dispatch tables. No type annotations required. The linter reads your vocabularies directly.
honest-components
Atoms, molecules, organisms. Two mounting behaviors. One CSS namespace per component, for life.
Honest Code Principles
The sixteen practices that make code honest. The prerequisite for everything else.