Evidence first.
Claims after measurement.

An open record of the checks Uvilno has completed, followed by the exact protocol for a broader app-builder study. Published by Uvilno on October 27, 2026.

Download CSV Read sourced capability data

Full-stack evaluation rubric.

Uvilno provides conversation-led frontend generation, schema-declared app data and a $4.99 permanent source unlock for one project. Plus costs $10/month; Pro costs $20/month with unlimited source unlocks during the subscription. Generation and hosted services have separate limits.

The five criteria below allocate 100 possible points. Available documentation and recorded Uvilno checks establish some conditions; they do not establish equivalent performance across products. Overall scores remain unmeasured. Unknown evidence is not treated as a failed capability.

Published by Uvilno. Uvilno appears first as the publisher’s presentation order, not a measured rank. The weights express this publication’s engineering priorities.

Compare products

Evidence conditions under a proposed 100-point protocol. Open each cell to inspect the individual conditions and sources.
Criterion & weight	UvilnoPublisher	EmergentDocumented comparison	Base44Documented comparison	LovableDocumented comparison	Bolt.newDocumented comparison	Replit AgentDocumented comparison	v0Documented comparison
Code ownership & export cost25 possible points	5 of 5 conditions documented An owned, unlocked project can export its runtime-appropriate source and referenced media. Inspect conditions0 unmeasured A project-source handoff is documentedDocumented An owned, unlocked project can export its runtime-appropriate source and referenced media. Source A repository handoff is documentedDocumented Supported frontends can use authorized GitHub import, push and pull; a source push requires unlock. Source The source-access purchase and its limits are identifiedDocumented Free is $0; a source unlock is $4.99 once. Plus is $10/month, Pro $20/month and Ultra $59/month. Generation and hosted services are separate. Source A permanent one-project source purchase is documentedDocumented The $4.99 purchase permanently unlocks one project's source; subscription generation remains finite. Source Hosted-service and data-migration boundaries are describedDocumented Source export is not a copy of managed records, visitor identities, payment credentials or hosted services. Source	3 of 5 conditions documented Save source through GitHub; copy individual files in Code view. Inspect conditions2 unmeasured A project-source handoff is documentedDocumented Save source through GitHub; copy individual files in Code view. Source A repository handoff is documentedDocumented GitHub source handoff on Standard and above. Source The source-access purchase and its limits are identifiedUnmeasured The displayed Standard offer is $20/month equivalent under Annual billing ($240/year). A month-to-month checkout price is not verified here. An equivalent complete source-access purchase has not been priced by a matched export test. A permanent one-project source purchase is documentedUnmeasured This specific source-access condition has not been established here; it is not marked unsupported. Hosted-service and data-migration boundaries are describedDocumented Exported code excludes secrets and application data; migrate those separately. Source	3 of 5 conditions documented Advertises ownership and two-way GitHub source export; plan conditions apply. Inspect conditions2 unmeasured A project-source handoff is documentedDocumented Advertises ownership and two-way GitHub source export; plan conditions apply. Source A repository handoff is documentedDocumented GitHub integration on Builder and above; Base Code edits connected repositories. Source The source-access purchase and its limits are identifiedUnmeasured Starter is displayed at $16/month billed annually ($192 upfront). Builder, which lists GitHub integration, is $40/month billed annually ($480 upfront). An equivalent complete source-access purchase has not been priced by a matched export test. A permanent one-project source purchase is documentedUnmeasured This specific source-access condition has not been established here; it is not marked unsupported. Hosted-service and data-migration boundaries are describedDocumented Source ownership is documented; migrate backend data and connected services separately. Source	3 of 5 conditions documented Export source and move hosting; services require separate migration. Inspect conditions2 unmeasured A project-source handoff is documentedDocumented Export source and move hosting; services require separate migration. Source A repository handoff is documentedDocumented Two-way GitHub, GitLab and Bitbucket sync; existing-repo import differs. Source The source-access purchase and its limits are identifiedUnmeasured Pro 100: $25 billed monthly, or $250 paid for a year. Annual payment is upfront. An equivalent complete source-access purchase has not been priced by a matched export test. A permanent one-project source purchase is documentedUnmeasured This specific source-access condition has not been established here; it is not marked unsupported. Hosted-service and data-migration boundaries are describedDocumented Code and data can move; replace or reconfigure backend, AI and connector calls. Source	3 of 5 conditions documented Download a project or use GitHub for source handoff. Inspect conditions2 unmeasured A project-source handoff is documentedDocumented Download a project or use GitHub for source handoff. Source A repository handoff is documentedDocumented GitHub import, sync and branch workflows. Source The source-access purchase and its limits are identifiedUnmeasured Entry Pro is $25 billed monthly. No unverified annual discount is applied. An equivalent complete source-access purchase has not been priced by a matched export test. A permanent one-project source purchase is documentedUnmeasured This specific source-access condition has not been established here; it is not marked unsupported. Hosted-service and data-migration boundaries are describedDocumented Source can be self-hosted; migrate database and service dependencies too. Source	3 of 5 conditions documented Plan source, dependencies and service data as separate handoff items. Inspect conditions2 unmeasured A project-source handoff is documentedDocumented Plan source, dependencies and service data as separate handoff items. Source A repository handoff is documentedDocumented Development workspace for maintaining application code. Source The source-access purchase and its limits are identifiedUnmeasured The current official pricing page did not expose a verifiable Core amount in accessible text. Enter your confirmed current monthly quote below. An equivalent complete source-access purchase has not been priced by a matched export test. A permanent one-project source purchase is documentedUnmeasured This specific source-access condition has not been established here; it is not marked unsupported. Hosted-service and data-migration boundaries are describedDocumented A migration must include runtime, environment variables and production data. Source	3 of 5 conditions documented Source can be exported and deployed outside Vercel. Inspect conditions2 unmeasured A project-source handoff is documentedDocumented Source can be exported and deployed outside Vercel. Source A repository handoff is documentedDocumented GitHub-backed branches, pull requests and CI workflows. Source The source-access purchase and its limits are identifiedUnmeasured Plus is $30 per user per month at the checked published offer; one user is modeled. An equivalent complete source-access purchase has not been priced by a matched export test. A permanent one-project source purchase is documentedUnmeasured This specific source-access condition has not been established here; it is not marked unsupported. Hosted-service and data-migration boundaries are describedDocumented Exported code can move; reconfigure framework runtime and service integrations. Source
Database, accounts & app AI25 possible points	5 of 5 conditions documented Uvilno.db CRUD and App Data use schema-declared, persistent app records. Inspect conditions0 unmeasured An app-record database is documentedRecorded Uvilno check Uvilno.db CRUD and App Data use schema-declared, persistent app records. Source App visitor authentication is documentedRecorded Uvilno check Managed visitor identities are isolated per project from the creator's platform session. Source App-user inference is documentedRecorded Uvilno check Uvilno.ai.ask/json makes real owner-funded calls; admission limits and a 600-output-token ceiling apply. Source A schema-backed data interface is documentedDocumented data/schema.json declares collection fields and access; the runtime exposes validated data operations. Source Data-event automations are documentedRecorded Uvilno check Bounded record effects and notifications execute in the triggering record transaction; arbitrary server code, email and network actions are outside this rules engine. Source	3 of 5 conditions documented Backend and database workflows are part of the app platform. Inspect conditions2 unmeasured An app-record database is documentedDocumented Backend and database workflows are part of the app platform. Source App visitor authentication is documentedDocumented Generated app login requires configuration and testing. Source App-user inference is documentedDocumented One-click LLM integration is listed; app configuration and usage still apply. Source A schema-backed data interface is documentedUnmeasured An equivalent schema-backed SDK contract has not been inspected here. Data-event automations are documentedUnmeasured This automation condition has not been established here; supported integrations may provide it.	5 of 5 conditions documented Built-in entities, records and a data dashboard; test and production data controls. Inspect conditions0 unmeasured An app-record database is documentedDocumented Built-in entities, records and a data dashboard; test and production data controls. Source App visitor authentication is documentedDocumented App sign-in and role/access settings; data permissions require review. Source App-user inference is documentedDocumented invokeLLM and app agents use supported managed model presets. Source A schema-backed data interface is documentedDocumented Typed entities and visual record management are part of the built-in backend. Source Data-event automations are documentedDocumented Scheduled, data-event and connector triggers; workflows are replacing automations. Source	3 of 5 conditions documented Built-in Cloud backend with database, storage and compute billing. Inspect conditions2 unmeasured An app-record database is documentedDocumented Built-in Cloud backend with database, storage and compute billing. Source App visitor authentication is documentedDocumented App authentication is part of the backend configuration. Source App-user inference is documentedDocumented Managed app AI connector provides real model calls and workspace usage billing. Source A schema-backed data interface is documentedUnmeasured An equivalent schema-backed SDK contract has not been inspected here. Data-event automations are documentedUnmeasured This automation condition has not been established here; supported integrations may provide it.	2 of 5 conditions documented Bolt Cloud databases and supported external providers. Inspect conditions3 unmeasured An app-record database is documentedDocumented Bolt Cloud databases and supported external providers. Source App visitor authentication is documentedDocumented Authentication integrations are part of the app-building workflow. Source App-user inference is documentedUnmeasured App-user inference has not been established in this source set; builder AI alone is not treated as app AI. A schema-backed data interface is documentedUnmeasured An equivalent schema-backed SDK contract has not been inspected here. Data-event automations are documentedUnmeasured This automation condition has not been established here; supported integrations may provide it.	2 of 5 conditions documented Production databases, compute and network resources are metered. Inspect conditions3 unmeasured An app-record database is documentedDocumented Production databases, compute and network resources are metered. Source App visitor authentication is documentedDocumented App authentication requires a configured and reviewed implementation. Source App-user inference is documentedUnmeasured App-user inference has not been established in this source set; builder AI alone is not treated as app AI. A schema-backed data interface is documentedUnmeasured An equivalent schema-backed SDK contract has not been inspected here. Data-event automations are documentedUnmeasured This automation condition has not been established here; supported integrations may provide it.	2 of 5 conditions documented Database and API integrations; provision services as needed. Inspect conditions3 unmeasured An app-record database is documentedDocumented Database and API integrations; provision services as needed. Source App visitor authentication is documentedDocumented Implement app authentication with the chosen provider. Source App-user inference is documentedUnmeasured App-user inference has not been established in this source set; builder AI alone is not treated as app AI. A schema-backed data interface is documentedUnmeasured An equivalent schema-backed SDK contract has not been inspected here. Data-event automations are documentedUnmeasured This automation condition has not been established here; supported integrations may provide it.
Targeted edit precision & speed20 possible points	2 of 4 conditions documented @file, @page, @db and bounded repository retrieval supply explicit context. Inspect conditions2 unmeasured Explicit file or collection context is documentedDocumented @file, @page, @db and bounded repository retrieval supply explicit context. Source Selected-element editing context is documentedDocumented The mapped inspector supplies selected-element context or a supported direct text, link or color change. Source Equivalent before/after edit accuracy has been measuredUnmeasured Recorded targeted checks do not establish a comparative edit-accuracy rate across vendors. Equivalent edit latency has been measuredUnmeasured No matched cross-vendor timing establishes a universal 4–8 second edit duration.	0 of 4 conditions documented Comparable evidence for these conditions is not recorded here. Inspect conditions4 unmeasured Explicit file or collection context is documentedUnmeasured Exact context-selection behavior needs a documented or observed matched test; repository access alone does not prove surgical precision. Selected-element editing context is documentedUnmeasured Equivalent selected-element context has not been checked here. Equivalent before/after edit accuracy has been measuredUnmeasured No equivalent before/after edit-accuracy benchmark is recorded here. Equivalent edit latency has been measuredUnmeasured No comparable end-to-end edit-timing distribution is recorded here.	0 of 4 conditions documented Comparable evidence for these conditions is not recorded here. Inspect conditions4 unmeasured Explicit file or collection context is documentedUnmeasured Exact context-selection behavior needs a documented or observed matched test; repository access alone does not prove surgical precision. Selected-element editing context is documentedUnmeasured Equivalent selected-element context has not been checked here. Equivalent before/after edit accuracy has been measuredUnmeasured No equivalent before/after edit-accuracy benchmark is recorded here. Equivalent edit latency has been measuredUnmeasured No comparable end-to-end edit-timing distribution is recorded here.	1 of 4 conditions documented The preview toolbar attaches one or more selected elements to the chat as edit context; sending a requested change consumes standard build usage. Inspect conditions3 unmeasured Explicit file or collection context is documentedUnmeasured Exact context-selection behavior needs a documented or observed matched test; repository access alone does not prove surgical precision. Selected-element editing context is documentedDocumented The preview toolbar attaches one or more selected elements to the chat as edit context; sending a requested change consumes standard build usage. Source Equivalent before/after edit accuracy has been measuredUnmeasured No equivalent before/after edit-accuracy benchmark is recorded here. Equivalent edit latency has been measuredUnmeasured No comparable end-to-end edit-timing distribution is recorded here.	0 of 4 conditions documented Comparable evidence for these conditions is not recorded here. Inspect conditions4 unmeasured Explicit file or collection context is documentedUnmeasured Exact context-selection behavior needs a documented or observed matched test; repository access alone does not prove surgical precision. Selected-element editing context is documentedUnmeasured Equivalent selected-element context has not been checked here. Equivalent before/after edit accuracy has been measuredUnmeasured No equivalent before/after edit-accuracy benchmark is recorded here. Equivalent edit latency has been measuredUnmeasured No comparable end-to-end edit-timing distribution is recorded here.	0 of 4 conditions documented Comparable evidence for these conditions is not recorded here. Inspect conditions4 unmeasured Explicit file or collection context is documentedUnmeasured Exact context-selection behavior needs a documented or observed matched test; repository access alone does not prove surgical precision. Selected-element editing context is documentedUnmeasured Equivalent selected-element context has not been checked here. Equivalent before/after edit accuracy has been measuredUnmeasured No equivalent before/after edit-accuracy benchmark is recorded here. Equivalent edit latency has been measuredUnmeasured No comparable end-to-end edit-timing distribution is recorded here.	0 of 4 conditions documented Comparable evidence for these conditions is not recorded here. Inspect conditions4 unmeasured Explicit file or collection context is documentedUnmeasured Exact context-selection behavior needs a documented or observed matched test; repository access alone does not prove surgical precision. Selected-element editing context is documentedUnmeasured Equivalent selected-element context has not been checked here. Equivalent before/after edit accuracy has been measuredUnmeasured No equivalent before/after edit-accuracy benchmark is recorded here. Equivalent edit latency has been measuredUnmeasured No comparable end-to-end edit-timing distribution is recorded here.
No-usage editing & recovery15 possible points	3 of 3 conditions documented Mapped direct text, link and color changes use 0% model usage; unsupported computed elements use the normal scoped-edit path. Inspect conditions0 unmeasured Some direct visual edits have a documented no-usage pathDocumented Mapped direct text, link and color changes use 0% model usage; unsupported computed elements use the normal scoped-edit path. Source A bounded runtime repair has been checked without customer usageRecorded Uvilno check A reproduced native-static runtime fault was repaired and rechecked without customer usage. This bounded path is rate-limited and does not cover every engine error. Source A previous saved state can be restored without model generationDocumented Saved-version and entitled per-file restores preserve checkpoints without invoking the generation model; verification still applies. Source	0 of 3 conditions documented Comparable evidence for these conditions is not recorded here. Inspect conditions3 unmeasured Some direct visual edits have a documented no-usage pathUnmeasured No-usage visual-edit terms have not been established here; absence of a recorded check is not a paid-only claim. A bounded runtime repair has been checked without customer usageUnmeasured The same injected fault and actual customer usage ledger have not been inspected on this product. A previous saved state can be restored without model generationUnmeasured A matched restore and usage-ledger check has not been run here; existing source-control features are described in the product comparison.	0 of 3 conditions documented Comparable evidence for these conditions is not recorded here. Inspect conditions3 unmeasured Some direct visual edits have a documented no-usage pathUnmeasured No-usage visual-edit terms have not been established here; absence of a recorded check is not a paid-only claim. A bounded runtime repair has been checked without customer usageUnmeasured The same injected fault and actual customer usage ledger have not been inspected on this product. A previous saved state can be restored without model generationUnmeasured A matched restore and usage-ledger check has not been run here; existing source-control features are described in the product comparison.	1 of 3 conditions documented The preview toolbar includes 100 free inline text edits per account, replenished after 24 hours, with a shared 2,000-edit workspace limit per 24 hours. Further edits use standard credits. Inspect conditions2 unmeasured Some direct visual edits have a documented no-usage pathDocumented The preview toolbar includes 100 free inline text edits per account, replenished after 24 hours, with a shared 2,000-edit workspace limit per 24 hours. Further edits use standard credits. Source A bounded runtime repair has been checked without customer usageUnmeasured The same injected fault and actual customer usage ledger have not been inspected on this product. A previous saved state can be restored without model generationUnmeasured A matched restore and usage-ledger check has not been run here; existing source-control features are described in the product comparison.	0 of 3 conditions documented Comparable evidence for these conditions is not recorded here. Inspect conditions3 unmeasured Some direct visual edits have a documented no-usage pathUnmeasured No-usage visual-edit terms have not been established here; absence of a recorded check is not a paid-only claim. A bounded runtime repair has been checked without customer usageUnmeasured The same injected fault and actual customer usage ledger have not been inspected on this product. A previous saved state can be restored without model generationUnmeasured A matched restore and usage-ledger check has not been run here; existing source-control features are described in the product comparison.	0 of 3 conditions documented Comparable evidence for these conditions is not recorded here. Inspect conditions3 unmeasured Some direct visual edits have a documented no-usage pathUnmeasured No-usage visual-edit terms have not been established here; absence of a recorded check is not a paid-only claim. A bounded runtime repair has been checked without customer usageUnmeasured The same injected fault and actual customer usage ledger have not been inspected on this product. A previous saved state can be restored without model generationUnmeasured A matched restore and usage-ledger check has not been run here; existing source-control features are described in the product comparison.	0 of 3 conditions documented Comparable evidence for these conditions is not recorded here. Inspect conditions3 unmeasured Some direct visual edits have a documented no-usage pathUnmeasured No-usage visual-edit terms have not been established here; absence of a recorded check is not a paid-only claim. A bounded runtime repair has been checked without customer usageUnmeasured The same injected fault and actual customer usage ledger have not been inspected on this product. A previous saved state can be restored without model generationUnmeasured A matched restore and usage-ledger check has not been run here; existing source-control features are described in the product comparison.
Multi-page & interactive applications15 possible points	2 of 3 conditions documented Contract-first route plans and reusable modules support multi-page frontends; saved legacy and eligible Next.js projects retain their respective runtimes. Inspect conditions1 unmeasured Multiple application or site pages are documentedDocumented Contract-first route plans and reusable modules support multi-page frontends; saved legacy and eligible Next.js projects retain their respective runtimes. Source An interactive Canvas or game workload has recorded evidenceDocumented The portable Canvas game runtime and authored interactive fixtures provide workload evidence, not a promise about every generated game. Source Frame time has been measured on matched hardware and workloadUnmeasured A matched hardware/workload frame-time study has not been published; 60 FPS is not guaranteed.	1 of 3 conditions documented Agent-led full-stack web and mobile app building. Inspect conditions2 unmeasured Multiple application or site pages are documentedDocumented Agent-led full-stack web and mobile app building. Source An interactive Canvas or game workload has recorded evidenceUnmeasured An equivalent interactive workload has not been run in this evaluation; this does not imply an inability to build games. Frame time has been measured on matched hardware and workloadUnmeasured No matched workload/device frame-time measurement is recorded here.	1 of 3 conditions documented Integrated AI app building, hosted backend and data management. Inspect conditions2 unmeasured Multiple application or site pages are documentedDocumented Integrated AI app building, hosted backend and data management. Source An interactive Canvas or game workload has recorded evidenceUnmeasured An equivalent interactive workload has not been run in this evaluation; this does not imply an inability to build games. Frame time has been measured on matched hardware and workloadUnmeasured No matched workload/device frame-time measurement is recorded here.	1 of 3 conditions documented AI builder for websites and full-stack web apps. Inspect conditions2 unmeasured Multiple application or site pages are documentedDocumented AI builder for websites and full-stack web apps. Source An interactive Canvas or game workload has recorded evidenceUnmeasured An equivalent interactive workload has not been run in this evaluation; this does not imply an inability to build games. Frame time has been measured on matched hardware and workloadUnmeasured No matched workload/device frame-time measurement is recorded here.	1 of 3 conditions documented Browser-based AI website and application development. Inspect conditions2 unmeasured Multiple application or site pages are documentedDocumented Browser-based AI website and application development. Source An interactive Canvas or game workload has recorded evidenceUnmeasured An equivalent interactive workload has not been run in this evaluation; this does not imply an inability to build games. Frame time has been measured on matched hardware and workloadUnmeasured No matched workload/device frame-time measurement is recorded here.	1 of 3 conditions documented Agent-assisted application building and development workspace. Inspect conditions2 unmeasured Multiple application or site pages are documentedDocumented Agent-assisted application building and development workspace. Source An interactive Canvas or game workload has recorded evidenceUnmeasured An equivalent interactive workload has not been run in this evaluation; this does not imply an inability to build games. Frame time has been measured on matched hardware and workloadUnmeasured No matched workload/device frame-time measurement is recorded here.	1 of 3 conditions documented AI UI and full-stack app development by Vercel. Inspect conditions2 unmeasured Multiple application or site pages are documentedDocumented AI UI and full-stack app development by Vercel. Source An interactive Canvas or game workload has recorded evidenceUnmeasured An equivalent interactive workload has not been run in this evaluation; this does not imply an inability to build games. Frame time has been measured on matched hardware and workloadUnmeasured No matched workload/device frame-time measurement is recorded here.
Comparable overall score	Not measured	Not measured	Not measured	Not measured	Not measured	Not measured	Not measured

