Skip to content

Console Walkthrough

Use this page the first time you open http://localhost:3000. The goal is to connect what you see in the console with the Stackfile and guard decisions you are learning.

Start The Runtime

make run

Open:

  • Console: http://localhost:3000
  • API docs: http://localhost:8080/docs

Expected result: the console loads and shows a connected or ready runtime state.

Check The Current Cycle

Look for:

Panel What it tells you
Risk gauge Current risk level: normal, elevated, critical, or emergency
Stats cards Cycle count, reject count, clamp count, and average latency
Guard status Latest decision per active guard
Event log Recent pass, clamp, reject, or control events

You are not trying to memorize every field. You are learning how to answer: did DAM allow, modify, or reject the latest action?

Read A Guard Decision

Use this pattern:

  1. Find the latest non-PASS event in the event log or guard table.
  2. Read the layer: L0, L1, L2, or L3.
  3. Read the guard name and reason.
  4. Open the Stackfile and find the matching boundary or guard layer.
  5. Decide whether the event is expected for the current run.

If the event names a boundary, search the Stackfile for that boundary name first.

Check Latency

The cycle latency panel tells you whether DAM is staying inside its time budget.

Signal Meaning
OK Healthy timing headroom
NEAR Watch more closely
TIGHT Close to the cycle budget
OVER The cycle exceeded the budget

For learning runs, focus on whether latency is stable and whether guard decisions still make sense.

Inspect An Incident

When a reject, fault, or repeated clamp needs investigation:

  1. Note the cycle ID or timestamp.
  2. Open MCAP Sessions if loopback logging is enabled.
  3. Select the relevant session.
  4. Inspect the cycle, guard result, action, observation, and nearby image context if available.

If no MCAP session appears, check the Stackfile loopback: section and confirm backend: mcap.

Next Step

After you can read a decision in the console, go back to Common Stackfile Edits, make one safe change, validate it, and watch how the console output changes.