Target Guide¶

Guide Maps¶

graph LR
  help["make help"] --> targets["Public targets"]
  targets --> review["Inspect, verify-report, proof, and confirm"]
  review --> guides["Local capstone guides"]

flowchart LR
  question["Pick the question you have"] --> target["Choose the smallest honest target"]
  target --> output["Inspect the command output or bundle"]
  output --> owner["Name the owning object or boundary"]
  owner --> decision["Return to the course with a clear answer"]

Use this guide when make help shows several commands but the right one is still not obvious. The goal is not target memorization. The goal is picking the smallest honest command for the question you actually have.

Stable targets¶

Target	What it is for
`confirm`	run the strongest local confirmation route
`demo`	run the human-readable monitoring scenario
`inspect`	build the learner-facing inspection bundle
`inspect-timeline`	print the ordered scenario flow directly in the terminal
`inspect-retirement`	print the retirement scenario before-and-after state
`inspect-rate-of-change`	print the alternate evaluation-mode scenario
`inspect-json`	print the default scenario as stable JSON
`tour`	build the learner-facing walkthrough bundle
`verify-report`	build the executable verification report bundle
`proof`	run the full course-sanctioned evidence route

Pick by output shape¶

If you need...	Choose
terminal narrative only	`make demo`
saved learner-facing state files	`make inspect`
saved walkthrough story plus guide set	`make tour`
saved tests plus learner-facing state	`make verify-report`
the strongest local confidence bar	`make confirm`
the published end-to-end learner route	`make proof`

Fast target selection¶

If the question is "does the design still hold?"¶

Use:

make confirm

If the question is "can I understand the scenario as a human?"¶

Use:

make demo
make tour
TOUR.md

If the question is "what is the current capstone state?"¶

Use:

make inspect
INSPECTION_GUIDE.md

If the question is "in what order did the teaching scenario happen?"¶

Use:

make inspect-timeline
SCENARIO_GUIDE.md
EVENT_FLOW_GUIDE.md

If the question is "what does retirement change and clean up?"¶

Use:

make inspect-retirement
RETIREMENT_SCENARIO_GUIDE.md
RULE_LIFECYCLE_GUIDE.md

If the question is "what proves the policy seam is real?"¶

Use:

make inspect-rate-of-change
RATE_OF_CHANGE_SCENARIO_GUIDE.md
TEST_GUIDE.md

If the question is "can I diff or script the same scenario state?"¶

Use:

make inspect-json
INSPECTION_GUIDE.md
BUNDLE_GUIDE.md

If the question is "what saved bundle proves the behavior?"¶

Use:

make verify-report
PROOF_GUIDE.md

If the question is "what is the strongest published route?"¶

Use:

make proof

Important distinctions¶

confirm versus proof confirm proves the local route as strongly as possible; proof builds the published learner-facing evidence route.
demo versus tour demo tells the story directly in the terminal; tour saves that story with matching review guides.
inspect versus verify-report inspect focuses on learner-facing state; verify-report combines tests and saved state for stronger review.

Signs a target is too heavy¶

you ran it mainly because it felt safer than naming the real question
the output answered several things, but not the one boundary you were reviewing
a lighter route could already have told you which file or test to open next

Best companion guides¶

Read these with the target guide:

PACKAGE_GUIDE.md
TEST_GUIDE.md
WALKTHROUGH_GUIDE.md
PROOF_GUIDE.md
INSPECTION_GUIDE.md
BUNDLE_GUIDE.md
SCENARIO_SELECTION_GUIDE.md
EXTENSION_GUIDE.md