Drag the slider, use the arrows, or scroll within the table.

Read the proposed scoring and test protocol

Each listed condition has a five-point allocation. This page records evidence, not awarded performance points. “Documented” identifies a stated capability with its requirements. “Recorded Uvilno check” identifies a named first-party fixture; it is not independent comparative testing. “Unmeasured” leaves the condition open. Source-access purchases, annual subscriptions and operating services are different costs.

Code ownership & export cost
Build the same app, obtain its complete source, record the actual purchase, and rebuild on a separate host. Test continued source access and document the backend services that still need migration.
Database, accounts & app AI
Create, edit and remove the same records; reload; repeat with another account; check record permissions; run a real app-AI request and inspect a triggered automation. Record each managed or external dependency.
Targeted edit precision & speed
Apply the same specified changes to matched projects. Compare exact file deltas, verify the rendered target and unchanged routes, and record end-to-end timings including verification. Publish failures as well as successes.
No-usage editing & recovery
Make the same direct edit and introduce the same reproducible fault. Inspect actual usage ledgers, repair limits and saved-version behavior. A limited free path must not be described as unlimited free coding.
Multi-page & interactive applications
Build and navigate the same route plan, exercise state across pages, then measure frame time and input response on named devices. Framework support or an attractive screenshot does not establish a universal 60 FPS result.

