Summary
Point source is organized as semantic blocks. Each block has a dedicated page in this guide with syntax, semantics, and examples from the examples/ directory.
New here? Point in 60 seconds → Golden app demo.
Block map
| Block | Purpose | Guide page |
|---|---|---|
record, variant | Named data shapes and tagged unions | Records, Types |
calculation | Pure derived values | Calculations |
rule | Scoring and accumulation | Rules |
label | Classification to text or other types | Labels |
| Types | Text, Int, List<T>, Maybe<T>, unions | Types |
| Loops and mutation | for each, add to, set to | Control flow |
module, use | Multi-file programs | Modules |
external, action, policy | Effects and boundaries | Effects |
view, page, layout, navigation | UI and app shells | UI |
route, middleware | HTTP handlers | Routes |
stream route | WebSockets and live views | Realtime |
workflow, schedule, command | Orchestration and CLI | Workflows |
pipeline, session, prompt, guard | Agent orchestration | Agents |
First commands
point check examples/math.point
point box examples/command.point
point launch examples/command.point hello cli
point index examples/math.pointAgent note
Run point index <file> to list every declaration with a point://semantic/ ref. Use those refs in explain and repair loops instead of line numbers.