# FND-008 local lab — Execution Context Trace v1

Safety boundary: local files only; no network, credentials, privilege changes, host deletion, or full environment dump. `setup_fixture.py` can reset only ownership-marked workspaces with fixed names inside this learner directory.

## Baseline

1. `python setup_fixture.py --case baseline`
2. Optionally capture Bash-specific shell evidence if you are in Bash: `pwd`, `command -v python`, `type -a python`. Label those observations as Bash-specific. These steps use the launcher token `python`; if you intentionally substitute another launcher, inspect that exact token instead.
3. `python inspect_workspace.py --case baseline`
4. `python run_probe.py --case baseline --cwd root --mode safe`
5. Record stdout, stderr, exit status, cwd, resolved executable, relevant env, and file hashes in the trace.
6. Reset baseline and run a cwd mutation using `alternate`. Do not infer which file changed from the filename; use the hashes/path evidence.
7. Reset and test a `DEMO_MODE` mutation while holding cwd fixed.

## Transfer

Create the transfer case with `python setup_fixture.py --case transfer`. The directory labels and sentinel data differ. Reconstruct your probes without a supplied sequence. Isolate cwd and DEMO_MODE rather than changing both and guessing.

The final decision is human. A green exit status is evidence only for the returned process status, not the intended file effect.