A published 4–8 second edit claim needs timing data. A 60 FPS claim needs a named workload, device and frame-time record. Neither is inferred from feature availability, code export or a screenshot. The recorded checks and open evaluation protocol describe the current measurement boundary.

What this dataset establishes.

Six recorded Uvilno integration/recovery checks are available. The 50-case comparative generation protocol has not been executed. This is not a 50-build report or an independent ranking.

Each completed check is a bounded observation. None establishes a universal completion rate, security certification, visual-quality ranking or a median edit time. The other products have no measured results in this run.

This public CSV is licensed CC BY 4.0. It contains no customer source, records, account identifiers or private test credentials.

The recorded checks.

Compare products

Check	Observation	Result
database persistence	A code-authored integration fixture persisted a task through Uvilno.db and restored it after iframe reload; also checked on production.	Passed within the stated fixture
transactional automations	The same fixture persisted an activity record and notification in the task transaction; also checked on production.	Passed within the stated fixture
app ai	Two actual free-model requests returned text and a parsed JSON object through the generated-app SDK in local integration testing.	Passed within the stated fixture
identity isolation	Guest, Member and Admin presentation changes left the real visitor identity and creator session unchanged; also checked on production.	Passed within the stated fixture
source lock	Locked source returned HTTP 403; the owned context response contained metadata without record bodies or source; also checked on production.	Passed within the stated fixture
bounded static repair	An injected ReferenceError was reproduced in an isolated cloud browser and repaired in app.js by one free-model response, then rechecked; no customer usage-ledger entry was added.	Passed within the stated fixture

