Overview
Squire
Squire is the deploy kit for Citadel. It writes your app's build, release and health-check scripts from templates, checks them with squire doctor, and runs the app locally on Citadel's PHP image behind the same kind of proxy.
Content and agent signals
For agents (AI-generated): Squire, the deploy kit for the Wayne State Citadel PHP stack: generates build, release and health-check scripts, runs squire doctor checks, and runs apps locall
Files
Publisher files and the directory’s indexed copy.
Read the cached llms.txt preview
Their llms.txt
The beginning of the file, from our validated copy saved 2026-11-14T06:20:52.062Z. Cached copy · Source on wayne.edu
# Squire
> Squire is the deploy kit for Citadel. It writes your app's build, release and health-check scripts from templates, checks them with squire doctor, and runs the app locally on Citadel's PHP image behind the same kind of proxy.
**Suits you up for deploy day.** A squire carries the kit, readies the armor and gets the knight on the field.
Documentation: [squire.apps.wayne.edu/docs/](https://squire.apps.wayne.edu/docs/)
Checks: `composer ci` (the same command runs on GitLab and GitHub).
Squire is the Citadel kit: build.sh, the release script, the health check, and local parity on the real images. Its docs builder turns `docs/` into the committed pages under `site/docs/`, with a changelog page generated from `CHANGELOG.md` when the nav lists one. It is part of WELD, the Wayne State application stack, beside WayneUI (project 0, the interface layer), CREED, PROCTOR, Preflight, SESAME, HELMET, Pinstripe, Sourdough and [Parity](https://git.wayne.edu/enterprise-apps/parity). Squire gets the app onto Citadel; Parity runs Citadel on your computer, and takes over from Squire's own parity kit, which is deprecated (see [Local parity](https://squire.apps.wayne.edu/docs/guides/local-parity.html)).
**Not to be confused with:** `squire doctor` checks deploy setup only; standards checks are PROCTOR's.
> A knight never suits up alone. Your app shouldn't deploy alone either.
Front page: [`site/index.html`](https://github.com/waynestate/squire/blob/HEAD/site/index.html), a static page you can serve from anywhere.
On Citadel it is served by the raw-PHP deploy layer in [`deploy/`](https://github.com/waynestate/squire/blob/HEAD/deploy/): a Squire kit whose front controller serves `site/` behind HELMET's security headers. For local development, keep serving `site/` directly.
Status: 0.11.1, tagged and on Packagist.
Every page below is Markdown. The HTML pages send the same Markdown to a client that asks for `text/markdown`. Written by Squire's agent-ready kit from the README and the pages; do not edit.
## Pages
- [Squire: Suits you up for the Citadel.](https://squire.apps.wayne.edu/index.md): Squire is the deploy kit for Citadel. It writes your app's build, release and health-check scripts from templates, checks them with squire doctor, and runs the app locally on Citadel's PHP image behind the same kind of proxy.
- [Squire 0.1 plan | Squire docs](https://squire.apps.wayne.edu/docs/0.1-plan.md)
- [Changelog | Squire docs](https://squire.apps.wayne.edu/docs/changelog.md): All notable changes to this project.
- [Contributing | Squire docs](https://squire.apps.wayne.edu/docs/contributing.md): Where Squire's code lives, the commands that build, lint and test it, and the steps a release goes through before it is tagged.
- [Use Squire from your coding agent (ADVISOR) | Squire docs](https://squire.apps.wayne.edu/docs/guides/advisor.md): Install the ADVISOR module so a coding agent can run Squire's checks from its sandbox with the two read-only tools squire_d
…
Published headings
The index marks this publisher’s heading coverage as partial.
5 indexed headings in this publisher record.
Headings describe indexed content. They do not establish a working integration or endorsement.
Agent access
Review the publisher’s own access terms before automated use.
Machine-readable: GET /v1/resolve?q=wayne.edu · GET /v1/domain/wayne.edu · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Indexing evidence
Authority, classification and country evidence
Own or manage this website?
If you own or manage wayne.edu, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free account required for verification and live checks. No backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for wayne.edu:
1. POST https://agentwebmap.com/v1/sites/wayne.edu/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://wayne.edu/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/wayne.edu/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/wayne.edu).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.