Translation
Translated from the Spanish source, which is the normative text. Status: draft pending human review. Differences are resolved in the Spanish text.
Method and implementation¶
A method describes purpose, concepts and rules. A profile makes choices for a declared context. An implementation performs actions and provides evidence. None establishes the authority of the others merely by having a similar name.
| Documentation | What belongs there |
|---|---|
| Method | Scope, concepts, principles, requirements, exceptions and versions. |
| Profile | Concrete formats, dependency rules and decisions for a declared context. |
| Implementation | Installation, API, configuration, operation, compatibility, tests and releases. |
Think of a map, a route and a journey. A map describes the space, a route selects conditions and the journey provides observations. Having a map does not prove the journey took place.
To claim coverage, identify the method edition, requirement IDs, implementation version, executed tests and results, and responsible people. Where MILPA-R-007 applies, declare the relationship at both ends. A link alone does not demonstrate compliance.
Related optional implementations¶
These links lead to software without making its APIs or formats methodological obligations. Capabilities and versions evolve in each repository; the table describes responsibilities, not complete conformance or distribution availability.
| Implementation | Declared purpose | Boundary |
|---|---|---|
| asilo-core | Portable utilities for ASILO controls and regional context. | A valid schema does not authorize an effect; each API declares its status. |
| milpa-sdk | Manifests, structural inspection and optional regional-context references. | A candidate SDK profile does not become a universal MILPA tree. |
| scaffold-core | Portable SCAFFOLD project, work, lifecycle and checking contracts. | Declares and validates data; its host supplies persistence, identity and execution. |
| Horcón | Integrates controls, execution and implementation adapters in operational and engineering flows. | An available integration does not establish coverage of the entire method. |
Applying the methods does not require these packages. Installation, commands, SDKs, extensions, compatibility and tests belong to each repository. To choose by need, see the problem catalogue.
Related software¶
By human decision in this review, Ollin is software that declares ASILO as its reference method for security. This declaration does not by itself establish conformance or executed controls. The implementation documents its version, requirements applied, checks and results in its own repository.
The documentation review on 14 October 2026 inspected source code at revision
feed47d293b4ac9073a84c9dd5922f7db560d39d. It compares layer declarations, dependency
rules and execution controls to inform the background guide.
This was a source inspection; software tests were not run and no conformity verdict was issued.