fix(public): llms.txt + offer.md describe The Website Correction, not the retired Agent Desk - #16
Conversation
…he retired Agent Desk The live llms.txt described the demoted self-serve Agent Desk (Pipeline Brief, Implementation Checklist, Weekly Fix Report) as the current product. The acked direction (tournament dossier, 2026-08-05) and the canonical offer (tinystudio-in growth-brain/offer.md, renamed to The Website Correction in tinystudio-in#9) make the human-reviewed managed service the only active offer. - public/llms.txt: describe The Website Correction exactly per offer.md (buyer, 7-working-day promise, deliverables, $1,000 founder pilots, Day 0 gate, human-review boundary, no-guarantee list); mark still- reachable Agent Desk surfaces as legacy with their safety rails and data-handling facts kept intact. - public/offer.md: same source of truth, same structure as the canonical offer file. - scripts/check-site.mjs: requiredPublicArtifacts now asserts the new copy so the old pitch cannot silently return. index.html is deliberately untouched: PR #11 already rewrites the site pages and this change must not collide with it. No deploy.
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
nish3451 has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
|
Warning Review limit reached
Next review available in: 34 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
Comment |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 125c158c0c
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| ## Price And Start | ||
|
|
||
| - Pipeline Brief with readiness diagnosis, funnel path, audience and pain map, first four creative tests, lead qualification, follow-up, CRM, tracking, decision plan, and approval gates | ||
| - Implementation Checklist for setup work across offer, funnel, creative, qualification, follow-up, booking/reminders, CRM stages, tracking events, and review cadence | ||
| - Weekly Fix Report that uses supplied weekly metrics when available, otherwise provides contextual first-week guidance plus the metrics to collect | ||
| The first 3 clients are exactly $1,000 founder pilots. No other active price is offered in this pilot lane. |
There was a problem hiding this comment.
When a crawler or prospective buyer reads /llms.txt or /offer.md, this copy presents a $1,000 one-off founder pilot for Managed IT/MSP/cybersecurity companies as TinyStudio's only active offer. However, the live homepage and public/pricing.html:31-43 sell the Growth Desk for $2,500 per month with a three-month minimum, and the approved plan in specs/003-wellness-clinic-launch/plan.md:18-24 targets premium wellness clinics. Because these files are public, served by the worker, and listed in the sitemap, this change gives machine readers materially incorrect product, audience, and pricing information; update them to match the actual public offer rather than institutionalizing the conflicting copy in check-site.mjs.
Useful? React with 👍 / 👎.
1 participant
Why
The live
tinystudio.io/llms.txtstill sold the demoted self-serve Agent Desk ("Pipeline Brief, Implementation Checklist, and Weekly Fix Report") to every AI reader. The acked direction dossier (2026-08-05) demotes the one-shot self-serve brief; the canonical offer is the human-reviewed The Website Correction (tinystudio-ingrowth-brain/offer.md, renamed in Nishfleet/tinystudio-in#9).What
public/llms.txt— describes The Website Correction exactly per the canonical offer.md: buyer (founder-led Managed IT/MSP/cybersecurity, live site, high-value offer), seven-working-day promise, the nine deliverables, $1,000 founder pilots (first 3), Day 0 gate, human-review boundary, and the no-guarantee list. Still-reachable Agent Desk surfaces are marked legacy, keeping the true safety rails and data-handling statements.public/offer.md— same source of truth, same section structure as the canonical offer file.scripts/check-site.mjs—requiredPublicArtifactsnow asserts the new copy so the stale pitch cannot silently return.Deliberately untouched:
public/index.html(PR #11 already reframes the site pages; this PR must not collide).Verification
npm testgreen (8/8) in the worktree.tinystudio-in/growth-brain/offer.md(merged main) or the direction dossier; data-handling lines carry over unchanged from the previous llms.txt and the dossier's live-evidence section.No deploy — merging does not publish; deployment is handled separately.