Package and model loading

Documentation status: guide — see Maturity and evidence.

A model becomes visible only after the application configuration activates the package that contains it and the package manifest exposes the corresponding model item.

Use this diagnostic chain:

configuration selected
  -> package enabled
  -> manifest entry visible
  -> model compiled
  -> conceptual graph initialized
  -> class/concept resolvable
  -> view and service bindings usable

A runtime smoke test should look for checkpoints equivalent to:

Loading application file
Loading package ...
Compiling package item ... ClassItems.manifest ...
Compiling model ...
Start initializing/updating semantic Hypergraphs
End initializing/updating semantic Hypergraphs

If the model never appears in this sequence, fix package or manifest assembly before debugging actions, services, or persistence.

For first-run troubleshooting, use the memory configuration before introducing persistent storage or externally published services.