Course / M2
Module 2 of 12

Think in layers

Use layered boundaries to concentrate complexity where it belongs

Break complex systems into independent layers, keep business logic in the core, and use ports and adapters as the standard shape for code humans and agents can both reason about.

6 sections

Start this module →

  1. 01

    The oldest trick, with a new reason

    ✎ Text

    Split responsibilities into layers so humans and agents can reason about each layer independently.

  2. 02

    A good boundary buys you independence

    ✎ Text

    A boundary earns its place only when the two sides can change without disturbing each other.

  3. 03

    The shape

    ✎ Text

    Keep business logic in the core; point infrastructure inward.

  4. 04

    The boundary is a contract: ports

    ✎ Text

    A port is the promise the core owns and adapters fulfill.

  5. 05

    Make it concrete: one command, one port

    ✎ Text

    Anchor the architecture in a single SaaS action: inviting a teammate to a workspace.

  6. 06

    Why this is the leash for an agent

    ✎ Text

    A boundary is not just structure. It is the smallest unit you can safely delegate.