1. Session & sourceGlapRootBinding

   The Lab acquires its private slot, creates random session material, obtains the current source binding and opens the local native journal. Measured together at the Lab caller boundary.

2. Packet encoderRoot-bound request v2

   The real action, verb, session, nonce and source binding are encoded into the native request packet. The displayed byte count comes from this buffer.

3. Native runtimeGlapNativeBackend<16,16>

   The existing handle_root_bound_v2 caller receives the actual packet and PublicReadOnly profile. Admission, authentication, catalog lookup and dispatch are inside this measured call; their individual durations are not observed.

4. Same-packet replaySame runtime + same bytes

   Only the replay scenario calls the same native runtime a second time with the exact same packet. Other scenarios display Not called, never a fabricated zero-duration invocation.

5. Response verifierGlapNativePacketOutcome

   The Lab checks the expected native class/error and zero effects, then encodes, authenticates, decodes and compares the actual response fields. It reports the digest and exact response bytes.

6. Owned cleanupCompleted private slot

   After dropping the runtime, the Lab validates and removes only its completed synthetic journal files and slot. Failed namespaces remain preserved.

7. Admission & catalogBounds · replay · auth · root

   The selected runtime caller invokes admit_packet_with_body_validator, resolves the action and checks source/catalog binding. This is source architecture inside one runtime call, with no separate live stage events.

8. Local journalPrivate run state

   The selected run owns a local journal and replay bookkeeping. This is a bounded isolated Lab namespace, not a customer database or a remote validator node.

9. Executor boundaryGL-T / GL-DDBS: None

   This Lab passes None for observed trust, trust admission and GL-DDBS executor arguments. Customer data writers, operator Health and consensus-network telemetry are not connected by these requests.

Selected source SHA-256: 12d5f0dde2c4ea2454fba7c9d30a70b6857986cb888ea9825926ac82db101bff. The Lab calls the retained native binary; this graph is not an inventory of every deployment component.

1. ProposalNqfcC3Proposal

   issue_nqfc_c3_proposal binds the chain, epoch, height, round, registry, checkpoint and value. The registry and signed checkpoint dependencies are separate inputs.

2. Lock voteNqfcC3PhaseVote

   sign_nqfc_c3_lock_vote_durable verifies proposal/state/registry, derives the Lock context and delegates to issue_phase_vote_durable. A signed slot is persisted before returning the vote.

3. LockQCPhase certificate + witness

   assemble_nqfc_c3_lock_certificate aggregates verified votes. The exact certificate-body digest is distinct from the certified context digest.

4. Commit voteDurable matching lock

   sign_nqfc_c3_commit_vote_durable verifies the supplied LockQC, carries its exact witness, records the local lock and persists the signing transition before returning.

5. Registry & cryptoWeights · signatures

   Registry binding, phase vote verification and checkpoint signing/verification are actual dependencies of these callers. Drawn nodes do not denote a real validator population.

6. Persist transitionNode state publication

   issue_phase_vote_durable and local apply both call persist_state_transition. Local memory is replaced after the durable operation returns successfully.

7. Local applyLock check → persist → memory

   apply_nqfc_c3_commit_certificate_durable verifies proposal and both certificates, requires the matching durable local lock, prepares the next height, persists it, then updates memory and clears the completed lock.

8. CommitQCExact LockQC witness binding

   assemble_nqfc_c3_commit_certificate verifies the supplied LockQC and builds the Commit context with that exact justification witness. Local application remains a separate operation.

9. Timeout pathSeparate round transition

   Timeout voting, certificate assembly and application have their own checked path. A successful diagram traversal does not establish distributed safety, liveness or recovery.

Selected source SHA-256: bec98a1073f5dc1344bc9b72aeaacea3191da8a02f120217ea54219e98f0a5c2. No validator network, operator state or live C3 event stream is connected to this view.