Developer notes

These documents are for framework contributors and maintainers. They distinguish current architectural constraints from proposed APIs and remaining work.

Architecture

• Principles defines the constraints intended to survive API changes.
• Compiler pipeline defines Go/TypeScript ownership, artifact invariants, protocol lifecycle, and validation.

Current package boundaries and targeted development commands remain colocated with their source:

• packages/core — application and request lifecycle.
• packages/compiler — compiler process and Vite integration.
• packages/typed-handlebars — language tooling.
• compiler — Go compiler and wire protocol.

Proposals

These pages contain design direction and draft syntax. They may describe behavior that is not implemented:

• Authoring model
• Execution model
• Project organization
• Web Components
• Draft API

Roadmap

• Framework capabilities distinguishes implemented behavior from the remaining full-stack framework work.
• Compiler roadmap prioritizes contract, typechecking, parsing, interactivity, composition, and operational work.
• Open questions records decisions that are still unresolved.

Before promoting proposal material into a guide or reference page, make the behavior executable in the workspace and update its status explicitly.