Blueprint Tutorial

Build an Operations model, extend it through modules, and connect it to a server and UI. Start with fields and entities, then add actions, permissions, and history.

Before coding, request package access, review the package map, and follow developer setup.

Learning path

Stage	Chapter	Tangible result
1	Think in Blueprint	Separate declaration, configuration, and execution.
2	Fields, types, and rows	Declare typed, reusable field tokens.
3	Facets and entities	Assemble one entity from coherent facets.
4	Relationships and projections	Connect entities without leaking raw IDs into the UI.
5	Actions, rules, and lifecycles	Declare governed behavior without domain-specific runtime code.
6	Modules and assembly	Compose bounded contexts and cross-module contributions.
7	Database and security hints	Lower declarations into a secure physical plan.
8	UI, queries, and forms	Generate adaptable UI while retaining extension points.
9	Actors, work, and policy	Resolve who may act and how work is assigned.
10	Runtime execution	Turn an action request into an ordered transaction.
11	Evidence, audit, and replay	Preserve who, when, what, where, and why.
12	Extension points	Add behavior without weakening the typed core.
13	Operations capstone	Put the core language together.
14	Governed revisions and database inspection	Evolve controlled records while inspecting the exact generated schema.
15	Authentication, IAM, and electronic signatures	Connect identity, product authorization, sessions, and signed actions.
16	Semantic composition and catalogs	Build reusable semantic Dart types and close the supported runtime type set.
17	Executable entity queries	Execute and subscribe to one immutable query contract across transports.

Start small

Follow the first eight chapters to build your first model. Use the later chapters when your application needs those capabilities. Each chapter includes examples and a short checkpoint.

Begin with Think in Blueprint, or read Why Blueprint for the ideas behind it.