Architecture practices: project tracker using Next.js · Ample Computer

Architecture practices: project tracker using Next.js

A project tracker blueprint for architecture practices built with Next.js on Ample. Domain schema:
client_entities (name, entity_type, site_address): clients and project sites;
projects (client_entity_id, project_name, stage, period_start, period_end): engagement periods by RIBA/AIA-style stage;
drawing_sets (project_id, set_name, revision, object_key, issued_at): versioned drawing issues;
approvals (project_id, drawing_set_id, approver_role, decided_at, decision): client sign-offs per issue;
state_transitions (record_type, from_state, to_state): the allowed state machine.
Public information: portfolio and services, team and accreditations, studio locations. Kept out of scope until handling is reviewed: unreleased drawings and site surveys, planning submissions before filing, client contact details. Drawings and surveys are client-confidential until issued; the portal models per-project authorization only. 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 runs on

You need

Exact tested configuration

build
npm run build --if-present
install
npm install
runtime
npm run start
sizes-1vcpu-1gb
template
node-22

Steps

  1. Model the architecture practices domain. Create the tables client_entities, projects, drawing_sets, approvals, state_transitions. Clients and project sites live in client_entities; keep the sensitive classes (unreleased drawings and site surveys, planning submissions before filing, client contact details) 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.

    $ 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. Verify. Run the pattern self-test(s) from the example (/p/relational-records) and your own acceptance checks for the architecture practices workflow.

    $ ample logs <deployment_id> --kind build
    

How it was checked

✓ app responds on its public URL · http get/ → “ample canary next js patterns”
✓ relational-records self-test from the example · http get/p/relational-records → “see the pattern fixture checks”

Evidence

  1. November 5, 2026 · canary run
    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 Architecture practices schema and workflow below build on that verified basis.

Tested examples

What it doesn’t cover