Translation
Translated from the Spanish source, which is the normative text. Status: draft pending human review. Differences are resolved in the Spanish text.
Application profiles¶
No profile is in force in edition 0.1. This page explains what a profile is and which ones are in preparation.
What a profile is¶
A profile selects and makes concrete requirements for a context: a language, a project type or a jurisdiction. It can fix file formats, names, tools or thresholds that the method leaves open. A profile does not change the base method nor add obligations to other projects.
That is why the requirements do not fix a folder tree, a language or ring numbering: those decisions belong to a profile.
To separate the international core from territorial decisions, see Applying jurisdictional profiles. The guide distinguishes language and formatting, time zone, jurisdiction and data location, without accepting a profile or changing requirements.
In preparation¶
| Profile | Method | What it would make concrete | Related requirements |
|---|---|---|---|
| Structure by project type: node, product dossier, single-repository software, monorepo, research and library | MILPA | Folders and files by project type, on top of the common core of seven functions. | MILPA-R-004, MILPA-R-006 |
| Manifest in JSON | MILPA | File name, format and schema of the manifest. | MILPA-R-004 |
| Reserved vocabulary by context | MILPA | Versioned list of reserved names. | MILPA-R-005 |
| ASILO for TypeScript | ASILO | Layers in packages, boundary contracts, context budget, agent scope and naming conventions. | ASILO-R-001 to ASILO-R-004, ASILO-R-007 |
| Privacy in Mexico: proposal | ASILO | Inventory and privacy questions for a limited private-sector case; sources and review pending. | ASILO-R-006 |
The existence of software that already uses one of these profiles does not make them in force: an implementation does not decide the authority of the method.
How a profile is proposed¶
- Name the application context and the requirements it makes concrete.
- Separate what the profile fixes from what the method already requires.
- Record its origin and conflicts with other sources.
- State which software, if any, intends to cover it, without claiming conformance.
- Request the decision of the method owner.
See layers and rings for a generic explanation. Its examples do not establish an accepted TypeScript profile.
Engineering and artifact evidence¶
Proposed engineering profile and artifact verification guide: agnostic application, criteria, evidence and limits; no new universal requirements.