Declarative conceptual programming: a short decision map

Documentation status: guide. This summarizes the developer and rich-client LaTeX volumes; exact MODEL grammar and H-Logic syntax remain with their published contracts.

The core shift

A model is not merely a schema for generated code. Concepts, roles, relations, actions, events, views and processes preserve business meaning in structures the Runtime can activate. User interface and service endpoints are projections of that model, not alternative authorities for the same facts.

Two development loops

Start with…	Preferred next step
Clear entities, collections, views and actions	Model-first workflow
Complex relations, constraints or inferential specifications	H-Logic-first workflow

In either loop, validate semantic meaning before deployment. MODEL source, activated APPLICATION metadata and compiled SEMANTIC graph must remain distinguishable. functionalP executes behavior where necessary; it does not replace declarative business meaning.

Client views are projections

The rich-client guide maps model objects to datasets, cursors, ObjectBehind, page controllers, reactive desktop frames and web components. These views have cache, event and lifecycle responsibilities, but should not invent a second model of identity or authority.

Direct implementation links

First verified run · Declarative guide · Views and UX · functionalP · Deployment

LaTeX sources: Declarative .../developer-guide/main-matter.tex; rich-client-view-guide/main-matter.tex; Runtime runtime-overview.tex.