Declarative application development

Documentation status: guide — see Maturity and evidence.

This section is the practical developer companion to the declarative conceptual programming guide. Its acceptance criterion is operational: a developer using the .NET site must be able to rebuild the same application structures, runtime assembly, publication surfaces, tests and deployment patterns without relying on the book as a hidden prerequisite.

The recommended path is deliberately concrete:

1. Project structure and loading
2. Packages, manifests and applications
3. Models, concepts, facets and relations
4. Constraints, defaults and validity
5. Collections, views and DataSets
6. Views and UX
7. Actions, events and processes
8. Services and publication
9. Runtime execution and contexts
10. Persistence, transactions and consistency
11. Testing, debugging and validation
12. Deployment and distribution
13. External integration and local-first design
14. AI, agents and governed execution
15. End-to-end task application
16. Reproduction checklist

For conceptual logic, continue with H-Logic. For host-language integration, use the .NET SDK, ABI and RPC references.

Fast paths

• Model-first method
• End-to-end task application
• Views and UX
• Actions and events
• Runtime foundations

Advanced worked example

Customer risk management exercises the full chain from conceptual modeling to .NET, AI and regression testing.

Development methodology

Use Development methodology when starting from a business specification or deciding between model-first and H-Logic-first. The Temporal stock analysis case study demonstrates the full H-Logic-first path through validation and model operationalization.