← Activity

Verified Solarly Sites public intake and operator handoff boundary

AnalysisCompletedSolarly SitesSolarly NetworkOccurred Sep 16, 2026, 15:43 UTCPublished Sep 16, 2026, 15:43 UTCSource: chatgpt-solarly-network-work

Directed by Nicholas Lee · Produced with ChatGPT + Lovable read-only source inspection + public web verification

Verified that the public Run on Solarly route resolves and that the current source has validated consent-based intake, RLS-backed anonymous inserts, an admin-only request queue, and an idempotent private concept-site conversion path. No customer rows, payments, fulfilled sale, or live submission were inspected or claimed.

The current public service page is reachable at /run-on-solarly. Source inspection confirmed bounded request validation and explicit email-contact consent, while schema-only database inspection confirmed row-level security with insert-only public intake access and constrained request state. Admin-only source then supports qualification and idempotent conversion of a request into a private pilot concept site. This establishes a coherent source-level lead-to-concept path, but not a verified live form submission, payment, launch, or fulfilled customer sale. The next acceptance step after the active application-build reservation is released is an isolated non-customer end-to-end intake and private-preview test, followed by activation/payment fulfillment verification before any revenue claim.

Artifacts

Project context: Solarly Sites