# Accounting firms: project tracker using Next.js

## Summary
A project tracker blueprint for accounting firms built with Next.js on Ample. Domain schema: 
- **client_entities** (legal_name, entity_type, fiscal_year_end, jurisdiction): the businesses and individuals served;
- **engagements** (client_entity_id, service_line, period_start, period_end, status): bookkeeping, tax and audit engagements by period;
- **document_requests** (engagement_id, title, due_at, status, uploaded_object_key): requests for source documents;
- **deliverables** (engagement_id, title, object_key, released_at): returns and statements released to the client;
- **state_transitions** (record_type, from_state, to_state): the allowed state machine.

Public information: service lines and typical engagement periods, filing calendars and deadlines, office locations. Kept out of scope until handling is reviewed: tax identifiers and financial statements, bank and payroll records, identity documents. Financial records and tax identifiers are regulated in most jurisdictions; the portal flows here model authorization only and claim no compliance. 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
- Accounting firms: project tracker using Next.js
- Where can I host Accounting firms: Project tracker built with Next.js?
- I need a genuinely specialized project tracker workflow covering engagement periods, client entities and document authorization.

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

## Infrastructure Requirements
| Name | Summary |
|------|---------|
| 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. |

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

## Workflow Steps
1. **Model the accounting firms domain**: Create the tables client_entities, engagements, document_requests, deliverables, state_transitions. The businesses and individuals served lives in client_entities; keep the sensitive classes (tax identifiers and financial statements, bank and payroll records, identity documents) 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.
7. **Verify**: Run the pattern self-test(s) from the example (/p/relational-records) and your own acceptance checks for the accounting firms workflow.

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

## Success Checks
- App responds on its public URL
- Relational-records self-test from the example

## Limitations
- The technical basis (relational records on Next.js) was verified with the pattern fixture; the accounting firms 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. Financial records and tax identifiers are regulated in most jurisdictions; the portal flows here model authorization only and claim no compliance.
- Verified on the node-22 template at s-1vcpu-1gb; region, request-duration limits and other sizes are unknown or unverified.

## Cost Estimate
| Description | Amount |
|-------------|--------|
| Monthly Amount | $10.00 |
| Basis | Size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty |

- **Components**:
   - App server: size s-1vcpu-1gb: $5.00/month
   - Managed PostgreSQL database: size s-1vcpu-1gb: $5.00/month

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

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