Database and system structure
A PostgreSQL relational model built for multi-company separation, immutable action history, reviewer-controlled closure, financial evidence and full meeting traceability.
Experience layer
- Executive command centre
- Meeting monitoring centre
- Live review workspace
- Owner and reviewer dashboards
- Responsive client access
Application layer
- Meeting and agenda engine
- Treatment workflow
- Action verification service
- Report generation
- Notifications and escalations
Data layer
- PostgreSQL and Prisma
- Tenant and company isolation
- Attachments and evidence metadata
- Audit logs and status history
- Analytical database views
Integration layer
- Phase 1 manual/Excel uploads
- Tally and ERP adapters
- Email and WhatsApp
- Object/file storage
- PDF and Excel export
Core database entities
32 normalized entitiesClosure rule
Action status cannot become Closed or Stabilised unless a corresponding reviewer decision exists.
Aging rule
Original due date is immutable. Revised commitments and carry-forward counts remain separately recorded.
Tenant rule
Every company-owned record carries a company key and is constrained through company membership and role permissions.
Evidence rule
Completion submission requires at least one evidence item before entering reviewer verification.
Meeting lineage
Recurring meetings retain series and previous-meeting links for week-on-week MOM and action comparisons.
Audit rule
Material changes are written to an audit log with before/after data, actor, time and entity reference.