database-architect-role

Design a PostgreSQL schema by structuring 11 interconnected tables (properties, owners, contacts, lead_status, validation_history, business_patterns, feedback_log, pattern_performance, spawned_skills, ab_tests, daily_metrics) with foreign keys, constraints, and indexes on frequently queried fields to support lead storage, validation, and role-based access.

Implement RLS policies in PostgreSQL to grant brokers visibility of all leads and restrict agents to only their assigned leads, using policy rules that enforce data access based on user role and ownership.

Yes, Supabase supports PostgreSQL schemas with RLS policies and migration files; you can deploy a production-ready database schema with seed data, indexes, and helper functions through Supabase migrations compatible with your lead generation system.

Create validation_history, business_patterns, feedback_log, pattern_performance, and daily_metrics tables to track lead validation states, AI patterns, performance metrics across 200+ business rules, and enable self-improvement loops in your lead generation workflow.

Add indexes on frequently queried fields like broker and agent role assignments, and create helper functions such as update_daily_metrics to automate metric calculations and optimize query performance across lead assignment workflows.

Populate seed data with 200+ business patterns relevant to lead generation, test datasets for brokers and agents, and initial performance benchmarks to enable immediate testing and validation of your schema's role-based access and assignment logic.