Applications

Summary

Application blocks connect application logic to HTTP, UI, orchestration, agents, and CLI entrypoints. Each area has a dedicated guide page — this page is the index.

Guide pages

When to use which block

• Pure logic — record, calculation, rule, label (see Language overview)
• Side effects — action, external, policy (Effects)
• HTTP API — route + optional middleware (Routes)
• React UI — view for fragments, page for document shells (UI)
• Multi-page app — layout, navigation, multiple page blocks (UI)
• Background work — workflow for async steps, schedule for intervals (Workflows)
• CLI / scripts — command (Workflows)
• LLM flows — pipeline, session, prompt, guard (Agents)

Compiler note

Application blocks share the same check and ref model as logic blocks. Views, routes, pipelines, and commands appear in point index with distinct semantic kinds for agent navigation.

Demo apps

• examples/app/dashboard/ — layout, navigation, data loading, lists
• examples/app/notes/ — database actions in views
• examples/app/log-viewer/ — stream route + subprocess
• examples/app/job-queue/ — SQL-backed jobs queue, routes + workflow runner
• examples/full-stack-template/ — SaaS admin shell
• examples/adopters/hatchingpoint/ — dogfood readiness demo (not the default teaching path)

See also

• Language overview
• Platform vision
• How Point runs
• Examples