Fleet attendance, Wayne State University
ROLLCALL
Every app answers “present”.
The ones on PHP 7.4 answer from the back row.
Rollcall is the stack's fleet scanner. For each app it records the PHP image, the lowest PHP its composer.json allows, the Laravel version, the auth package and the PROCTOR result. Then it looks up each version in CREED's policy.json. Every scan is kept as a snapshot, so you can see drift and how fast the EOL apps are going away.
composer require waynestate/rollcall
Promoted to 1.2.0, on Packagist. Inside 1.x the report, the snapshot and the image list never lose or retype a field: the contract says so.
Works alongside WELD. Rollcall doesn't go inside your app. You run it on its own to see what every app in the fleet is running, WELD apps included.
- kiln-bookingPHP 8.5present
- tuba-rentalPHP 8.4present
- pigeon-postPHP 8.3late
- lunch-ledgerPHP 8.3late
- abacus-classicPHP 7.4back row
Answered 5 of 5
A sample roll
Take the roll
Seventeen made-up apps, seated by PHP version with the newest at the front. As you scroll, Rollcall calls each name. The back row answers with a hand in the air.
Sample data · fictional apps · policy as of 2026-10-28
| No. | App | PHP image | Laravel | Auth | PROCTOR | Mark |
|---|---|---|---|---|---|---|
| Front row PHP 8.5 and 8.4, active | ||||||
| 01 | kiln-booking | 8.5 | 13 | sesame | pass | present |
| 02 | tuba-rental | 8.4 | 13 | sesame | pass | present |
| 03 | moth-catalog | 8.4 | 12 | sesame | pass | present |
| 04 | quad-weather | 8.4 | 13 | none | pass | present |
| 05 | greenhouse-log | 8.4 | 12 | sesame | pass | present |
| 06 | sundial | 8.4 | 13 | sesame | pass | present |
| 07 | otter-tracker | 8.4 | 12 | sesame | pass | present |
| Middle rows PHP 8.3 and 8.2, security fixes only | ||||||
| 08 | pigeon-post | 8.3 | 12 | phpcas | pass | late |
| 09 | lunch-ledger | 8.3 | 12 | sesame | fail | late |
| 10 | chess-club | 8.3 | 11, EOL | phpcas | pass | late |
| 11 | lost-mittens | 8.3 | 12 | none | none | late |
| 12 | fog-index | 8.2 64 days left | 11, EOL | phpcas | pass | late |
| Back row past end of life | ||||||
| 13 | abacus-classic | 7.4 | 8, EOL | phpcas | none | back row |
| 14 | punch-card-pal | 7.4 | none | none | none | back row |
| 15 | dial-up-directory | 8.1 | 10, EOL | phpcas | fail | back row |
| 16 | floppy-archive | 8.0 | 9, EOL | sesame | pass | back row |
| 17 | ghost-kiosk | legacy-base no version in the tag | none | none | none | inaudible |
- present
- 7
- late
- 5
- back row
- 4
- inaudible
- 1
- Answered
- 17
Nobody is marked absent. If one source has a gap, like a missing PROCTOR report or a bad image tag, that app gets a note and the scan carries on. The public report only shows totals like these. The per-app list is the internal view (--internal), and it stays inside the project.
Five answers per app
What “present” means
Four of the answers are versions, and Rollcall looks each one up by date in CREED's policy.json. No support date is written into Rollcall's code. The fifth answer is PROCTOR's own result.
PHP image
The image the app actually runs on, read from its tag in the app list.
PHP floor
The lowest PHP its
composer.jsonallows.*counts as no floor at all.Laravel
The version that's installed, read from
composer.lock.Auth package
Which sign-in package is installed: SESAME, a CAS client, or none.
PROCTOR
pass,failornone, from PROCTOR's JSON report. Rollcall never re-runs a rule.
Key to the marks
- present
active: fully supported - late
security_only: security fixes only, and the end date is set - back row
eol: past its security date, or older than anything the policy lists - inaudible
unknown: newer than the policy knows, or a tag nobody can read
| Runtime or tool | Version | Support state | End of support |
|---|---|---|---|
| php | 8.1 | eol_grace_expired | 2025-12-31 |
| php | 8.2 | security | 2026-12-31 |
| php | 8.3 | security | 2027-12-31 |
| php | 8.4 | active | 2028-12-31 |
| php | 8.5 | active | 2029-12-31 |
| laravel | 10 | eol_grace_expired | 2025-02-04 |
| laravel | 11 | eol_grace_expired | 2026-03-12 |
| laravel | 12 | security | 2027-02-24 |
| laravel | 13 | active | 2028-03-17 |
| node | 20 | eol_grace_expired | 2026-04-30 |
| node | 22 | security | 2027-04-30 |
| node | 24 | security | 2028-04-30 |
| node | 26 | active | 2029-04-30 |
| mysql | 5.6 | eol_grace_expired | 2021-02-28 |
| mysql | 5.7 | eol_grace_expired | 2023-10-31 |
| mysql | 8.0 | eol_grace_expired | 2026-04-30 |
| mysql | 8.4 | active | 2032-04-30 |
| mysql | 9.7 | active | 2034-04-30 |
| vue | 2 | eol_grace_expired | 2023-12-31 |
| vue | 3 | active | n/a |
| inertia | 2 | active | n/a |
| inertia | 3 | active | n/a |
| composer | 2.8.0 | minimum | n/a |
Drift and the burn-down
Watch the back row empty
Rollcall keeps one snapshot per scan day. Count the apps on an EOL image in each one and you get a line that should only go down.
Grafana draws the same line from /metrics with the bundled dashboard, grafana/rollcall-burn-down.json. Each scan day also counts the roll per PHP minor, Laravel major and support state, so the JSON report shows which lines the fleet is leaving and which it is joining.
Drift, counted per kind
image_eolruns on an EOL PHP imageimage_unknownan image tag nobody can readimage_below_floorthe image is older than the app allowsfloor_allows_eolthe PHP floor still lets an EOL version infloor_unboundedno PHP floor declared at alleol_past_gracepast the policy's grace dayslaravel_eolLaravel past its security dateproctor_missingno PROCTOR report on fileproctor_failingPROCTOR says failoverride_expireda PROCTOR override ran out
rollcall drift also compares the policy with a saved endoflife.date page. A difference is a flag for a person; the policy stays the source of truth.
From a checkout, with the bundled fixtures
Quick start
This runs on the fixtures in the repo, so you need no network and no token, just PHP 8.3 or newer. Run composer install once, then the commands below.
bash
export ROLLCALL_POLICY_FILE=tests/fixtures/policy.json export ROLLCALL_REPOS_DIR=tests/fixtures/repos export ROLLCALL_IMAGES_FILE=tests/fixtures/images.json export ROLLCALL_PROCTOR_DIR=tests/fixtures/proctor export ROLLCALL_STORE_DIR=var/snapshots php bin/rollcall scan php bin/rollcall report
PowerShell, no bash or WSL needed
$env:ROLLCALL_POLICY_FILE = "tests/fixtures/policy.json" $env:ROLLCALL_REPOS_DIR = "tests/fixtures/repos" $env:ROLLCALL_IMAGES_FILE = "tests/fixtures/images.json" $env:ROLLCALL_PROCTOR_DIR = "tests/fixtures/proctor" $env:ROLLCALL_STORE_DIR = "var/snapshots" php bin/rollcall scan php bin/rollcall report
What comes back real output, abridged, Rollcall 1.1, bundled fixtures (four demo apps)
Present: 4 apps. Snapshot 2026-10-28 saved to var/snapshots. ROLLCALL 1.1.1 | scan 2026-10-28 | as of 2026-10-28 | public Apps present: 4 (scan notes: 0) PHP image VERSION APPS STATE SECURITY UNTIL DAYS TO EOL 8.1 1 eol 2025-12-31 -320 8.3 1 security_only 2027-12-31 410 8.4 1 active 2028-12-31 776 unknown 1 unknown - - EOL burn-down (state on each scan day) DATE APPS EOL SUPPORTED UNKNOWN 2026-11-16 4 1 2 1
exit 0, however the fleet looks. There is no exit 1: Rollcall takes attendance, it does not hand out detention.
2026-10-28 4 1 2 1exit 0, however the fleet looks. Neither command exits 1: Rollcall takes attendance, it does not hand out detention.
rollcall scan- Scans once and saves
<date>.json. A second scan on the same day replaces it. rollcall report--format=text|json|prometheus.--internaladds the per-app list; keep that inside the project.rollcall drift--feed=<file>, a saved endoflife.date page. Rollcall never fetches it itself.- In Laravel
- The package registers itself. Publish the config with
php artisan vendor:publish --tag=rollcall-config, then schedulephp artisan rollcall:scan.
Left on the desk for your agent
Notes for the substitute
Your coding agent is the substitute teacher here: it has never met this class. Each note tells it where to read up on Rollcall and what it must leave alone, and asks it to check with you before it guesses. Copy one, or open it in OpenCode, Claude Code, Codex or ChatGPT.
Note 1 · Any machine with PHP or Docker
Get started with Rollcall
Call the sample roll from a checkout, with the bundled fixtures, and have the agent read the report back to you.
You are a coding agent helping a Wayne State University developer try Rollcall, the fleet scanner of WELD, the Wayne State application stack. Rollcall reads each app's composer.json and composer.lock, its PHP image and its PROCTOR report, and checks every version against CREED's policy.json by date. It enforces nothing: scan and report always exit 0.
Read first:
- https://rollcall.apps.wayne.edu/llms.txt, the index of Rollcall's pages, each one as Markdown. Work from them, not from memory.
- ADVISOR, the stack's MCP server, if it is connected: get_project_status and read_project_docs with project rollcall, and policy_lookup for PHP. If it is not connected, say so and work from the pages. How to add it: https://advisor.apps.wayne.edu/llms.txt
- The README in this folder, if this folder is a Rollcall checkout. If it is not, ask me whether to clone https://github.com/waynestate/rollcall first.
Task:
1. Install the dependencies once with `composer install` (PHP 8.3 or newer). If the host has no PHP, use the Docker line in the README's Run the checks section.
2. Point Rollcall at the bundled fixtures: set ROLLCALL_POLICY_FILE, ROLLCALL_REPOS_DIR, ROLLCALL_IMAGES_FILE, ROLLCALL_PROCTOR_DIR and ROLLCALL_STORE_DIR the way the README's Quick start does.
3. Call the roll with `php bin/rollcall scan`, then print it with `php bin/rollcall report`.
4. Read the report back to me: each PHP image, the state CREED gives it, and the days left before end of life.
Constraints:
- Fixtures only: no network and no GitLab token. A real scan needs a read_api group or project access token (a GitLab bot), which a role, the stack maintainer, makes and rotates; never invent one.
- Give separate commands for Windows (PowerShell), macOS and Linux wherever they differ.
- The per-app list (report --internal) stays inside the project. Never paste app names anywhere public.
- Ask me before you guess, and before you touch anything outside this folder.
Output: the commands you ran, the report, then a short reading of it and your questions.
Or leave the note for your kind of app
Note 2 · Raw PHP, no framework
Rollcall as a plain PHP tool
The CLI on a schedule, and the dashboard page and the /metrics and /report.json front controller only if you ask for them.
You are a coding agent setting up Rollcall, the fleet scanner of WELD, the Wayne State application stack, as a plain PHP tool with no framework: a scan on a schedule from the command line and, only if I ask, the dashboard page of totals and the /metrics and /report.json endpoints.
Read first:
- https://rollcall.apps.wayne.edu/llms.txt, then the README it links: the Commands, Configuration and Metrics sections, and The dashboard in a raw PHP app.
- ADVISOR, the stack's MCP server, if it is connected: list_stack_rules with permutation raw-php for the rules that apply, and policy_lookup for PHP. If it is not connected, say so and work from the pages.
- This project's composer.json, and how this host runs scheduled jobs.
Task:
1. Add Rollcall with `composer require waynestate/rollcall`. The CLI is `vendor/bin/rollcall`.
2. Write the settings as environment variables from the README's Configuration table: the policy file, the store folder and the source. Start with directory fixtures; switch to GitLab only once the read_api token exists (the stack maintainer makes it) and you have the group.
3. Schedule the scan subcommand once a day with --prune, and show me the report subcommand in text and in json.
4. Only if I ask for metrics: serve the package's public/index.php front controller, with ROLLCALL_METRICS_ENABLED and either ROLLCALL_METRICS_TOKEN or ROLLCALL_METRICS_ALLOW set.
5. Only if I ask for the dashboard: add one file under the served folder that calls rollcall_dashboard(), after helmet_boot() with its nonce when this app runs HELMET. Turn it on with ROLLCALL_DASHBOARD_ENABLED and give it WayneUI's stylesheet with ROLLCALL_WAYNEUI_CSS. Leave the per-app page (ROLLCALL_INTERNAL_ENABLED plus 'internal' => true) off unless I ask; it belongs only behind this app's sign-in.
Constraints:
- Rollcall is read-only toward every source and writes only its snapshot folder (plus digest files, when `rollcall digest --out` is asked for). Keep it that way.
- The GitLab token is a read_api group or project access token (a GitLab bot) that the stack maintainer makes and rotates; it comes from the environment as ROLLCALL_GITLAB_TOKEN. Never commit it, log it or print it.
- Metrics, the public report and the dashboard stay off unless I turn them on.
- Give separate commands for Windows (PowerShell), macOS and Linux wherever they differ, schedules included.
- Ask me before you guess, and before you touch a deploy or a scheduler.
Output: the files you changed, the schedule entry for each OS, then your questions.
Note 3 · Laravel, Blade or Inertia
Rollcall in a Laravel app
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.
You are a coding agent adding Rollcall, the fleet scanner of WELD, the Wayne State application stack, to a Laravel app: the scheduled scan, the dashboard page of totals and, only if I ask, the internal per-app page.
Read first:
- https://rollcall.apps.wayne.edu/llms.txt, then the README it links: the Laravel, Configuration and Metrics sections.
- ADVISOR, the stack's MCP server, if it is connected: list_stack_rules with the permutation that fits this app (laravel-blade, laravel-blade-vue or laravel-inertia-vue), and policy_lookup for PHP and Laravel. If it is not connected, say so and work from the pages.
- composer.json, composer.lock, config/, routes/, bootstrap/app.php and .env.example.
Task:
1. Add Rollcall with `composer require waynestate/rollcall`. Its service provider registers itself.
2. Publish the config with `php artisan vendor:publish --tag=rollcall-config`, and add the settings to .env.example as placeholders.
3. Schedule `php artisan rollcall:scan` once a day.
4. Turn on the dashboard with ROLLCALL_DASHBOARD_ENABLED. In a Blade app it is the package's page in WayneUI's class names; give it WayneUI's stylesheet with ROLLCALL_WAYNEUI_CSS. In an Inertia app (WELD), publish the Vue page with `php artisan vendor:publish --tag=rollcall-inertia`, set ROLLCALL_DASHBOARD_INERTIA and rebuild the assets, so it renders inside this app's own layout.
5. Leave the per-app page (ROLLCALL_INTERNAL_ENABLED) off unless I ask. It runs behind the web and auth.sesame middleware and fails closed without them.
Constraints:
- Meet each setting the Laravel way (config, the scheduler, middleware) before writing code of your own.
- If this app already serves /metrics (HELMET does), leave Rollcall's metrics off.
- Never commit a real token or a .env file.
- Ask me before you guess, and before you touch migrations, auth or anything that deploys.
Output: the files you changed, the scheduler entry, then your questions.
Your agent reads the same pages you do. llms.txt lists them, llms-full.txt has all of them in one file, and this page has a Markdown twin. The buttons only copy text or open the tool you pick; nothing is sent anywhere.
Classroom rules
For noticing who is missing, not for shaming them
It enforces nothing.
It never opens an issue, leaves a comment or deploys anything, and its scan and report exit
0whatever they find.The public report has totals only.
Counts and progress. There are no app names, owners or rankings in it.
It only reads.
GETandHEADonly, and a test fails if a write verb shows up insrc/. It writes its own snapshot folder, and digest files only when you ask.Metrics stay off until you turn them on.
Once they're on,
/metricsneeds a bearer token or an allowed address. If neither is set, nobody gets in.
Three sources and a policy
Where the answers come from
Rollcall reads three sources plus CREED's policy, and writes one snapshot per scan day. Each source also has a fixture adapter, so you can try all of it without a live GitLab.
- Repositories
composer.jsonand.lock, from GitLab or a folder - App listthe PHP image each app runs
PROCTORone JSON report per app, from a folder or CI
CREEDpolicy.json, the dates
- Terminal
textandjsonreports - /metricsPrometheus text, off by default
- Grafanathe bundled burn-down dashboard
- Dashboard pageWayneUI totals, in Laravel, Inertia/Vue or raw PHP
Rollcall's place in the stack
The class list
These are the parts of the Wayne State application stack, and what each one has to do with Rollcall. WELD is the Laravel starter app that has most of them installed.
WayneUIthe interface; the dashboard wears its classes
CREEDwrites the dates Rollcall reads
PROCTORchecks one app; Rollcall collects the results
PreflightCI templates, where PROCTOR reports are born
SESAMEthe auth package Rollcall counts
HELMETbaseline runtime, with its own /metrics
Pinstripethe Pint and PHPStan rules this repo wears
Sourdoughstarters that begin in the front row
WELDthe Laravel starter app, with the stack already set up
Rollcallyou are here: the fleet census and EOL burn-down
Boostermoves the back row forward
Squirecarries the release to Citadel
ParityCitadel on your computer, so the dress rehearsal counts
Drawbridgethe sign-in gateway for Citadel
ADVISORthe MCP server your agent asks about the stack