Boundaries & Dependencies

Boundaries are not blockers. They are edges. When we know the edges, we can optimize inside them instead of constantly re-negotiating them.

Mapping the Edges

This is where the Lens becomes architectural, not just procedural. Before we build, we map the four critical edges:

• ☐Internal Boundaries: Platform limits, domain rules, where objects/data live.
• ☐External Boundaries: Other teams, APIs, third-party systems.
• ☐Process Boundaries: Who we depend on for decisions or approvals.
• ☐Data Constraints: Which system is the source of truth for what.

Dependency Contracts

Hope is not a dependency strategy. Every dependency must be logged with strict parameters: What we need, why we need it, the drop-dead date, the owner, the risk if late, and the fallback plan.