Synthetic proof · member intake control
Member intake QA proof.
A first paid slice for service teams whose consultation, profile, matchmaker, referral, no-show, and feedback rows need a reviewable control layer. Synthetic member events become intake QA ledgers, owner-review queues, blocked actions, and hard errors before any live member data, customer message, CRM write, profile update, or date action is touched.
Input
Synthetic consultation, profile update, matchmaker note, referral, no-show, and date-feedback rows plus a policy map.
Checks
Duplicate keys, required fields, source boundary, sensitive details, consent state, and member-facing action scope are checked first.
Output
Safe rows become an intake QA ledger; duplicates and reengagement rows go to owner review with evidence.
Blocks
Live-channel sources, sensitive member details, SMS, member messages, date booking, CRM writes, and profile updates stop before action.
| Event | Source Shape | Check | Decision | Boundary |
|---|---|---|---|---|
| miq-1001 | New consultation | Complete profile, approved source boundary, unique duplicate key | QA ledger | Owner review before any CRM or member workflow impact. |
| miq-1003 | Duplicate profile update | Duplicate key already seen | Owner review | Confirm replay intent before staging another profile row. |
| miq-1007 | No-show follow-up | Reengagement policy requires owner approval | Owner review | No automated member follow-up. |
| miq-1004 | Matchmaker note | Sensitive member detail present | Blocked action | Use synthetic or redacted detail only. |
| miq-1008 | Date feedback | Member-facing message requested | Blocked action | No member message or date action. |