Auditable architecture · Unit 5 of 5

The plan before the disk

The current generators run preflight, write and verify certain results. Internally they produce an inspectable GenerationResult, but the public skeleton doesn't expose --dry-run.

Intermediate to senior40 min

By the end, you'll be able to

Separate preflight, writing and verification
Avoid attributing --dry-run to the public CLI

Understand

The current generators run preflight, write and verify certain results. Internally they produce an inspectable GenerationResult, but the public skeleton doesn't expose --dry-run.

The lesson is to review scope and conflicts before mutating, not to document a flag that doesn't exist.

See

Open the plan before the disk

Explore the conceptual sequence and keep the difference from the published CLI in view.

Open artifact

Do

Run the practice in your checkout and keep the output as evidence.

terminal

$php bin/coa make:controller CatalogPlugin HealthController --path=/health

$php bin/coa inspect:routes

Generate and inspect

Verify

Show that you can apply the unit. Progress only advances once you pass the assessment.

Criteria assessed

Tell the internal plan apart from a --dry-run flag that the public CLI doesn't expose.
Check the resulting registration after generating.

Graded assessment

Solve the 3 scenarios. This unit requires 3 of 3 correct answers.

0 attempts

Question 1 of 3A guide proposes php bin/coa make:controller ... --dry-run to teach the write plan. How should it be reviewed against the current public CLI?

Publish it: if an internal GenerationResult exists, then every imaginable flag is supported.Drop --dry-run; explain preflight/WriteGuard as an internal mechanism and use only exposed commands, followed by inspect:*.Rename it to --plan without checking the help output, because it communicates the intent better.

Question 2 of 3The generator created HealthController.php, but /health doesn't appear in the host. Which evidence should close the task?

The existence of the file; writing is equivalent to registering correctly.A visual review of the controller's name, without booting or inspecting the host.The output of php bin/coa inspect:routes showing /health, in addition to the generation result.

Question 3 of 3A generation would produce three files, but one of them already exists. Which outcome represents the safest behavior?

Preflight detects the conflict before writing the set, reports it and lets you resolve it before deliberately retrying.It writes the two free files and fails on the third, leaving the user to infer the partial state.It always overwrites the existing file; scaffold speed matters more than preserving work.

Grading validates answers in this browser; it doesn't certify identity.

Primary sources

Devtools

Content verified: 2026-07-10

By the end, you'll be able to

1Understand

2See

3Do

4Verify

Primary sources

Understand

See

Do

Verify