Hive Brain
Live Hive
AdventureNLearn · AOS control plane

Hive BrainPublic system brief · interactive reasoning demo

A workshop that builds public tools for civic learning and craft education, while protecting private research. Watch active reasoning play through formation modes — or download the clean seed for a new Grok Build chat.

Open interactive HiveDownload clean seed
Class
PUBLIC
Demo
8 formation modes · live reasoning
Seed
2026-08-10

Hive Brain

Replication · Fidelity · Honest work

Enter the live 3D workspace →

Non-negotiable

North star

Replication

Another competent builder should be able to continue from the record.

Fidelity

Finished work freezes; claims stay honest; history is not polished into fiction.

Not engagement

Not optimized for likes, dwell time, virality, or attention metrics.

Rooms in one building

System layers

01

Control plane

Purpose and product discipline in one place — AOS holds the workshop law.

02

Knowledge (Hive)

Sources become linked knowledge that compounds. Wiki over chat amnesia.

03

Reasoning

Structured scrutiny. Models assist; they do not crown truth.

04

Public products

Civic suite and Educational Tutor — plain language, public-safe surfaces.

05

Private research

Experiments stay fenced until deliberately promoted. Not silent production.

06

Archive

Finished eras freeze for fidelity. History is not polished into fiction.

What ships publicly

Public products

Civic suite

Map-style tools for claims and jobsite-style surfaces. Public-facing UI stays plain and educational.

Educational Tutor

Craft learning in plain language. Success is understanding that transfers — not time-on-page theater.

Always

Integrity kernel

Supported

Backed by primary record

Unproven

Open; do not overclaim

Disputed

Conflict remains visible

  • Evidence / Inference / Assumption labeled
  • Primary records beat commentary
  • Multi-model agreement ≠ automatic truth
  • Human final call is non-negotiable
  • Prefer honest incomplete state over confident fiction
  • Attention is not a truth signal

Discipline

Principles

  1. 01Replication over engagement
  2. 02Fidelity over narrative polish
  3. 03One integrity framework for every builder
  4. 04Separate control plane from products people use
  5. 05Keep public products free of private theater
  6. 06Ship nothing from tokens alone

Boundaries

What it is not

  • Not an engagement farm or content theater
  • Not an auto-truth engine
  • Not silent parallel production of every experiment
  • Not operator-runbook publishing
  • Not finished by token spend or traction

Ship criteria

How to judge success

Could another team continue this from the record?
Does the record stay honest?
Are public tools clear and free of private theater?
Were engagement metrics never used as the ship criterion?
OPSEC-audited clean seed · 2026-08-10

Download clean seed ZIP

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.zip

01-NEW-CHAT-SEED.md

# NEW CHAT SEED — AdventureNLearn / AOS / Hive Brain
**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 control plane is **AOS**. **Hive Brain** is the living picture of the system: purpose, knowledge discipline, and public products.

### North star (non-negotiable)
- **Replication** — another competent builder should be able to continue from the record.
- **Fidelity** — finished work freezes; claims stay honest; history is not polished into fiction.
- **Not engagement** — this system is **not** optimized for likes, dwell time, virality, or attention metrics.

### What the system is
- A **control plane** for serious build work: public tools stay clean, private research stays fenced.
- A **knowledge layer** that compounds (wiki over chat amnesia).
- A **reasoning layer** that labels claims (Supported / Unproven / Disputed) and keeps **human final call**.
- **Public products**: civic suite (map-style claims/jobsite surfaces) and Educational Tutor (craft learning, plain language).
- **Local-first** stewardship; exports and public ships are deliberate.

### What the system is not
- Not an engagement product or content farm.
- Not an auto-truth engine.
- Not a dump of every experiment as production.
- Not a place for private operator chrome on public product navigation.
- Not finished “because tokens were spent” or “because it trended.”

### Integrity kernel (always)
- Supported / Unproven / Disputed
- Evidence / Inference / Assumption labeled
- Primary records beat commentary
- Multi-model agreement ≠ automatic truth
- Human final call is non-negotiable
- Prefer honest incomplete state over confident fiction

### OPSEC for this conversation
- Do **not** invent or request private family history, re-identifying biography, or operator-surface 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 any other conversation memory about private history).
2. Confirm understanding of **replication + fidelity, not engagement** 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.

### Optional product request (fill in when ready)
- [ ] Build: _______________________________
- [ ] Audience: ____________________________
- [ ] Public-safe: yes

---

**Motto:** REPLICATION · FIDELITY · HONEST WORK
**Date seed prepared:** 2026-08-10
**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

Start-here checklist

  • New conversation only (do not continue old thread)
  • Paste 01-NEW-CHAT-SEED.md as message 1
  • Confirm agent restates: replication + fidelity, not engagement
  • Give one concrete public-safe build request
  • Refuse re-import of private history or ops inventories into public UI
  • Ship = live product / tagged release / written decision — not token spend