Translation
Translated from the Spanish source, which is the normative text. Status: draft pending human review. Differences are resolved in the Spanish text.
MILPA — Knowledge and provenance¶
Edition in force: MILPA 0.1 (in force since 28 Sep 2026)
MILPA helps a project's knowledge have a recognizable place, owner, provenance and status. It is a methodology, not a manager nor a taxonomy of agents.
Start with its purpose and limits. Then prepare a project's identity or look up a specific rule.
What is available today¶
- MILPA principles
- MILPA requirements
- Identity and manifest
- Files, folders and names
- Artifact records
- Application profiles
- Related software and conformance limits
- Versions and changes
Provenance of content by jurisdiction¶
Jurisdictional content retains its own source, status and revision. A package reference can pin a version and digest to check which bytes were consumed; that check confers neither methodological acceptance nor legal authority. Also identify the owner, relationships between projects where MILPA-R-007 applies, and pending conflicts under R-008.
The shared jurisdictional guide relates those records to ASILO's context and SCAFFOLD's change lifecycle. Package format and configuration fields belong to the technical profile or implementation declaring them; MILPA 0.1 prescribes neither a loader nor effective manifest inheritance.
Documentation structure¶
- Purpose, scope and limits.
- Concepts, vocabulary and distinctions from products with related names.
- Accepted principles.
- Verifiable requirements, provenance and evidence handling.
- Application profiles and their status; none accepted in edition 0.1.
- Reference for manifests, names, structures and rules.
- External reference to software repositories, without duplicating their documentation.
The metaphor of maize, beans and squash is a didactic analogy, not a classification of agents. It grants no permissions and defines no operational roles. See the explanatory concept if you need that distinction.