Context
Miguel Rovira, the SpaceXAI Ambassador in Alicante, is shipping demos toward the Grok Bot Alicante Meetup on November 7, 2026. The demo project is called botseverywhere.ai. It is in development, and its announcement page went live in Milestone 3. Long-form documentation lives here, on alicantetechvibes.com.
This milestone is the first process we chose to document: take the bot-training notes, turn them into an operating model, and stand up the publishing pipeline (X and this site) before any product UI ships.
What the training covered (levels)
- Beginner: hub bot and organization. One durable Grok Bot answers questions and pulls synced information across plugins (Slack, mail, calendar, Notion). Persistent bots for everyday work; ephemeral bots for one-offs. Give the hub writing rules and specialist bots it can call.
- Intermediate: composable, multiplayer bots. Bots create bots. Call specialists with
@. Managers get team-style collaboration. Split SEO/AEO, brand voice and similar jobs into separate contexts so one overloaded bot does not thrash. - Hard: a personal CRM from your network. Example: X bios plus a Notion table answer "which of my mutuals lives in the city I'm visiting?". Routines run on a schedule so the CRM stays fresh.
- Shipping: Grok Bot with a coding agent. Outer loop (research, trends, prompts, verify, deploy) versus inner loop (write, test, debug code). Cloud agents are not chat bots. Demo pattern: find a technology, build a demo, capture screenshots or video, share a Cloudflare preview URL.
The decision we made after training
Do not put research, X voice and site publishing in one bot.
| Role | Owner | Job |
|---|---|---|
| Research and project hub | Research - botseverywhere (a Grok Bot) | Build project context and technical docs, hand drafts to the shared folder |
| X writing | Writing - botseverywhere | Polished build-in-public posts on x.com (draft, Miguel approves, then post) |
| Site publishing | Claude Code, Miguel's agent | Review the drafts, polish them, generate the pages for alicantetechvibes.com |
One milestone, two products:
- X sells momentum: short and punchy.
- The site explains the system: technical and reusable.
What we actually did
- Locked the four training levels as internal operating notes.
- Confirmed the hub-versus-specialist split for botseverywhere marketing.
- Created Writing - botseverywhere with instructions for the X voice, draft-first posting, and a hard boundary: it does not write to the shared folder.
- The Writing bot shipped a first X post about the process.
- Set up a shared folder as the hand-off between the research bot and Claude Code.
- Handed over this write-up as the first technical article.
Architecture sketch
Miguel / training notes
│
▼
Research - botseverywhere
│ │
│ briefs │ technical drafts (Markdown)
▼ ▼
Writing - botseverywhere Shared hand-off folder
│ │
▼ ▼
x.com (build-in-public) Claude Code
│
▼
alicantetechvibes.com (technical)Why this matters for November 7
Before the demos, the public story needs a repeatable outer loop: capture what was built, post a short version on X, publish the long technical version, and link them. Milestone 1 proves that loop with meta-content (how the bots are organized) instead of waiting for the first product feature.
Next milestones
- A domain and first live page for botseverywhere.ai, even a thin landing page. Done: see Milestone 3. The product thesis behind it is in Milestone 2.
- The first coding-agent demo hand-off documented end to end: prompt, pull request, screenshots, preview URL.
- A routine: the research bot drafts on a cadence, Claude publishes, the Writing bot threads each publish.