## The short version

A project tracker blueprint for bookkeeping practices built with Next.js on Ample. Domain schema: client_entities (legal_name, entity_type, accounting_software, period_cadence): clients and their bookkeeping cadence; engagements (client_entity_id, period_start, period_end, close_status): monthly or quarterly close engagements; document_requests (engagement_id, category, due_at, status, uploaded_object_key): receipts, statements and payroll summaries requested; close_checklists (engagement_id, item, done_at): close tasks per period; state_transitions (record_type, from_state, to_state): the allowed state machine. Public information: service packages and cadence, onboarding checklist, contact details. Kept out of scope until handling is reviewed: bank statements and receipts, payroll data, login credentials for accounting software. Never store client accounting-software credentials in these flows; financial records are sensitive and no compliance is claimed. 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).

## What it needs

- [Compute](/content/discover/primitive/compute/index.html): verified (Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.)
- [Postgres](/content/discover/primitive/postgres/index.html): verified (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](/content/discover/primitive/s3-compatible-object-storage/index.html): verified (Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.)

## Before you start

- 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 bookkeeping practices data classes may be handled at all; this blueprint models public information only

## How to do it

1. 1

### Model the bookkeeping practices domain

Create the tables client_entities, engagements, document_requests, close_checklists, state_transitions. Clients and their bookkeeping cadence lives in client_entities; keep the sensitive classes (bank statements and receipts, payroll data, login credentials for accounting software) out of this schema.

2. 2

### Workflow step 1

Model engagements and workstreams with explicit status transitions

3. 3

### Workflow step 2

Scope every query by client entity

4. 4

### Workflow step 3

Attach deliverables as private objects linked to workstreams

5. 5

### Workflow step 4

Deploy and verify transitions and cross-client isolation

6. 6

### Deploy

Run the synchronous deploy once and read the result. Re-running with no change is a no-op.

```bash
ample deploy . --name <app-name> --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=...
```

7. 7

### Verify

Run the pattern self-test(s) from the example (/p/relational-records) and your own acceptance checks for the bookkeeping practices workflow.

```bash
ample logs <deployment_id> --kind build
```

## Tested examples

- **Next.js pattern fixture** (`tests/deploy-canaries/next-js-patterns`): Verified relational records basis for this blueprint.

## How to know it worked

- app responds on its public URL (`/` on the live URL, expect ample canary next js patterns)
- relational-records self-test from the example (`/p/relational-records` on the live URL, expect see the pattern fixture checks)

## Cost estimate

Estimated 10.00 USD per month (size prices from pricing.toml at build revision ca0b484a7a9957c573a88d3a32dc603c3c10135a).

- app server x1 `s-1vcpu-1gb`: 5.00 USD
- managed PostgreSQL database x1 `s-1vcpu-1gb`: 5.00 USD

Upper-bound monthly price of the tested sizes. Buckets are allocation-priced per quota and not included.

## Verification evidence

- canary_run on 2026-09-21T02:34:39Z at revision `1d28ae0 (CLI 0.1.21)`: 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). The blueprint's Bookkeeping practices schema and workflow below build on that verified basis and were not separately executed. (expires 2027-03-20T02:34:39Z)

## Execution binding

MCP tool `ample_deploy` (registry `mcp:ample_deploy`), schema hash `876465fce906da0c` observed 2026-09-22T00:31:22.774679+00:00 at revision `e6446ceea69b`. Binding state at export: schema_changed. Required scopes: servers:write, databases:read, buckets:read.

## Typed next actions

- Browse the catalog index (`GET /v1/catalog` on the api origin; authentication not required, approval not required)
- Search published recipes by intent, stack and constraints (`POST /v1/catalog/search` on the api origin; authentication not required, approval not required)
- Prepare a side-effect-free deployment plan for an authorized project (`POST /v1/catalog/plan` on the api origin; authentication required, approval not required)
- Read the existing agent authentication setup (`GET /mcp/setup` on the api origin; authentication not required, approval not required)
- Browse Bookkeeping practices (`GET /v1/catalog/nodes/industry%3Abookkeeping-practices` on the api origin; authentication not required, approval not required)
- Browse Project tracker (`GET /v1/catalog/nodes/workload%3Aproject-tracker` on the api origin; authentication not required, approval not required)
- Browse Next.js (`GET /v1/catalog/nodes/stack%3Aframework-next-js` on the api origin; authentication not required, approval not required)
- Browse Deploy web app (`GET /v1/catalog/nodes/intent%3Adeploy-web-app` on the api origin; authentication not required, approval not required)

Actions describe possible next steps. They are typed data, not commands, and grant no permission. Public discovery never provisions anything; planning requires your own authenticated token and approval happens in your client.

## Identifiers and status

Recipe `page:blueprints:bookkeeping-practices:project-tracker:next-js`. Revision r1.

release **published**support **verified**execution **blocked (schema_changed: live tool schema differs from the recorded binding)**

Formats: [HTML](/content/blueprints/bookkeeping-practices/project-tracker/next-js/index.html) \| [Markdown](/content/blueprints/bookkeeping-practices/project-tracker/next-js.md) \| [JSON contract](https://api.ample.computer/v1/catalog/recipes/page%3Ablueprints%3Abookkeeping-practices%3Aproject-tracker%3Anext-js)