Architecture practices: Project tracker using Laravel

Summary

A project tracker blueprint for architecture practices built with Laravel 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 includes 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 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).

Representative Queries

• Architecture practices: project tracker using Laravel
• Where can I host Architecture practices: Project tracker built with Laravel?
• I need a genuinely specialized project tracker workflow covering project phases, drawing versions, and reviewer access.

Resource Requirements

• Compute
• Postgres
• 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.

Prerequisites

• A Laravel project (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)
• 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 architecture practices data classes may be handled at all; this blueprint models public information only

Workflow Steps

1. Model the architecture practices domain. Create the tables client_entities, projects, drawing_sets, approvals, state_transitions.
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 and your own acceptance checks for the architecture practices workflow. Command: ample logs --kind build

Examples

• Laravel pattern fixture: Verified relational records basis for this blueprint.

Success Checks

• The app responds on its public URL.
• Relational-records self-test from the example.

Limitations

• The technical basis (relational records on Laravel) was verified with the pattern fixture; the architecture practices 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.
• Verified on the php-8.5 template at s-1vcpu-1gb; region, request-duration limits, and other sizes are unknown or unverified.