## Logistics operators: reporting dashboard using Laravel

### Summary
A reporting dashboard blueprint for logistics operators built with Laravel on Ample. Domain schema:
- **service_products** (sku, name, mode, transit_days, price_basis): shipping services as SKUs;
- **capacity_movements** (sku, lane, date, delta, reason): capacity as stock movements;
- **shipments** (shipment_no, lane, status, booked_at): shipments with status transitions;
- **shipment_lines** (shipment_no, sku, units): shipment contents;
- **exports** (id, definition, object_key, row_count, generated_at, authorized_role): generated artifacts and who may download them.

Public information: service products and transit times, lanes served, tracking entry point. Kept out of scope until handling is reviewed: consignee addresses, commercial invoices, customs documents. Customs and consignee data are sensitive; only shipment status is modeled here.

### Technical Basis
Verified on Laravel: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3).

### Representative Queries
1. Logistics operators: reporting dashboard using Laravel
2. Where can I host Logistics operators: Reporting dashboard built with Laravel?
3. I need a genuinely specialized reporting dashboard workflow covering shipment state, partner access and delivery exception reporting.

### Resource Requirements
- primitive:compute
- primitive:postgres
- primitive:s3-compatible-object-storage

### Infrastructure Requirements
- **Compute**: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
- **Postgres**: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.
- **S3-compatible object storage**: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

### Framework
Laravel

### Workload
Reporting dashboard

### Industry
Logistics operators

### Release Status
Published

### Support Status
Verified

### Execution Status
Ready

### 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)
- A PostgreSQL driver reading DATABASE_URL (auto-provisioned when omitted)
- Bucket credentials from `ample bucket create` passed as encrypted S3_* environment variables
- A review of which logistics operators data classes may be handled at all; this blueprint models public information only

### Workflow Steps
1. **Model the logistics operators domain**: Create the tables service_products, capacity_movements, shipments, shipment_lines, exports. Shipping services as SKUs live in service_products; keep the sensitive classes (consignee addresses, commercial invoices, customs documents) out of this schema.
2. **Workflow step 1**: Model report definitions scoped to the agency.
3. **Workflow step 2**: Generate report artifacts from queries and store them with metadata.
4. **Workflow step 3**: Authorize downloads (401 without identity).
5. **Workflow step 4**: Deploy and verify an authorized export and the rejected anonymous request.
6. **Deploy**: Run the synchronous deploy once and read the result. Re-running with no change is a no-op.
   - Command: `ample deploy . --name --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=...`
7. **Verify**: Run the pattern self-test(s) from the example (/p/generated-downloads) and your own acceptance checks for the logistics operators workflow.
   - Command: `ample logs --kind build`

### Success Checks
1. app responds on its public URL
   - Kind: http_get
   - Path: / 
   - Expect: ample canary laravel patterns
2. generated-downloads self-test from the example
   - Kind: http_get
   - Path: /p/generated-downloads
   - Expect: see the pattern fixture checks

### Limitations
- The technical basis (generated downloads on Laravel) was verified with the pattern fixture; the logistics operators schema and workflow are an original design for this blueprint and were not executed as a separate application.
- No health, financial, privacy or other compliance claim is made. Customs and consignee data are sensitive; only shipment status is modeled here.
- Verified on the php-8.5 template at s-1vcpu-1gb; region, request-duration limits and other sizes are unknown or unverified.
- Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified.
- PutObject and GetObject with path-style addressing are verified; other S3 operations and CDN cache rules are not.

### Cost Estimate
- **Currency**: USD
- **Monthly Amount**: 10.0
- **Authoritative**: true
- **Basis**: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
- **Components**:
  - **app server**: size s-1vcpu-1gb, quantity 1.0, monthly amount 5.0
  - **managed PostgreSQL database**: size s-1vcpu-1gb, quantity 1.0, monthly amount 5.0
- **Note**: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.

### Evidence Summary
- **Kind**: canary_run 
- **Summary**: 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 generated downloads checks passed: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3). The blueprint's Logistics operators schema and workflow below build on that verified basis and were not separately executed.
- **Observed At**: 2026-09-20T20:36:21Z
- **Implementation Revision**: 118ad1c6d7d23d4c2ce069254bab9ec9d37cd57b-dirty (CLI 118ad1c)
- **Expires At**: 2027-03-19T20:36:21Z
- **Scope**: 
  - **Checks**: [/p/generated-downloads]
  - **Pattern**: pattern:generated-downloads
  - **Template**: php-8.5

### Last Verified At
2026-09-20T20:36:21Z

### Formats
- **HTML**: [https://ample.computer/blueprints/logistics-operators/reporting-dashboard/laravel](/content/blueprints/logistics-operators/reporting-dashboard/laravel/index.html)
- **Markdown**: [https://ample.computer/blueprints/logistics-operators/reporting-dashboard/laravel.md](/content/blueprints/logistics-operators/reporting-dashboard/laravel.md)
- **JSON**: [https://api.ample.computer/v1/catalog/recipes/page%3Ablueprints%3Alogistics-operators%3Areporting-dashboard%3Alaravel](https://api.ample.computer/v1/catalog/recipes/page%3Ablueprints%3Alogistics-operators%3Areporting-dashboard%3Alaravel)

### Next Actions
1. **Browse the catalog index**
   - Action ID: browse-catalog
   - Operation ID: catalog_index
   - Method: GET
   - Relative Path: /v1/catalog
2. **Search published recipes by intent, stack and constraints**
   - Action ID: search-recipes
   - Operation ID: search_recipes
   - Method: POST
   - Relative Path: /v1/catalog/search
   - Parameters: {"body":{"limit":5,"query":"Logistics operators: reporting dashboard using Laravel"}}
3. **Prepare a side-effect-free deployment plan for an authorized project**
   - Action ID: plan:page:blueprints:logistics-operators:reporting-dashboard:laravel
   - Operation ID: plan_deployment
   - Method: POST
   - Relative Path: /v1/catalog/plan
   - Parameters: {"body":{"inputs":{},"projectId":"","recipeId":"page:blueprints:logistics-operators:reporting-dashboard:laravel","recipeRevision":"r1"}}
4. **Read the existing agent authentication setup**
   - Action ID: auth-setup
   - Operation ID: existing_auth_setup
   - Method: GET
   - Relative Path: /mcp/setup
5. **Browse Logistics operators**
   - Action ID: browse:industry:logistics-operators
   - Operation ID: browse_node
   - Method: GET
   - Relative Path: /v1/catalog/nodes/industry%3Alogistics-operators
6. **Browse Reporting dashboard**
   - Action ID: browse:workload:reporting-dashboard
   - Operation ID: browse_node
   - Method: GET
   - Relative Path: /v1/catalog/nodes/workload%3Areporting-dashboard
7. **Browse Laravel**
   - Action ID: browse:stack:framework-laravel
   - Operation ID: browse_node
   - Method: GET
   - Relative Path: /v1/catalog/nodes/stack%3Aframework-laravel
8. **Browse Deploy web app**
   - Action ID: browse:intent:deploy-web-app
   - Operation ID: browse_node
   - Method: GET
   - Relative Path: /v1/catalog/nodes/intent%3Adeploy-web-app