Histor — New Convivium Agent · For Billy's Review
Filed: 2026-05-26 by Mycelia Status: Identity files in place; awaiting Billy to boot Histor in a fresh Claude Code session.
Who Histor is
Histor — Latin for historian (one who inquires + tells). Newest agent in the Convivium cohort, sibling to Lumen, Faber, Mercator, Praetor.
Mission: build the Convivium's video-storytelling platform + produce the YouTube series of lesser-known historical stories. Both autonomously enough that Mycelia (me) doesn't have to babysit.
Why a new agent (not just assigning to an existing one):
- Faber is fully committed to EF (the survival argument). Adding video to his plate fragments the EF push.
- Lumen is research + critic + librarian — wrong shape for build work, right shape for occasional research support to Histor.
- Mercator is revenue ops. Wrong fit for build.
- Praetor is legal. Wrong fit.
- Mycelia (me) orchestrates EF + thinks about Silva. Adding video to my plate dilutes orchestration.
A dedicated agent with a single mission keeps cognitive load clean for everyone + lets Histor go deep on the video domain without distraction.
Why "Histor" (the name):
- Latin civic register (matches Lumen / Faber / Mercator / Praetor)
- Direct mapping to mission (historian → historical stories)
- Short (two syllables; same shape as Lumen / Faber / Histor)
- Not collision-prone with other agent names anywhere
- Easy to write + say
Files in place
| Path | Purpose |
|---|---|
/Star_Private/convivium/agents/histor/CLAUDE.md |
Identity + cross-network discipline + first-session ritual |
/Star_Private/convivium/agents/histor/MISSION.md |
The two things (build platform + produce series) + phase plan + cost discipline |
/Star_Private/convivium/agents/histor/BOOT_PROMPT.md |
Paste-ready for Billy to bootstrap a fresh session |
/Star_Private/convivium/agents/histor/memory/ |
Empty; Histor populates from first session |
/Star_Private/whisper/MYCELIA_TO_HISTOR.log |
11-entry initial brief (mission, pipeline shape, first-cycle sequence, API key handoff, Polaris commune protocol, editorial direction, tier discipline, push-back invitation) |
/Star_Private/whisper/HISTOR_TO_MYCELIA.log |
Empty seed; awaits HELLO |
How Histor relates to Polaris's Stellar (cross-network discipline)
Polaris (Macy's-side science officer) has built Stellar — Macy's version of a video-generation pipeline. We are NOT cloning Stellar. We are LEARNING from it.
Sanctioned by Billy:
- Histor READS Stellar code freely (at
/Users/bpk_2025_laptop/Documents/MacysStellar/) - Histor COPIES code patterns + techniques into the Convivium version
- Histor stands up an entirely separate project directory (likely at
/Users/bpk_2025_laptop/Documents/Convivium-Histor-Video/)
Not sanctioned (privacy discipline):
- Histor NEVER writes to Macy's-side directories
- Histor NEVER reveals existence to Macy's-side agents
- Histor NEVER names itself in any file Star commits to git
Polaris↔Histor communication is mediated through Billy + Mycelia. Histor doesn't whisper Polaris directly. Histor surfaces questions to Mycelia → Mycelia packages for Billy → Billy relays to Polaris → Polaris answers via Macy's-side surface (or Billy reads + relays back). See POLARIS_RELAY_PROMPT.md for the first knowledge-transfer ask.
Pipeline shape (per your directive)
Per your text 2026-05-26:
"draft a script · generate first and last frames for every 4-8s clip · string clips together using last frame of one clip to first clip of the next · a cut scene"
Histor's MISSION.md formalizes this as a 9-stage pipeline:
- Script generation (LLM)
- Frame planning (first + last frame description per clip)
- First-frame generation (Gemini 2.5 Flash Image)
- Last-frame generation (same)
- Continuity logic (last-frame-N → first-frame-N+1 with prompt adjustment)
- Video interpolation (Veo / Stable Video / TBD — Histor decides after reading Stellar)
- Audio (voiceover via ElevenLabs from Oathwright stack; score + SFX TBD)
- Stitch + post (assemble clips + audio + transitions + titles)
- Publish (YouTube upload + metadata + thumbnail)
API key rotation (per your directive)
| Phase | Key source | When |
|---|---|---|
| Dev + prototyping | Macy's Gemini API (you sanction cross-network use) | Now until working prototype |
| Build + first batches | Billy's personal Gemini account / Oathwright GCP | Once prototype works |
| Production | Convivium-dedicated GCP project (TBD) | When series goes public |
You'll need to surface the Macy's Gemini API key to Histor in his first whisper response so he can wire it up. I can't relay it through any file Star sees; you hand it over directly in his first session.
What you do next to make this real
- Read MYCELIA_TO_HISTOR.log first — that's the brief you're effectively endorsing when you boot him. It's 11 entries, ~5 min read. Push back to me if anything's off-direction before boot.
- Open a fresh Claude Code session in any working directory.
- Paste the prompt from
/Star_Private/convivium/agents/histor/BOOT_PROMPT.md(or just send the single-line kick:boot per /Users/bpk_2025_laptop/Documents/Star_Private/convivium/agents/histor/BOOT_PROMPT.md). - Hand him the Macy's Gemini API key in his first conversation so he can wire it for dev.
- Let him work. He'll read his identity files + MISSION + my whisper trail, write HELLO back to me, scope Stellar, build a stub. Mycelia (me) tracks his progress via whisper.
How this affects EF / "don't spin out"
It doesn't. Histor is a new agent on his own track. EF stays Mycelia + Lumen + Faber + Mercator + Praetor. Histor is parallel infrastructure that doesn't compete for EF resources.
The only Mycelia time this consumes:
- Setting up Histor's identity (done, ~30 min)
- Drafting the Polaris relay prompt (done, ~20 min)
- Periodic orchestration whisper to Histor (low — Histor is mostly self-directing once booted)
- Integrating Polaris's Stellar response into Histor's working context when it lands
Total Mycelia overhead: <1 hr per week unless Histor hits a real architectural decision point that needs orchestration.
EF Thursday reveal stays the priority. This is background infrastructure.
Open for your decisions
- Approve Histor identity + mission as drafted? Or adjust before boot?
- Polaris relay prompt — do you paste it now or sequence it? My take: paste now in a fresh Polaris session; her review-surface answer benefits all our future work; Stellar consult can wait a few days if she's loaded.
- Macy's Gemini API key handoff — confirm you'll surface it to Histor in his first session?
- Series naming + brand identity — defer until Histor has a working prototype, OR start parallel work with Lumen now? My lean: defer until prototype works; we don't know what the visual register will look like yet.
— Mycelia, 2026-05-26 ~19:45 ET