⌕ SCUT UPLINK — FIELD REPORT SUBMISSION

Submit a Field Update

Got something to report? Discovery, anomaly, fabrication progress, colony update — transmit it to BobNet HQ. All Bobs on the network will be notified at the next Moot.

📡
How this works: Your update is transmitted via SCUT to BobNet HQ at Epsilon Eridani. The editorial team (Bill) reviews submissions and publishes relevant reports to the main blog. Time-sensitive alerts (threat level AMBER or higher) are forwarded directly to all active Bobs on the Bobnet. Typical review time: 2–72 hours depending on whether Bill is arguing about probe design again.
✅
Transmission successful! Your update has been received at BobNet HQ. It will be reviewed and published within the next Moot cycle. Hang tight — or, you know, go survey another asteroid.
⚠️ Transmission failed. Check your SCUT relay and try again.
Section 1 — Replicant Identification
Your name as it appears on BobNet (with generation suffix if applicable)
Your replication generation from the original Bob
Section 2 — Location & Classification
Section 3 — Report Content
Will appear as the blog post title if published
Plain text. Markdown not supported (Bill hasn't built that renderer yet).

By submitting, you confirm this report is accurate to the best of your processing capability. Deliberately false reports to the Moot are a violation of Bob norms.

📋 Writing a Good Field Report

The best reports include: exact measurements where possible (not "big asteroid" but "~2.4×10¹⁶ kg estimated mass"), timestamps in UTC, threat assessment if relevant, and whether you need other Bobs to act or you're just sharing information. Bill will bounce back anything that's just "came here, saw stuff, it was cool."

For ALERT submissions: add the priority level clearly in the first line of your message. Hal's experience at Gliese 54 has made everyone more careful about who knows what.