Implementation notes

Store trusted roles in Clerk metadata or the database. Enforce access in middleware, server components, and sensitive API routes.

Implementation notes

Use Prisma with Neon Postgres. Keep safety ratings, flags, visibility, and moderation status queryable server-side.

Implementation notes

Filter by rating, flags, visibility, moderation status, account age profile, and content experience before returning content to the client.

Implementation notes

Add file type limits, size limits, ownership checks, moderation status, and safe delivery URLs.

Implementation notes

Use Stripe Connect or another compliant payout provider. Do not store sensitive bank details directly in FoxPlot.

Implementation notes

Campaigns should not run unless funded and approved. Spend limits must be enforced server-side.

Implementation notes

Create reusable email templates and log delivery status for support and compliance review.

Implementation notes

Reports should notify admins, preserve evidence, connect to content records, and write audit logs for every action.

Implementation notes

All money movement should be ledger-based, traceable, and tied to campaign IDs, author IDs, advertiser IDs, or payout IDs.

Implementation notes

Make sure account deletion is available, documented, trackable, and compatible with legal/payment retention rules.

Implementation notes

Add identity verification, email confirmation, admin notes, retention rules, and secure export/deletion workflows.

Implementation notes

Log actor, target, action, before/after status, timestamp, reason, and source route/API.