Not yet reviewed. Artifacts stay locked until you approve them.
Context Packs
Not everything belongs in context
A migration needs the database policy, the migration skill and a database tool contract — not every brand rule and every unrelated workflow. This is which packs load for which kind of work, the reason each one activated, and what happens when two rules disagree.
Pick the kind of work
A trigger is you saying what kind of task is starting, not a guess about your intent. The same trigger always activates the same packs, so what an agent carries is predictable before it starts rather than discovered afterwards.
Nothing beyond the always-active core is loaded.
Always active
Loaded for every task. Only one pack earns this — a pack that loads every time has to.
- Core ProfileAlways active
Minimum behaviour and non-negotiable safety. Loads for every task.
Loaded for this task
Activated by the trigger above, with the reason stated.
Pick a trigger to see what it would activate.
Retrievable, not loaded
Available if the agent goes looking. Not carried by default.
- ResearchRetrievable
No trigger selected, so nothing beyond the always-active core is loaded.
- ToolRetrievable
No trigger selected, so nothing beyond the always-active core is loaded.
What loads every time
A pack pinned here is carried on every task, so it costs its tokens on every task. Suppressing one we load by default is allowed — it is your policy — but it is the direction worth being deliberate about.
5tokens
1 pack carried on every task
10tokens
3 packs the rider has content for
What these numbers assume
Priced with the claude-sonnet-5 tokenizer profile at ~2.4 characters per token.
Ratio source: derived.
A ratio applied to the text, not a count returned by the model.
A placeholder figure: the wizard does not yet author rules per pack, so there is no pack body to price.
The two figures are counts of different sets of packs. Neither is a before and after, and the gap between them is not money.
- Core ProfileEvery task
5 tokens when carried · we load this by default
- ToolOn demand
2 tokens when carried
- ResearchOn demand
3 tokens when carried
Only packs your rider has content for are listed. An empty pack cannot be pinned, because there would be nothing to carry.
When two rules disagree
Higher wins. A lower level may add detail, but it never weakens a locked rule above it. Environment is deliberately not on this list: it decides whether a rule applies right now, not whose rule wins, so it lives with activation rather than authority.
- 01Host and system restrictionsThe platform's own limits. Nothing below can lift them.
- 02Locked global safetyRules the owner locked deliberately. Where an environment rule must never lose — never write to production unasked — it belongs here.
- 03Client policyContractual, and owed to someone outside the team. It outranks the team's own defaults because breaking it has consequences the team cannot absorb.
- 04Team and workspace policyOrganisational standards, binding on everyone in the workspace.
- 05Personal RiderHow you work. It beats project convention on purpose — a project may add detail, but only a locked rule may overrule your working conditions.
- 06Project Policy PackThe product's own facts and constraints. A project may span several repositories.
- 07Repository policyCodebase conventions. Kept separate from project because one repository can hold several projects, and one project can span several repositories.
- 08Tool ContractWhat a specific tool may do, and what it must confirm first.
- 09SkillA reusable workflow, active only while that workflow is running.
- 10Task briefThis request. The narrowest thing that can add detail.
- 11Reference materialRetrieved on demand. It informs an answer; it never overrules a rule.