Update integrity

JKPanel Pro's updater architecture is designed around release validation, transaction state and recoverability rather than uncontrolled replacement of live files.

Safe update sequence

1. Identify the target release.
2. Validate the update package and required metadata.
3. Run preflight checks.
4. Create or verify the rollback source.
5. Enter the controlled update transaction.
6. Apply the software change.
7. Validate application and database health.
8. Complete the transaction only after validation succeeds.

Rollback

Rollback should restore from a verified known-good recovery source and should preserve deployment-specific runtime and trust configuration where required by the installed release.

Failure behaviour

A failed recovery or update operation should fail closed rather than silently reporting success.

Security boundary

Public documentation intentionally describes the lifecycle model without publishing private signing material or implementation details that would help bypass update verification.