Known Data Issues
⚠ 6 flagged issues requiring attention
Tag
4 buyers have
entity='HR.com Ltd' instead of next_chapter — will be excluded from NC dashboards
Gap
4 buyers are missing
one_pager_json — no one-pager content generated for these buyers
Corrupt
1 buyer (MyPeople.ai) has a corrupted
buyer_type value. likely a parse error from enrichment
Wrong side
dossier_final.deal_side='buy' but HR.com is a sell-side client. incorrect classification stored
Research
3 Exa research executions failed. those buyers have incomplete intelligence profiles
Activity
0 letters sent • 0 calls made • 0 buyer feedback collected. deal is fully pre-outreach
Redundancy Detected
⚠ Overlapping Data Structures
engagement_buyers vs buyer_intelligence — Both store buyer company profiles for the same 68 buyers.
engagement_buyers is proposal-scoped; buyer_intelligence is company-scoped. Overlapping fields: company description, AUM, HQ, buyer type.deal_research vs dossier_final —
deal_research has 6 rows of raw research; dossier_final has 1 compiled dossier. There is partial overlap in narrative fields. research synthesis exists in both.research_executions vs deal_research — Execution log tracks what was run; deal_research stores the output. Both reference the same company. No cleanup pipeline to retire stale execution records after results are written.
page_versions vs page_comments — Both are keyed on company_name with no foreign key constraint to proposals. Risk of orphaned records if company_name changes.
HR.com Specific Tables
Loading tables...
NC-Wide Tables (entity='next_chapter')
Loading tables...