GuardLaticeNATIVE LAB
Modules
WORKSPACEDocumentation
Documentation
DOCUMENTATION / NATIVE PATHS

One question. A path you can inspect.

Understand the contract. Try an existing case. Read its own result.

Explore the eight starting questions
SELECTED QUESTION

What does this program return?

Edit real GL-C, compile it through GL-Core, then inspect its returned value or native refusal.

  1. 01GL-C source + arguments
  2. 02Compile & run
  3. 03Value + original artifacts
Implementation & contract

GL-C compilation and checked IR execution; Prepared::call is the native execution boundary.

The Studio admits Bool/Int arguments and a selected 4, 8 or 16 KiB source profile. An accepted Bool false is a value, not a refusal.

Run the existing case

Choose a preset or edit the source. Only Compile & run requests execution; no customer state is changed.

Where to read the result & proof

Read the native report beneath the editor. Its original downloads bind source, arguments, profile and returned artifacts; they are not a proof of every program.

Who uses this?

An application engineer checks a small calculation and its failure boundary before choosing an integration.

Context, results & evidence
CURRENT WORKSPACE

Component details

Run an admitted GLAP scenario to capture a native result.