HiiLSE parser, simulator or native runtime where built.
HiiLSE Engineering, Programming & Computing
Compiler & Runtime
The runtime layer separates learning analysis from real execution and routes each language only to technically appropriate environments.
23 permanent language tracks
Own editable coding ideas
Runtime truth governance
Old Coding Studio preserved
RUNTIME ROUTER
Real execution is a security boundary
HEPC separates language intelligence from browser execution, secure server execution, local tools and special enterprise platforms.
SourceTokenizerGrammarParserASTSemantic ChecksHEPC Error IntelligenceRuntime RouterExecutionResult
Run locally in a browser using native JavaScript or qualified WebAssembly.
Separate isolated runtime host for untrusted compiled/interpreted code.
Isolated per-user PHP web workspace, never production CMS execution.
Qualified third-party compiler or virtual IDE where appropriate.
User-owned local toolchain; future desktop manager may detect and qualify.
IBM i, z/OS and other environments that require their native platform.
Production isolation rule
Arbitrary learner code must never execute inside the production HDcms process or receive access to HiiLSEDroneKeys, production DB credentials, SMTP secrets, WeR secrets or unrestricted production network/filesystem resources.
HEPC Internal, Browser Runtime, HiiLSE Sandbox, HiiLSE PHP Lab, External Verified Runtime, Local Compiler and Special Platform are distinct execution classes.
Arbitrary user code must not execute inside the production HDcms process or with production secrets. Server execution requires isolation, quotas and controlled networking.
Artifacts differ by language and target. A source editor is not itself proof of compilation or executable generation.
All existing public simulation, Coding Studio, Intelligent Coding and current working pages remain unchanged. New HEPC features start from the new Programming Studio onward.