One action, explicit policies

Understand

A CLI, HTTP or an agent can start work, but the entry point must not become a second implementation of the domain. The action crosses the same pipeline and leaves the same kind of evidence.

A human gate doesn't replace automatic validations. It steps in when policy demands intent, accountability or context that a mechanical rule can't decide.

milpa/command names that same principle as an atom: an Operation is declared once and projected to coa, MCP and HTTP without reimplementing the domain at each door — but the door can change the policy, and today not all of them enforce the same scopes.

See

Walk the pipeline

Change the entry door and remove a permission to pinpoint exactly where the action stops.

Open artifact

Do

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

Operate the gate

Verify

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

Criteria assessed

The entry point doesn't contain the use-case logic.
An approval produces an auditable decision, not an invisible shortcut.

Graded assessment

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

0 attempts

Question 1 of 3The HTTP route for publishing an article checks permissions and applies different rules than the CLI command that publishes the same article. Inconsistent results have already shown up. Which change fixes the boundary?

Have HTTP and CLI adapt their input and dispatch the same action through the same pipelineCopy the HTTP implementation into the CLI command every time it changesMove both implementations into Runtime and keep them separateDrop the CLI's validation because it's only used internally

Question 2 of 3A deployment passes schema, permissions and automated tests. Production policy additionally requires the responsible person to confirm the context of the change. How should that be modeled?

As another automated check that always approves if the tests passBy skipping the prior validations and leaving the whole decision to the personAs a human gate that comes after the automated validationsAs a second implementation of the deployment, exclusive to production

Question 3 of 3A person approves a sensitive operation. Six weeks later, an audit needs to reconstruct why the pipeline continued. What evidence is adequate?

A boolean approved=true with no actor or timestampThe resource's final state, because it implies someone approvedA record that gets overwritten every time the decision changesAn append-only decision with outcome, actor and policy context

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

Routes

One action, explicit policies

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