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

Which claim does this result support?

Read the result together with its source, profile, assumptions and original artifacts. Observations, finite certificates and measurements answer different questions.

  1. 01Named input + profile
  2. 02Native execution or verification
  3. 03Artifact + stated scope
Implementation & contract

The Studio uses the existing GL-C/GL-Core caller and canonical artifacts. The Evidence view separately exposes the checked finite UI model.

An observation checksum checks bytes, not independent attestation. A finite-model certificate concerns its named domain, not all runtime code or DLT security.

Run the existing case

Compile one small program, inspect the actual result and download its original artifacts. Evidence in the related catalog explains the separate finite UI certificates.

Where to read the result & proof

Use the downloads in the native Studio report. Never substitute an earlier run's artifact or interpret a diagram as a test result.

Who uses this?

An engineering or release reviewer decides which exact claim can be accepted and what independent check remains necessary.

Context, results & evidence
CURRENT WORKSPACE

Component details

Run an admitted GLAP scenario to capture a native result.