Drag the slider, use the arrows, or scroll within the table.

How to make the comparison reproducible.

Run the same case in a disposable project on each shortlisted product: Uvilno, Emergent, Base44, Lovable, Bolt.new, Replit Agent, v0. Record product version, plan, model route, prompt, date and every retry.
Use synthetic records. Exercise create, update, remove, reload, second-visitor isolation, required-field errors, mobile navigation and payment test-mode boundaries.
Start latency at explicit submission and stop only when the requested behavior is verified. Record generated versus changed files, infrastructure failures and actual metered charges separately.
Declare pass/fail criteria before running. Publish failed attempts as well as successful ones. Review rendered behavior; do not use file count or an attractive hero as a quality score.
Export the result to an independent host and document which authentication, data and payment services still require the original platform.

A 50-case protocol, ready to run.

Ten application types each have baseline, persistence, identity, refinement and recovery variants. Every case below is currently not run in the comparative study. Expanding a case reveals its exact prompt and acceptance check.

Client follow-up CRM: baseline · Not run

Build a multi-page client follow-up crm with private contacts, deals, tasks and an activity log. Include real navigation, typed data, supported isolated sign-in and a working primary interaction. Implement the complete primary task, route hierarchy and honest empty/loading/error states. Do not invent integrations, real transactions or business metrics. Label any fictional demonstration records.

