Support

Licence issues

The ULM-PD Engine performs all licence validation locally. If a licence problem occurs, the engine will refuse execution with a clear error. This behaviour is expected and intentional.

Step 1: Ensure you have a valid licence

• The ulmpd.lic file exists in the ./licence/ directory
• The licence has not expired
• The licence matches the product and domains you purchased

If a licence is expired or incorrect, the engine will refuse to run. No partial execution occurs.

Step 2: Rebind the licence (most common fix)

If the engine reports a licence or binding error, delete the local binding file and run the engine again.

licence/.ulmpd.bind

When the engine is restarted, the licence will automatically rebind to the current machine.

This resolves the majority of licence-related issues, including:

• Hardware changes
• Licence renewals or reissues
• Corrupted or stale binding files
• Accidental copying of engine directories between machines

Important notes

• Deleting .ulmpd.bind is equivalent to explicitly rebinding the licence to the current machine.
• This is the only supported recovery mechanism for binding-related issues.
• No internet connection is required for licence validation or execution.

What support does not need to do

The ULM-PD Engine enforces correctness structurally. In most cases, no manual intervention is required.

• Licences do not need to be regenerated for routine issues
• Machine identifiers do not need to be inspected
• Cryptographic mechanisms do not need to be debugged
• Invariant systems do not need to be explained to resolve licence errors
• Log files do not need to be shared for standard licence recovery