Translation
Translated from the Spanish source, which is the normative text. Status: draft pending human review. Differences are resolved in the Spanish text.
Glossary¶
Informative equivalents for this revision. Spanish remains the normative language of ASILO 0.1 and MILPA 0.1. This glossary explains terms; it does not change accepted definitions. An equivalent word alone does not establish equivalence between classifications.
| Español | English | Meaning |
|---|---|---|
| Método | Method | An explicit way to organise decisions, actions and checks. |
| Axioma editorial | Editorial axiom | A rule governing how documentation communicates; it does not replace a method requirement. |
| Principio | Principle | A criterion guiding decisions. Requirements make it concrete. |
| Requisito | Requirement | An obligation with an identifiable actor, scope, condition, evidence and exception. |
| Perfil | Profile | A word with three senses that are not mixed. (1) Profile of a method (technological or application profile): a concrete application of the method to a declared context, such as a language or a type of project; acceptance is decided separately (MILPA-R-006; see profiles). (2) Project profile: the profile a project declares in its manifest, with its status (MILPA-R-004, MILPA-R-006). (3) Agent profile: scope, per-run limits and supervising person of each agent in a crew (SCAFFOLD-R-030); it describes responsibilities, grants no permissions, and is not the project profile of MILPA-R-006. |
| Implementación | Implementation | Software or a process attempting to apply rules and providing evidence of its behaviour. |
| Responsable | Responsible person / owner | A person or human role accountable for a decision or resource. This does not imply legal ownership. |
| Responsable metodológico (owner metodológico) | Methodological owner | The person who decides the normative changes of a method within the scope assigned to them. A new or modified rule takes effect only with their recorded human decision (editions; governance; MILPA-R-006 names them as the actor for the core). They are not the repository administration. |
| Procedencia | Provenance | The identifiable origin and history of a claim or artifact. They do not prove truth by themselves. |
| Evidencia | Evidence | A documented observation or result used to assess a claim within a specific scope. |
| Hecho | Fact | A claim supported by verifiable observation in the stated context. |
| Inferencia | Inference | A reasoned conclusion drawn from sources and explicit assumptions. |
| Hipótesis | Hypothesis | An explanation or expectation awaiting evaluation. |
| Autoridad documental | Document authority | The declared authority and change regime of a document. This differs from the certainty of its claims and a person’s permissions. |
| Exposición de datos | Data exposure | Classification of potential harm from disclosure. This is not a rule status. |
| Contrato | Contract | Agreed structure and conditions for exchanging data or requesting actions. Here it does not mean a legal contract. |
| Validación | Validation | Checking whether input meets a contract; it proves neither permission nor truth. |
| Autenticación | Authentication | Checking the claimed identity of an actor. |
| Autorización | Authorisation | A decision about whether an identity may act on a specific resource. |
| Capacidad | Capability | Bounded authority over an operation and resource, with a defined control mechanism. It is not any identifier or flag. |
| Revocación | Revocation | Withdrawal of authority and checking that it is no longer usable. |
| Núcleo | Core | Rules and types kept independent of external mechanisms. |
| Puerto | Port | A contract through which the core requests or receives an external interaction. Do not confuse it with a network port. |
| Adaptador | Adapter | A concrete mechanism implementing a port, such as file access. |
| Capa o anillo | Layer or ring | A grouping of responsibilities and dependency rules. It does not imply process isolation. |
| Punto de efecto | Point of effect | The point where an action changes a resource or produces an external consequence. |
| Riesgo residual | Residual risk | Harm that remains possible after applying and checking a control. |
| Revisión humana | Human review | A decision by a person with authority over the specific object and action. |
| RAG | Retrieval-augmented generation | Retrieving relevant sources to ground a response. Retrieval does not validate a source. |
| Sandbox | Sandbox | An environment with declared and tested technical restrictions. Its name does not prove isolation. |
SCAFFOLD's own terms are in its vocabulary; ASILO architecture and security terms are in their guide.
Keep requirement IDs and declared classification values unchanged in records. Translate the explanation rather than inventing a correspondence. See concepts and normative language.
Names and design approach¶
- ASILO / ASILO: retained in both languages; its name draws on Spanish asilo, meaning shelter, refuge or protection.
- IA desde el diseño / AI first: editorial guidance for bounding context, data, authority and effects from task definition; it neither requires model integration nor demonstrates security by itself.
See the name and controls and the analogy map.