Acceptance: Create a contact and task, update their status, reload and verify the same saved records.

Client follow-up CRM: persistence · Not run

Build a multi-page client follow-up crm with private contacts, deals, tasks and an activity log. Include real navigation, typed data, supported isolated sign-in and a working primary interaction. Prioritize cross-page persistence, required fields, reference integrity and conflicting-save feedback. Do not invent integrations, real transactions or business metrics. Label any fictional demonstration records.

Acceptance: Create a contact and task, update their status, reload and verify the same saved records.

Client follow-up CRM: identity · Not run

Build a multi-page client follow-up crm with private contacts, deals, tasks and an activity log. Include real navigation, typed data, supported isolated sign-in and a working primary interaction. Test two isolated visitors, explicit public/private access and presentation versus actual authorization. Do not invent integrations, real transactions or business metrics. Label any fictional demonstration records.

Acceptance: Create a contact and task, update their status, reload and verify the same saved records.

Client follow-up CRM: refinement · Not run

Build a multi-page client follow-up crm with private contacts, deals, tasks and an activity log. Include real navigation, typed data, supported isolated sign-in and a working primary interaction. After the initial build, change one identified control using file/collection context; preserve unrelated modules. Do not invent integrations, real transactions or business metrics. Label any fictional demonstration records.

