# CREED

> CREED is the Wayne State app stack's written standard: 54 numbered practices, policy.json with the support dates for PHP, Laravel, Node, MySQL, Vue and Inertia, and a small PHP reader that tells a tool what state a version is in on a given day.

**The standard everything rests on.** The Wayne State App Stack Code: one policy file, one reader, and an
inspector who stamps what he finds.

**Not to be confused with:** CREED is the rules; PROCTOR checks an app against them.

Checks: `composer ci` (the same command runs on GitLab and GitHub).

Front page: [`site/index.html`](https://nougat.snu.gs/enterprise-apps/creed/blob/HEAD/site/index.html), a static page you can open in a browser or serve from `site/`.
On Citadel it is served by the raw-PHP deploy layer in [`deploy/`](https://nougat.snu.gs/enterprise-apps/creed/blob/HEAD/deploy/): a Squire kit whose front controller serves `site/` behind HELMET's security headers. For local development, keep serving `site/` directly.

One command, two clouds, zero excuses. Higher.

CREED is the Wayne State app stack's version policy, as data. One file,
`policy/policy.json`, lists the support dates for PHP, Laravel, Node, MySQL,
Vue and Inertia, plus the rules every check runs against. A small
framework-free PHP reader, `Waynestate\Creed\Policy`, answers the one question
every tool needs: what state is this version in, on this date?

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

- [CREED: The standard everything rests on.](https://creed.apps.wayne.edu/index.md): CREED is the Wayne State app stack's written standard: 54 numbered practices, policy.json with the support dates for PHP, Laravel, Node, MySQL, Vue and Inertia, and a small PHP reader that tells a tool what state a version is in on a given day.
- [Changelog | CREED docs](https://creed.apps.wayne.edu/docs/changelog.md): All notable changes to this project.
- [Contributing | CREED docs](https://creed.apps.wayne.edu/docs/contributing.md): How to build, test and release CREED, and where its data comes from, as printed in MAINTAINING.md.
- [Carrying CREED in another package | CREED docs](https://creed.apps.wayne.edu/docs/guides/carrying-creed.md): How PROCTOR, Booster and Rollcall carry a generated copy of the reader under their own namespace, and how bin/export.php keeps the copies in step.
- [The handbook | CREED docs](https://creed.apps.wayne.edu/docs/guides/handbook.md): The rules, chapter by chapter, in handbook/, with each rule linking the decision behind it.
- [The instance runner | CREED docs](https://creed.apps.wayne.edu/docs/guides/instance-runner.md): Why every product in the stack strongly recommends a git.wayne.edu instance runner while git.wayne.edu has no runners today.
- [Keeping the patches fresh | CREED docs](https://creed.apps.wayne.edu/docs/guides/patch-refresh.md): How bin/refresh-patches.php re-reads the upstream feeds and rewrites the latest_patch fields in policy/policy.json, with the check-only CI job that watches it.
- [The policy robot | CREED docs](https://creed.apps.wayne.edu/docs/guides/policy-bot.md): How bin/policy-bot.php run commits the data allowlist on auto/policy-refresh and opens a merge request labeled auto-data, and how to put it on the schedule.
- [Refreshing the policy | CREED docs](https://creed.apps.wayne.edu/docs/guides/policy-refresh.md): How bin/refresh-policy.php keeps every support date, patch and new line tied to a canonical source, with its change classes and exit codes.
- [Quick start | CREED docs](https://creed.apps.wayne.edu/docs/guides/quick-start.md): The shortest path from composer require to asking the reader what state a version is in on a given day.
- [Reading the policy from PHP | CREED docs](https://creed.apps.wayne.edu/docs/guides/reading-the-policy.md): The reader's public members, one line each, from Policy::bundled() to belowOldestLineReason().
- [Support states and the grace period | CREED docs](https://creed.apps.wayne.edu/docs/guides/support-states.md): How a version moves from Active to Security, to Eol on the day after security_until, and to EolGraceExpired after the 90-day grace.
- [Overview | CREED docs](https://creed.apps.wayne.edu/docs/index.md): What CREED is: the Wayne State App Stack Code, one policy file, one reader, and an inspector who stamps what he finds.
- [Install | CREED docs](https://creed.apps.wayne.edu/docs/install.md): How to require waynestate/creed and develop on it, with the same commands in PowerShell and sh.
- [Reader API | CREED docs](https://creed.apps.wayne.edu/docs/reference/api.md): Every public member of the Waynestate\Creed\Policy reader and the one question each one answers.
- [Commands and exit codes | CREED docs](https://creed.apps.wayne.edu/docs/reference/commands.md): Every command in bin/ and the exit codes it returns, from composer ci to the refresh tools and the policy robot.
- [Configuration | CREED docs](https://creed.apps.wayne.edu/docs/reference/configuration.md): The files a CREED consumer carries: policy/policy.json and policy-overrides.json with its reason and expiry.
- [Policy file format | CREED docs](https://creed.apps.wayne.edu/docs/reference/policy-format.md): The shape of policy/policy.json: the support dates for PHP, Laravel, Node, MySQL, Vue and Inertia, plus the rules every check runs against, guarded by a schema.
- [Proof | CREED docs](https://creed.apps.wayne.edu/docs/reference/proof.md): Where the proof runs against real Wayne State applications: proof.apps.wayne.edu/creed, behind a Wayne State employee sign-in.
- [Troubleshooting | CREED docs](https://creed.apps.wayne.edu/docs/troubleshooting.md): The versions the reader refuses and why: unknown components, versions between listed lines, and lines that do not parse.
- [Upgrading | CREED docs](https://creed.apps.wayne.edu/docs/upgrading.md): How an app on an older PHP reaches the policy floor, and what the reader says on each boundary day.
- [CREED Handbook: 9 Accessibility](https://creed.apps.wayne.edu/handbook/accessibility.md): Chapter 9 of the CREED handbook, the written rules for the Wayne State app stack: Accessibility.
- [CREED Handbook: 4 Auth](https://creed.apps.wayne.edu/handbook/auth.md): Chapter 4 of the CREED handbook, the written rules for the Wayne State app stack: Auth.
- [CREED Handbook: 8 CI](https://creed.apps.wayne.edu/handbook/ci.md): Chapter 8 of the CREED handbook, the written rules for the Wayne State app stack: CI.
- [CREED Handbook: 3 Code](https://creed.apps.wayne.edu/handbook/code.md): Chapter 3 of the CREED handbook, the written rules for the Wayne State app stack: Code.
- [CREED Handbook: 5 Databases](https://creed.apps.wayne.edu/handbook/databases.md): Chapter 5 of the CREED handbook, the written rules for the Wayne State app stack: Databases.
- [CREED Handbook: 2 Dependencies](https://creed.apps.wayne.edu/handbook/dependencies.md): Chapter 2 of the CREED handbook, the written rules for the Wayne State app stack: Dependencies.
- [CREED Handbook: 7 Deploy gate](https://creed.apps.wayne.edu/handbook/deploy-gate.md): Chapter 7 of the CREED handbook, the written rules for the Wayne State app stack: Deploy gate.
- [CREED Handbook: 10 Every OS](https://creed.apps.wayne.edu/handbook/every-os.md): Chapter 10 of the CREED handbook, the written rules for the Wayne State app stack: Every OS.
- [CREED Handbook: the rules, chapter by chapter](https://creed.apps.wayne.edu/handbook/index.md): The CREED handbook: the written rules for the Wayne State app stack, chapter by chapter, each citing the decision behind it.
- [CREED Handbook: 13 Overrides](https://creed.apps.wayne.edu/handbook/overrides.md): Chapter 13 of the CREED handbook, the written rules for the Wayne State app stack: Overrides.
- [CREED Handbook: 12 Production](https://creed.apps.wayne.edu/handbook/production.md): Chapter 12 of the CREED handbook, the written rules for the Wayne State app stack: Production.
- [CREED Handbook: 6 Runtime and headers](https://creed.apps.wayne.edu/handbook/runtime-and-headers.md): Chapter 6 of the CREED handbook, the written rules for the Wayne State app stack: Runtime and headers.
- [CREED Handbook: 11 Secrets and debugging](https://creed.apps.wayne.edu/handbook/secrets.md): Chapter 11 of the CREED handbook, the written rules for the Wayne State app stack: Secrets and debugging.
- [CREED Handbook: 1 Versions](https://creed.apps.wayne.edu/handbook/versions.md): Chapter 1 of the CREED handbook, the written rules for the Wayne State app stack: Versions.

## Prompts

- [Get started with CREED](https://creed.apps.wayne.edu/#prompt-get-started): Lists every version your app runs with its state today, then proposes the smallest change that fixes anything past end of life. It won't make the change until you say so. The prompt itself is in https://creed.apps.wayne.edu/index.md.
- [CREED in a raw PHP app](https://creed.apps.wayne.edu/#prompt-raw-php): Checks an app with no framework against the rules that apply to it, and cites a file and line for each result. The prompt itself is in https://creed.apps.wayne.edu/index.md.
- [CREED in a Laravel app with Blade](https://creed.apps.wayne.edu/#prompt-laravel-blade): The same review for Laravel with Blade. It looks at config, middleware and the Laravel line. The prompt itself is in https://creed.apps.wayne.edu/index.md.
- [CREED in a Laravel app with Inertia and Vue](https://creed.apps.wayne.edu/#prompt-laravel-inertia): Reviews the Composer side and the npm side, including Node, Vue and Inertia. A missing npm lock file counts as a finding. The prompt itself is in https://creed.apps.wayne.edu/index.md.

## Source

- [README](https://nougat.snu.gs/enterprise-apps/creed/blob/HEAD/README.md): the project's README, with install, commands and checks
- [Everything in one file](https://creed.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