Translation

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

A visual guide to the methodologies

Diagrams explain concepts; their arrows do not implement controls. SVG files can be opened and enlarged without running JavaScript. The Mermaid version keeps editable sources beside each page.

Three methodologies with complementary scopes

flowchart TD
  accTitle: Relationships between methods and evidence
  accDescr: A project, with its purpose and responsible people, connects to three methods: MILPA 0.1 for knowledge and provenance, ASILO 0.1 for action boundaries and SCAFFOLD 0.1 for engineering with assistants. All three feed the project evidence of application with reviewable records, checks and results, and work history.
  Q["A project: purpose and responsible people"] -->|knowledge and provenance| M["MILPA 0.1: sources, facts and authority"]
  Q -->|action boundaries| A["ASILO 0.1: scope, data and permissions"]
  Q -->|engineering with assistants| S["SCAFFOLD 0.1: from framing to delivery"]
  M -->|reviewable records| E["Project evidence of application"]
  A -->|checks and results| E
  S -->|work history| E

SVG diagram: Relationships between methods and evidence · Editable Mermaid source.

Solid arrows indicate each method’s contribution and the records used to review it. ASILO, MILPA and SCAFFOLD retain their accepted 0.1 editions. Architecture, layers, capabilities and permissions are explained within ASILO; guides and profiles add no obligations to another methodology. ASILO addresses model interactions under its conditions; SCAFFOLD organises engineering with one AI assistant or several. MILPA preserves project knowledge.

Four classifications that do not convert into one another

flowchart TD
  accTitle: Authority, certainty, exposure and personal data
  accDescr: A document or claim is classified on four scales: authority, by decision maker and state; certainty, by source and result; exposure, by harm from disclosure; and personal data, by data type. Dashed arrows warn that authority does not determine certainty, certainty does not determine exposure and exposure does not replace personal-data classification.
  D["A document or claim"] -->|decision maker and state| A["Authority: who may approve or change it"]
  D -->|source and result| C["Certainty: evidence supporting the claim"]
  D -->|harm from disclosure| E["Exposure: harm from revealing the data"]
  D -->|personal data type| P["Personal data: classification and treatment"]
  A -.->|does not determine| C
  C -.->|does not determine| E
  E -.->|does not replace| P

SVG diagram: Authority, certainty, exposure and personal data · Editable Mermaid source.

Solid arrows separate the questions; dashed arrows show that one answer does not determine another. An approved text may support a still uncertain claim; public data can be personal. See the declared scales, without translating one scale’s level into another merely because they share a name or number.

Concept, analogy and diagram

Concept to understand	Page with explanation and diagram
Purpose and relationships between methods	This page and Choose a method.
Contract, authorisation, scope and effect	ASILO: shelter, keys and action flow.
Structure, relationships and care	MILPA: Mesoamerican polyculture.
Source, claim, certainty and review	MILPA: library and knowledge cycle.
Zones, context, batches and handoff states	SCAFFOLD: scaffolding and shift handover.
Core, ports, adapters and composition	ASILO: rings view and dependencies.
Identity, permission, revocation and effect point	ASILO: capabilities and effects.
Spanish source and translation	Axioms and translation review.

A port is an interaction contract; an adapter implements it for a specific environment. A capability is a bounded authorisation for operations and resources. A batch organises work; a handoff note preserves what is needed to deliver it. The glossary collects the terms; each analogy explains its own correspondences and limits.