Authoring

Start with Architect when you want the model-driven app builder path. It turns a product brief and optional context into a generated Pharos app, runs local validation, and writes source plus evidence files for review. The hand-authored tutorials then show how to work directly with the same declarative app surfaces.

Main tutorial path

1. Architect App Builder
2. Todo List App
3. Beacon Beats Audio Store
4. UCAL App

Authoring references

1. Dynamic Apps
2. Static Apps
3. dev_docs

What these pages are for

Use these pages when you want to study a specific app shape more closely:

• how Architect creates a model-driven generated app and records validation evidence
• how a dynamic Pharos app declares routes, actions, data, workflows, integrations, and templates
• how a static Pharos app packages content and assets into a served artifact
• how the documentation app maps Markdown into a navigable Pharos site
• how app-owned files stay separate from framework-owned runtime behavior
• how built artifacts land under dist/apps/

Related docs

• Declarative CRM: schemas, actions and UI
• Tutorial
• Architect overview
• Build a database-backed Todo List
• Build the Beacon Beats audio store
• Build a scheduling and workflow app
• Why Pharos changes the app boundary