Artifact
Execute a defined component.
The runtime receives the portable unit produced by the compiler path.
Declared inputSecurity
Isolation is part of the execution model—not an add-on page.
Hyjal creates a fresh runtime boundary for each request and discards it after the work completes.
Keep the runtime boundary narrow and explicit.
Security reasoning starts with what enters an instance, what can persist, and when the instance ends.
Instance
Create a fresh boundary.
Each request receives isolated execution rather than shared application memory.
Fresh runtimeCompletion
Discard the boundary.
The instance lifecycle closes after the work returns.
No warm stateInspect the isolation boundary from the inside out.
The boundary view makes the verified runtime claims clear and leaves unsupported claims out.
REQUEST
InsideOne request’s execution
Application code runs within a fresh instance boundary.
ScopedEdgeDeclared runtime interfaces
The component interacts through the platform contract.
ExplicitAfterThe instance is discarded
Execution state does not become a permanent warm process.
ClosedBring the workload’s real security questions.
Review the runtime model with the Hyjal team before making an architecture decision.