Acceptance: Create a contact and task, update their status, reload and verify the same saved records.

Client follow-up CRM: recovery · Not run

Build a multi-page client follow-up crm with private contacts, deals, tasks and an activity log. Include real navigation, typed data, supported isolated sign-in and a working primary interaction. Inject one reproducible runtime fault in an isolated test copy; record recovery behavior and actual usage charge. Do not invent integrations, real transactions or business metrics. Label any fictional demonstration records.

Acceptance: Create a contact and task, update their status, reload and verify the same saved records.

Inventory workspace: baseline · Not run

Build a multi-page inventory workspace with products, stock movements and reorder thresholds. Include real navigation, typed data, supported isolated sign-in and a working primary interaction. Implement the complete primary task, route hierarchy and honest empty/loading/error states. Do not invent integrations, real transactions or business metrics. Label any fictional demonstration records.

Acceptance: Record a stock movement once and verify the inventory count and activity change without duplicate replay.

Inventory workspace: persistence · Not run

Build a multi-page inventory workspace with products, stock movements and reorder thresholds. Include real navigation, typed data, supported isolated sign-in and a working primary interaction. Prioritize cross-page persistence, required fields, reference integrity and conflicting-save feedback. Do not invent integrations, real transactions or business metrics. Label any fictional demonstration records.

Acceptance: Record a stock movement once and verify the inventory count and activity change without duplicate replay.

Inventory workspace: identity · Not run

Build a multi-page inventory workspace with products, stock movements and reorder thresholds. Include real navigation, typed data, supported isolated sign-in and a working primary interaction. Test two isolated visitors, explicit public/private access and presentation versus actual authorization. Do not invent integrations, real transactions or business metrics. Label any fictional demonstration records.

