H-Logic-first workflow

Documentation status: guide — see Maturity and evidence.

Use H-Logic-first when semantic ambiguity and consistency are more dangerous than delayed UI delivery.

Construction flow

1. Write a compact business specification without implementation terms.
2. Normalize vocabulary and record synonyms.
3. Decide which concepts need durable identity and which are pure relations or conclusions.
4. Declare foundational types before structural use.
5. Mark complete vocabularies only when they are truly closed.
6. Carry time, context and provenance through rules when conclusions depend on them.
7. Express replaceable calculations as typed support relations.
8. Represent invalid states as positive diagnostic facts when they must be queried or explained.
9. Derive indexed projections from real query patterns rather than speculative optimization.
10. Define expected deductions before model generation.
11. Pass explicit validation gates.
12. Generate declarative model skeletons using a reviewed generation policy.
13. Add operationalization only where a declared action or support relation needs concrete execution.

Business verbs and operationalization

Business verbs such as Validate, Compute, Reserve, Approve, Publish or Notify should become declared actions before implementation code is introduced.

ontology verb -> declared action -> candidate operationalization -> minimal implementation

This keeps custom code at the edge of the conceptual model rather than making code the only place where business meaning exists.