# Construction contractors: public directory using Next.js

## Summary
A public directory blueprint for construction contractors built with Next.js on Ample. Domain schema: listings (reference, project_type, location, publishing_status, agency_id): showcase projects with publishing status; agencies (name, license_number, service_region): branches or divisions; vendors (name, trade, agency_id, prequalified): subcontractors and suppliers per branch; reports (agency_id, period, object_key, generated_at): branch progress reports; state_transitions (record_type, from_state, to_state): the allowed state machine. Public information: published project showcases, services and regions, licenses and insurance summary. Kept out of scope until handling is reviewed: site safety incidents, bid pricing, client contracts. Safety and bid data are confidential; only published showcases and branch reporting are modeled. Technical basis verified on Next.js: 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
- Construction contractors: public directory using Next.js
- Where can I host Construction contractors: Public directory built with Next.js?
- I need a genuinely specialized public directory workflow covering project/vendor relationships, job progress and project reporting.

## Resource Requirements
- primitive:compute
- primitive:postgres
- primitive:cdn

## 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. **CDN**: 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 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 and a published bucket for public assets (CDN_*)
- A review of which construction contractors data classes may be handled at all; this blueprint models public information only

## Workflow Steps
1. **Model the construction contractors domain**: Create the tables listings, agencies, vendors, reports, state_transitions. Showcase projects with publishing status lives in listings; keep the sensitive classes (site safety incidents, bid pricing, client contracts) 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.
7. **Verify**: Run the pattern self-test(s) from the example (/p/relational-records) and your own acceptance checks for the construction contractors workflow.

## Examples
- **Next.js pattern fixture**: Verified relational records basis for this blueprint. Source: tests/deploy-canaries/next-js-patterns.

## Success Checks
1. **App responds on its public URL**: `ample canary next js patterns`
2. **Relational-records self-test from the example**: `see the pattern fixture checks`

## Limitations
- The technical basis (relational records on Next.js) was verified with the pattern fixture; the construction contractors 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. Safety and bid data are confidential; only published showcases and branch reporting are modeled.
- Public content and synthetic examples only until actual data-handling requirements have been reviewed.

## Cost Estimate
- **Currency**: USD
- **Monthly Amount**: 10.0
- **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, monthlyAmount: 5.0)
  - Managed PostgreSQL database (size: s-1vcpu-1gb, quantity: 1.0, monthlyAmount: 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
- **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 relational records checks passed. The blueprint's Construction contractors schema and workflow below build on that verified basis and were not separately executed.

## Formats
- **HTML**: [Link](/content/blueprints/construction-contractors/public-directory/next-js/index.html)
- **Markdown**: [Link](/content/blueprints/construction-contractors/public-directory/next-js.md)
- **JSON**: [Link](https://api.ample.computer/v1/catalog/recipes/page%3Ablueprints%3Aconstruction-contractors%3Apublic-directory%3Anext-js)