honest framework
Start here,
Go developer.
The framework concepts map directly to what you already know. The reading order below is chosen for Go developers: start with the type system, which will feel familiar, end with the client-side model, which formalizes what server-rendered Go already implies.
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-type
You know interface assertions and switch statements. This replaces the switch with a map lookup — same guarantee, no branching.
honest-features
You know build tags. This replaces compile-time flags with runtime flags, toggled without rebuilding the binary.
honest-persist
You know golang-migrate. This replaces numbered migration files with a schema diff against the live database.
honest-observe
Append-only event sourcing: state is a projection. slog tells you what happened; this tells you why.
DATAOS
You know server-rendered HTML. This names the principle behind it and makes it enforceable.
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.