---
source_hash: 7fcac847e82d748c40b6ffff303981bbba6b2d7cbad77f03c8fee211e298132c
---

# Context Pack: Hold the System

## Gist

Make inputs, saved state, feedback and judgement available outside one conversation.

## Verbatim excerpts

> Inputs, saved state, feedback, judgement. Keep the map small enough that you will actually use it.

> Models have the same problem. Make the current state easy to identify. Keep settled decisions close to the work. Say what is still open.

## Working rules

- A finish line still needs a working system around it.
- Save current files, agreed decisions and open questions where the next session can find them.
- Feedback must allow the work to fail a check.
- Assign authority to approve the result explicitly.
- Decide the working structure before prescribing a sequence.

## Use and boundaries

Use this pack to understand the essay and apply its reasoning to a project. Read the full essay for its examples. Examples introduced as hypothetical are not claims about Ari's personal history. This pack contains no private teaching transcript.

## Links

- Essay: /documents/outcomes-and-systems/hold-the-system
- Ordered practice: /courses/define-outcomes-build-products
- Related: /documents/outcomes-and-systems/context-is-king
- Related: /documents/outcomes-and-systems/define-done-as-thinking

## Source

content/posts/outcomes-and-systems/hold-the-system.mdx