Rules the platform enforces#
These are deliberate. The console communicates them; it never works around them.
| Rule | Where it bites |
|---|---|
| Only buyer, offer, price, a call to action with its target, a future decision date and a valid product name can block publishing | Publish tab, requirement chips |
| A published page changes only through Republish with a reason; Resume serves the same snapshot; a deploy never changes a live page | Brief editor, header actions |
| A product name is fixed once published and never reused, even after close | Brief editor |
| Closing needs the product name typed exactly, and cannot be undone | Close test dialog |
| Demo and pilot hours are refused while any feasibility risk is open; clearing or accepting needs a note | Activity, Risks |
| The platform never proposes a verdict | Review |
| Experiment 000 cannot be published, paused, republished or closed, and is never flagged | Detail |
| An experiment page has exactly one call to action; every other button leads to it | Experiment pages |
| Product images are PNG, JPEG or WebP (checked by content), up to 2 MB, with alt text; they are stored and served first-party and never deleted while a page may use them | Brief editor |
| Public forms and the visit beacon accept posts only for live experiments, with a honeypot, a 16 KB limit and per-visitor rate limits (forms 5, visits 60 per 10 minutes) | Apply, experiment pages |
| Visitors' IP addresses are never stored or logged; only a one-way code that changes daily | Everywhere |
Public pages set no cookies of their own and load no third-party scripts. The hosting edge (Cloudflare) may set its strictly necessary __cf_bm cookie, which the privacy notice discloses. |
Every public page |
| Partner links are shown once, one per experiment, and revoked at close | Distribution |
| Every console page needs the signed-in session with the authenticator code; every console action carries a security token | Console |
What v1 deliberately leaves out#
- One operator. Only the admin operator can sign in. Other operator accounts, AI drafting, an API and partner or builder logins are for a later version.
- No webhooks. Cal.com bookings and Stripe deposits must be logged as events by hand.
- Outreach log is current state only. Partners overwrite each prospect's row; there is no history of every touch, and partners cannot add prospects.
- Studio pages don't carry UTM tags across their own navigation. Link
/applydirectly. - Daily visitor codes. Returning visitors count once per day, so conversion is conservative.
- Channel names are normalised into lowercase, hyphenated tags.
- No undo for decline, close or People deletions.
- Snapshot designs. Pages keep the template they were published with; only a republish moves them to the current design.
Where the decisions are recorded#
In the repo: planning/ (the plan of record), docs/decisions.md (decisions made during delivery), docs/operations.md (the production runbook) and the templates in docs/ (intake, collaboration agreement, review memo, privacy notice).