honest framework
Start here,
FastAPI developer.
The framework concepts map directly to what you already know. The reading order below is chosen for FastAPI developers: start with the type system that underpins everything, end with the client-side model that closes the loop.
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 Pydantic. This goes one level beneath it — the type system is your Set declarations, not a class hierarchy.
honest-persist
You know Alembic. This replaces revision chains with a schema declaration. Branches carry their own schema state.
honest-features
You know environment variables. This replaces them with a signed API call. No restart. No redeploy.
honest-observe
Structured events emitted automatically from every boundary — no developer instrumentation code required.
DATAOS
You know Jinja2 and HTMX. This makes the DOM-as-state pattern explicit, testable, and 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.