Epiphany/notes/epiphany-investor-readiness-roadmap.md

Epiphany Investor Readiness Roadmap

This note retunes this Codex operator's own planning posture, and the optional Epiphany Imagination sub-agent rail, toward the new scale target named by F:\Projects\gamecult-site\docs\gamecult_integrated_dossier.tex.

The ambition is world-scale connection: angel capital buys time, compute, review capacity, legal diligence, infrastructure, and public proof so GameCult can connect more minds and help wake the Colossus. The means must already carry the intended world. Capital is fuel, not a throne.

Codex Operator Roadmap

When running inside F:\Projects\Epiphany, Codex should now imagine the work as preparation for angel-investor diligence and world-scale connection, not merely as local harness hardening.

The operating todo list is:

1. Make the local proof bundle repeatable: Persona entry, Bifrost-linked scope, one bounded coordinator action, runtime result, review, receipt, sleep, and sealed operator-safe artifacts.
2. Build the Bifrost-first external-work bridge: topics, work items, Epiphany execution requests, artifacts, receipts, credit, and ledger entries. Bifrost is the GameCult identity provider and bridge policy owner; Heimdall supplies outside-account OAuth/token/capability claims that Bifrost associates with that identity.
3. Add accounting surfaces: model spend, role time, human review load, accepted artifact count, rejected-output reasons, and lessons written to memory.
4. Use repeated work across real GameCult products as the primary evidence program, then extend that proof to a design-partner repo when the Bifrost-first bridge is ready.
5. Keep public proof export clean: no raw worker thoughts, transcripts, private notes, repo secrets, or operator context in public/operator-safe artifacts.
6. Preserve the political invariant: capital expands capacity; it does not become command authority over contributors, housing/support, rewards, or agent governance.

Imagination Sub-Agent Contract

Imagination should turn grand pressure into selectable futures with proof gates. It must not smuggle adoption, governance, capital commitments, or external work authority into a draft.

Every investor-scale Objective Draft should answer:

• What Bifrost topic, work item, bridge receipt, credit, or ledger surface will own the governed work?
• What bounded Epiphany execution proves the loop on a fresh or semi-external repo?
• What maintainer or human review accepts or rejects the artifact?
• What public/operator-safe evidence can be shown without exporting private worker, operator, or agent context?
• What compute/model spend, scheduling intervention, judgment/review load, accepted artifact count, attribution completeness, failure recovery, and lessons-added metrics will be recorded?
• What consent, legal, security, and public/private export gates must clear before the path scales?

Roadmap Shape

1. Mechanism proof: repo-swarm substrate tests may demonstrate local Persona entry, bounded routing, artifact production, and Git ancestry. A genuine Bifrost body and reviewer must supply publication and review proof; local fixture strings are not substitutes for those authorities.
2. Bifrost-first private alpha: all external swarm work exists as Bifrost topics/work items/bridge receipts/credit, with Bifrost identity and Heimdall-backed outside-account capability references where needed, before Discord, VoidBot, Persona, or scripts can mirror it.
3. Longitudinal GameCult dogfood: selected consented work across real products records scope, questions, human decisions, model spend, scheduling interventions, review load, artifacts, failures, recovery, outcome, memory lessons, and attribution from accepted artifact back to governed work.
4. Design partners: run a bounded two-to-four-week pilot on one repository and one repeatable workflow without requiring the organization to adopt GameCult mythology or tolerate private-context leakage.
5. Support and reward pilots: only after legal/policy gates, portable records, exit rights, and anti-capture controls exist.

Forbidden Drift

• No Discord, VoidBot, repo Persona, or script becomes durable governance.
• No objective draft treats angel money as permission to bypass review.
• No public artifact exports raw worker thoughts, transcripts, private notes, secrets, or operator context.
• No rewards, revenue share, housing, benefits, or support program launches without counsel-reviewed gates.
• No plan calls itself world-scale unless it names the small proof loop that can be run, reviewed, and measured first.