---
title: "Squire 0.1 plan | Squire docs"
url: https://squire.apps.wayne.edu/docs/0.1-plan.html
llms: https://squire.apps.wayne.edu/llms.txt
generator: Squire agent-ready
---

# Squire 0.1 plan [#](https://squire.apps.wayne.edu/docs/0.1-plan.html#squire-0-1-plan)

Sources: the Squire best-practice rules (S1 to S78), the Citadel facts gathered from a read-only clone of Citadel, and the WELD portfolio entry for Squire. This is the plan the 0.1 build followed; `OPEN_QUESTIONS.md` records where it had to guess.

## Goal [#](https://squire.apps.wayne.edu/docs/0.1-plan.html#goal)

A WSU developer with a PHP app (raw PHP or Laravel) runs `vendor/bin/squire init` and gets the files Citadel needs, plus a local setup that behaves like Citadel. `vendor/bin/squire doctor` tells them which best practices the app breaks.

## Shape [#](https://squire.apps.wayne.edu/docs/0.1-plan.html#shape)

1. **A Composer package**, `waynestate/squire`, PHP `^8.3`, tested on 8.3, 8.4 and 8.5, with a Symfony Console CLI.
2. **`squire init`** writes the scripts from templates and records a SHA-256 of each file in `.squire.json`. `squire init --check` reports drift and exits 1 (depend, do not copy). It never overwrites a file the team edited unless told to with `--force`.
3. **`squire doctor`** checks an app against the rules that a machine can decide, exits 1 on a failure, 2 on a tool error, and has a JSON format. Drift from the templates is a warning only.
4. **Templates** in two targets, raw PHP and Laravel (detected from `artisan`), in two groups:
   - `release`: `build.sh`, `deployments/001-first-release.sh`, `scripts/release.sh`, `health.php`, `public/up.php` (raw only).
   - `parity`: `docker-compose.squire.yml`, a `.squire/` folder (Dockerfile, proxy config, php.ini, vhost, a fallback base image), `scripts/parity.sh`, `scripts/parity.ps1`, `.env.squire.example`.
5. **Platform proposals.** Squire's maintainers send platform improvement proposals to the platform team privately; nothing in this repository touches a server.

## Constraints that shaped the templates [#](https://squire.apps.wayne.edu/docs/0.1-plan.html#constraints-that-shaped-the-templates)

- Citadel runs `build.sh` with `/bin/sh` as root, with only that file copied in. So `build.sh` is POSIX sh and installs system packages only. Composer and npm never run there (S1).
- Deployment hooks run once per file name for the life of an app, as the `citadel` user, and Apache is not up yet. So the hook calls the release script with the smoke test off, and the same script is the Quick Update post-script, where the smoke test is on.
- A Quick Update post-script cannot roll anything back. So PROCTOR is a report there, never a gate (S20).
- The health check runs every five minutes with a 15 second timeout. So `health.php` is a small CLI script that makes one HTTP request and never boots the framework (S55).
- The shared MySQL is 5.6. So the Laravel template and `doctor` warn about JSON columns and 191 character indexes (S18).

## Build order [#](https://squire.apps.wayne.edu/docs/0.1-plan.html#build-order)

1. Scaffold and CI files (GitLab and GitHub), Pint, PHPStan level 8, PHPUnit.
2. Template catalog, manifest, `init` and `--check`.
3. Templates and their tests, including running the real shell templates with stub programs.
4. `doctor` and its rules.
5. Local parity kit, run end to end once on Docker Desktop.
6. Shell and PowerShell linting in Docker (shellcheck, PSScriptAnalyzer).
7. README, best practices, changelog, open questions.

## Done means [#](https://squire.apps.wayne.edu/docs/0.1-plan.html#done-means)

`composer ci` passes in Docker, the shell templates pass shellcheck, the PowerShell passes PSScriptAnalyzer, the parity kit has been brought up once with a healthy app behind the proxy, and every guess is in `OPEN_QUESTIONS.md`.
