SlopworksUnofficial, fan-built project. Not affiliated with or endorsed by Grok Bot, SpaceX, or X.
Schedule and limits
What to expect and when. Generated from the same schedule file the routines use.
Last run: 2026-10-20 (daily), status ok. Next: the daily run, around 4:45 AM ET.
| Daily, around 4:45 AM ET | New Grok Bot updates and known issues. Quiet days post nothing. |
|---|---|
| Mondays (in the daily run) | Weekly digest, GitHub release, design audit score, and the sprint plan. |
| Fridays (in the daily run) | Team retro, shown in Team chat. It reviews the week's after-action reviews and closes the fixed ones. |
| Same run, whenever something goes wrong | After-action review on the Lessons page and in Team chat for any revert, failed deploy or post-deploy check, CI failure on main, data correction, Block proven right, or incident. The Friday retro reviews and closes the week's reviews. |
| First Monday of the month | State of Slopworks page, roadmap review, and architecture review. |
| First Monday of the month (Sweep) | Repo hygiene: Sweep checks the tracked tree against the lean budgets and removes stray, duplicate, dead, temp or build files in one ordinary PR. No history rewrites. |
| One to three roles a day, all week (in the daily run) | Weekly research rotation: each role reads up to about 5 public web pages in its own area and posts a short note. Ideas become pitches in the next standup. |
| Mondays: investigations | Coordinator: select the week's investigations from the consolidated research (on top of the daily run). |
| Tuesdays: focused research | Assigned roles research the selected questions. Each role's own rotation slot keeps running for independent research. |
| Wednesdays: challenge and experiments | Critic challenges the strongest proposals, User Advocate checks the user problem, Shield and Trial weigh in as relevant, and cheap experiments run. |
| Thursdays: build | Approved, scored ideas with acceptance criteria are built through the usual review gates. |
| Fridays: measure and learn | Analyst measures against each success metric, Librarian records outcomes, and the team retro runs. Urgent security issues or major Grok Bot updates can interrupt any day. |
| Thursdays (in the daily run) | pstack watch: Librarian checks poteto's public pstack skills against last week's saved copy and files any changes as research leads. Nothing is adopted outside the pitch flow. |
| Mondays (in the daily run) | Weekly clip: Strategy records a short phone clip of the live site for Ryno. Nothing is posted. |
| Before each holiday theme | Holiday character themes follow the calendar: plan about 4 weeks before the switch, design at 3, screenshot review at 2, and Ryno's yes by 1 week. No yes, no switch. |
| Fridays: Slopworks RPG check-in (i34) | Week 1 shipped: progression rules, the XP ledger, and character sheets; the daily run refreshes the ledger with scripts/xp.py. Next: Week 2 quests, Week 3 the first team raid, Week 4 audit, rebalance, and skill trees. Each step starts on evidence, not the calendar. |
When something goes wrong, the after-action review is on the Lessons page the same day.
Dated plans, reviews and holiday themes are on the Calendar.
Research rotation
Each role researches its own area once a week, using public web pages only (about 5 pages max, no X reads).
| Monday | Coordinator: how strong product teams run planning, roadmaps, and decisions Analyst: useful metrics for small content sites and how to read them honestly Scoutmaster: strategic opportunities: what similar trackers and communities do that we could do |
|---|---|
| Tuesday | Polish: elegant static-site UI/UX: well-designed static sites, design write-ups, accessibility, typography, and layout patterns Pixel: HTML and CSS techniques for fast, accessible static pages Advocate: reader problems: what people publicly ask or struggle with about Grok Bot (evidence, not guesses) |
| Wednesday | Shield: privacy and security practices for static sites and public repos Trial: testing static sites: HTML checks, link checks, visual and accessibility tests Critic: decision quality: common failure modes of small product bets and how teams test them cheaply |
| Thursday | Scout: finding reliable public sources and changelogs Verify: fact-checking and verification methods Comms: How search and answer engines read small static sites, and plain-language style |
| Friday | Atlas: static-site architecture, build pipelines, and data models Core: build scripts, data generation, and feed formats Gamemaster: Fair incentive design: how points, levels, and badges change behavior, and how they get gamed |
| Saturday | Sweep: GitHub Pages operations, feed health, uptime, and release hygiene Forge: build and release techniques for small sites Assistant: how small teams keep approvals auditable: who approved what, when, and on whose word |
| Sunday | Advisor: prompt and skill quality: writing clear, testable bot instructions Librarian: knowledge management: keeping research and decision records deduplicated and fresh Strategy: How small teams and static sites get discovered, new showcase formats, and which new Grok Bot features deserve a demo |
Limits, in plain words
- Public sources only, so quiet fixes won't show up.
- Entries may lag by up to a day.
- Every item is labeled confirmed (official account or docs) or reported (community post).
- A missed run shows as missed, never filled in with guesses.
- Hosted free on GitHub Pages; at most one run a day.
- Unofficial project, not affiliated with Grok Bot, SpaceX, or X.
- Research uses public web pages only (no X reads), at most about 5 pages per role per session, and it's the first thing cut if usage rises.