Capability labels describe the current product path—not just whether code or a database model exists. Preview and shadow operations are never presented as finalized proof.
Available for normal use with a complete product path.
Available for real use, but still being hardened or expanded.
Demonstrates the intended experience without completing every implied action.
Records intended operations without treating them as externally finalized proof.
Designed or modeled, but not available as a complete product feature.
The feature cannot run in the current environment or configuration.
public.discoveryProject, campaign, brand, learning, and transparency pages.
Why this status
Status is defined by the current product capability registry.
Evidence: Public routes and route-integrity tests
identity.accountsAuthentication, account recovery, profiles, and anonymous-to-account continuation.
Why this status
Status is defined by the current product capability registry.
Evidence: Supabase authentication routes and profile APIs
contributions.coreAuthenticated and anonymous contribution creation with attribution and status tracking.
Why this status
Status is defined by the current product capability registry.
Evidence: Contribution APIs, payment state polling, and integration tests
payments.stripeStripe payment intents, confirmation webhook handling, and refunds.
Why this status
Stripe checkout is not configured in this environment.
Evidence: Stripe service, webhook routes, and payment tests
payments.cryptoTransaction-proof submission with administrative verification.
Why this status
Status is defined by the current product capability registry.
Evidence: Crypto submission API, verification queue, and tests
proof.receiptsContribution receipts and their external proof-processing state.
Why this status
Proof operations are recorded in shadow mode and are not externally finalized.
Evidence: Receipt service, chain adapter, and shadow log
engagement.progressRP balances, history, tiers, unlock guidance, and leaderboards.
Why this status
Status is defined by the current product capability registry.
Evidence: RP services, engagement helpers, and tests
engagement.missionsState-aware mission progress, streaks, and activity history.
Why this status
Status is defined by the current product capability registry.
Evidence: Mission routes, components, and weekly mission tests
engagement.referralsReferral links, attribution, funnel status, rewards, and sharing guidance.
Why this status
Status is defined by the current product capability registry.
Evidence: Referral routes, service, analytics, and tests
engagement.questsMulti-step educational and challenge journeys.
Why this status
Status is defined by the current product capability registry.
Evidence: Schema foundation without a current page route
brands.campaignsCampaign creation, management, rewards, winners, teams, and analytics.
Why this status
Status is defined by the current product capability registry.
Evidence: Brand portal pages and APIs
brands.apiKeysSelf-service API credentials and integration management.
Why this status
Status is defined by the current product capability registry.
Evidence: Settings placeholder and schema fields
brands.experimentsA/B testing and controlled campaign variants.
Why this status
Status is defined by the current product capability registry.
Evidence: Schema foundation without a complete exposed workflow
widgets.authoringWidget configuration, flow editing, publishing, embed code, and analytics.
Why this status
Status is defined by the current product capability registry.
Evidence: Widget APIs, flow builder, and embed management
widgets.informationPublished information, campaign statistics, and interaction telemetry.
Why this status
Status is defined by the current product capability registry.
Evidence: Public widget config and event APIs
widgets.identityIdentity input recorded within a widget flow; it does not yet create or bind an account.
Why this status
Status is defined by the current product capability registry.
Evidence: Widget step telemetry only
widgets.tasksSocial and external task steps without independent completion verification.
Why this status
Status is defined by the current product capability registry.
Evidence: Self-reported widget task completion
widgets.contributionsContribution amount and reward previews that do not yet complete canonical checkout inside the widget.
Why this status
Status is defined by the current product capability registry.
Evidence: Widget telemetry without payment creation
widgets.referralsReferral-flow previews without a reward-bearing participant identity.
Why this status
Status is defined by the current product capability registry.
Evidence: Preview referral link generated in widget runtime
operations.adminOperational management for contributions, projects, campaigns, brands, and lifecycle actions.
Why this status
Status is defined by the current product capability registry.
Evidence: Admin pages, guarded APIs, and authorization tests
operations.reconciliationCross-system snapshots, mismatch detection, alerting, and administrative review.
Why this status
Status is defined by the current product capability registry.
Evidence: Reconciliation service, cron, snapshots, and admin UI
operations.signalOsInternal signals, dispatch plans, run sync, and approved writeback proposals.
Why this status
Status is defined by the current product capability registry.
Evidence: Admin UI, service, APIs, and model tests
operations.publicExecutionPublic evidence of completed governance and operational execution.
Why this status
Status is defined by the current product capability registry.
Evidence: Current page explicitly marked Coming Soon
communications.transactionalEmailPayment, account, and receipt lifecycle email delivery.
Why this status
No transactional email provider is configured.
Evidence: Resend service with SendGrid fallback
communications.preferencesUser-controlled email, push, and in-app lifecycle notifications.
Why this status
Status is defined by the current product capability registry.
Evidence: Unconnected component and schema foundation
communications.automationTrigger-based campaign communications and workflow actions.
Why this status
Status is defined by the current product capability registry.
Evidence: Schema foundation without a complete runner and UI loop