Translation
Translated from the Spanish source, which is the normative text. Status: draft pending human review. Differences are resolved in the Spanish text.
Decision records¶
This page gathers in one public place who accepted each edition, when, on which revision and
which contradictions remain open. It serves the purpose MILPA-R-001 and MILPA-R-008 set for any
project that adopts the method: decisions with a responsible person and contradictions visible
until resolved. Integrity records are in reference/; the edition history is in
Versions and changes.
ASILO 0.1 and MILPA 0.1¶
| Field | Value |
|---|---|
| Editions | ASILO 0.1 and MILPA 0.1 |
| Acceptance date | 28 Sep 2026 |
| Methodology owner | José Adrián Ruiz-Carmona (public account kasailabs on Codeberg) |
| Acceptance revision | Commit 31ff230 |
| Registered bytes | Editorial revision 0.1.1 (commit fd7d0c3). Its verifiable formulations are identical to those of the acceptance revision; headers, provenance notes and internal references differ. Decision of 15 Oct 2026. |
| Form of the decision | Communicated by the methodology owner in an AI-assisted working session and transcribed into the original record, which the owner reviewed. |
| Accepted | Normative language and requirement card; concepts; principles ASILO-P-01 to P-06 and MILPA-P-01 to P-06; requirements ASILO-R-001 to R-008 and MILPA-R-001 to R-008. No requirement excluded. |
| Not accepted | Any profile (they remain candidates); any earlier design document as such; any conformity claim for an implementation; any conformity or certification with OWASP, NIST, MITRE ATLAS or ISO/IEC 42001. |
| Accepted risks | Some design sources had incomplete Git history; implementation evidence was code reading without executed tests; declared gaps: data and model poisoning, unexpected code execution and the NIST bias and harmful-content categories. |
Changes applied on acceptance¶
| ID | Change |
|---|---|
| MILPA-R-004 | The depth field may not be named like an authority or certainty scale; inheritance between manifests is outside 0.1. |
| MILPA-R-006 | The invariant core is defined as seven functions; file names belong to the profile. |
| ASILO-R-003 | Restricted classifications are the two highest values of the exposure scale. |
| ASILO-R-004 | Checking revocation before each action becomes SHOULD. |
| ASILO-R-005 | The critical-effects catalogue covers at least payments, deletions, permissions, publication to third parties and decisions about people. |
| ASILO-R-008 | No numerical thresholds in 0.1. |
Original records¶
The complete acceptance records are kept in the repository history at revision fd7d0c3. They
contain references to internal design sources and are cited as provenance, not as current text:
acceptance record,
contradictions,
provenance and
editorial revision 0.1.1 (Spanish).
SCAFFOLD 0.1¶
| Field | Value |
|---|---|
| Edition | SCAFFOLD 0.1 |
| Acceptance | 13 Oct 2026, commit e41ff0a: SCAFFOLD-R-001 to R-016 and R-018 |
| Edition completed | 14 Oct 2026, commit 6a13fa3: SCAFFOLD-R-019 to R-032 (31 requirements in force) |
| Methodology owner | José Adrián Ruiz-Carmona (public account kasailabs on Codeberg) |
| Excluded | SCAFFOLD-R-017, proposed amendment to MILPA-R-007 |
| Principles | SCAFFOLD 0.1 has no principles of its own; each requirement states its basis in the "Basis" field. |
| Detail | SCAFFOLD status |
The edition keeps the name "SCAFFOLD 0.1" with the note "completed on 14 Oct 2026" (decision of
15 Oct 2026). The fingerprints of 13 Oct are kept as a superseded revision in
reference/scaffold-accepted-0.1-sha256.json.
Open contradictions¶
Each row stays open until a new edition resolves it. Responsible: the methodology owner of the affected method. Recorded on 15 Oct 2026 unless stated otherwise.
| ID | Contradiction | Next action |
|---|---|---|
| CA-01 | ASILO-R-004: the exception ("none for agents with external effects") does not say what happens with agents without external effects. | Make the exception precise in the next ASILO edition. |
| CA-02 | ASILO-R-007: the scope ("agent runs and model calls with cost or effect") is narrower than the condition ("every automated run with cost or effects"). | Align scope and condition. |
| CA-03 | MILPA-R-001: "none for accepted" suggests exceptions in other states, but the only one described (guidance pages without rules) is outside the card's scope. |
Clarify whether there are exceptions by state. |
| CA-04 | SCAFFOLD-R-018 only governs batches of type feature; other batch types have no rule. | Propose that it applies to every batch. |
| CA-05 | The normative language is declared common to ASILO 0.1 and MILPA 0.1, but SCAFFOLD 0.1 uses it. | Extend its scope to SCAFFOLD in the next edition. |
| C-05 | Content of rings 2 and 3 in the ASILO profile for TypeScript (deferred on 28 Sep 2026). | Resolve when that profile is accepted. |
| C-11 | Axiom identifiers reused with different meanings in another documentation base (opened on 30 Sep 2026). | See the original contradictions record. |
SCAFFOLD 0.2 — 2026-10-16¶
José Adrián Ruiz-Carmona accepts the five additions R-033–R-037. The decision records scope, intact 0.1 baseline, transition, pending translations, and acceptance limits. There are 36 requirements; ASILO/MILPA, R-017, and profiles retain their status.