# Travel operators: reporting dashboard using Next.js

## Summary
A reporting dashboard blueprint for travel operators built with Next.js on Ample. Domain schema: listings (reference, destination, departure_dates, price_from, publishing_status, agency_id): trips as listings with publishing status; agencies (name, license_number, region): operators or branches; suppliers (name, type, agency_id, status): hotels and transport suppliers; reports (agency_id, period, object_key, generated_at): branch sales reports; exports (id, definition, object_key, row_count, generated_at, authorized_role): generated artifacts and who may download them. Public information: published trips and departure dates, destination guides, booking conditions. Kept out of scope until handling is reviewed: traveler passports and identity, payment details, supplier contracts. Passport and payment data are regulated; only published trips and branch reporting are modeled. Technical basis verified on Next.js: 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
- Travel operators: reporting dashboard using Next.js
- Where can I host Travel operators: Reporting dashboard built with Next.js?
- I need a genuinely specialized reporting dashboard workflow covering tour listings, supplier access and itinerary reporting.

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

## Infrastructure Requirements
1. **Compute**  
   Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.

2. **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.

3. **S3-compatible object storage**  
   Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

## Prerequisites
- A Next.js project (next build then next start -H 0.0.0.0 -p $PORT on the node-22 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 travel operators data classes may be handled at all; this blueprint models public information only

## Workflow Steps
1. **Model the travel operators domain**  
   Create the tables listings, agencies, suppliers, reports, exports. Trips as listings with publishing status lives in listings; keep the sensitive classes (traveler passports and identity, payment details, supplier contracts) 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 travel operators workflow.  
   **Command:** `ample logs  --kind build`

## Success Checks
1. **App responds on its public URL**  
   - Kind: `http_get`  
   - Path: `/`  
   - Expect: `ample canary next js 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 Next.js) was verified with the pattern fixture; the travel 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. Passport and payment data are regulated; only published trips and branch reporting are modeled.
- Public content and synthetic examples only until actual data-handling requirements have been reviewed.
- Verified on the node-22 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: Next.js pattern fixture deployed on Ample (next build then next start -H 0.0.0.0 -p $PORT on the node-22 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 Travel operators schema and workflow below build on that verified basis and were not separately executed.  
  - Observed At: 2026-09-21T02:34:39Z  
  - Implementation Revision: 1d28ae0-dirty (CLI 0.1.21)  
  - Expires At: 2027-03-20T02:34:39Z  
  - Scope:  
   - Checks: `/p/generated-downloads`  
   - Pattern: `pattern:generated-downloads`  
   - Template: `node-22`

## Last Verified At
2026-09-21T02:34:39Z

## Unknowns
- Region availability is unknown until a verified region fact is recorded.
- Compliance attestations are unknown; none are claimed.

## Formats
- HTML: [https://ample.computer/blueprints/travel-operators/reporting-dashboard/next-js](/content/blueprints/travel-operators/reporting-dashboard/next-js/index.html)  
- Markdown: [https://ample.computer/blueprints/travel-operators/reporting-dashboard/next-js.md](/content/blueprints/travel-operators/reporting-dashboard/next-js.md)  
- JSON: [https://api.ample.computer/v1/catalog/recipes/page%3Ablueprints%3Atravel-operators%3Areporting-dashboard%3Anext-js](https://api.ample.computer/v1/catalog/recipes/page%3Ablueprints%3Atravel-operators%3Areporting-dashboard%3Anext-js)

## Next Actions
1. **Browse the catalog index**  
   **Operation ID:** catalog_index  
   **Method:** GET  
   **Relative Path:** /v1/catalog  
   **Requires Authentication:** false  
   **Requires Approval:** false

2. **Search published recipes by intent, stack and constraints**  
   **Operation ID:** search_recipes  
   **Method:** POST  
   **Relative Path:** /v1/catalog/search  
   **Parameters:**  
   ```json
   {
     "body": {
       "limit": 5,
       "query": "Travel operators: reporting dashboard using Next.js"
     }
   }
   ```
   **Requires Authentication:** false  
   **Requires Approval:** false

3. **Prepare a side-effect-free deployment plan for an authorized project**  
   **Operation ID:** plan_deployment  
   **Method:** POST  
   **Relative Path:** /v1/catalog/plan  
   **Parameters:**  
   ```json
   {
     "body": {
       "inputs": {},
       "projectId": "",
       "recipeId": "page:blueprints:travel-operators:reporting-dashboard:next-js",
       "recipeRevision": "r1"
     }
   }
   ```
   **Requires Authentication:** true  
   **Requires Approval:** false

4. **Read the existing agent authentication setup**  
   **Operation ID:** existing_auth_setup  
   **Method:** GET  
   **Relative Path:** /mcp/setup  
   **Requires Authentication:** false  
   **Requires Approval:** false

5. **Browse Travel operators**  
   **Operation ID:** browse_node  
   **Method:** GET  
   **Relative Path:** /v1/catalog/nodes/industry%3Atravel-operators  
   **Parameters:**  
   ```json
   {
     "nodeId": "industry:travel-operators"
   }
   ```
   **Requires Authentication:** false  
   **Requires Approval:** false

6. **Browse Reporting dashboard**  
   **Operation ID:** browse_node  
   **Method:** GET  
   **Relative Path:** /v1/catalog/nodes/workload%3Areporting-dashboard  
   **Parameters:**  
   ```json
   {
     "nodeId": "workload:reporting-dashboard"
   }
   ```
   **Requires Authentication:** false  
   **Requires Approval:** false

7. **Browse Next.js**  
   **Operation ID:** browse_node  
   **Method:** GET  
   **Relative Path:** /v1/catalog/nodes/stack%3Aframework-next-js  
   **Parameters:**  
   ```json
   {
     "nodeId": "stack:framework-next-js"
   }
   ```
   **Requires Authentication:** false  
   **Requires Approval:** false

8. **Browse Deploy web app**  
   **Operation ID:** browse_node  
   **Method:** GET  
   **Relative Path:** /v1/catalog/nodes/intent%3Adeploy-web-app  
   **Parameters:**  
   ```json
   {
     "nodeId": "intent:deploy-web-app"
   }
   ```
   **Requires Authentication:** false  
   **Requires Approval:** false