# Rollcall > Rollcall scans Wayne State's apps and reports each one's PHP image, Laravel version, auth package and PROCTOR result, checked against the dates in CREED's policy. It keeps a snapshot per scan, so you can see drift and an EOL burn-down. Checks: `composer ci` (the same command runs on GitLab and GitHub). > Every app answers "present". The ones on PHP 7.4 answer from the back row. Front page: [`site/index.html`](https://github.com/waynestate/rollcall/blob/HEAD/site/index.html). It is static, with no build step (see `site/README.md`). On Citadel, the raw-PHP deploy layer in [`deploy/`](https://github.com/waynestate/rollcall/blob/HEAD/deploy/) serves it: a Squire kit whose front controller puts `site/` behind HELMET's security headers. For local development, serve `site/` directly. Rollcall is the fleet scanner for the Wayne State application stack. For each app it records the PHP image, the lowest PHP its `composer.json` allows, the Laravel version, the auth package and its version, the PROCTOR result, and, when the app commits one, the result, Booster version and finish time of Booster's hop record (`booster-hop.json`). Then it looks up each version by date in CREED's `policy.json`. It keeps one snapshot per scan, so you can see drift and an EOL burn-down over time. It prunes old snapshots after the retention window (default 90 days; the newest one always stays). Rollcall enforces nothing. It never opens an issue, leaves a comment or deploys anything, and `scan` and `report` exit `0` whatever the fleet looks like (only `rollcall owners`, a check of the owners file, exits `1`). The public report has totals only: counts and progress, no app names, owners or rankings. The per-app list is internal. Like a good attendance sheet, it is for noticing who is missing, not for shaming them. 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 - [Rollcall: Every app answers present.](https://rollcall.apps.wayne.edu/index.md): Rollcall scans Wayne State's apps and reports each one's PHP image, Laravel version, auth package and PROCTOR result, checked against the dates in CREED's policy. It keeps a snapshot per scan, so you can see drift and an EOL burn-down. - [How it is built | Rollcall docs](https://rollcall.apps.wayne.edu/docs/architecture.md): A framework-free core plus thin entry points, a generated copy of CREED's policy reader, three data sources and the decisions behind them. - [Run the checks | Rollcall docs](https://rollcall.apps.wayne.edu/docs/checks.md): composer ci is the contract, with Docker, pipelines and the front page accessibility gate; Contributing follows. - [Use Rollcall from your coding agent (ADVISOR) | Rollcall docs](https://rollcall.apps.wayne.edu/docs/guides/advisor.md): Rollcall ships an ADVISOR module with three read-only tools that answer public counts only. - [Citadel's registrations export | Rollcall docs](https://rollcall.apps.wayne.edu/docs/guides/citadel.md): Read base images and forced upgrade dates from a saved Citadel export, in Citadel's own field names. Rollcall never calls Citadel. - [Run the collector in Docker | Rollcall docs](https://rollcall.apps.wayne.edu/docs/guides/collector-docker.md): Build the collector image and run a scan with docker run, with no PHP on the machine. - [Owner digests | Rollcall docs](https://rollcall.apps.wayne.edu/docs/guides/digest.md): An opt-in digest per owner, about only their apps and only when something changed; printed by default, mailed only behind a flag and three settings. - [Laravel | Rollcall docs](https://rollcall.apps.wayne.edu/docs/guides/laravel.md): Register the package, publish the config, schedule the scan, and enable the dashboard routes; show the same dashboard as one of your own Inertia (Vue) pages, or serve it from a raw PHP app with one call. - [Metrics | Rollcall docs](https://rollcall.apps.wayne.edu/docs/guides/metrics.md): Metrics are off by default; with ROLLCALL_METRICS_ENABLED=true, /metrics serves Prometheus text from the latest snapshot. - [Quick start | Rollcall docs](https://rollcall.apps.wayne.edu/docs/guides/quick-start.md): Scan and report on the fixtures in the repo, with no network and no token. - [What the report says | Rollcall docs](https://rollcall.apps.wayne.edu/docs/guides/what-the-report-says.md): The sections of a Rollcall report: versions, states, drift kinds, progress, the EOL burn-down and forced upgrades. - [WSU values (Playbook) | Rollcall docs](https://rollcall.apps.wayne.edu/docs/guides/wsu-values.md): ROLLCALL_GITLAB_URL may come from Playbook when the environment has none; the token never does. - [Rollcall | Rollcall docs](https://rollcall.apps.wayne.edu/docs/index.md): Rollcall is the fleet scanner for the Wayne State application stack. - [Install | Rollcall docs](https://rollcall.apps.wayne.edu/docs/install.md): Install Rollcall from Packagist with one Composer line. - [Commands | Rollcall docs](https://rollcall.apps.wayne.edu/docs/reference/commands.md): The rollcall commands, generated from the CLI, with the exit codes and what each one prints. - [Configuration | Rollcall docs](https://rollcall.apps.wayne.edu/docs/reference/configuration.md): Every Rollcall setting is an environment variable; the table is generated and the GitLab setup follows it. - [Contract | Rollcall docs](https://rollcall.apps.wayne.edu/docs/reference/contract.md): The JSON Schemas Rollcall's report, snapshots and inputs must match, and the suite that checks real output against them. - [Proof | Rollcall docs](https://rollcall.apps.wayne.edu/docs/reference/proof.md): Rollcall's first scheduled scan of the stack on GitLab CI, and a rerun over 58 Wayne State applications on 2026-11-06: what ran, what held, what it caught in Rollcall, and what it does not prove yet. - [Scripts on every OS | Rollcall docs](https://rollcall.apps.wayne.edu/docs/reference/scripts.md): Which Rollcall commands are one PHP command for every OS, which ship as a PowerShell and bash pair, and which run only inside Citadel's container. - [Security notes | Rollcall docs](https://rollcall.apps.wayne.edu/docs/security.md): Rollcall is read-only toward every source, needs one read_api token and says exactly why, keeps that token out of git and output, and treats scanned files as data. ## Prompts - [Get started with Rollcall](https://rollcall.apps.wayne.edu/#prompt-get-started): Call the sample roll from a checkout, with the bundled fixtures, and have the agent read the report back to you. The prompt itself is in https://rollcall.apps.wayne.edu/index.md. - [Rollcall as a plain PHP tool](https://rollcall.apps.wayne.edu/#prompt-raw-php): The CLI on a schedule, and the dashboard page and the /metrics and /report.json front controller only if you ask for them. The prompt itself is in https://rollcall.apps.wayne.edu/index.md. - [Rollcall in a Laravel app](https://rollcall.apps.wayne.edu/#prompt-laravel): The scheduled scan and the dashboard of totals: the package's Blade page, or in an Inertia app one of your own Vue pages, inside your layout. The prompt itself is in https://rollcall.apps.wayne.edu/index.md. ## Source - [README](https://github.com/waynestate/rollcall/blob/HEAD/README.md): the project's README, with install, commands and checks - [Everything in one file](https://rollcall.apps.wayne.edu/llms-full.txt): the README and every page above, as one Markdown file ## Optional - [ADVISOR](https://advisor.apps.wayne.edu/llms.txt): the stack's MCP server: read-only tools that answer from CREED's policy and the parts' docs instead of from memory - [WELD](https://weld.apps.wayne.edu/llms.txt): the Wayne State application stack: every part, and the reference app