Application Building Path

Documentation status: guide — see Maturity and evidence.

A full-code application should consume generated/public contracts rather than reconstruct Runtime internals.

Recommended sequence

1. Define or select the conceptual model and package.
2. Build and validate the model before writing host-language orchestration.
3. Generate or consume the supported binding.
4. Obtain the Runtime client abstraction through dependency injection or application bootstrap.
5. Load/query conceptual objects through generated/public types.
6. Implement application policies, UI or services at the boundary.
7. Run the same contract tests against local and remote Runtime adapters where supported.
8. Add health, logging, cancellation and failure mapping before production.

Keep the boundary clean

Do not encode memory addresses, private node layouts, journal formats or implementation-class names in application code. Those belong below the public ABI/binding boundary.