Global State

Global State is a real-time health snapshot maintained by the TechUI Wasm core during runtime.

For security reasons, the Core module does not directly expose its internal raw memory structures. Developers with authorization can obtain a preliminarily de-sensitized summary of the system state via the tuiCoreInfo('pandoraKey') interface.

The pandoraKey must be requested from a sales manager and has a limited validity period (typically a few minutes to an hour). This information is primarily used for troubleshooting and authorization confirmation during the development phase; under normal circumstances, there is no need to view the state information within the Wasm.

For the Free Version, there is absolutely no need to view the internal Wasm state because the entire licensing mechanism remains in a dormant state.

Because exposing the internal state of the Wasm could potentially lead to reverse engineering, the content of this chapter is presented as an abstract, simplified introduction.

Authorization Summary

The system summarizes complex decrypted key parameters into a set of readable identity information used to confirm "who is currently using the system".

State Item	Description	Example Value
License Type	The grade of the currently loaded license.	Commerce
Holder	The name of the authorized legal entity.	TechUI Studio
Status	Integrated authorization status.	Active / Expired
Region	The geographical region where the authorization is effective.	CN-BJ
Binding	Whether strict binding mode (domain/project) is enabled.	Yes

Note: If a Sub-License exists, the system will additionally display the authorization status of the "End Customer".

Health Diagnosis

The Guard subsystem monitors security indicators across multiple dimensions in real-time and summarizes them into the following health states. In debug mode, any anomaly will cause the status to become Abnormal and trigger corresponding protection mechanisms.

🛡️ Integrity

• Environment Fingerprinting: Detects whether the running environment (Browser/Electron) meets expectations.
• Native Interfaces: Monitors whether native browser APIs such as fetch, Date, and setTimeout remain pure and have not been tampered with or hooked by third-party scripts.
• Core Hash: Validates the integrity of the Wasm binary code in memory to prevent runtime modification.

🌐 Environmental Compliance

• Domain Whitelist: Checks whether the current running hostname is in the authorized list.
• Deployment Location: Detects if an "Intranet-only authorization" has been illegally deployed to a public network environment.
• Project Consistency: Validates whether document.title contains the bound project identifier (only effective in binding mode).

⏳ Timeline

• Main License Validity: Checks whether the current system time is within the authorized period.
• Trial Countdown: Restricted to Prime trial mode, or cases where advanced components are enabled without the component library being authorized.

Core Metadata

Used to confirm the currently loaded Wasm kernel version information, assisting technical support in locating issues.

• Kernel Version: Kernel version number (e.g., v1.0.2).
• Build Timestamp: The timestamp of the build.
• Target Platform: The compiled target component library.