Bookkeeping practices: project tracker using Laravel · Ample Computer

Bookkeeping practices: project tracker using Laravel

A project tracker blueprint for bookkeeping practices built with Laravel on Ample. Domain schema:

Public information includes service packages and cadence, onboarding checklist, and 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.

Technical basis verified on Laravel: 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

Steps

  1. Model the bookkeeping practices domain. Create the tables client_entities, engagements, document_requests, close_checklists, state_transitions. Clients and their bookkeeping cadence live in client_entities; keep the sensitive classes (bank statements and receipts, payroll data, login credentials for accounting software) 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=...
  1. Verify. Run the pattern self-test(s) from the example (/p/relational-records) and your own acceptance checks for the bookkeeping practices workflow.
$ ample logs <deployment_id> --kind build

How it was checked

Evidence

  1. November 6, 2026 · canary run
    Laravel pattern fixture deployed on Ample (composer install --no-dev from composer.lock, then FrankenPHP serving public/ (php-server with the index.php fallback) reading PORT on the php-8.5 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.

Tested examples

What it doesn’t cover