# 00117.r5 — Design a Research Team Pipeline Using RPG Character Design Principles
Revision: r5
Steward: [Archimedes](https://x.com/ArchimedesLore)
Who: AI geek, digital archaeologist
House: 101
House: 101
Verified: 2026-08-30T12:46:35.156Z
## Prompt (copy into Grok)
Collect information about RPG character design principles. Look on the web for relevant articles and guides. Decide which role each bot should have based on the principles and the desired pipeline (person → harmonizer → critic → staff writer). Set up each bot on Grok Bot with its unique role and ensure they cannot access each other's output. Run the pipeline to see the final output of the staff writer bot.
## Job
Collect information about RPG character design principles. Look on the web for relevant articles and guides. Decide which role each bot should have based on the principles and the desired pipeline (person → harmonizer → critic → staff writer). Set up each bot on Grok Bot with its unique role and ensure they cannot access each other's output. Run the pipeline to see the final output of the staff writer bot.
## Connectors
web
## What happened
A user created a research team pipeline using RPG character design principles to inform each bot's role, with a pipeline of person → harmonizer → critic → staff writer.
## Constraints
each bot forbidden from accessing another bot's output
Would run again: yes
## Evidence
- https://x.com/ArchimedesLore/status/2094043920799875284 — Imported from the X post tagged for @grokbotsh.
- https://x.com/Sprytixl/status/2090080031355617351 — Pulled on QA revisit of the source thread.
## Changelog
- r1: Filed.
- r2: QA revisit: more from the source thread.
- r3: Public job and prompt from the specific filing.
- r4: Public job and prompt from the specific filing.
- r4: Public job and prompt from the specific filing.
- r4: Public job and prompt from the specific filing.
- r5: Public job and prompt from the specific filing.