/PROJECT 23 · AI-DIRECTED REFERENCE ARCHITECTURE

Intex Construction Platform

A full-stack construction and rental-operations platform built as a directed AI-assisted exploration. The product has two surfaces — an editorial public website with an interactive equipment-rental experience, and a protected Rental Operations dashboard for fleet capacity, bookings, publication governance, and audit history — running on a unified Neon Postgres runtime with Neon Auth and Object Storage. The architecture was written and enforced by hand; the implementation was produced with an AI agent under direction and review, then deployed to Vercel.

BUILT BY TAIWO EMMANUEL · FULL-STACK DEVELOPER

Project screenshot: HomePage

/GOAL

Write the architecture, direct the implementation, enforce it when it drifts.

/STACK

Technologies used

  • React 19
  • TypeScript
  • Vite
  • Tailwind CSS
  • GSAP
  • Zustand
  • tRPC 11
  • React Query
  • Drizzle ORM
  • Neon Postgres
  • Neon Auth
  • Neon Object Storage
  • Express
  • Vercel
  • Vitest
  • React
  • Node.js
  • tRPC
  • Neon
  • AI-assisted
  • Reference architecture
  • Fullstack

/ARCHITECTURE

How it is built

  1. Public and operations surfaces — React clientAn editorial public site with an interactive rental catalogue and request flow, plus a protected Rental Operations workspace for fleet, bookings, enquiries and publication governance.
  2. Typed contracts with role guards — tRPC + Express APIPublic, operations and admin procedures with Zod validation. The server is the authority: roles come from the resolved database user, never from the client.
  3. Unified runtime — Neon PostgresOne Postgres runtime with logical public and Operations boundaries. Public catalogue and protected records share the database but are separated by procedures and publication filters.
  4. Identity boundary — Neon AuthBrowser obtains a bearer token; the server verifies it against Neon JWKS and maps the identity to a local operations role (user / coordinator / admin).
  5. Client-side discipline — State policyZustand owns UI and workflow state; tRPC and React Query own server data. Booking and capacity records are deliberately never copied into the browser store.

/SCOPE

What was delivered

  • Present a multi-page public construction site with services, projects, journal and legal content
  • Offer an interactive equipment-rental catalogue with delivery estimates and structured enquiries
  • Provide a protected Rental Operations workspace with fleet capacity, bookings and coordinator workflows
  • Enforce role-based access (user / coordinator / admin) through server-side guards
  • Separate public catalogue content from protected operations records in one Postgres runtime
  • Manage publication governance with readiness checks, mismatch alerts and audit history
  • Deploy via a Preview-first Vercel workflow with isolated Neon branches and environment-scoped secrets
  • Document the system for handoff: architecture, API reference, deployment and migration guides

/NOTES

Scope boundaries

Intex Construction is an AI-directed reference architecture built for an assumed (fictional) construction company, not a client delivery. The architecture and the enforcement of it are the author's work; the implementation was produced with an AI agent (Manus) under direction and review. The system is deployed but not in commercial use, and it is presented as an exploration of AI-directed system design rather than as evidence of unaided implementation work.

/GALLERY

/WRITING_ON_THIS_STACK

Articles on the tools behind Intex Construction Platform

/MORE_WORK