# TOL001-LAB1 — Workspace Boundary Map

1. Run `python setup_fixture.py --case baseline`.
2. Inspect `workspace/` and run `python inspect_repository.py`.
3. Copy the reported `environment_identity` and `observation_boundary` into `submission_notes.md`. Do not dump environment variables or credentials.
4. Fill `workspace_boundary_map.csv`. Do not infer membership from folder names. Cite a file/command observation for each material row; the reviewer compares your result with a hidden oracle.
5. Reset before each mutation, then run one mutation at a time with `mutate_fixture.py`.
6. Record what changed, which authority changed, what stayed unknown, and one independent observation that could falsify your conclusion.
7. For transfer, run `python setup_fixture.py --case transfer` and reconstruct the map without a supplied sequence.

If no build/install was executed, keep observed build state as `UNKNOWN_NOT_OBSERVED`; do not turn static architecture evidence into a reproducibility claim.

Safety boundary: local fixture only; no network, credentials, privileges, broad environment dumps, or host-destructive operations.