---
source_hash: 674476b7006227be6e290fbdfaade9f0d8f1371f94492fc88a38c97f9eb90427
post: /posts/workflows/work-your-way-with-pi
shape: doctrinal
---

# Context Pack: Work YOUR Way With Pi

Agent reference for the rewritten operating-contract essay. Only the quoted excerpts are verbatim. The tier names describe work, not immutable model rankings.

## Verbatim excerpts

> Give each specialist four things: an outcome, its boundary, the evidence expected on return and a stop condition.

> Use consequence and complexity together.

> claim → artifact check → test or inspection → accept / retry / escalate

## Parent and specialists

Pi supplies a small extensible harness. The operator defines policy around it: tools, skills, extensions, provider choices and working conventions. Keep the stable core's guarantees small and explicit.

The parent seat remains with the human conversation, holds the outcome and constraints, separates work and checks the returned pieces as a whole. Delegation does not end its responsibility. Specialists receive bounded briefs, return an artefact with concise findings and surface decisions outside their authority instead of expanding scope silently.

## Routing contract

- Reason: high consequences, deep ambiguity, architecture and hard debugging. Expose assumptions, viable options and the cost of a wrong decision.
- Perform: substantive implementation within a known outcome and boundary. Return the change, a targeted check and conflicts for the parent.
- Do: bounded repeatable classification, parsing, transforms, routing and boilerplate. Use a stated rule and sample check. Ambiguity stops execution in the Do lane and returns the task for reassessment.

Consequence and complexity both matter. A simple irreversible action belongs in Reason; a complex reversible implementation may fit Perform. Human authority remains over judgement-heavy and irreversible decisions.

## Completion and starting point

Locate the claimed artefact and check its shape. Test or inspect against the requested constraints. Then accept, request a targeted retry or escalate. A confident report is not completion evidence. Missing evidence leaves the job open.

Start with one parent and a few specialist contracts, then inspect a real result before adding automation. The public [AGENTS.md starter](/downloads/work-your-way-with-pi/AGENTS.md) contains specialist boundaries, routing, evidence and escalation rules.

Canonical body: `content/posts/workflows/work-your-way-with-pi.mdx`. Retained diagrams cover the kernel, parent contract, Reason/Perform/Do, routing and evidence loop.