honest framework
Start here,
Rails developer.
The framework concepts map directly to what you already know. The reading order below is chosen for Rails developers: start with the persistence layer where the differences are most concrete, end with the client-side model where they are most radical.
Recommended reading order
01
02
03
04
05
06
Why should I care?
The bugs that disappear. The bugs that remain. The benchmark numbers, run yourself.
honest-persist
You know ActiveRecord migrations. This replaces them entirely — declare the schema you want, the diff is computed.
honest-type
You know strong parameters. This replaces them with one classify() call at the boundary.
honest-features
You know Flipper. This is simpler: one endpoint, one dict, no database required for the flag state.
honest-observe
One append-only event log spanning browser and server. State is a projection, not a snapshot.
DATAOS
You know UJS and Turbo. This is the same instinct formalized: let the server own the state.
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.