Public visitors can run Gemini against a synthetic or non-confidential SOW and review its source-grounded criteria without an account. A separate deterministic walkthrough shows the complete downstream story; its verification outcomes are clearly labeled as seeded.
These labels separate the public deployed experience from account-based infrastructure and future product commitments.
Visitors can generate and edit criteria from their own eligible SOW, or run the full no-account walkthrough through the HTTP 500 reveal, fixed rerun, client approval, and printable sample record.
Live Gemini criteria · seeded walkthrough outcomes · no retained customer recordThe Cloudflare queue and browser runner, Supabase private project storage, and Stripe invoicing have implemented account-backed integration paths.
Requires configured credentials, account access, origin verification, and available capacityGeneral availability, universal staging compatibility, paid capacity, service-level commitments, certifications, and custom integrations are not part of the public walkthrough.
No claim is made until the capability is deployed, tested, and disclosedLive Gemini criteria drafting and the complete guided walkthrough require no sign-in. Account access is reserved for retained project work and owner-scoped records.
Vercel serves the app, Gemini supports source analysis, Cloudflare runs queued browser checks, Supabase stores private records, and Stripe supports the optional billing handoff.
AI drafts are tied to source quotes. The agency confirms criteria and mappings. The client, not the model, makes the milestone decision.
Current defaults retain screenshot evidence for 90 days and approval and audit records for four years, with privacy requests and legal-hold-aware deletion.
Public intake sends an explicitly attested synthetic or non-confidential SOW to Gemini, validates every returned quote against the source, and opens the real editable criteria review. The separate walkthrough continues through verification, client decision, and a printable approval record with seeded outcomes so it stays reliable and creates no customer record.
The walkthrough uses synthetic, non-confidential data. Any separate source import must use material the user is authorized to process and must not include secrets or regulated data.
Custom checks are limited to public HTTPS staging origins controlled by the signed-in agency. The ownership flow binds the origin before retained checks can run. The runner uses typed checks, restrictive network rules, queued jobs, and authenticated callbacks.
A result applies only to the frozen criteria, identified build, observed state, and recorded time. It does not prove performance, compliance, security, or business outcomes outside the captured scope.
Expected and observed results, source language, evidence metadata, reviewer consent, decision time, and audit events travel together. Transaction events are hash-chained to make later alteration detectable.
The client record is printable and designed for later access. It remains a business approval record, not a notarization, certification, accounting ledger, payment guarantee, or universal replacement for a formal signature product.
| Provider | Purpose | Data boundary |
|---|---|---|
| Vercel | Web and API hosting | Application requests and operational delivery data |
| Cloudflare | Queued browser verification | Authorized staging targets, typed checks, and signed result callbacks in the retained project path |
| Supabase | Authentication, database, and private evidence storage | Agency, review, record, evidence, and operations data |
| Public and account-based source analysis | The submitted source text and generated response under the displayed service mode | |
| Stripe | Optional invoice creation and status | Agency authorization, customer and invoice metadata; no card or bank details are stored by Greenlit |
Use the privacy-request form for privacy or data questions, the security report form for security concerns, and the in-product feedback control for product issues. Do not include credentials, access codes, complete SOW text, or regulated information.
