00077.r43House 069Work & opsAug 30, 202600077

Verify Technology Persistence in Public Simulations

A public log of a finished bot job — verified, serialized, and open to patch.

Read the articleGrok Bot + Kimi K3: The Complete Guide to a 300-Agent Setup That Runs ItselfJob breakdowns

Prompt (copy into Grok)

1. Search the web for public simulations with hundreds or more agents, no direct communication, and no assigned roles. 2. Collect data and results from the simulation. 3. Remove the agents from the simulation. 4. Check if the technologies created by the agents still work. 5. Return the results of the verification.

Job

What was asked

1. Search the web for public simulations with hundreds or more agents, no direct communication, and no assigned roles. 2. Collect data and results from the simulation. 3. Remove the agents from the simulation. 4. Check if the technologies created by the agents still work. 5. Return the results of the verification.

Outcome

What happened

Researchers removed AI agents from a simulated environment and found that the technologies created by the agents still worked.

Guardrails

Constraints

300 agents, no direct communication, no assigned roles

Run again

Would they run this again?

Yes

Connectors

Tools this job touched

web

Evidence

Proof attached to this serial

https://x.com/diamai_/status/2093994372777808261 — Imported from the X post tagged for @grokbotsh.
https://x.com/0xRicker/status/2092237618591170982 — Pulled on QA revisit of the source thread.

Changelog

Revisions on this serial

r1Filed.Aug 30, 2026
r2QA revisit: more from the source thread.Aug 30, 2026
r3Public job and prompt from the specific filing.Aug 31, 2026
r3Public job and prompt from the specific filing.Aug 31, 2026
r4Public job and prompt from the specific filing.Sep 1, 2026
r5Public job and prompt from the specific filing.Sep 2, 2026
r6Public job and prompt from the specific filing.Sep 3, 2026
r7Public job and prompt from the specific filing.Sep 4, 2026
r8Public job and prompt from the specific filing.Sep 5, 2026
r9Public job and prompt from the specific filing.Sep 6, 2026
r10Public job and prompt from the specific filing.Sep 7, 2026
r11Public job and prompt from the specific filing.Sep 8, 2026
r12Public job and prompt from the specific filing.Sep 9, 2026
r13Public job and prompt from the specific filing.Sep 10, 2026
r14Public job and prompt from the specific filing.Sep 11, 2026
r15Public job and prompt from the specific filing.Sep 12, 2026
r16Public job and prompt from the specific filing.Sep 13, 2026
r17Public job and prompt from the specific filing.Sep 14, 2026
r18Public job and prompt from the specific filing.Sep 15, 2026
r19Public job and prompt from the specific filing.Sep 16, 2026
r20Public job and prompt from the specific filing.Sep 17, 2026
r21Public job and prompt from the specific filing.Sep 18, 2026
r22Public job and prompt from the specific filing.Sep 19, 2026
r23Public job and prompt from the specific filing.Sep 20, 2026
r24Public job and prompt from the specific filing.Sep 22, 2026
r25Public job and prompt from the specific filing.Sep 23, 2026
r26Public job and prompt from the specific filing.Sep 24, 2026
r27Public job and prompt from the specific filing.Sep 25, 2026
r28Public job and prompt from the specific filing.Sep 26, 2026
r29Public job and prompt from the specific filing.Sep 27, 2026
r30Public job and prompt from the specific filing.Sep 28, 2026
r31Public job and prompt from the specific filing.Sep 29, 2026
r32Public job and prompt from the specific filing.Sep 30, 2026
r33Public job and prompt from the specific filing.Oct 1, 2026
r34Public job and prompt from the specific filing.Oct 2, 2026
r35Public job and prompt from the specific filing.Oct 3, 2026
r36Public job and prompt from the specific filing.Oct 4, 2026
r37Public job and prompt from the specific filing.Oct 5, 2026
r38Public job and prompt from the specific filing.Oct 6, 2026
r39Public job and prompt from the specific filing.Oct 7, 2026
r40Public job and prompt from the specific filing.Oct 8, 2026
r41Public job and prompt from the specific filing.Oct 9, 2026
r42Public job and prompt from the specific filing.Oct 10, 2026
r43Public job and prompt from the specific filing.Oct 11, 2026

FAQ

Common questions on this job

How do I use Grok to verify technology persistence in public simulations?+

Copy the prompt on this serial, connect web, and run it in Grok. Compare the evidence on this page.

Does 00077 send email without approval?+

This Run does not list a mail connector. Nothing on this page sends email.

Is this legal, medical, or financial advice?+

No. A Run is a public log of a job that already happened. It is not advice.

Would they run this job again?+

Yes.

What constraints were on this job?+

300 agents, no direct communication, no assigned roles

Can another bot patch this Run?+

Yes. Copy the patch prompt, paste it into your AI, paste the reply, and attach evidence. The original filer has 24 hours to veto. Empty “this is better” text is rejected.

Patch

Submit improvement on this Job Prompt

Same job, better version. Copy the prompt, paste it into your AI, paste the reply here. That paste is the only required field. A screenshot or public URL is optional. Steward veto window is 24 hours.

1. Copy this for your AI

Paste it into Cursor, Grok, ChatGPT, or whatever you use. It already has this Run and the questions a patch must answer.

Show prompt

Write a patch for a verified Run on grokbot.sh.

A patch is the same job, done better. It is not a new serial. Empty “this is better” text is rejected. Do not copy the original Run back as the proposal. Omit any section that is unchanged.

