Translation
Translated from the Spanish source, which is the normative text. Status: draft pending human review. Differences are resolved in the Spanish text.
Artifacts and records¶
Current explanatory reference. Obligations are in the requirements; the records do not fix a format, file name, SDK fields, or a new standard.
An artifact keeps information so it can be understood, acted on, or reviewed. A rule says what is required; a record helps prepare it; evidence lets you verify what happened. They are not interchangeable.
What to prepare depending on your need¶
| Need | Artifact | Rule or nature |
|---|---|---|
| Identify the project | Manifest. | MILPA-R-004. |
| Locate knowledge | Structure and sources map. | MILPA-R-001, R-005, R-006, R-007. |
| Scope a task | Context budget. | ASILO-R-003, R-006. |
| Declare actions and boundaries | Controls. | ASILO-R-001, R-002, R-004, R-005, R-007. |
| Check failures | Evaluation. | ASILO-R-008. |
| Keep a conclusion | Report, decision, and conflict. | MILPA-R-001, R-002, R-008. |
| Continue with another tool | Handoff. | Suggested technique; not a normative artifact of edition 0.1. |
The requirements do not impose a separate file for each row. Nor do all rows apply to every project: check scope, condition, and exception in the normative record.
Manifest¶
Minimum content of MILPA-R-004:
| Content | Value to fill in |
|---|---|
| Identifier | Identity of the project or node. |
| Node role | Function of the node, not an agent's permission. |
| Human owner | Identified responsible person. |
| Scope | What it includes and what stays out. |
| Declared profile | Reference and status. If there is no accepted one, declare the proposal or transition with the conditions of MILPA-R-006. |
| Parent | Reference of the parent node, or none. |
| Restricted zones | Areas whose access is restricted. |
The requirement demands a machine-readable representation at the root. This table is not its schema or a representation ready for validation. Depth and homonymous scales are kept distinct; effective inheritance is not presumed.
Structure and sources¶
The structure guide lists the seven accepted functions of MILPA-R-006. A suggested map relates each function to its actual location and owner. Reserved vocabulary declares its version in line with MILPA-R-005.
For rules, MILPA-R-001 asks for source, revision or SHA-256, status, and owner. For a link, MILPA-R-007 asks both ends for provider, consumer, contract and version, data that crosses, owner, status, and evidence. A path index does not prove authority or compatibility.
Context budget¶
Content declared by ASILO-R-003: allowed sources, excluded paths, maximum classification, size limit, and expiry. It is not reused across different tasks when the requirement applies. As a reading aid you can add a reference to the task and its owner; those additional fields are suggestions of this record.
Evidence includes what was actually received, not only the planned budget. The data inventory of ASILO-R-006 covers classification, purpose, applicable basis or consent, retention, revocation/deletion, and owner. Do not include credentials as example values or as data to send to the model.
Controls¶
| Artifact | Content to consult in the requirement |
|---|---|
| Effect contract | Inputs/outputs, version, validation, and authorization at the boundary; ASILO-R-001. |
| Architecture model | Name and content of layers, profile of origin, and dependency direction; ASILO-R-002. |
| Agent scope | Identity, operations, data, action limit, and delegation depth; ASILO-R-004. |
| Critical catalog and approval | Cataloged effects; identity, date, and specific object approved; ASILO-R-005. |
| Execution budget and stop mechanism | Cost or tokens, actions, time, stop owner, and environment evidence; ASILO-R-007. |
A signature, a seal, or a receipt can be solutions of a profile; the edition fixes no algorithm or protocol. A scope declaration also does not enforce permissions by itself.
Evaluation¶
Content of ASILO-R-008: model and version, configuration, case set, method, result, and residual risk. The cases cover the applicable failures, not a universal catalog of attacks. Mark designed, simulated, and executed tests separately. An unrecorded result stays pending, not approved by default.
Report, decision, and conflict¶
MILPA-R-002 separates cited facts, inferences, and hypotheses. A decision that accepts a rule identifies person, version, and date according to MILPA-R-001. MILPA-R-008 records the two sources of the conflict, revision/hash, phrases, and consequence; resolving keeps provenance and cites the decision.
You can present a proposal as an RFC and keep a decision as an ADR or another record. It is a documentation choice of the project: these acronyms and their file names are not a universal format required by edition 0.1.
Suggested handoff¶
- Objective of the next task.
- Owning references and revisions of documents and artifacts.
- Limits and authorizations whose validity will be checked.
- Cited facts, inferences, hypotheses, and observed results.
- Decisions, conflicts, and next pending action.
This technique makes it easier to resume work; it does not synchronize memories, grant permissions, or demonstrate continuity. The context and handoffs guide explains those boundaries.