# Logistics operators: public directory using Laravel

## Summary
A public directory 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;
- **state_transitions** (record_type, from_state, to_state): the allowed state machine.
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: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true).

## Representative Queries
- Logistics operators: public directory using Laravel
- Where can I host Logistics operators: Public directory built with Laravel?
- I need a genuinely specialized public directory workflow covering shipment state, partner access and delivery exception reporting.

## Workflow Steps
1. **Model the logistics operators domain**: Create the tables service_products, capacity_movements, shipments, shipment_lines, state_transitions. 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 listings with a publishing_status state machine scoped to the agency.
3. **Workflow step 2**: Serve only published listings, with media from the CDN bucket.
4. **Workflow step 3**: Enforce the agency scope on every query.
5. **Workflow step 4**: Deploy and verify a published listing and that unpublished listings are absent.
6. **Deploy**: Run the synchronous deploy once and read the result. Re-running with no change is a no-op.
   ```bash
   ample deploy . --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/relational-records) and your own acceptance checks for the logistics operators workflow.
   ```bash
   ample logs  --kind build
   ```

## Limitations
- The technical basis (relational records 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.
- Public content and synthetic examples only until actual data-handling requirements have been reviewed.
- Verified on the php-8.5 template at s-1vcpu-1gb; region, request-duration limits and other sizes are unknown or unverified.

## Cost Estimate
- **Currency**: USD
- **Monthly Amount**: $10.00
- **Authoritative**: true
- **Basis**: size prices from pricing.toml (loaded by the API) at build revision... 
- **Components**:
  - **app server**: s-1vcpu-1gb, quantity: 1.0, monthly amount: $5.00
  - **managed PostgreSQL database**: s-1vcpu-1gb, quantity: 1.0, monthly amount: $5.00
- **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.

## Examples
### Laravel pattern fixture
- **Description**: Verified relational records basis for this blueprint.
- **Source Reference**: tests/deploy-canaries/laravel-patterns

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

## Next Actions
- **Browse the catalog index**
- **Search published recipes by intent, stack and constraints**
- **Prepare a side-effect-free deployment plan for an authorized project**
- **Read the existing agent authentication setup**
- **Browse Logistics operators**
- **Browse Public directory**
- **Browse Laravel**
- **Browse Deploy web app**