Handbook
Poi is a frontend language whose product is a constraint system. It makes incorrect programs fail to compile — unhandled async, swallowed errors, non-exhaustive branches, unvalidated foreign data, runaway mutation.
Install, compile a .poi file, run the playground.
Why sugar is not enough; why constraints are the product.
What looks like TS, what diverges, what is rejected.
store, getters, reactive let, implicit subscribe.
Import is free; trust is never free.
Habit → Poi path table for React developers.
| Section | Purpose |
|---|---|
| Handbook | Positioning, constraints, entropy × AI |
| Get Started | Install, playground, editors |
| Guides | Syntax, reactivity, interop, migration, scaffold |
| Reference | Keywords, rejections, match/ADT, store, CLI |
docs/08-thesis.md · Constraints: docs/10-constraint-catalog.md ·
Cheatsheet: src/reference/cheatsheet.poi. If a doc and a .poi file disagree, the .poi file wins for “what compiles.”
The Rust of frontend — but the safety is logical, not memory.