Boot a verifiable host

Understand

The skeleton is a minimal host. Its job is to assemble packages, configuration and routes without introducing a second architecture.

Doctor is not a welcome screen: it checks that the kernel booted, lists plugins and routes, and makes the container's state visible.

The host also declares its profile: the architectural shape it expects from the installed packages. That profile can go stale and ask for a world that no longer exists; the report names it (MILPA_HOST_PROFILE_OUTDATED) and makes clear which side went stale: the profile, not the code.

See

Inspect the runtime

Use the x-ray to relate boot, container, dispatcher and registry.

Open artifact

Do

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

terminal

$composer create-project milpa/skeleton myapp

$cd myapp

$php bin/coa doctor

Run the boot lab

Verify

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

Criteria assessed

Doctor confirms kernel, plugins, container and routes.
The public server is served from public/.

Graded assessment

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

0 attempts

Question 1 of 3A new server must expose the skeleton over HTTP. Which configuration preserves the public boundary the project intends?

Use the repository root as the document root so config/ is reachableUse public/ as the document root and leave everything else out of web reachServe src/ and redirect every request to the first pluginExpose vendor/ so Composer can resolve packages from the browser

Question 2 of 3php bin/coa doctor reports that the kernel booted, lists configured and booted plugins, shows the container and dispatcher, and counts declared routes. Which conclusion is actually supported?

Every use case and HTTP response has already passed functional testsThe application is production-ready and needs no further observabilityEvery route reaches a database correctlyThe composition was able to boot and its RouteProviders declared the counted routes

Question 3 of 3A PR adds pricing rules and catalog queries directly into public/index.php because that's where the request lands. What review is appropriate?

Ask that the entry point adapt and dispatch; the domain capability belongs in plugins and servicesAccept the change because the host should implement the whole domainMove the rules into bin/coa to share them with HTTPMove the queries into the kernel so they're available during boot

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

Routes

Boot a verifiable host

By the end, you'll be able to

Understand

See

Do

Verify

Primary sources

By the end, you'll be able to

1Understand

2See

3Do

4Verify

Primary sources

Understand

See

Do

Verify