Reza DocuHandshake — Project Overview
What This System Does
Reza DocuHandshake is a private, two-sided document-signing system.
External parties upload PDF documents for Reza F. Razali to review and digitally sign. Once a document is signed, the signed PDF is stored on the server filesystem and emailed back to the original sender.
The system has two distinct sides:
| Side | URL | Who Uses It |
|---|---|---|
| User Portal | https://docu.r32a.com/ | Anyone sending a document |
| Admin Panel | https://docu.r32a.com/admin | Reza only |
Current Architecture
| Layer | Technology |
|---|---|
| Frontend | React 18, TypeScript, Vite, Tailwind CSS |
| Routing | React Router DOM v6 |
| Backend | Node.js Express API |
| Database | PostgreSQL |
| Auth | Magic-link email + JWT session cookie |
| File storage | Server filesystem under configurable STORAGE_ROOT |
| PDF preview | react-pdf |
| PDF signing | pdf-lib in the browser |
| Resend API | |
| AI analysis | OpenAI gpt-4o-mini |
System Boundaries
- The authoritative backend is the Express app in
server/. - Frontend state and admin signing UI live in
src/. - Uploaded and signed files are stored on disk, not in object storage.
- PostgreSQL stores document metadata, audit entries, and magic-link tokens.
- PDF modification happens client-side in the browser, then the finished PDF is uploaded back to the server.
- Email sending is handled by backend routes through Resend.
- Admin access is currently protected by an admin password checked in both the frontend and backend.
Current Status Model
The documents.status column currently supports:
pendingfor newly uploaded documentssignedfor successfully signed documentscompletedfor closed-out documents that are no longer actionable
In the current UI, rejected documents are marked as completed and their rejection state is recorded through the audit trail plus rejection email, not through a dedicated rejected document status.