Translation
Translated from the Spanish source, which is the normative text. Status: draft pending human review. Differences are resolved in the Spanish text.
Files, folders, and names¶
Current application guide based on MILPA 0.1. It does not prescribe a universal folder tree.
Structure helps you find knowledge and know what can be changed. Start with the functions you need to locate, not by copying another project's tree.
Seven functions, not seven files¶
The core of MILPA-R-006 contains these functions. Each has an identifiable place; the specific names belong to the profile.
| Function | What it lets you find |
|---|---|
| Manifest | The project's identity, scope, and owner. |
| Entry point for readers | What the project is and where to start. |
| Sources and links | Origin of the knowledge and declared relationships. |
| Instructions for agents | Rules that apply when agents operate. |
| Document index | Map from the general to the detail. |
| Decisions | What was decided, by whom, and on which revision. |
| Separate temporary material | Drafts and exploration that are not confused with accepted text. |
A project can spread them across several documents or gather some into one. The guide does not
turn README.md, AGENTS.md, SOURCE.md, docs/, plans/, or .asilo/ into mandatory
universal names.
Order from the general to the particular¶
A short entry point explains purpose, scope, and next step. The index leads to topics; topics link to decisions, requirements, and evidence. That path avoids loading the whole project to answer a small question.
As an exercise, build a table with “function → actual location → owner → review”. Check that the locations exist and that the index does not link to a plan as if it were already implemented. The table is a reading aid, not an accepted methodological schema.
Declare names before using them¶
MILPA-R-005 asks for declared and versioned reserved vocabulary. A reserved name keeps its meaning; a new one needs a recorded change in that vocabulary. Proper names of products or domains are excluded.
Earlier lists and a language's conventions do not thereby become universal vocabulary. The content and version of the base vocabulary need to be specified; see the profiles in preparation.
Integrate without merging¶
When two projects are related, MILPA-R-007 asks for both ends to declare provider, consumer, contract and version, data that crosses, owner, status, and evidence. Sharing a folder or a brand does not demonstrate integration. For a published version, a local path cannot be the only link mechanism.
A structure change keeps its provenance and the decisions that justify it. If there are incompatible rules, record the conflict according to MILPA-R-008; do not resolve it only by renaming folders.
Next: context and handoffs · See artifacts
A map of functions¶
Building signs show where activities happen. A structure similarly helps locate sources and decisions. Room names may change while functions remain identifiable. The map enforces no permissions.