Operational diagnostics

Documentation status: guide — see Maturity and evidence.

Diagnose the assembly from the inside out. Do not start with the external endpoint when the model itself may not be loaded.

configuration
  -> package
  -> manifest
  -> model compilation
  -> graph initialization
  -> runtime resolution
  -> data/view binding
  -> persistence
  -> service publication

Separate these failure domains:

• configuration parsing or missing parameters;
• package/manifest resolution;
• model compilation and conceptual initialization;
• database mapping and persistence;
• service registration and startup;
• remote endpoint availability and transport;
• application-level validation or authorization.

For deployment readiness, process liveness is insufficient. Readiness should prove that required model packages are loaded and the runtime capabilities needed by the application can actually be resolved.