Model-first workflow

Documentation status: guide — see Maturity and evidence.

Use model-first when the application structure is already understood well enough to build a useful system directly from declarative artifacts.

Construction flow

1. Extract business concepts, relations, states and intentions from the specification.
2. Declare the conceptual models and their facets.
3. Add collections, views and DataSets for task-specific projections.
4. Add actions, events and process objects for executable behavior.
5. Publish only stable actions and views.
6. Run the application and collect runtime and user feedback.
7. Refine the model as new business distinctions appear.
8. Generate or write an H-Logic synthesis when the accumulated conceptual surface needs a coherence review.

The important boundary is that the declarative model remains the primary construction surface. H-Logic is not mandatory for the first usable application.

When to synthesize H-Logic

Introduce a semantic synthesis when concepts created by different modules begin to overlap, rule interactions become hard to review, a human or AI assistant needs a compact semantic representation, or the project starts to require symbolic querying and explanations.

The synthesis does not replace the application model. It provides a compact semantic view that can expose missing relations, inconsistent vocabulary and hidden assumptions.