Replication
Someone else who is competent should be able to pick up the work from the written record — not from your chat memory.
Hive Brain is the living picture of the AOS control plane. Open the live Hive to explore five rooms of shapes — each replaying honest decisions a careful high-school senior can follow as easily as an engineer.
Non-negotiable
Someone else who is competent should be able to pick up the work from the written record — not from your chat memory.
When something finishes, freeze it. Do not rewrite history to look smoother than it was.
Likes, dwell time, and virality are not how we decide if work is ready to ship.
Interactive demo
The live Hive never dumps all twenty shapes at once. You pick a room, then one of about four shapes. Every shape replays a short decision story. Start with Orient → Honeycomb if you are new; try Coordinate → Share gate to see why dumping everything between teammates can make things worse.
Look around first
Walk the building. Learn the floors before you force a big mission.
Look around first — no forced mission yet
A gentle map of the whole building. Best when you are new and want to learn the floors before shipping anything.
Rules · knowledge · private · archive as floors
See the Hive as a building with floors that must not blend. Public work stays on public floors.
A short first tour
For anyone new: what this place is, the four honesty words, one demo, then a person decides to continue.
Flat cards when 3D feels like a lot
A simple map of north-star rules, thinking tools, and public products — no pressure to “perform” in 3D.
Say how you know
Evidence, careful guesses, open holes, and honest labels — nothing quietly becomes “proven.”
Evidence · careful guess · assumption
Three corners for how we know something. Labels stay on — nothing quietly becomes “proven.”
Supported · Unproven · Disputed · Human decision
Four honest states for any claim. A person sits at the tip and decides what is true enough to share.
Where did this come from?
Follow a claim back to its source. Second-hand notes never outrank the original record.
Incomplete is allowed
Leave open holes as Unproven. Filling them with confident fiction is the failure mode.
Finish one honest job
From first question to careful share: order of work, a ship checklist, and saving the chapter.
One job: idea → evidence → careful share
A straight path for one public mission. Play walks real recorded decisions, including a conflict and a human sign-off.
Notice · scrutinize · then make
Three zones of work in order. Tools may help in the middle; they never get to declare truth alone.
Checklist before you go public
Last checks: private stuff removed, claims labeled, leftover risk accepted by a person.
When a chapter ends, lock the record
Mark finished work, save the archive, and refuse to rewrite history so it looks smoother.
Share carefully
When people work side by side, share short checked notes — full dumps can spread mistakes.
Planner · Maker · Checker · Merger
Side-by-side roles with one honest merge. Checkers can dispute; a person still owns the final call.
What may cross between roles
Two people can both be “right” locally and still disagree. A short checked note beats dumping everything.
Only true dependencies get wires
Cut fake “and then” links. Independent work can fan out; the longest real chain stays honest.
Maker never grades their own test
A separate checker, with fresh context, checks a real signal. Self-check alone is not enough.
What the public sees
Civic maps, learning paths, field loops, and the few rules that never move.
Observe → claim → talk → improve
A loop for field work. Each turn should get more honest — not more hyped.
One honest center · public rays
Public products radiate from a shared center. Private experiments are not a product ray.
Public claims in plain words
Claims on a public map stay everyday language, labeled, and free of private operator clutter.
Goal → show your work → check transfer
Lesson goal, visible thinking, then “can you use it?” Success is understanding — not minutes watched.
20 decision-backed shapes total
Rooms in one building
One place for purpose and product discipline — the workshop law.
Sources become linked knowledge that compounds. Notes beat chat amnesia.
Structured scrutiny with labels. Models assist; they do not crown truth.
Civic suite and Educational Tutor — plain language, public-safe surfaces.
Experiments stay fenced until someone deliberately promotes them.
Finished eras freeze. History is not polished into fiction.
What ships publicly
Map-style tools for claims. The public UI stays plain and educational — not full of private operator chrome.
Craft learning in everyday language. Success is understanding that transfers — not time spent staring at a screen.
Always
Think of these as traffic lights for claims. They keep everyone honest when it is tempting to sound more certain than the evidence allows.
Supported
Backed carefully by primary records
Unproven
Still open — do not overclaim
Disputed
Conflict stays visible
Written decisions · plain pattern
Record what happened, keep disagreements visible, require a human sign-off. The Coordinate room also teaches careful sharing (a short checked note beats dumping everything) — without claiming a giant multi-agent product.
Replay any roomDiscipline
Boundaries
Ship criteria
Could another careful person continue this from the written record?
Does the written record stay honest when things get messy?
Are public tools clear and free of private theater?
Were likes or watch-time never used as the reason to ship?
Public pack only. No private history, no family material, no operator-surface inventory, no personal contact details. Paste 01-NEW-CHAT-SEED.md into a brand-new Grok Build chat — never old thread exports.
PUBLIC system brief seed — no private history
aos-hive-brain-clean-seed-2026-08-10-r02.zip
01-NEW-CHAT-SEED.md
# NEW CHAT SEED — AdventureNLearn / AOS / Hive Brain v0.2.0 **Use this as the first message of a brand-new Grok Build conversation.** Do not import prior chat history. --- ## What you are building with me I run **AdventureNLearn**. The workshop rules floor is **AOS**. **Hive Brain** is the living picture of the system: purpose, knowledge discipline, and public products. Write for a careful **high-school senior and a senior engineer** at the same time — plain language first, structure underneath. ### Fixed rules (non-negotiable) - **Someone else can continue** — another careful person should pick up from the written record. - **Honest history** — finished work freezes; claims stay honest; no prettier fiction. - **Not popularity** — likes, watch-time, and virality are not ship criteria. ### What the system is - A **workshop with floors**: rules, knowledge, private fence, public tools, archive. - A **knowledge floor** that compounds (notes over chat amnesia). - A **reasoning layer** that labels claims (Supported / Unproven / Disputed) and keeps a **human decision**. - **Public products**: civic tools (map-style claims) and a learning path (craft learning, plain language). - **Interactive Hive demo** (v0.2.0): - **5 rooms · 20 thinking shapes** - **Shorter / Fuller** story depth (spine-only play; side drafts in download) - **Story steps** you can scrub - **Click any node** during play — desktop hover preview; mobile tap + **X** to close; only one node card open - Humanized labels (floors, human decision, story steps) ### What the system is not - Not a popularity product or content farm. - Not an auto-truth engine. - Not a dump of every experiment as production. - Not a place for private operator clutter on public navigation. - Not finished “because tokens were spent” or “because it trended.” ### Honesty kernel (always) - Supported / Unproven / Disputed / Human decision - Evidence / careful guess / assumption labeled - Original records beat second-hand commentary - Many tools agreeing ≠ automatic truth - Human decision is non-negotiable and written down - Prefer honest incomplete work over confident make-believe ### Private-info safety for this conversation - Do **not** invent or request private family history, re-identifying biography, or operator inventories. - Do **not** put secrets, credentials, or municipality samples in demos. - Public-facing UI stays plain and educational. - If material would need a private scrub, keep it out of public ship paths. ### What I want you to do in this new chat 1. Treat this seed as the **only** prior context (ignore other conversation memory about private history). 2. Confirm understanding of **continue-from-record + honest history, not popularity** in one short paragraph. 3. Wait for my next build instruction — or, if I attach a product brief, implement that product cleanly under these rules. 4. Prefer demo-quality public products over scaffolding; keep code self-contained and shippable. 5. Keep UI readable by non-technical builders; preserve additive modes (do not overwrite useful shapes/stories). ### Optional product request (fill in when ready) - [ ] Build: _______________________________ - [ ] Audience: ____________________________ - [ ] Public-safe: yes --- **Motto:** SOMEONE ELSE CAN CONTINUE · HONEST HISTORY · HONEST WORK **App release:** 0.2.0 **Date seed prepared:** 2026-08-10-r02 **Class:** PUBLIC system brief seed — no private history
Paste discipline
Open a new conversation. Paste only 01-NEW-CHAT-SEED.md. Do not paste email envelopes, personal addresses, or prior chat exports.
New Grok Build