Aspire Connectivity
Developer

Project History

Concise history of completed platform and documentation work.

Project History

2026-09-17 — Monorepo Application Separation

The repository was organized into independent Admin, Resident, and Docs applications using npm workspaces and Turborepo. Admin serves its dashboard at /; Resident serves property pages at /p/[propertySlug]; Docs runs as a separate Fumadocs application.

The root commands npm run lint, npm run typecheck, and npm run build now validate all workspaces.

2026-09-18 — Audience Documentation Skeleton

The Docs application gained one generic landing page for each audience: Developer, Admin, and Resident. The documentation home links directly to each section. These pages are structural placeholders, not product instructions.

2026-09-18 — Database Workspace Foundation

Created packages/db as the shared database boundary for Prisma and PostgreSQL. It now contains the Prisma schema, configuration, generated-client workflow, and @aspire/db export.

The initial neutral SystemRecord schema model establishes Aspire-controlled PostgreSQL UUID primary keys and timezone-aware created_at/updated_at timestamps, mapped to camel-case TypeScript fields. The checked-in initial migration was applied to a verified clean database, its status is current, and a read-only shared-client verification query succeeds. No business-domain models or application queries were added.

Linked the repository to its Neon production branch, added the minimal neon.ts policy, and deployed it with no branch changes required. The root .env is managed locally by Neon and is ignored by Git.

On this page