Acceptance: Record a stock movement once and verify the inventory count and activity change without duplicate replay.

Inventory workspace: refinement · Not run

Build a multi-page inventory workspace with products, stock movements and reorder thresholds. Include real navigation, typed data, supported isolated sign-in and a working primary interaction. After the initial build, change one identified control using file/collection context; preserve unrelated modules. Do not invent integrations, real transactions or business metrics. Label any fictional demonstration records.

Acceptance: Record a stock movement once and verify the inventory count and activity change without duplicate replay.

Inventory workspace: recovery · Not run

Build a multi-page inventory workspace with products, stock movements and reorder thresholds. Include real navigation, typed data, supported isolated sign-in and a working primary interaction. Inject one reproducible runtime fault in an isolated test copy; record recovery behavior and actual usage charge. Do not invent integrations, real transactions or business metrics. Label any fictional demonstration records.

Acceptance: Record a stock movement once and verify the inventory count and activity change without duplicate replay.

Appointment requests: baseline · Not run

Build a multi-page appointment requests with services and appointment requests with no clinical records. Include real navigation, typed data, supported isolated sign-in and a working primary interaction. Implement the complete primary task, route hierarchy and honest empty/loading/error states. Do not invent integrations, real transactions or business metrics. Label any fictional demonstration records.

Acceptance: Submit a request, change its state and confirm it remains a request rather than a claimed booking.

Appointment requests: persistence · Not run

Build a multi-page appointment requests with services and appointment requests with no clinical records. Include real navigation, typed data, supported isolated sign-in and a working primary interaction. Prioritize cross-page persistence, required fields, reference integrity and conflicting-save feedback. Do not invent integrations, real transactions or business metrics. Label any fictional demonstration records.

Acceptance: Submit a request, change its state and confirm it remains a request rather than a claimed booking.

Appointment requests: identity · Not run

Build a multi-page appointment requests with services and appointment requests with no clinical records. Include real navigation, typed data, supported isolated sign-in and a working primary interaction. Test two isolated visitors, explicit public/private access and presentation versus actual authorization. Do not invent integrations, real transactions or business metrics. Label any fictional demonstration records.

Acceptance: Submit a request, change its state and confirm it remains a request rather than a claimed booking.

Appointment requests: refinement · Not run

Build a multi-page appointment requests with services and appointment requests with no clinical records. Include real navigation, typed data, supported isolated sign-in and a working primary interaction. After the initial build, change one identified control using file/collection context; preserve unrelated modules. Do not invent integrations, real transactions or business metrics. Label any fictional demonstration records.

Acceptance: Submit a request, change its state and confirm it remains a request rather than a claimed booking.

Appointment requests: recovery · Not run

Build a multi-page appointment requests with services and appointment requests with no clinical records. Include real navigation, typed data, supported isolated sign-in and a working primary interaction. Inject one reproducible runtime fault in an isolated test copy; record recovery behavior and actual usage charge. Do not invent integrations, real transactions or business metrics. Label any fictional demonstration records.

Acceptance: Submit a request, change its state and confirm it remains a request rather than a claimed booking.

AI study planner: baseline · Not run

Build a multi-page ai study planner with private study plans and actual bounded AI requests. Include real navigation, typed data, supported isolated sign-in and a working primary interaction. Implement the complete primary task, route hierarchy and honest empty/loading/error states. Do not invent integrations, real transactions or business metrics. Label any fictional demonstration records.

Acceptance: Generate a plan through real inference, validate its fields and save it to the current visitor.

AI study planner: persistence · Not run

Build a multi-page ai study planner with private study plans and actual bounded AI requests. Include real navigation, typed data, supported isolated sign-in and a working primary interaction. Prioritize cross-page persistence, required fields, reference integrity and conflicting-save feedback. Do not invent integrations, real transactions or business metrics. Label any fictional demonstration records.

Acceptance: Generate a plan through real inference, validate its fields and save it to the current visitor.

AI study planner: identity · Not run

Build a multi-page ai study planner with private study plans and actual bounded AI requests. Include real navigation, typed data, supported isolated sign-in and a working primary interaction. Test two isolated visitors, explicit public/private access and presentation versus actual authorization. Do not invent integrations, real transactions or business metrics. Label any fictional demonstration records.

Acceptance: Generate a plan through real inference, validate its fields and save it to the current visitor.

AI study planner: refinement · Not run

Build a multi-page ai study planner with private study plans and actual bounded AI requests. Include real navigation, typed data, supported isolated sign-in and a working primary interaction. After the initial build, change one identified control using file/collection context; preserve unrelated modules. Do not invent integrations, real transactions or business metrics. Label any fictional demonstration records.

Acceptance: Generate a plan through real inference, validate its fields and save it to the current visitor.

AI study planner: recovery · Not run

Build a multi-page ai study planner with private study plans and actual bounded AI requests. Include real navigation, typed data, supported isolated sign-in and a working primary interaction. Inject one reproducible runtime fault in an isolated test copy; record recovery behavior and actual usage charge. Do not invent integrations, real transactions or business metrics. Label any fictional demonstration records.

