PHPAML

Documentation · Chapter 19

Recover AML and the project runtime safely.

A missing aml command, a damaged cache, and an absent project runtime are three different problems. Identify which layer fails before reinstalling anything.

Every lesson starts from the problem, explains the mechanism, then gives a concrete verification.

LESSON OBJECTIVE

What you will be able to do

Distinguish shell installation, cache, project manifest, runtime, permission, and network failures.

When aml is not found

Open a new terminal, check the installation path and PATH, then run aml version. Do not confuse a shell alias problem with a broken project.

phpaml — zsh
aml version
aml install
aml doctor --json

When runtime is missing

If runtime disappeared, keep src, routes, public, manifests, and locks intact; run aml install then doctor. Never restore by copying an unknown runtime from another project.

When downloads or permissions fail

Permission denied and network unavailable need different actions. Inspect the target directory, cache, checksum, proxy/DNS, and offline availability.

CHECKPOINT

Before you continue

Which exact layer is broken, and what single observation rules out the neighboring layers?