# Make the separation stick

Principle `make-the-separation-stick`. Agents copy the patterns they find, so a separation must live in code, types, or checks rather than in one reviewer's head.

Give each concern one named place. Choose the highest rung that can hold it: a type or API that makes the braid impossible to write, then a lint rule or import boundary, and only then a written rule. Keep one paved path.

Read the full section in the [uncomplect skill](/skills/uncomplect#agent-sized-context-make-the-separation-stick).

## Related
- [Separate what was braided](/principles/separate-what-was-braided)

## Skills
- [uncomplect](/skills/uncomplect)

## Sources
- Tan, Lauren. *Dune*, post on X. [Link](https://x.com/poteto/status/2102050467505430555). ([lauren-tan-dune](/bibliography#lauren-tan-dune))