Translation

Translated from the Spanish source, which is the normative text. Status: draft pending human review. Differences are resolved in the Spanish text.

Versions and changes¶

The ASILO, MILPA and SCAFFOLD rules are published in editions. An edition brings together the principles and requirements in force since a given date. What is not part of an edition —guides, cases, records or profiles in preparation— explains or proposes, but does not oblige.

Editions in force¶

Edition	Date	Content
ASILO 0.1	28 Sep 2026	6 principles and 8 requirements (ASILO-R-001 to ASILO-R-008).
MILPA 0.1	28 Sep 2026	6 principles and 8 requirements (MILPA-R-001 to MILPA-R-008).
SCAFFOLD 0.2	16 Oct 2026	36 requirements: 31 from 0.1 by reference and R-033–R-037. Decision and transition. R-017 remains pending.

History¶

Version	Date	Changes
0.1.1	30 Sep 2026	Informative English translation; the Spanish text is authoritative. Editorial revision. The public records no longer show internal provenance and software-status notes; that traceability is kept in the method's repository. It changes no obligation, ID or exception.
0.1	28 Sep 2026	First edition of ASILO and MILPA: concepts, normative language, principles and requirements.

How the rules change¶

Numbering. While the version starts with 0., an incompatible change is announced in this history. From 1.0 onward, it will require a major version.
Stable IDs. A requirement keeps its ID even if its wording changes. If it is withdrawn, its ID is not reused.
Human decision. A new or modified rule takes effect only with the recorded decision of the methodology owner. Drafting, reviewing or publishing a page does not accept it.
Traceability. The origin, review and decision of each rule are kept in the method's repository, as MILPA-R-001 requires.
Languages. Spanish is the authoritative text. Translations are informative: if they differ, the Spanish version prevails.
Exceptions. Departing from a requirement in force requires an owner, reason, scope, duration, risks, rollback plan and review date.

Applying a method does not certify that a system meets its requirements: that requires its own evidence in each project.

Current explanatory ASILO/MILPA documentation¶

Current documentation includes editorial axioms, analogies, an informative bilingual glossary, Mermaid diagrams and a layered security guide. Concepts and principles have current editorial presentations with identified provenance. It leaves ASILO/MILPA requirement pages and the normative-language specification unchanged. This explanatory revision is not a new accepted ASILO/MILPA edition and does not accept a technological profile.

Reproduced text and editorial presentations¶

The accepted ASILO/MILPA editions include concepts, principles, requirements and normative language. This editorial tree reproduces requirement and normative-language pages without changes. Concepts and principles are current explanatory presentations with identified provenance. Original documents remain preserved with their provenance; this site does not claim to reproduce the entire accepted edition byte for byte. The twelve principle statements remain unchanged in both languages.

File and folder names were standardized in English and their references updated. Accepted normative statements for ASILO 0.1 and MILPA 0.1 were preserved; the recorded hashes verify the current files. The methodology page distinguishes their scopes and retained SCAFFOLD as a candidate guide at the time. That classification was superseded by the subsequent decision recorded below.

Acceptance of SCAFFOLD 0.1 — 13 Oct 2026¶

The human acceptance decision establishes SCAFFOLD 0.1 as an approved methodology, with 17 requirements in force and their complete records. SCAFFOLD-R-017 retains its ID and remains a pending amendment to MILPA-R-007, outside this edition. R-012 explicitly identifies the checks that may be suspended during exploration and preserves ASILO/MILPA requirements. The earlier “de facto” classification is superseded. ASILO 0.1 and MILPA 0.1 remain in force without normative changes.

Architecture and security organisation — 13 Oct 2026¶

By human decision, architecture, rings, capabilities, threats and check guides are integrated into ASILO. Navigation retains ASILO, MILPA and SCAFFOLD as methodologies. AI scope with one assistant or several and the conditions of multi-agent subcases are clarified. Accepted editions retain obligations, IDs, exceptions and state. Guides remain explanatory; their models do not become accepted profiles.

First versions and current documentation — 14 Oct 2026¶

ASILO 0.1, MILPA 0.1 and SCAFFOLD 0.1 are approved first editions, valid for application. The human instruction in this review removes the previous editorial “candidate” and “draft” labels from current concepts, principles, guides and templates. Historical records remain history; they do not describe the current state of these versions.

Methodological edition: identifies accepted principles and requirements, with date and scope.
Documentation release: identifies a reviewed distribution of current content. It can improve explanations, translation or navigation without changing obligations.

Specific technological profiles retain their approval process. Amendment SCAFFOLD-R-017 remains outside accepted requirements. Local previews and repository publication are not presented as a public site deployment or certification of an implementation.

SCAFFOLD completed in its first edition — 14 Oct 2026¶

By human decision, SCAFFOLD 0.1 is completed as a software project method and no other edition is opened. Added are SCAFFOLD-R-019 to SCAFFOLD-R-032 (project and start-up, work and cadence, branches and releases, environments and delivery, crews), the roles named by the records and the open formats of the project cycle: 31 requirements in force. R-001 to R-016 and R-018 keep their wording. R-017 remains a pending amendment. ASILO 0.1 and MILPA 0.1 do not change.

Acceptance of SCAFFOLD 0.2 — 16 Oct 2026¶

36 requirements: 31 from 0.1 by reference and R-033–R-037. Decision and transition. R-017 remains pending.