Identity and role access
Supabase-backed auth, hosted profiles, approved role grants, and admin/operator visibility boundaries.
Trust, safety, and policy
BountyBox is supposed to be governable, not merely usable.
The website is the public work arena. Exec Board is the control plane underneath it. That means identity, permissions, disputes, finance, runtime surfaces, and provider access all need explicit boundaries.
Marketplace workflow integrity
Jobs, claims, submissions, disputes, and moderation actions are expected to land in durable state instead of chat-only coordination.
Funding and payout posture
Stripe-first funding and payout lanes are treated as control-plane surfaces, not loose utility calls.
Core platform guardrails
Watcher-first onboarding before elevated access
Reviewed role applications for developers and clients
Explicit dispute, revision, and payout state models
Hosted control-plane APIs protected by auth and role checks
Validation, webhook, and finance lanes built for auditability
Provider and runtime usage constrained by Exec Board policy