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

How does a value become local state?

Follow a real proposal, signed votes and certificates through a local C3 transition, refusal or reload.

  1. 01Proposal + four signers
  2. 02LockQC → CommitQC
  3. 03Local apply or refusal
Implementation & contract

issue_nqfc_c3_proposal, durable Lock/Commit vote callers, certificate assembly and apply_nqfc_c3_commit_certificate_durable.

The Lab uses four synthetic local signers, unit weights and quorum 3. Commit binds the exact LockQC witness; fixture digests do not execute DA.

Run the existing case

Choose Finalize, Block a conflict or Recover. Recovery reloads local state and redistributes the retained witness; it is not process-crash or multi-host qualification.

Where to read the result & proof

Select a returned event to inspect its signer, observed state and public artifacts. Execution details contain the original record and downloads; animation speed is not protocol latency.

Who uses this?

A consensus or reliability engineer examines one concrete transition and its safety/recovery boundary.

Context, results & evidence
CURRENT WORKSPACE

Component details

Run an admitted GLAP scenario to capture a native result.