Three hosted investigations · Ubuntu x86_64

Stop guessing.
Ask the kernel.

Seven incident-first labs for engineers who operate Linux. Reproduce one bounded failure, collect one useful signal, and learn exactly where the evidence ends.

Current boundaryLabs 01, 02, and 07 are browser-accessible. Four more run through the documented local VM.
01Predict
02Observe
03Explain
04Bound
05Transfer

THE INCIDENT QUEUE

Seven failures worth understanding

Every lab starts with an operational question. Hosted badges describe what runs here today.

LAB 01HOSTED

What Just Ran on My Server?

A short-lived process changes the system, then disappears before snapshot-based monitoring sees it.

HOOKsyscalls/sys_enter_execve
Open investigation →
LAB 02HOSTED

Who Touched This File—and Did It Fail?

A service repeatedly looks for configuration, but ordinary logs omit the pathname or return code.

HOOKsys_enter_openat + sys_exit_openat
Open investigation →
LAB 03LOCAL VM

Why Can’t This Service Connect?

A client cannot connect, but the failure disappears inside generic application telemetry.

HOOKsys_enter_connect + sys_exit_connect
Read local lab ↗
LAB 04LOCAL VM

Is DNS Actually the Slow Part?

A request is slow and DNS is suspected without a measured resolver boundary.

HOOKresolve_backend uprobe
Read local lab ↗
LAB 05LOCAL VM

Why Does the Network Keep Retrying?

Latency coincides with packet loss, but averages hide the affected flows.

HOOKtcp/tcp_retransmit_skb
Read local lab ↗
LAB 06LOCAL VM

Why Is PID 1 Not PID 1?

Container and host process identifiers appear to contradict each other.

HOOKsys_enter_execve + /proc enrichment
Read local lab ↗
LAB 07HOSTED

Reading Verifier Errors and Surviving Kernel Drift

A program that looks correct fails before attachment at the kernel verifier boundary.

HOOKsyscalls/sys_enter_write + CO-RE
Open investigation →

THE METHOD

Evidence before explanation

01

Reproduce a bounded symptom

Each fixture creates a controlled failure. It is a teaching environment, never a production claim.

02

Capture the smallest useful signal

The observer attaches to a named kernel boundary and emits typed, time-bounded events.

03

State what remains unknown

A learner completes the incident only after naming what the evidence cannot establish.

PUBLIC ROADMAP

Expand only after proof

NOW

Three hosted labs

Execution, file access, and verifier portability with fixed operations.

NEXT

Kernel matrix

ARM64 and additional distribution kernels with observed compatibility receipts.

FELLOWSHIP

Community fixtures

Operator workshops, translations, and reviewed contributor incidents.