Translation
Translated from the Spanish source, which is the normative text. Status: draft pending human review. Differences are resolved in the Spanish text.
Context and handoffs¶
Current application guide based on ASILO 0.1 and MILPA 0.1. It does not require a specific provider or assistant.
Context is what a task receives in order to work. Having access to the project does not mean needing all of its content. Preparing it explicitly helps review exposure, size, and validity, without promising token savings or immunity to malicious instructions.
Define a budget per task¶
ASILO-R-003 lists five contents:
| Content | Practical question |
|---|---|
| Allowed sources | Which documents and revisions does this task need? |
| Excluded paths | What stays out even if the tool can find it? |
| Maximum classification | What data exposure does the task allow? |
| Size limit | How much context can it receive? |
| Expiry | Until when is this budget valid? |
The requirement's exception and conditions are in its record. When it applies, the budget is not reused across different tasks. Declaring a limit does not show that the tool respects it: the evidence includes what actually entered the context.
Separate the scales and protect the data¶
The data exposure scale distinguishes public, internal, confidential, and critical. It is not the scale of document authority or of certainty. Do not translate values because they share a number or a word; see MILPA-R-003.
For an external model, ASILO-R-003 requires recorded human approval or verified anonymization before incorporating confidential or critical data. Detecting a pattern is not the same as anonymizing. Credentials are excluded from the context, in line with ASILO-R-006, also when a model is local.
An external source, attached file, or retrieved content can contain malicious instructions. It is treated as untrusted content; it gains no authority over the task's rules or permissions (ASILO-R-001).
Share references, not imaginary memories¶
Two assistants can read the same versioned sources. That does not synchronize their sessions, their private histories, or their effective limits. Each tool's entry point can point to the owning document instead of duplicating all the rules; checking that it reads it is still necessary.
A suggested handoff contains objective, references and revisions, limits in force, results, facts/inferences/hypotheses, decisions, and the next pending action. It is an explanatory technique, not an accepted session standard. As a handoff practice, review who will receive the data and what actions they will be able to take when changing tool or provider. The obligations of ASILO-R-003, R-004, and R-006 apply according to their conditions; the change grants no permissions or automatic continuity.
Review the task result¶
Check whether the cited sources exist, whether the actual context stayed within the budget, and whether exclusions and expiry were respected. A short answer can still be false; a correct answer can have exposed data improperly. Record those results separately.
Next: architecture and security · Context record
A backpack for one task¶
For a specific trip, pack what is needed rather than the whole house. A context budget makes that selection explicit for a task. A small backpack may still contain an unsuitable item: classification and provenance need review too.