# WELD

> WELD is a Laravel 13 app with Inertia and Vue that comes with the rest of the Wayne State stack already set up: sign-in, security headers, the standards check, code style and CI. Start your app from it.

**W**ired, **E**verything, **L**inked, **D**eployed. Many parts, one piece.

WELD is the whole Wayne State app stack joined into one application. Install it, deploy it, and every part is already
hooked up: sign-in, security headers, checks, coding standards, CI and the WayneUI interface. Think of it as the
Megazord, except it comes with a deploy script and nobody has to shout to make it combine.

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

- [WELD: Many parts, one piece.](https://weld.apps.wayne.edu/index.md): WELD is a Laravel 13 app with Inertia and Vue that comes with the rest of the Wayne State stack already set up: sign-in, security headers, the standards check, code style and CI. Start your app from it.
- [Changelog | WELD docs](https://weld.apps.wayne.edu/docs/changelog.md): All notable changes to this project.
- [Contributing | WELD docs](https://weld.apps.wayne.edu/docs/contributing.md): How to contribute to WELD: the canonical repository, the mirrors, the checks and the release path.
- [App structure | WELD docs](https://weld.apps.wayne.edu/docs/guides/app-structure.md): Where the code lives in a WELD app: the Laravel app, the Vue front end, the static site and the deploy layer.
- [Build and supply chain | WELD docs](https://weld.apps.wayne.edu/docs/guides/build-and-supply-chain.md): Building and shipping WELD: composer ci as the gate, the audit, and the release path through Squire.
- [Check your setup | WELD docs](https://weld.apps.wayne.edu/docs/guides/check-your-setup.md): weld:doctor strikes an arc across the local setup and reports every joint: PASS, WARN or FAIL, one line per check.
- [The container contract | WELD docs](https://weld.apps.wayne.edu/docs/guides/container-contract.md): The container contract a WELD app meets: environment-only config, logs to stderr, writable paths, non-root, /up, and what to run after every deploy.
- [Oracle | WELD docs](https://weld.apps.wayne.edu/docs/guides/oracle.md): How WELD speaks Oracle through yajra/laravel-oci8: the settings, oracle:check, and the parity image for a real connection.
- [Queues and scheduling | WELD docs](https://weld.apps.wayne.edu/docs/guides/queues-and-scheduling.md): Queues and scheduling in WELD: how jobs and scheduled tasks run, and what changes between local and deploy.
- [Quick start | WELD docs](https://weld.apps.wayne.edu/docs/guides/quick-start.md): Get a new app running in Docker, check the setup with weld:doctor, and plan the rename.
- [Is WELD still Sourdough's shape? | WELD docs](https://weld.apps.wayne.edu/docs/guides/regen-check.md): Whether WELD is still Sourdough's Inertia shape: the regen gate compares a fresh generation with WELD and fails only on new drift.
- [Security | WELD docs](https://weld.apps.wayne.edu/docs/guides/security.md): Security in WELD: sign-in through SESAME, the security headers and CSP from HELMET, and the standards checks from PROCTOR.
- [WELD and Sourdough | WELD docs](https://weld.apps.wayne.edu/docs/guides/sourdough.md): WELD and Sourdough: the starter tool for every shape of Wayne State app, and why WELD is the finished piece.
- [What is welded in | WELD docs](https://weld.apps.wayne.edu/docs/guides/whats-welded-in.md): The parts welded into WELD: WayneUI, CREED, Pinstripe, Preflight, PROCTOR, SESAME, HELMET and Ziggy, and what each does in the app.
- [Overview | WELD docs](https://weld.apps.wayne.edu/docs/index.md): What WELD is: the whole Wayne State app stack joined into one application, and where each part sits in it.
- [Install | WELD docs](https://weld.apps.wayne.edu/docs/install.md): How to get WELD: composer create-project or clone, then one Docker command brings the app, PHP and Node up.
- [Commands | WELD docs](https://weld.apps.wayne.edu/docs/reference/commands.md): The commands a WELD app runs: the composer scripts, the artisan commands and the bin/weld subcommands.
- [Configuration | WELD docs](https://weld.apps.wayne.edu/docs/reference/configuration.md): The configuration a WELD app reads: the environment variables, their defaults and where they live.
- [Status | WELD docs](https://weld.apps.wayne.edu/docs/reference/status.md): What is on the bench today: the state of every part welded into WELD.
- [Running WELD off Citadel | WELD docs](https://weld.apps.wayne.edu/docs/running-off-citadel.md): The per-platform contract for running WELD off Citadel: how traffic reaches the app, where logs go, what may be written, which user runs it, how the platform knows it is alive, and what to run after every deploy.
- [Troubleshooting | WELD docs](https://weld.apps.wayne.edu/docs/troubleshooting.md): When something does not hold: the common failures, what they mean, and what to run next.
- [Upgrading | WELD docs](https://weld.apps.wayne.edu/docs/upgrading.md): How to move a WELD app forward: PHP and Laravel upgrades through Booster, one hop at a time.

## Prompts

- [Get started with WELD](https://weld.apps.wayne.edu/#prompt-get-started): Gets a new app running in Docker, checks it, and plans the rename. It won't rename anything until you say so. The prompt itself is in https://weld.apps.wayne.edu/index.md.
- [Add a signed-in page to a WELD app](https://weld.apps.wayne.edu/#prompt-add-page): Adds a route behind SESAME, a Vue page in the app layout and a feature test, then runs the checks. The prompt itself is in https://weld.apps.wayne.edu/index.md.

## Source

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