The metaphor is the design

Understand

Milpa doesn't use the milpa as decoration. Each crop keeps a single responsibility and cooperates through small contracts.

The host decides what to plant; the runtime boots the system; plugins contribute capabilities; workflows coordinate actions. No layer needs to pretend it is the whole platform.

See

Open Plant your milpa

Build the graph module by module and watch when a dependency can't germinate yet.

Open artifact

Do

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

Build the graph

Verify

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

Criteria assessed

Tell the host's decisions apart from the runtime's responsibilities.
Identify responsibilities that don't belong to Core.

Graded assessment

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

0 attempts

Question 1 of 3A team is preparing two products with Milpa. Both use the same runtime, but each one needs different plugins, configuration and routes. Where should that composition decision live?

In Core, because it must know every possible productIn each product's host, which decides what pieces to plantIn Runtime, through conditions specific to each productIn a global Workflow that replaces the host's configuration

Question 2 of 3The application needs catalog search, a domain capability that is not part of boot or of the base contracts. Which location best preserves Milpa's boundaries?

Adding search to Core so any module can call itFolding it into Runtime because it already knows the containerContributing it from a plugin with an explicit contractImplementing it in full inside each HTTP and CLI entry point

Question 3 of 3Confirming a purchase requires reserving inventory, charging and sending a notification. Each capability already belongs to a different plugin. Which piece should coordinate the sequence without absorbing those responsibilities?

A workflow that orchestrates the plugins' actionsCore, by adding a special method for purchasesRuntime, by running inventory and payment queries during bootThe host, by duplicating the sequence at each entry door

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

Routes

The metaphor is the design

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