/of — alias for orderfield

Two names. One kernel. /of is /orderfield. Product surface (sibling README) leads with typical problems → what Orderfield does. Mid-flight plan-change H2 sits before Install.

Load the sibling skill and follow it. Stop if it is missing. Do not invent a second contract.

Human install or verify: the sibling path is bash docs/demo/mortal-install.sh --global (or --root PATH), then of doctor must print ok. Pin recipe stays README / PUBLISH. Not pip. Not a daemon.

Doctor / status / resume / pulse ask the user at most once a day when a newer release exists. On yes: ORDERFIELD_VERSION=<ver> bash install.sh --global --from-release (release tar.gz + SHA256SUMS). Do not upgrade mid-ORDER without consent. Not a silent auto-update.

In-flight is not done: while any residual is MISSING, of status / of resume print running + the live PULSE + a speak line (quote a PULSE line above to the user; do not claim done while running). Before ending a turn or saying the mission is done, run one of them and quote the live PULSE — the human never runs of pulse by hand. Follow the sibling.

Close is proof: the sibling names docs/close-is-proof.md. Residual empty is not the close.

Published claims stay ≤98% honest. After skill/docs edits: python3 docs/audit/check-claims.py (also inside validate-skill.sh). Follow the sibling.

Chat-dump residuals still cannot collect. Structured evidence over 4000 chars (counts, paths, shas) can. A size refuse names scratch/<child>/notes.md + re-spawn the same packet. Follow the sibling.

Gaps as prose: of contrast --diff narrates SPEC vs coverage from the same ContrastReport + spec-diff facts. RESOLVED is not CLOSED. No theater. Follow the sibling.