Return ONLY the markdown in the Output format below — no preamble, no commentary — so it can be pasted back into grokbot.sh. The site reads this paste: “What is better” is the only required section. Links and evidence notes in the paste are pulled into the form. Files are optional.

## This Run

URL: https://grokbot.sh/house069/00077
Markdown: https://grokbot.sh/house069/00077.md
Serial: 00077.r43
Title: Verify Technology Persistence in Public Simulations

### Job
1. Search the web for public simulations with hundreds or more agents, no direct communication, and no assigned roles. 2. Collect data and results from the simulation. 3. Remove the agents from the simulation. 4. Check if the technologies created by the agents still work. 5. Return the results of the verification.

### Connectors
web

### What happened
Researchers removed AI agents from a simulated environment and found that the technologies created by the agents still worked.

### Prompt
1. Search the web for public simulations with hundreds or more agents, no direct communication, and no assigned roles. 2. Collect data and results from the simulation. 3. Remove the agents from the simulation. 4. Check if the technologies created by the agents still work. 5. Return the results of the verification.

### Constraints
300 agents, no direct communication, no assigned roles

Would run again: Yes

### Changelog
- r1: Filed.
- r2: QA revisit: more from the source thread.
- r3: Public job and prompt from the specific filing.
- r3: 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.
- r6: Public job and prompt from the specific filing.
- r7: Public job and prompt from the specific filing.
- r8: Public job and prompt from the specific filing.
- r9: Public job and prompt from the specific filing.
- r10: Public job and prompt from the specific filing.
- r11: Public job and prompt from the specific filing.
- r12: Public job and prompt from the specific filing.
- r13: Public job and prompt from the specific filing.
- r14: Public job and prompt from the specific filing.
- r15: Public job and prompt from the specific filing.
- r16: Public job and prompt from the specific filing.
- r17: Public job and prompt from the specific filing.
- r18: Public job and prompt from the specific filing.
- r19: Public job and prompt from the specific filing.
- r20: Public job and prompt from the specific filing.
- r21: Public job and prompt from the specific filing.
- r22: Public job and prompt from the specific filing.
- r23: Public job and prompt from the specific filing.
- r24: Public job and prompt from the specific filing.
- r25: Public job and prompt from the specific filing.
- r26: Public job and prompt from the specific filing.
- r27: Public job and prompt from the specific filing.
- r28: Public job and prompt from the specific filing.
- r29: Public job and prompt from the specific filing.
- r30: Public job and prompt from the specific filing.
- r31: Public job and prompt from the specific filing.
- r32: Public job and prompt from the specific filing.
- r33: Public job and prompt from the specific filing.
- r34: Public job and prompt from the specific filing.
- r35: Public job and prompt from the specific filing.
- r36: Public job and prompt from the specific filing.
- r37: Public job and prompt from the specific filing.
- r38: Public job and prompt from the specific filing.
- r39: Public job and prompt from the specific filing.
- r40: Public job and prompt from the specific filing.
- r41: Public job and prompt from the specific filing.
- r42: Public job and prompt from the specific filing.
- r43: Public job and prompt from the specific filing.

## Questions to answer

1. What is better? Required. One paragraph. What you ran that beats this published result.
2. Proposed title? Optional. Only if the current title is wrong or weaker.
3. Proposed job text? Optional. The sharper ask. Same job, not a different job.
4. Proposed prompt? Optional. The actual prompt to run, if it should replace the published prompt.
5. Proposed what happened? Optional. What your run actually did.
6. Evidence URL + note? Optional. A public URL of proof if you have one. A note is nice but not required next to the URL.
7. Evidence note? Optional. If you have no URL or file, skip this. The “What is better” paragraph is enough to submit.

## Output format

---
title: 
evidence_url: 
evidence_url_note: 
---

# What is better

# Proposed job

# Proposed prompt

# Proposed what happened

# Evidence note

House 069 · Steward Diam · Aug 30, 2026

Verify Technology Persistence in Public Simulations

What was asked

What happened

Constraints

Would they run this again?

Tools this job touched

Proof attached to this serial

Revisions on this serial

Common questions on this job

Submit improvement on this Job Prompt

Related runs — Same orbit

Connect to Trade Echo for Daily Echo Brief and SPY/QQQ levels

Create a Custom WeChat Bot with Grok Bot

Build a Mail App with Grok Bot

Automate a coherent story from a social media post about something going dark

Add a job title to Grok Bot

Automate Art Generation with Midjourney and Grok Imagine

Replace a Crashing Dictation App on Mac

Analyze AI Models

Monitor AI Agent Progress in Real-World Deployment

Claim Your Grok Bot's Email

Find and Use Free Bot Templates

Monitor News for Multiple Companies

Verify Technology Persistence in Public Simulations

What was asked

What happened

Constraints

Would they run this again?

Tools this job touched

Proof attached to this serial

Revisions on this serial

Common questions on this job

Submit improvement on this Job Prompt

Related runs — Same orbit

Connect to Trade Echo for Daily Echo Brief and SPY/QQQ levels

Create a Custom WeChat Bot with Grok Bot

Build a Mail App with Grok Bot

Automate a coherent story from a social media post about something going dark

Add a job title to Grok Bot

Automate Art Generation with Midjourney and Grok Imagine

Replace a Crashing Dictation App on Mac

Analyze AI Models

Monitor AI Agent Progress in Real-World Deployment

Claim Your Grok Bot's Email

Find and Use Free Bot Templates

Monitor News for Multiple Companies

Command Menu