Journey areas
8
Marketplace, intake, workspace, lifecycle, order, support, admin, legal
Closed beta validation
Validate the AI-powered marketplace with real buyer journeys.
DesirForge closed beta measures service discovery, package selection, project intake, delivery workspace clarity, order lifecycle confidence, support responsiveness, and operator readiness through the same backend used by marketplace and admin surfaces.
Program status
DesirForge Controlled Public Beta
Target testers
5 to 20 trusted testers
Required scenarios
20
Closed beta verdict
GO
Public production verdict
NO_GO
Task scenarios
24
Buyer and operator validation tasks
Open public blockers
7
Visible before any launch decision
Catalog persistence
5 override lanes
Blocker 8 carry-forward
Controlled public beta scope
Non-paid, invite-only, safe-data validation.
Non-paid preview
Public beta uses mock payment states only. No live payment is processed and paid marketplace launch remains blocked.
Uploads unavailable
Buyer file upload is disabled during public beta while production storage and scanning proof remains open.
Invite-only access
External self-registration is disabled. Testers use safe sample data and structured feedback paths.
Guided task scenarios
Testers validate marketplace flows against structured success criteria and friction prompts.
First-party beta analytics
Funnel, task, feedback, support, and friction metrics stay in DesirForge systems.
Support workflow validation
Support requests become beta triage records and issue candidates.
Legal and AI disclosure
Closed beta consent, safe-data guidance, and AI-powered workforce disclosure remain visible.
Tester workflow
Sign in, browse, search, compare packages, submit a safe-data intake, review the workspace, open the mock order flow, then submit feedback.
Feedback expectation
Every tester should record friction, clarity gaps, bugs, and trust concerns through `/beta/feedback` before the session closes.
Support path
Use `/beta/support` for blockers, support issues, security concerns, and anything that should become operator-triaged evidence.
Required carry-forward visibility
Closed beta is not public launch approval.
The beta layer measures user experience and operational readiness while preserving legal, observability, backup, storage, and catalog-persistence blockers.
Launch blocker
Closed beta validation does not override remaining operational blockers from Blocker 6.
Launch blocker
Observability stack remains configuration-validated only and must be started/validated before public production.
Launch blocker
Backup archive verification exists, but restore drill remains required before public production.
Launch blocker
Production storage/file scanning remains a blocker before public production.
Launch blocker
Attorney review has not been completed; public production launch remains blocked.
Launch blocker
Some marketplace catalog operations remain read-only or override-based until the persistence model is expanded.
Launch blocker
Admin operations readiness does not override remaining operational blockers from Blocker 6.
Transparent AI delivery
DesirForge uses an AI-powered delivery team to generate, review, and package work. You are not hiring hidden human freelancers, and final outputs should be reviewed before business use. Some legal, financial, medical, security, or compliance-sensitive work may require qualified human review outside the platform.
Read the AI disclosure