Endodontics: campaign site using Laravel

Summary

A campaign site blueprint for endodontics built with Laravel on Ample. Domain schema includes:

• procedures (code, name, description, typical_visits): root canal and retreatment procedures
• referral_guides (procedure_id, referring_dentist_checklist, imaging_needed): public guidance for referring practices
• locations (name, address, phone, opening_hours): clinic locations
• endodontists (name, registration_number, technologies): specialists and equipment listed publicly
• asset_versions (version, cdn_key, published_at): versioned assets served from the CDN bucket.

Public information includes procedure catalog, referral guidance for general dentists, specialist profiles and technology, and locations. Sensitive information such as referral letters with patient identities, imaging files, and clinical notes is kept out of scope until handling is reviewed.

Infrastructure requirements

• Compute: verified (Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.)
• CDN: verified (The CDN host serves objects from published buckets. It does not front app compute and is not a cache or key-value store.)

Prerequisites

• 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 endodontics data classes may be handled at all; this blueprint models public information only

Exact tested configuration

• template: php-8.5
• runtime: php
• size: s-1vcpu-1gb
• install: composer install --no-dev --prefer-dist --no-interaction --no-progress --optimize-autoloader
• start: frankenphp php-server --listen :$PORT --root public

Steps

1. Model the endodontics domain. Create the tables procedures, referral_guides, locations, endodontists, asset_versions.
2. Workflow step 1. Model the campaign's offers and locations as tables with start and end dates.
3. Workflow step 2. Build the site and publish versioned static assets to the CDN bucket.
4. Workflow step 3. Collect no personal data on the site itself; hand off to an authorized system.
5. Workflow step 4. Deploy, verify the public URL and the CDN asset URL, and retire the campaign by end date.
6. Deploy. Run the synchronous deploy once and read the result.
7. Verify. Run the pattern self-test(s) from the example and your own acceptance checks for the endodontics workflow.

Tested examples

• Laravel pattern fixture: Verified public web service basis for this blueprint.

Success checks

• App responds on its public URL.
• Versioned-static-assets self-test from the example.

Limitations

• No compliance claim is made. Referral documents carry patient identity; keep them out of workflows until handling is reviewed.
• Public content and synthetic examples only until actual data-handling requirements have been reviewed.

Cost estimate

Estimated 5.00 USD per month (size prices from pricing.toml). Buckets are allocation-priced per quota and not included.

Verification evidence

• Canary run details and checks passed.

Execution binding

MCP tool ample_deploy observed at revision.