🏆Capstone project: Build and Inspect a Project Workspace

This capstone is a small systems task, not a memory test for commands. You will read a supplied workspace, plan two changes, make them safely, run the supplied program, and leave evidence that someone else could check without watching you work.

The terminal beside this lesson follows your account preference: Windows opens PowerShell Core, while macOS and Linux open Bash. The commands differ, but both hosted routes work in /workspace and must leave the same checked result.

Starting conditions and recovery

Reset the chapter workspace before you begin. The starting tree is:

/workspace
├── README.md
├── report.py
├── data
│   └── README.txt
├── destination
│   └── README.txt
├── evidence
│   └── safety-check.txt
└── notes with spaces.txt

README.md, report.py, and data/README.txt are supplied and must survive unchanged. Running report.py from /workspace prints Workspace report: ready. Reset restores this exact tree, so it is your way back if the structure stops making sense.

Plan before you change state

Your finished workspace has to contain three new or completed results:

• a notes directory holding project-plan.txt, moved and renamed from notes with spaces.txt;

• destination/data-copy.txt, copied from data/README.txt with the original left in place;

• a completed evidence/safety-check.txt recording what you checked before you moved anything.

The seeded evidence/safety-check.txt shows four blank fields. Read it first with Get-Content -LiteralPath ./evidence/safety-check.txt in PowerShell or cat evidence/safety-check.txt in Bash.

Before moving anything, preview both the source and proposed destination. The source should exist and the destination should not. Then replace the template with exactly four key=value lines:

source=<move source>
destination=<move destination>
source_present=<yes or no>
destination_absent=<yes or no>

Use paths relative to /workspace, without a leading ./. Record yes or no in lowercase. This is a deliberately constrained receipt, not a prose contest; the interesting work is making the observations before you fill it in.

Build and verify

Decide the command sequence yourself. Here is the route vocabulary, not a finished solution.

Your plan needs three phases: orient and preview; record the preflight before mutation; then build, verify, and run. The source/destination requirements above determine the individual commands. If you are about to type a broad wildcard or a force option, stop. The capstone needs neither.

Do not run a removal command in this capstone. The move should make its old path disappear; deleting anything else would only add risk without adding evidence.

What Check my work verifies

The check reads the resulting state, not your terminal history. Any safe sequence passes as long as it leaves these facts true:

1. README.md, report.py, and data/README.txt still hold their supplied text.

2. notes/project-plan.txt holds the original notes text.

3. notes with spaces.txt is gone from the workspace root, because it was moved rather than copied.

4. destination/data-copy.txt matches data/README.txt, and destination/README.txt is still there.

5. evidence/safety-check.txt contains the four exact source, destination, and yes/no preflight fields.

6. Running the supplied program from /workspace prints Workspace report: ready.

Inspect the tree yourself before you submit. If unexpected paths appeared and you are not sure what changed, reset and start again rather than reaching for a broad cleanup command.

You have produced something another person could inspect without asking you a single question: an organized tree, untouched inputs, a program that runs, and a written record of the check you made before you changed anything. The last lesson asks you to explain how the whole machine made that possible.