Translation
Translated from the Spanish source, which is the normative text. Status: draft pending human review. Differences are resolved in the Spanish text.
Reference¶
Look up a specific rule without going through all the guides. This page organizes what is already documented; it adds no obligations and certifies no compliance.
Accepted rules and explanations¶
| You need to consult… | Document |
|---|---|
| Meaning of the terms | Concepts. |
| Why each rule exists | Principles. |
| Knowledge, identity, structure, and links | MILPA 0.1. |
| Contracts, permissions, data, limits, and evaluation | ASILO 0.1. |
| Software lifecycle management | SCAFFOLD 0.2, with the 0.1 base. |
| Problems and capabilities of all three methods | Problem catalogue. |
| Meaning of MUST, SHOULD, and MAY | Normative language. |
The full requirement records keep scope, conditions, exceptions, sources, and residual risk. A summary or a checklist does not replace them.
Explanatory material and proposals¶
- Artifacts and records: semantic fields and evidence for preparing a project.
- Application profiles: formats and conventions not yet accepted.
- External frameworks: versioned contrast, not OWASP/NIST/ISO conformance.
If you want to learn the method before consulting its rules, go back to Methodologies. To see what changed between versions, see Versions and changes.
Reading and writing support¶
- Glossary: definitions and informative Spanish-English equivalents.
- Editorial axioms: accessible, neutral and precise voice; self-contained methods.
-
Layers and rings: example with text, diagram and limits.
- Architecture and security in ASILO.
-
Research: from requirements to evidence: primary sources, verification limits and proposals without amending requirements.