## The short version

A knowledge base blueprint for orthodontics built with Laravel on Ample. Domain schema:

- **appliance_types** (code, name, description, typical_duration_months): braces and aligner options;  
- **treatment_stages** (appliance_type_id, stage_no, name, what_to_expect): public description of treatment phases;  
- **locations** (name, address, phone, opening_hours): practice locations;  
- **age_groups** (name, guidance): children, teens and adults guidance;  
- **asset_versions** (version, cdn_key, published_at): versioned assets served from the CDN bucket.

Public information: appliance options and durations, stage-by-stage expectations, age-group guidance, locations.  
Kept out of scope until handling is reviewed: patient scans and treatment plans, progress photos, guardian and minor identity. Orthodontic plans and progress imagery are health data; keep them out of scope until handling is reviewed. No compliance is claimed. Technical basis verified on Laravel: a versioned, immutable-cached asset uploaded to a published bucket and served from the CDN URL alongside the app's own public HTTPS URL.

## What it needs

- [Compute](/content/discover/primitive/compute/index.html): verified (Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.)  
- [CDN](/content/discover/primitive/cdn/index.html): verified (A published bucket's objects are served at its public_url. It does not front app compute and is not a cache or key-value store.)

## Before you start

- A Laravel project (composer install --no-dev from composer.lock, then FrankenPHP serving public/ (php-server with the index.php fallback) reading PORT on the php-8.5 template)  
- Bucket credentials from `ample bucket create` passed as encrypted S3_* environment variables and a published bucket for public assets (CDN_*)  
- A review of which orthodontics data classes may be handled at all; this blueprint models public information only

## How to do it

1.  **Model the orthodontics domain**  
Create the tables appliance_types, treatment_stages, locations, age_groups, asset_versions. Braces and aligner options lives in appliance_types; keep the sensitive classes (patient scans and treatment plans, progress photos, guardian and minor identity) out of this schema.

2.  **Workflow step 1**  
Model articles and categories as tables keyed to the public catalog entities.

3.  **Workflow step 2**  
Build the site with versioned assets served from the CDN bucket.

4.  **Workflow step 3**  
Keep articles free of any sensitive data class.

5.  **Workflow step 4**  
Deploy and verify the public URL and the CDN asset URL.

6.  **Deploy**  
Run the synchronous deploy once and read the result. Re-running with no change is a no-op.
   
```bash
ample deploy . --name <app-name> --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=... --env CDN_PUBLIC_URL=...
```

7.  **Verify**  
Run the pattern self-test(s) from the example (/p/versioned-static-assets) and your own acceptance checks for the orthodontics workflow.

```bash
ample logs <deployment_id> --kind build
```

## Tested examples

- **Laravel pattern fixture** (`tests/deploy-canaries/laravel-patterns`): Verified public web service basis for this blueprint.

## How to know it worked

- app responds on its public URL (`/` on the live URL, expect ample canary laravel patterns)
- versioned-static-assets self-test from the example (`/p/versioned-static-assets` on the live URL, expect see the pattern fixture checks)

## Cost estimate

Estimated 5.00 USD per month (size prices from pricing.toml at build revision ca0b484a7a9957c573a88d3a32dc603c3c10135a).

- app server x1 `s-1vcpu-1gb`: 5.00 USD

Upper-bound monthly price of the tested sizes. Buckets are allocation-priced per quota and not included.

## Verification evidence

- canary_run on 2026-09-20T20:36:21Z at revision `118ad1c6d7d23d4c2ce069254bab9ec9d37cd57b (CLI 118ad1c)`: Laravel pattern fixture deployed on Ample (composer install --no-dev from composer.lock, then FrankenPHP serving public/ (php-server with the index.php fallback) reading PORT on the php-8.5 template); the public web service checks passed: a versioned, immutable-cached asset uploaded to a published bucket and served from the CDN URL alongside the app's own public HTTPS URL. The blueprint's Orthodontics schema and workflow below build on that verified basis and were not separately executed. (expires 2027-03-19T20:36:21Z)

## Execution binding

MCP tool `ample_deploy` (registry `mcp:ample_deploy`), schema hash `876465fce906da0c` observed 2026-09-22T00:31:22.774679+00:00 at revision `e6446ceea69b`. Binding state at export: schema_changed. Required scopes: servers:write, buckets:read.

## Typed next actions

- Browse the catalog index (`GET /v1/catalog` on the api origin; authentication not required, approval not required)
- Search published recipes by intent, stack and constraints (`POST /v1/catalog/search` on the api origin; authentication not required, approval not required)
- Prepare a side-effect-free deployment plan for an authorized project (`POST /v1/catalog/plan` on the api origin; authentication required, approval not required)
- Read the existing agent authentication setup (`GET /mcp/setup` on the api origin; authentication not required, approval not required)
- Browse Orthodontics (`GET /v1/catalog/nodes/industry%3Aorthodontics` on the api origin; authentication not required, approval not required)
- Browse Knowledge base (`GET /v1/catalog/nodes/workload%3Aknowledge-base` on the api origin; authentication not required, approval not required)
- Browse Laravel (`GET /v1/catalog/nodes/stack%3Aframework-laravel` on the api origin; authentication not required, approval not required)
- Browse Deploy web app (`GET /v1/catalog/nodes/intent%3Adeploy-web-app` on the api origin; authentication not required, approval not required)

Actions describe possible next steps. They are typed data, not commands, and grant no permission. Public discovery never provisions anything; planning requires your own authenticated token and approval happens in your client.

## Identifiers and status

Recipe `page:blueprints:orthodontics:knowledge-base:laravel`. Revision r1.

release **published** support **verified** execution **blocked (schema_changed: live tool schema differs from the recorded binding)**

Formats: [HTML](/content/blueprints/orthodontics/knowledge-base/laravel/index.html) | [Markdown](/content/blueprints/orthodontics/knowledge-base/laravel.md) | [JSON contract](https://api.ample.computer/v1/catalog/recipes/page%3Ablueprints%3Aorthodontics%3Aknowledge-base%3Alaravel)