Translation
Translated from the Spanish source, which is the normative text. Status: draft pending human review. Differences are resolved in the Spanish text.
ASILO: evaluate boundaries and effects¶
Current ASILO 0.1 guide; informative translation. Each test identifies contract, version, environment, configuration, scenario, expected result, observed result and limitations. A favourable test list does not establish complete security.
| Scenario | Illustrative check |
|---|---|
| Forbidden dependency | Detect the link, including indirect paths within the check's declared scope. |
| Malformed input | Reject without the requested operation. |
| Valid input without authority | A valid contract does not bypass permission rejection. |
| Different resource or context | Authority cannot be reused outside its declared scope. |
| Expiry or revocation | The relevant point rejects expired or withdrawn authority according to the contract. |
| Single use and concurrency | The mechanism respects the declared number of uses and effects. |
| Cached data | A cached response does not bypass current authorisation. |
| Deferred work | Queues and retries preserve or recheck authority according to the profile. |
| Later failure | Distinguish completed effect, response failure and possible compensation. |
| Exhausted limit | Stopping preserves evidence and prevents additional prohibited effects. |
| Untrusted code | State the host boundary; modules and types do not establish isolation. |
A negative result may reveal a defect or an ill-defined applicability condition. Preserve both; do not change the expected result merely to pass. Residual risks and uninspected scenarios remain visible.
When claiming ASILO requirements, cite their applicability conditions. MILPA may organise sources, authority and evidence. This guide does not extend either method's scope automatically.