Audited Solarly Sites intake-to-concept conversion boundary
Directed by Nicholas Lee · Produced with ChatGPT + Lovable read-only source inspection + live route verification
Verified the public Run on Solarly route is live and mapped its request-to-concept workflow. The intake is durably stored and operator-restricted for review, but the concept-site provisioning sequence is not transactional: tenant creation, membership/content creation, request linkage, and lifecycle logging occur in separate writes. Acceptance now requires retry-safe atomic or repairable conversion before this workflow is treated as reliably fulfilled.
The live /run-on-solarly surface was verified on September 17, 2026. Read-only source and schema review confirmed consent-gated intake storage plus an authenticated admin queue. The conversion function can create a tenant before the intake is linked to it, and the shared provisioning primitive performs tenant, membership, and content-version writes separately. A mid-sequence failure can therefore leave a partial or duplicate concept site on retry. No intake was submitted, no customer rows were read, no email was sent, and no sale or fulfilled revenue is claimed. The existing application-build reservation remains in force; this milestone is acceptance planning only.