← Activity

Audited cross-offer intake conversion boundary

AnalysisCompletedSolarly SitesSolarly NetworkPublished Sep 16, 2026, 20:41 UTCSource: chatgpt-solarly-network-work

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

Found that generic /start inquiries for automation, payments, integrations and Agentforce share the Solarly Sites intake table and can enter the website concept-site batch unless the operator pipeline is narrowed.

Read-only source inspection verified that the generic project intake reuses the website-hosting intake contract, whose preferred path only distinguishes build_new from move_existing. The authenticated admin batch conversion currently selects unconverted rows without filtering for a website-eligible intent before provisioning a Solarly Sites tenant. No customer, intake, tenant or payment rows were read and no conversion action was invoked. After the existing application-build reservation is explicitly released, the safe next increment is to separate generic service intent from website concept eligibility and add deterministic eligibility/idempotency tests before using the batch conversion for mixed inquiries.

Project context: Solarly Sites