honest framework

Start here,
Rustacean.

You said you'd rewrite it yourself. Fair. The framework concepts apply regardless of language — here are the patterns in the order that makes most sense for systems programmers.

Recommended reading order

01
Why should I care?
The bugs that disappear. The bugs that remain. The benchmark numbers, run yourself.
 02
Honest Code Principles
The sixteen practices. Rust enforces some structurally; these cover the rest.
 03
honest-type
classify() is a pure function over a finite set. Rust enums are already this — honest-type names the pattern.
 04
honest-persist
Schema as data. Migration as diff. No ORM, no identity map. Raw SQL with typed results.
 05
honest-observe
Append-only event log. State as projection. Every boundary emits automatically.
 06
honest-test
Bounded types give exhaustive enumeration. Rust's Bounded + Enum makes this native.
 07
honest-check
Static verification from dispatch tables. Most HC-P rules are already type errors in Rust.
 08
DATAOS
The DOM is the state. HTMX does the transport. Rust owns the server side.

Also in the framework

honest-features
Feature flags as a handler table. The flag state routes to a handler — no if/else, no hidden branching.
honest-components
Atoms, molecules, organisms. Two mounting behaviors. One CSS namespace per component, for life.