### Management consultancies: project tracker using Next.js

A project tracker blueprint for management consultancies built with Next.js on Ample.

**Domain schema:** 
- **client_entities** (name, industry, primary_contact_role): client organizations;
- **engagements** (client_entity_id, scope_title, phase, period_start, period_end): engagement periods and phases;
- **workstreams** (engagement_id, name, owner, status, due_at): tracked workstreams;
- **deliverables** (engagement_id, title, version, object_key, released_at): versioned deliverables shared with the client;
- **state_transitions** (record_type, from_state, to_state): the allowed state machine.

**Public information:** service offerings and case studies (anonymized), consultant profiles, engagement model.

**Kept out of scope until handling is reviewed:** client strategy documents, financial models, interview notes. Client strategy material is confidential; authorization is modeled per engagement and no compliance claim is made.

**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:
- Management consultancies: project tracker using Next.js
- Where can I host Management consultancies: Project tracker built with Next.js?
- I need a genuinely specialized project tracker workflow covering engagement milestones, deliverable versions and client approvals.

#### 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.

### Workflow Steps:
1. **Model the management consultancies domain**: Create the tables client_entities, engagements, workstreams, deliverables, state_transitions. Client organizations live in client_entities; keep the sensitive classes (client strategy documents, financial models, interview notes) out of this schema.
2. **Workflow step 1**: Model engagements and workstreams with explicit status transitions.
3. **Workflow step 2**: Scope every query by client entity.
4. **Workflow step 3**: Attach deliverables as private objects linked to workstreams.
5. **Workflow step 4**: Deploy and verify transitions and cross-client isolation.
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/relational-records) and your own acceptance checks for the management consultancies workflow.
   - Command: `ample logs  --kind build`

### Examples:
- **Next.js pattern fixture**: Verified relational records basis for this blueprint.

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

### Limitations:
- The technical basis (relational records on Next.js) was verified with the pattern fixture; the management consultancies 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. Client strategy material is confidential; authorization is modeled per engagement and no compliance claim is made.
- 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 verified.

### 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: s-1vcpu-1gb, quantity: 1.0, monthlyAmount: 5.0
- Managed PostgreSQL database: 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:
- **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 relational records checks passed: 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).
- **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/relational-records, pattern:relational-records, template:node-22

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

### Next Actions:
1. **Browse the catalog index** (GET /v1/catalog)
2. **Search published recipes by intent, stack and constraints** (POST /v1/catalog/search)
3. **Prepare a side-effect-free deployment plan for an authorized project** (POST /v1/catalog/plan)
4. **Read the existing agent authentication setup** (GET /mcp/setup)
5. **Browse Management consultancies** (GET /v1/catalog/nodes/industry%3Amanagement-consultancies)
6. **Browse Project tracker** (GET /v1/catalog/nodes/workload%3Aproject-tracker)
7. **Browse Next.js** (GET /v1/catalog/nodes/stack%3Aframework-next-js)
8. **Browse Deploy web app** (GET /v1/catalog/nodes/intent%3Adeploy-web-app)