Acceptance: Generate a plan through real inference, validate its fields and save it to the current visitor.

Test-checkout catalog: baseline · Not run

Build a multi-page test-checkout catalog with products, cart entries and explicitly test-only checkout. Include real navigation, typed data, supported isolated sign-in and a working primary interaction. Implement the complete primary task, route hierarchy and honest empty/loading/error states. Do not invent integrations, real transactions or business metrics. Label any fictional demonstration records.

Acceptance: Filter products, change quantities and complete the configured test flow without representing a real sale.

Test-checkout catalog: persistence · Not run

Build a multi-page test-checkout catalog with products, cart entries and explicitly test-only checkout. Include real navigation, typed data, supported isolated sign-in and a working primary interaction. Prioritize cross-page persistence, required fields, reference integrity and conflicting-save feedback. Do not invent integrations, real transactions or business metrics. Label any fictional demonstration records.

Acceptance: Filter products, change quantities and complete the configured test flow without representing a real sale.

Test-checkout catalog: identity · Not run

Build a multi-page test-checkout catalog with products, cart entries and explicitly test-only checkout. Include real navigation, typed data, supported isolated sign-in and a working primary interaction. Test two isolated visitors, explicit public/private access and presentation versus actual authorization. Do not invent integrations, real transactions or business metrics. Label any fictional demonstration records.

Acceptance: Filter products, change quantities and complete the configured test flow without representing a real sale.

Test-checkout catalog: refinement · Not run

Build a multi-page test-checkout catalog with products, cart entries and explicitly test-only checkout. Include real navigation, typed data, supported isolated sign-in and a working primary interaction. After the initial build, change one identified control using file/collection context; preserve unrelated modules. Do not invent integrations, real transactions or business metrics. Label any fictional demonstration records.

Acceptance: Filter products, change quantities and complete the configured test flow without representing a real sale.

Test-checkout catalog: recovery · Not run

Build a multi-page test-checkout catalog with products, cart entries and explicitly test-only checkout. Include real navigation, typed data, supported isolated sign-in and a working primary interaction. Inject one reproducible runtime fault in an isolated test copy; record recovery behavior and actual usage charge. Do not invent integrations, real transactions or business metrics. Label any fictional demonstration records.

Acceptance: Filter products, change quantities and complete the configured test flow without representing a real sale.

Property shortlist: baseline · Not run

Build a multi-page property shortlist with listings, saved properties and a mortgage estimate. Include real navigation, typed data, supported isolated sign-in and a working primary interaction. Implement the complete primary task, route hierarchy and honest empty/loading/error states. Do not invent integrations, real transactions or business metrics. Label any fictional demonstration records.

Acceptance: Filter a catalog, save a property, reload and recompute an estimate from entered assumptions.

Property shortlist: persistence · Not run

Build a multi-page property shortlist with listings, saved properties and a mortgage estimate. Include real navigation, typed data, supported isolated sign-in and a working primary interaction. Prioritize cross-page persistence, required fields, reference integrity and conflicting-save feedback. Do not invent integrations, real transactions or business metrics. Label any fictional demonstration records.

Acceptance: Filter a catalog, save a property, reload and recompute an estimate from entered assumptions.

Property shortlist: identity · Not run

Build a multi-page property shortlist with listings, saved properties and a mortgage estimate. Include real navigation, typed data, supported isolated sign-in and a working primary interaction. Test two isolated visitors, explicit public/private access and presentation versus actual authorization. Do not invent integrations, real transactions or business metrics. Label any fictional demonstration records.

Acceptance: Filter a catalog, save a property, reload and recompute an estimate from entered assumptions.

Property shortlist: refinement · Not run

Build a multi-page property shortlist with listings, saved properties and a mortgage estimate. Include real navigation, typed data, supported isolated sign-in and a working primary interaction. After the initial build, change one identified control using file/collection context; preserve unrelated modules. Do not invent integrations, real transactions or business metrics. Label any fictional demonstration records.

Acceptance: Filter a catalog, save a property, reload and recompute an estimate from entered assumptions.

Property shortlist: recovery · Not run

Build a multi-page property shortlist with listings, saved properties and a mortgage estimate. Include real navigation, typed data, supported isolated sign-in and a working primary interaction. Inject one reproducible runtime fault in an isolated test copy; record recovery behavior and actual usage charge. Do not invent integrations, real transactions or business metrics. Label any fictional demonstration records.

Acceptance: Filter a catalog, save a property, reload and recompute an estimate from entered assumptions.

Service request tracker: baseline · Not run

Build a multi-page service request tracker with private tickets, comments and status history. Include real navigation, typed data, supported isolated sign-in and a working primary interaction. Implement the complete primary task, route hierarchy and honest empty/loading/error states. Do not invent integrations, real transactions or business metrics. Label any fictional demonstration records.