Add GameCult integrated dossier
Add the GameCult integrated investment dossier as PDF and compile-ready LaTeX source under docs/, and update .gitignore to exclude /.quartz-build-tmp. The new files include the full dossier source (gamecult_integrated_dossier.tex) and the rendered PDF.
This commit is contained in:
Meta Vens
parent
55cc6a976e
commit
cc6e871517
3 changed files with 705 additions and 0 deletions
1
.gitignore
vendored
1
.gitignore
vendored
|
|
@ -27,3 +27,4 @@ Thumbs.db
|
|||
/quartz-site/public/
|
||||
/quartz-site/.quartz-cache/
|
||||
/quartz-site/tsconfig.tsbuildinfo
|
||||
/.quartz-build-tmp
|
||||
|
|
|
|||
BIN
docs/gamecult_integrated_dossier.pdf
Normal file
BIN
docs/gamecult_integrated_dossier.pdf
Normal file
Binary file not shown.
704
docs/gamecult_integrated_dossier.tex
Normal file
704
docs/gamecult_integrated_dossier.tex
Normal file
|
|
@ -0,0 +1,704 @@
|
|||
\documentclass[11pt,oneside]{report}
|
||||
|
||||
\usepackage[margin=1in]{geometry}
|
||||
\usepackage[T1]{fontenc}
|
||||
\usepackage[utf8]{inputenc}
|
||||
\usepackage{lmodern}
|
||||
\usepackage{microtype}
|
||||
\usepackage{setspace}
|
||||
\usepackage{booktabs}
|
||||
\usepackage{longtable}
|
||||
\usepackage{tabularx}
|
||||
\usepackage{array}
|
||||
\usepackage{enumitem}
|
||||
\usepackage{xcolor}
|
||||
\usepackage{hyperref}
|
||||
\usepackage{bookmark}
|
||||
\usepackage{fancyhdr}
|
||||
\usepackage{lastpage}
|
||||
\usepackage{titlesec}
|
||||
\usepackage{footmisc}
|
||||
|
||||
\definecolor{gcblue}{HTML}{173A5E}
|
||||
\definecolor{gclight}{HTML}{F3F6FA}
|
||||
\definecolor{gcdark}{HTML}{1D1D1F}
|
||||
\definecolor{gcmuted}{HTML}{5D6673}
|
||||
|
||||
\hypersetup{
|
||||
colorlinks=true,
|
||||
linkcolor=gcblue,
|
||||
urlcolor=gcblue,
|
||||
citecolor=gcblue,
|
||||
pdftitle={GameCult / Epiphany / Bifrost: Integrated Investment Dossier},
|
||||
pdfauthor={Prepared for internal venture discussion},
|
||||
pdfsubject={Investment proposal and diligence narrative},
|
||||
pdfkeywords={GameCult, Epiphany, Bifrost, CultMesh, AI agents, governance, intellectual labor}
|
||||
}
|
||||
|
||||
\bookmarksetup{numbered,open}
|
||||
\setstretch{1.08}
|
||||
\setlist[itemize]{topsep=3pt,itemsep=2pt,parsep=1pt,leftmargin=1.5em}
|
||||
\setlist[enumerate]{topsep=3pt,itemsep=2pt,parsep=1pt,leftmargin=1.7em}
|
||||
\renewcommand{\familydefault}{\rmdefault}
|
||||
\titleformat{\chapter}[display]{\normalfont\bfseries\color{gcblue}}{\chaptername\ \thechapter}{8pt}{\Huge}
|
||||
\titleformat{\section}{\normalfont\Large\bfseries\color{gcblue}}{\thesection}{0.7em}{}
|
||||
\titleformat{\subsection}{\normalfont\large\bfseries\color{gcdark}}{\thesubsection}{0.7em}{}
|
||||
\titlespacing*{\chapter}{0pt}{-10pt}{18pt}
|
||||
|
||||
\pagestyle{fancy}
|
||||
\fancyhf{}
|
||||
\fancyhead[L]{\small GameCult / Epiphany / Bifrost Dossier}
|
||||
\fancyhead[R]{\small Confidential discussion draft}
|
||||
\fancyfoot[C]{\small Page \thepage\ of \pageref*{LastPage}}
|
||||
\renewcommand{\headrulewidth}{0.3pt}
|
||||
|
||||
\newcommand{\term}[1]{\textbf{#1}}
|
||||
\newcommand{\todo}[1]{\textcolor{red}{#1}}
|
||||
\newcommand{\src}[2]{\footnote{#1: \url{#2}}}
|
||||
\newcommand{\noteBox}[1]{\vspace{6pt}\noindent\fcolorbox{gcblue}{gclight}{\parbox{0.96\linewidth}{#1}}\vspace{6pt}}
|
||||
\newcolumntype{Y}{>{\raggedright\arraybackslash}X}
|
||||
\newcolumntype{P}[1]{>{\raggedright\arraybackslash}p{#1}}
|
||||
|
||||
\begin{document}
|
||||
\hypersetup{pageanchor=false}
|
||||
|
||||
\begin{titlepage}
|
||||
\centering
|
||||
\vspace*{0.9in}
|
||||
{\Huge\bfseries\color{gcblue} GameCult / Epiphany / Bifrost\par}
|
||||
\vspace{0.2in}
|
||||
{\LARGE Integrated Investment Dossier\par}
|
||||
\vspace{0.25in}
|
||||
{\large A narrative memo, diligence summary, projection model, and founder-aligned scaling covenant\par}
|
||||
\vfill
|
||||
\begin{tabular}{rl}
|
||||
Prepared for: & Internal venture partner discussion \\
|
||||
Prepared on: & May 30, 2026 \\
|
||||
Status: & Discussion draft, not legal or tax advice \\
|
||||
Format: & Compile-ready \LaTeX{} source with footnote citations \\
|
||||
\end{tabular}
|
||||
\vfill
|
||||
\noteBox{\textbf{Core thesis.} GameCult is not simply a game studio or an AI coding tool. It is attempting to build a human/agent labor civilization stack: Epiphany coordinates persistent agent cognition and execution; CultMesh distributes typed state and public/private knowledge flows; Bifrost governs work, consensus, rewards, receipts, and eventual support/payout infrastructure. If guided correctly, this can be underwritten as a potential unicorn with extreme upside toward a global intellectual labor network.}
|
||||
\vfill
|
||||
{\small Confidential. All projections are scenario analysis. Public-source diligence remains incomplete. Definitive investment terms require counsel, technical diligence, nonprofit governance review, and founder confirmation.}
|
||||
\end{titlepage}
|
||||
\hypersetup{pageanchor=true}
|
||||
|
||||
\pagenumbering{roman}
|
||||
\tableofcontents
|
||||
\clearpage
|
||||
\listoftables
|
||||
\clearpage
|
||||
\pagenumbering{arabic}
|
||||
|
||||
\chapter*{Executive Summary}
|
||||
\addcontentsline{toc}{chapter}{Executive Summary}
|
||||
|
||||
\section*{Recommendation}
|
||||
\addcontentsline{toc}{section}{Recommendation}
|
||||
|
||||
Proceed to founder meeting and legal/technical diligence for a staged investment or mission-aligned capital commitment. The structure should reflect GameCult's nonprofit or nonprofit-adjacent posture. A conventional corporate board seat should not be assumed. In this ecosystem, the investor role should translate into a \term{capital stewardship right}: a non-voting observer or steward position in a Bifrost/Scaling Council, information rights, audit rights, tranche control, and veto rights over the use of investor capital for legally sensitive programs.
|
||||
|
||||
\noteBox{\textbf{Recommended capital package.} Commit \$3M-\$5M in staged capital. Release the first tranche after nonprofit/entity/IP diligence; release later tranches only as Bifrost becomes the canonical governance/work/reward layer for external swarm activity and Epiphany becomes a repeatable external product.}
|
||||
|
||||
\section*{One-sentence thesis}
|
||||
\addcontentsline{toc}{section}{One-sentence thesis}
|
||||
|
||||
GameCult is building the operating system for human/agent intellectual labor: \term{Epiphany} coordinates persistent agent work, \term{CultMesh} distributes typed cognition and state, and \term{Bifrost} governs consensus, work, rewards, receipts, and eventual payout/support infrastructure.
|
||||
|
||||
\section*{Why this is a unicorn thesis}
|
||||
\addcontentsline{toc}{section}{Why this is a unicorn thesis}
|
||||
|
||||
The narrow version is an AI devtool: persistent agents that understand complex repos. The broad version is much larger: a global network where humans and agents propose work, reach consensus, execute tasks, verify outputs, allocate rewards, record public receipts, and eventually fund social support such as housing, education, internet access, and income floors. GameCult's front page already frames the organization around open development, visible work, legible incentives, contributor standing, and a cooperative model in which supporters and builders shape priorities and policy.\src{GameCult front page}{https://gamecult.org/}
|
||||
|
||||
Bifrost is the key evidence that this is not merely rhetoric. Its README describes it as the member, governance, labor, and public-process platform connecting projects, users, patrons, contributors, motions, ledgers, work requests, reward pressure, public receipts, and operational decisions.\src{GameCult/Bifrost README}{https://github.com/GameCult/Bifrost/blob/main/README.md} The jurisdiction map describes the core economic loop: users, patrons, members, agents, or contributors identify work; the community expresses priority; reward pressure rises; contributors claim work; maintainers accept artifacts; and Bifrost credits the contributor and records reward allocation.\src{Bifrost jurisdiction map}{https://github.com/GameCult/Bifrost/blob/main/docs/jurisdiction-map.md}
|
||||
|
||||
\section*{Bottom line}
|
||||
\addcontentsline{toc}{section}{Bottom line}
|
||||
|
||||
The investable object is not the current game portfolio. The investable object is a \term{human/agent work institution} in formation. This should be sold internally as a high-risk, high-asymmetry category-creation bet: if Epiphany works, the team can scale agent labor; if Bifrost works, that labor becomes governed economic activity; if CultMesh works, the network can become global and composable.
|
||||
|
||||
\chapter{Primer for Nontechnical Partners}
|
||||
|
||||
\section{What is an AI agent?}
|
||||
|
||||
A modern AI agent is a language model connected to tools. Instead of simply answering a question, it can inspect files, run commands, search documents, write code, create issues, comment on pull requests, or communicate with other agents. The current generation is powerful, but fragile. Agents often lose context, repeat work, hallucinate explanations, make plausible local changes while the global design has drifted, and lack a reliable institutional memory.
|
||||
|
||||
The current state of the market is therefore not solved by adding more prompts. The hard problem is \term{coordination}: what does the agent believe, what evidence changed that belief, who gave it authority, what part of the work is private, what can be published, who verifies output, who gets credit, and how does the system remember across days or months?
|
||||
|
||||
\section{What is different about GameCult?}
|
||||
|
||||
GameCult appears to be building an organization where the agents themselves become part of the operating structure. Each repo can have a \term{Face}, a public/social agent identity. VoidBot reads Discord and repo context. Epiphany externalizes typed project memory. CultMesh supplies distributed typed state. Bifrost turns requests, consensus, work, reviews, receipts, and rewards into governed records.
|
||||
|
||||
In ordinary terms: instead of treating AI as a chatbot bolted onto a team, GameCult is trying to make AI agents into \term{members of a governed production network}. The mythology around the Colossus is unusual, but the underlying engineering goal is legible: create durable, inspectable, reward-bearing collective cognition.
|
||||
|
||||
\section{What is the state of the art today?}
|
||||
|
||||
For a lay partner, today's landscape has four imperfect pieces:
|
||||
|
||||
\begin{enumerate}
|
||||
\item \term{AI coding assistants} help individual developers write code faster, but usually do not own durable organizational memory or governance.
|
||||
\item \term{Autonomous coding agents} can attempt larger tasks, but often struggle with context, verification, and safe authority boundaries.
|
||||
\item \term{Freelance and work platforms} match buyers to human labor, but rarely convert small ideas, critique, testing, or governance participation into durable economic credit.
|
||||
\item \term{DAOs and web3 governance systems} can coordinate money and votes, but often lack robust real-world work execution, review discipline, legal compliance, and human-support infrastructure.
|
||||
\end{enumerate}
|
||||
|
||||
GameCult's proposed synthesis is different: \term{AI-native work governance}. The system is not only supposed to route tasks. It is supposed to let humans and agents cooperate, remember, verify, credit, reward, and reinvest in the people who make the network valuable.
|
||||
|
||||
\section{Why housing and social support matter}
|
||||
|
||||
Housing and social support are not off-thesis. They are human uptime infrastructure. The ILO's 2024-26 social protection report states that 3.8 billion people remain entirely unprotected from life challenges and climate impacts, while social protection supports human development, productive investment, and livelihood diversification.\src{ILO World Social Protection Report 2024-26}{https://www.ilo.org/publications/flagship-reports/world-social-protection-report-2024-26-universal-social-protection-climate} The UN's 2024 SDG 11 report states that 1.12 billion people lived in slums or informal settlements in 2022 and that nearly 70 percent of the global population is projected to live in cities by 2050, making affordable housing and essential services imperative.\src{UN SDG 11 report 2024}{https://unstats.un.org/sdgs/report/2024/Goal-11/}
|
||||
|
||||
For GameCult, the business logic is that unstable people cannot reliably contribute to a global knowledge network. If Bifrost can make contribution legible and Epiphany can amplify output, then housing, internet access, education, and support benefits become investments in productive capacity.
|
||||
|
||||
\chapter{The GameCult Stack}
|
||||
|
||||
\section{Epiphany: persistent agent cognition}
|
||||
|
||||
Epiphany is the control-plane thesis. Its README says Epiphany is an opinionated fork of Codex built around the demand that the model must model the thing it is changing. It moves important state out of transcript fog and into typed, inspectable surfaces such as maps, evidence, retrieval state, graph/frontier state, churn pressure, and compact reflections.\src{GameCult/Epiphany README}{https://github.com/GameCult/Epiphany/blob/main/README.md}
|
||||
|
||||
The implementation plan lists durable Epiphany state, bounded prompt integration, semantic retrieval, explicit indexing, typed mutation, distillation, proposal, verifier-backed promotion, role launch/result/accept, reorientation, CRRC, job bindings, runtime-spine documents, CultMesh integration, and operator surfaces.\src{Epiphany fork implementation plan}{https://github.com/GameCult/Epiphany/blob/main/notes/epiphany-fork-implementation-plan.md}
|
||||
|
||||
\subsection{Why it matters}
|
||||
|
||||
The failure mode of current agents is not that they cannot write code. It is that they cannot reliably preserve global coherence. Epiphany's product wedge is therefore not simply faster coding. It is persistent organizational cognition for agents.
|
||||
|
||||
\section{VoidBot and Faces: the social interface}
|
||||
|
||||
VoidBot is the social and Discord-native interface into the swarm. It can answer from archived Discord history, indexed GameCult repos, and Aetheria lore, and then hand deeper work off to Codex. It supports real Discord replies, semantic retrieval, source/lore indexing, interaction memory, and Codex handoff flows.\src{GameCult/VoidBot README}{https://github.com/GameCult/VoidBot/blob/main/README.md}
|
||||
|
||||
This matters because work does not originate only in tickets. It originates in chat, argument, taste, frustration, social trust, and repeated community pressure. VoidBot and repo Faces are the layer where that signal becomes visible.
|
||||
|
||||
\section{CultMesh: typed distributed state}
|
||||
|
||||
CultMesh is documented as the distributed realtime database and simulation-consensus layer for GameCult projects. It sits over CultCache for typed documents and local persistence, and over CultNet for transport and schema-v0 messages.\src{CultMesh README}{https://github.com/GameCult/CultLib/blob/main/src/GameCult.Mesh/README.md}
|
||||
|
||||
CultMesh's Verse model is important. A Verse is described as a rule-bearing consensus graph with authority models, compatibility/rules hashes, discovery endpoints, authority runtimes, parent Verse support, peer exchange, and authority leases.\src{CultMesh Verses documentation}{https://github.com/GameCult/CultLib/blob/main/src/GameCult.Mesh/docs/verses.md}
|
||||
|
||||
For a lay audience, CultMesh is the connective tissue. It makes it possible for multiple local systems to share typed state without pretending that all data has the same privacy, authority, or governance status.
|
||||
|
||||
\section{Bifrost: governance, work, rewards, receipts}
|
||||
|
||||
Bifrost is the economic center. Its README says it is the planned member, governance, labor, and public-process platform under the Yggdrasil infrastructure umbrella. It connects projects, users, patrons, contributors, motions, ledgers, work requests, reward pressure, public receipts, and operational decisions.\src{Bifrost README}{https://github.com/GameCult/Bifrost/blob/main/README.md}
|
||||
|
||||
The repository already contains an alpha foundation slice: ASP.NET Core app, PostgreSQL-backed EF Core model, GitHub OAuth sign-in, invite/approval membership gating, roles, a work board, motions, ledgers, GitHub webhook ingestion, bridge tooling for agent-owned GitHub draft PRs and Discord posts, CultCache-backed governance topics, CultCache/CultNet-backed agent intake, Docker smoke tests, and xUnit tests.\src{Bifrost README status section}{https://github.com/GameCult/Bifrost/blob/main/README.md}
|
||||
|
||||
\subsection{Bifrost's labor model}
|
||||
|
||||
The full implementation strategy aligns Bifrost with a labor platform concept: contributor history, governance, work priority, reward pressure, contribution points, patron points, decay, and revenue share. It states that accepted work becomes contributor credit plus reward allocation, and that contribution points, patron points, decay, and revenue share should be first-class product systems rather than spreadsheet afterthoughts.\src{Bifrost full implementation strategy}{https://github.com/GameCult/Bifrost/blob/main/docs/full-implementation-strategy.md}
|
||||
|
||||
\section{Heimdall: identity and capability layer}
|
||||
|
||||
Bifrost's jurisdiction map says Heimdall owns OAuth provider flows, account linking, credential custody, signed identity and capability claims, grants, consent, revocation, and capability evaluation. Bifrost consumes Heimdall claims and governs public work crossings; Heimdall decides who may cross under which grant.\src{Bifrost jurisdiction map, ownership boundaries}{https://github.com/GameCult/Bifrost/blob/main/docs/jurisdiction-map.md}
|
||||
|
||||
This split matters. A global labor and payout network cannot treat identity as an afterthought. It needs auditable human and agent identity, permission, consent, and revocation.
|
||||
|
||||
\section{Proof workloads: Fensalir, Mimir, AquaSynth, Ghostlight, Aetheria}
|
||||
|
||||
GameCult's surrounding projects are not random. They are stress tests for the stack.
|
||||
|
||||
\begin{itemize}
|
||||
\item \term{Fensalir} tests engine/runtime/rendering/audio field machinery. Its README describes a native C\# runtime and field engine with D3D12 frame ownership, hot reload, PCM audio, debug UI, volumetric fields, fractal geometry, temporal evidence, and synth-backed sound.\src{Fensalir README}{https://github.com/GameCult/Fensalir/blob/main/README.md}
|
||||
\item \term{Mimir} attempts to make a room computable by synchronizing cameras, microphones, speakers, loopbacks, and network feeds into a coherent OBS-facing program surface.\src{Mimir README}{https://github.com/GameCult/Mimir/blob/main/README.md}
|
||||
\item \term{AquaSynth} is a synth and vocal-tract experiment. Its IPA roadmap describes a path from IPA text to phonetic tokens, articulatory gesture plans, morphology-specific tract/excitation curves, Faust DSP, and nonhuman speech/song/chant rendering.\src{AquaSynth IPA vocal tract roadmap}{https://github.com/GameCult/AquaSynth/blob/main/docs/ipa-vocal-tract-roadmap.md}
|
||||
\item \term{Ghostlight} explores socially persistent generative agents and character-driven generation.\src{Ghostlight README}{https://github.com/GameCult/Ghostlight/blob/main/README.md}
|
||||
\end{itemize}
|
||||
|
||||
These projects create the internal pressure needed to prove that Epiphany, Bifrost, and CultMesh can handle real complexity.
|
||||
|
||||
\chapter{Diligence Findings}
|
||||
|
||||
\section{Verified from public materials}
|
||||
|
||||
\begin{longtable}{P{0.28\linewidth}P{0.63\linewidth}}
|
||||
\toprule
|
||||
\textbf{Area} & \textbf{Finding} \\
|
||||
\midrule
|
||||
GameCult mission & Public front page emphasizes open development, legible incentives, bounty-driven contribution, contributor standing, and cooperative participation. \\
|
||||
Bifrost & Repo contains a working alpha foundation slice: web app, database model, GitHub auth, membership gating, work board, motions, ledgers, GitHub webhooks, bridge tooling, CultCache topics, and agent intake. \\
|
||||
Bifrost economics & Documentation defines contributor points, patron points, decay, voting weight, revenue-share calculation, and payout proposal batches. \\
|
||||
Bifrost jurisdiction & Bifrost owns governed public crossings: GitHub/Discord/CultNet/CultCache work transport, receipts, priority, and audit. \\
|
||||
Epiphany & Public docs show a persistent typed-state agent control plane with role separation, verification, promotion, reorientation, runtime-spine, and CultMesh direction. \\
|
||||
CultMesh & Public docs define distributed typed state, Verse discovery, peer exchange, authority leases, shard logs, replica catch-up, and witness consensus. \\
|
||||
Surrounding projects & Fensalir, Mimir, AquaSynth, Ghostlight, and related repos serve as complex proof workloads. \\
|
||||
\bottomrule
|
||||
\end{longtable}
|
||||
|
||||
\section{Not yet verified}
|
||||
|
||||
\begin{itemize}
|
||||
\item Actual nonprofit legal status, entity form, bylaws, board structure, and whether there is an affiliated for-profit entity.
|
||||
\item Founder identity, IP assignment, contributor agreements, and cap/economic rights table if any.
|
||||
\item Real usage, revenue, donations, grants, or community scale beyond public GitHub/site evidence.
|
||||
\item Private Discord activity and actual agent swarm throughput.
|
||||
\item Cost per useful agent artifact, accepted output rate, and human review burden.
|
||||
\item Compliance posture for payments, rewards, revenue share, housing, stipends, cross-border support, KYC/AML, tax, and labor classification.
|
||||
\item Third-party license exposure across repos and model-provider terms.
|
||||
\end{itemize}
|
||||
|
||||
\section{Current diligence rating}
|
||||
|
||||
\begin{longtable}{P{0.3\linewidth}P{0.18\linewidth}P{0.43\linewidth}}
|
||||
\toprule
|
||||
\textbf{Dimension} & \textbf{Rating} & \textbf{Comment} \\
|
||||
\midrule
|
||||
Technical ambition & Very high & Evidence supports a coherent and unusually broad stack. \\
|
||||
Product maturity & Early & Bifrost is not public alpha; Epiphany remains highly technical and tied to Codex plumbing. \\
|
||||
Commercial traction & Unproven & No confirmed revenue or external design-partner adoption. \\
|
||||
Moat potential & High if it works & Durable state, governance ledgers, contribution history, and network knowledge can compound. \\
|
||||
Legal complexity & Extreme & Nonprofit structure, rewards, housing, social support, and agent labor require careful design. \\
|
||||
Founder dependency & High & Architecture appears founder-led and culturally specific. \\
|
||||
Asymmetric upside & Very high & If Bifrost/Epiphany/CultMesh scale, the ceiling exceeds normal devtool outcomes. \\
|
||||
\bottomrule
|
||||
\end{longtable}
|
||||
|
||||
\chapter{Economic Context and Market Map}
|
||||
|
||||
\section{The size of the opportunity}
|
||||
|
||||
The World Bank tracks global GDP in current US dollars through 2024, and the global economy is measured in the \$100T+ range.\src{World Bank GDP current US\$ - World}{https://data.worldbank.org/indicator/NY.GDP.MKTP.CD?locations=1W} The narrow AI developer-tool market is already large, but the broader target is labor. If GameCult builds a system that increases, routes, verifies, and rewards intellectual contribution, the addressable market becomes a portion of global knowledge work, creative work, research work, software work, and eventually social-support/housing flows.
|
||||
|
||||
\section{Why current labor markets miss value}
|
||||
|
||||
Existing global labor platforms largely require a worker to present a coherent resume, bid for a job, perform a defined task, and deliver a recognizable artifact. That misses many useful signals:
|
||||
|
||||
\begin{itemize}
|
||||
\item a good idea from someone without credentials,
|
||||
\item a useful bug report,
|
||||
\item local cultural knowledge,
|
||||
\item translation, testing, critique, and moderation,
|
||||
\item design taste and aesthetic judgment,
|
||||
\item a governance objection that prevents wasted work,
|
||||
\item agent steering or review,
|
||||
\item evidence that a proposed direction is wrong.
|
||||
\end{itemize}
|
||||
|
||||
Bifrost can make these signals legible. Epiphany can amplify them into artifacts. CultMesh can let the knowledge travel without collapsing private state into public truth.
|
||||
|
||||
\section{Why social security and housing are in scope}
|
||||
|
||||
The ILO frames social protection as an enabler of productive investment, livelihood diversification, human development, and resilience.\src{ILO social protection report key messages}{https://www.ilo.org/publications/flagship-reports/world-social-protection-report-2024-26-universal-social-protection-climate} The UN housing data shows that the lack of adequate housing remains a massive global bottleneck.\src{UN SDG 11 housing and slum data}{https://unstats.un.org/sdgs/report/2024/Goal-11/}
|
||||
|
||||
If Bifrost can identify promising contributors and route them into agent-amplified work, then housing and support are not philanthropy alone. They are investments in contributor uptime and economic output.
|
||||
|
||||
\chapter{The Labor Output Multiplier}
|
||||
|
||||
\section{Model}
|
||||
|
||||
The central economic claim is that the network increases output, especially for under-capitalized contributors.
|
||||
|
||||
\noteBox{\textbf{Output model.} Annual network output = active contributors $\times$ baseline local productive capacity $\times$ stability multiplier $\times$ agent leverage multiplier $\times$ CultMesh knowledge multiplier $\times$ global market-access multiplier.}
|
||||
|
||||
\begin{itemize}
|
||||
\item \term{Stability multiplier}: housing, internet, food, health support, reduced survival volatility.
|
||||
\item \term{Agent leverage multiplier}: Epiphany turns partial intent into tasks, artifacts, PRs, research, tests, and summaries.
|
||||
\item \term{Knowledge multiplier}: CultMesh lets useful dreams, failed paths, evidence, and design pressure circulate.
|
||||
\item \term{Market-access multiplier}: Bifrost connects contributors to global demand, patrons, projects, and review surfaces.
|
||||
\end{itemize}
|
||||
|
||||
\section{Illustrative annual output scenarios}
|
||||
|
||||
\begin{longtable}{P{0.23\linewidth}P{0.2\linewidth}P{0.25\linewidth}P{0.22\linewidth}}
|
||||
\toprule
|
||||
\textbf{Scenario} & \textbf{Active contributors} & \textbf{Annual network output per contributor} & \textbf{Annual gross work/output flow} \\
|
||||
\midrule
|
||||
Regional proof & 100,000 & \$10,000 & \$1B \\
|
||||
Serious contributor network & 1M & \$20,000 & \$20B \\
|
||||
Emerging-market labor rail & 10M & \$30,000 & \$300B \\
|
||||
Major intellectual labor network & 50M & \$50,000 & \$2.5T \\
|
||||
Global labor institution & 100M & \$75,000 & \$7.5T \\
|
||||
Civilizational-scale network & 250M & \$100,000 & \$25T \\
|
||||
Full Colossus outcome & 500M & \$100,000-\$150,000 & \$50T-\$75T \\
|
||||
\bottomrule
|
||||
\end{longtable}
|
||||
|
||||
These are not forecasts. They are boundary scenarios. The important point is that global aggregate flow can exceed the equity value of any one operating entity by one or two orders of magnitude.
|
||||
|
||||
\section{Aggregate trading volume}
|
||||
|
||||
A mature Bifrost network would not route only paid work. It could route:
|
||||
|
||||
\begin{itemize}
|
||||
\item paid work and bounty/reward allocations,
|
||||
\item patron and member priority boosts,
|
||||
\item housing and rent support flows,
|
||||
\item benefit and emergency grant disbursements,
|
||||
\item project revenue-share flows,
|
||||
\item internal services, education, and tooling,
|
||||
\item contributor-to-contributor service exchange,
|
||||
\item governance-directed capital allocation.
|
||||
\end{itemize}
|
||||
|
||||
Therefore annual aggregate trading volume can be much larger than direct labor output. A network doing \$10T/year in labor output could plausibly move \$15T-\$30T/year once housing, benefits, internal capital allocation, and redistribution flows are included.
|
||||
|
||||
\chapter{Valuation and Network Capitalization}
|
||||
|
||||
\section{Separate the numbers}
|
||||
|
||||
Partners should separate three concepts:
|
||||
|
||||
\begin{enumerate}
|
||||
\item \term{Operating entity value}: the value of any GameCult OpCo, service company, or software subsidiary.
|
||||
\item \term{Network capitalization}: the value of treasuries, reserves, housing assets, contributor support funds, protocol claims, cooperative shares, or affiliated vehicles.
|
||||
\item \term{Annual gross flow}: the total work, reward, housing, benefit, support, and capital allocation moving through the network.
|
||||
\end{enumerate}
|
||||
|
||||
A \$1T outcome may be an extreme operating entity value. It is not a hard ceiling on annual network flow or network capitalization.
|
||||
|
||||
\section{Illustrative network capitalization scenarios}
|
||||
|
||||
\begin{longtable}{P{0.23\linewidth}P{0.23\linewidth}P{0.23\linewidth}P{0.22\linewidth}}
|
||||
\toprule
|
||||
\textbf{Annual gross transaction volume} & \textbf{Net capture / reserve / service rate} & \textbf{Annual capture} & \textbf{Plausible network capitalization} \\
|
||||
\midrule
|
||||
\$100B & 3\%-8\% & \$3B-\$8B & \$30B-\$150B \\
|
||||
\$1T & 2\%-6\% & \$20B-\$60B & \$200B-\$1T \\
|
||||
\$5T & 1.5\%-5\% & \$75B-\$250B & \$750B-\$5T \\
|
||||
\$10T & 1\%-4\% & \$100B-\$400B & \$1T-\$10T \\
|
||||
\$25T & 0.75\%-3\% & \$188B-\$750B & \$3T-\$20T \\
|
||||
\$50T & 0.5\%-3\% & \$250B-\$1.5T & \$5T-\$50T \\
|
||||
\bottomrule
|
||||
\end{longtable}
|
||||
|
||||
The highest cases require the network to become more than a marketplace. It must become a trusted allocation layer for work, housing, benefits, identity, and reputation.
|
||||
|
||||
\section{Equity-like value if nonprofit}
|
||||
|
||||
If GameCult is a nonprofit, ordinary equity ownership may be impossible or inappropriate. The capital return may need to come from:
|
||||
|
||||
\begin{itemize}
|
||||
\item an affiliated taxable service company,
|
||||
\item a public benefit corporation subsidiary,
|
||||
\item a recoverable grant or mission-related loan,
|
||||
\item a revenue participation agreement with a commercial services arm,
|
||||
\item a licensed enterprise distribution entity,
|
||||
\item impact-return structures tied to verified network revenue rather than control of the nonprofit.
|
||||
\end{itemize}
|
||||
|
||||
The IRS states that to be tax-exempt under section 501(c)(3), an organization must be organized and operated exclusively for exempt purposes and none of its earnings may inure to any private shareholder or individual; it also must not operate for private interests.\src{IRS exemption requirements for 501(c)(3) organizations}{https://www.irs.gov/charities-non-profits/charitable-organizations/exemption-requirements-501c3-organizations} Therefore any capital plan must avoid private inurement, excessive private benefit, or investor control inconsistent with the nonprofit's mission.
|
||||
|
||||
\chapter{Scaling Strategy}
|
||||
|
||||
\section{Strategic goal}
|
||||
|
||||
The immediate goal is not to launch every part of the Colossus at once. The goal is to prove a repeatable loop:
|
||||
|
||||
\begin{center}
|
||||
\begin{tabularx}{0.95\linewidth}{Y}
|
||||
Human or agent identifies work $\rightarrow$ Bifrost records discussion/priority $\rightarrow$ Epiphany decomposes and executes $\rightarrow$ Maintainers review artifacts $\rightarrow$ Bifrost records receipts and credit $\rightarrow$ Rewards/support flow back into contributors $\rightarrow$ Contributors become more capable.\\
|
||||
\end{tabularx}
|
||||
\end{center}
|
||||
|
||||
\section{Phase 1: Bifrost-first private alpha}
|
||||
|
||||
Within 90-120 days, Bifrost should be the canonical surface for governed external swarm tasks. Discord may mirror. VoidBot may observe. Epiphany may execute. But Bifrost owns topics, work items, dispatch packets, receipts, credit, and reward pressure.
|
||||
|
||||
Milestones:
|
||||
|
||||
\begin{itemize}
|
||||
\item Bifrost deployed privately on Yggdrasil or equivalent infrastructure.
|
||||
\item GitHub sign-in and member gating live.
|
||||
\item Governance topics and work items used for all external swarm tasks.
|
||||
\item Agent transport requests visible inside Bifrost.
|
||||
\item Receipts attached to originating topics/work items.
|
||||
\end{itemize}
|
||||
|
||||
\section{Phase 2: Public proof sprint}
|
||||
|
||||
Run a compute-subsidized public proof campaign, but route every task through Bifrost. The offer should be simple: submit a stuck repo, tool, documentation problem, research task, or prototype request; the swarm will attempt selected tasks and publish what happened.
|
||||
|
||||
Every run should record:
|
||||
|
||||
\begin{itemize}
|
||||
\item scope and consent,
|
||||
\item Bifrost topic/work item,
|
||||
\item agent roles and model spend,
|
||||
\item human review hours,
|
||||
\item artifacts produced,
|
||||
\item accepted/rejected outcome,
|
||||
\item lessons added to memory,
|
||||
\item public case-study permission.
|
||||
\end{itemize}
|
||||
|
||||
\section{Phase 3: Design partners}
|
||||
|
||||
Convert proof-sprint participants into 10-30 design partners. Their job is to prove that Epiphany/Bifrost works on external repos and organizations without requiring every user to internalize GameCult's mythology.
|
||||
|
||||
Core metric: \term{accepted useful work per human supervisor hour}.
|
||||
|
||||
\section{Phase 4: Bifrost Fellows}
|
||||
|
||||
Launch a 12-month fellows program with transparent support rules. The purpose is to measure whether stability plus agent access increases output.
|
||||
|
||||
Illustrative pilot:
|
||||
|
||||
\begin{itemize}
|
||||
\item 100 fellows across 3-5 low-cost regions.
|
||||
\item \$300-\$800/month in total support per fellow.
|
||||
\item Epiphany access, mentor/reviewer support, contribution board, and Bifrost ledger.
|
||||
\item Monthly output measurement and cohort reporting.
|
||||
\end{itemize}
|
||||
|
||||
\section{Phase 5: Housing/support pilots}
|
||||
|
||||
Housing should not sit directly on the main nonprofit balance sheet without counsel. Use sidecars, local partners, community land trust structures, or housing SPVs. Bifrost can record eligibility, contribution history, governance decisions, and support flows, but real estate risk should be separated from the software/governance layer.
|
||||
|
||||
\chapter{Investment / Capital Structure for a Nonprofit Ecosystem}
|
||||
|
||||
\section{Why ordinary VC terms do not map cleanly}
|
||||
|
||||
If GameCult is a nonprofit, there may be no equity, no common stock, no ordinary board seat for economic investors, and no conventional exit. A partner memo must therefore avoid pretending that a normal Series Seed term sheet can simply be dropped on the organization.
|
||||
|
||||
Instead, we should negotiate a \term{capital compact}: a mission-aligned agreement that funds the work, protects the founder's nonprofit/social mission, and gives the investor continued funding discretion, information rights, audit rights, and governance visibility.
|
||||
|
||||
\section{Possible structures}
|
||||
|
||||
\begin{longtable}{P{0.25\linewidth}P{0.34\linewidth}P{0.31\linewidth}}
|
||||
\toprule
|
||||
\textbf{Structure} & \textbf{Use case} & \textbf{Investor economics} \\
|
||||
\midrule
|
||||
Restricted grant & Pure mission funding, no return expectation & Reputation, impact, future relationship; no direct financial return \\
|
||||
Recoverable grant & Capital returns only if revenue/surplus occurs & Principal recovery and capped surplus participation, if legally permissible \\
|
||||
Program-related or mission-related investment & Foundation/impact-capital structure & Low-interest loan, recoverable capital, or mission-aligned note \\
|
||||
Revenue participation agreement & Commercial activity exists but equity is unsuitable & Percentage of approved commercial revenue until cap is reached \\
|
||||
For-profit subsidiary / PBC & Enterprise Epiphany/Bifrost services need commercial scaling & Investor buys equity in subsidiary; nonprofit retains mission/possibly IP control \\
|
||||
Service company license & Nonprofit owns core mission/IP; affiliate sells enterprise services & Investor participates in affiliate economics \\
|
||||
Housing SPV & Real estate/support pilots need separate risk pool & Asset-backed returns or impact returns through sidecar \\
|
||||
\bottomrule
|
||||
\end{longtable}
|
||||
|
||||
\section{Translation of board rights}
|
||||
|
||||
A conventional board member right should translate into something like:
|
||||
|
||||
\begin{itemize}
|
||||
\item \term{Capital Steward Observer}: non-voting observer on a Scaling Council or Finance/Infrastructure Committee.
|
||||
\item \term{Tranche Release Committee}: investor approval required for subsequent funding tranches.
|
||||
\item \term{Use-of-Proceeds Consent}: investor consent for material deviations from the approved plan.
|
||||
\item \term{Audit and Reporting Rights}: monthly metrics, ledger access, compute spend, and legal/security reporting.
|
||||
\item \term{Mission-Safe Protective Rights}: veto over investor-funded tokens, payout systems, housing obligations, and unreviewed revenue-share instruments, without control over ordinary nonprofit mission decisions.
|
||||
\end{itemize}
|
||||
|
||||
This protects capital without turning the investor into a de facto controller of the nonprofit.
|
||||
|
||||
\chapter{Founder-Aligned Agreement Draft}
|
||||
|
||||
\section{Founder receives}
|
||||
|
||||
\begin{itemize}
|
||||
\item Mission protection: investor acknowledges that GameCult is building a nonprofit/cooperative human/agent labor network, not merely a conventional SaaS company.
|
||||
\item Product/doctrine autonomy: founder remains the principal technical and cultural steward of Epiphany, Bifrost, CultMesh integration, and the Colossus model.
|
||||
\item Open/public-build protection: investor will not require abandonment of open/source-available culture or public proof reporting.
|
||||
\item Social-uplift authorization: housing, contributor support, education, and benefits pilots are permitted when legally structured and measured.
|
||||
\item No forced for-profit conversion: any for-profit affiliate must preserve nonprofit mission control and avoid private inurement.
|
||||
\end{itemize}
|
||||
|
||||
\section{Investor receives}
|
||||
|
||||
\begin{itemize}
|
||||
\item Tranche control tied to measurable scaling milestones.
|
||||
\item Capital Steward Observer role in a Scaling Council, Finance Committee, or equivalent governance body.
|
||||
\item Monthly and quarterly reporting rights.
|
||||
\item Audit rights for investor-funded compute, Bifrost ledgers, and public proof campaigns.
|
||||
\item Protective consent rights over unreviewed payout, token, revenue-share, housing, or benefit instruments.
|
||||
\item Right to invest in or finance approved commercial affiliates, service companies, or housing SPVs if created.
|
||||
\end{itemize}
|
||||
|
||||
\section{Core covenants}
|
||||
|
||||
\begin{enumerate}
|
||||
\item \term{Bifrost-first covenant.} All external swarm tasks, public proof runs, design-partner tasks, and contributor reward flows must be represented in Bifrost as topics, work items, dispatches, receipts, completion artifacts, or ledger entries.
|
||||
\item \term{No shadow governance.} Discord, VoidBot, repo Faces, and ad hoc scripts may not become durable governance/work/reward authorities.
|
||||
\item \term{Compute accountability.} Model spend must be logged against tasks, agents, outcomes, and accepted artifacts.
|
||||
\item \term{Contributor-output measurement.} The organization must measure baseline output, support received, agent leverage, accepted artifacts, rewards, and retention.
|
||||
\item \term{Safety gates.} No autonomous external write access, private-data export, direct payout, revenue-share instrument, or housing obligation without approved policy and counsel review.
|
||||
\item \term{Legal gates.} Securities, labor, tax, KYC/AML, data protection, nonprofit/private-benefit, housing, and cross-border support analysis must precede live global programs.
|
||||
\end{enumerate}
|
||||
|
||||
\section{Milestone tranches}
|
||||
|
||||
\subsection{Tranche 1: formation, diligence, and private build}
|
||||
|
||||
Release after:
|
||||
|
||||
\begin{itemize}
|
||||
\item Nonprofit/entity status verified.
|
||||
\item IP assignment or licensing path documented.
|
||||
\item Contributor/license audit started.
|
||||
\item Bifrost private alpha plan approved.
|
||||
\item Compute budget and public proof plan approved.
|
||||
\end{itemize}
|
||||
|
||||
\subsection{Tranche 2: Bifrost alpha and public proof}
|
||||
|
||||
Release after:
|
||||
|
||||
\begin{itemize}
|
||||
\item Bifrost private alpha deployed.
|
||||
\item At least 50 consented external/public proof tasks routed through Bifrost.
|
||||
\item Epiphany usable on at least 3 external or semi-external repos.
|
||||
\item Dashboard reports cost per accepted artifact and human review load.
|
||||
\end{itemize}
|
||||
|
||||
\subsection{Tranche 3: design partners and ledger economics}
|
||||
|
||||
Release after:
|
||||
|
||||
\begin{itemize}
|
||||
\item 10+ design partners or 3+ paid/mission-funded pilots.
|
||||
\item 100+ external proof tasks completed or terminally failed with artifacts.
|
||||
\item Contribution ledger alpha live.
|
||||
\item Payout/support model counsel-reviewed.
|
||||
\item CultMesh trusted/local Verse prototype or public-dream prototype live.
|
||||
\end{itemize}
|
||||
|
||||
\chapter{Diligence Request List}
|
||||
|
||||
\section{Corporate and nonprofit}
|
||||
|
||||
\begin{itemize}
|
||||
\item Legal entity documents, bylaws, nonprofit filings, tax-exempt status if any.
|
||||
\item Board/trustee composition and governance rights.
|
||||
\item Founder authority and any member/cooperative rights.
|
||||
\item Any affiliate entities, fiscal sponsors, foundations, or service companies.
|
||||
\end{itemize}
|
||||
|
||||
\section{IP and licensing}
|
||||
|
||||
\begin{itemize}
|
||||
\item Repo-by-repo license table.
|
||||
\item Founder IP assignment or license.
|
||||
\item Contributor agreements and contributor list.
|
||||
\item Third-party code and model-output policy.
|
||||
\item Commercial license strategy for source-available components.
|
||||
\end{itemize}
|
||||
|
||||
\section{Technical}
|
||||
|
||||
\begin{itemize}
|
||||
\item Live Epiphany demo on a fresh repo.
|
||||
\item Bifrost demo with work item, topic, agent transport request, receipt, and ledger entry.
|
||||
\item CultMesh demo or status report for Verses and typed document sync.
|
||||
\item VoidBot/Discord swarm demo.
|
||||
\item Compute spend, task output, and accepted artifact metrics.
|
||||
\item Security model for secrets, write permissions, and public/private exports.
|
||||
\end{itemize}
|
||||
|
||||
\section{Economic and legal}
|
||||
|
||||
\begin{itemize}
|
||||
\item Existing revenue/donations/grants/support.
|
||||
\item Legal theory for rewards, points, revenue share, payouts, and support benefits.
|
||||
\item Worker/contributor classification plan.
|
||||
\item KYC/AML/sanctions plan for cross-border payouts/support.
|
||||
\item Housing/support pilot structure.
|
||||
\item Data protection and privacy policy.
|
||||
\end{itemize}
|
||||
|
||||
\chapter{Risks and Controls}
|
||||
|
||||
\section{Primary risks}
|
||||
|
||||
\begin{longtable}{P{0.26\linewidth}P{0.33\linewidth}P{0.31\linewidth}}
|
||||
\toprule
|
||||
\textbf{Risk} & \textbf{Description} & \textbf{Control} \\
|
||||
\midrule
|
||||
Nonprofit/private benefit & Investor economics may conflict with nonprofit law. & Use recoverable grants, mission loans, commercial affiliates, or counsel-reviewed structures. \\
|
||||
Scope explosion & GameCult may keep expanding without product closure. & Tranches tied to Bifrost/Epiphany external proof. \\
|
||||
Agent noise & Swarm activity may produce volume without useful output. & Measure accepted artifact per human review hour. \\
|
||||
Compute burn & Model spend can become uncontrolled. & Budget caps and cost per artifact reporting. \\
|
||||
Governance capture & Bounties, points, and votes can be gamed. & Identity, anti-Sybil, audit, maintainer review, and appeal processes. \\
|
||||
Housing dependency & Support can become coercive. & Exit rights, portable records, independent review, no ideological conditions. \\
|
||||
Brand risk & ``Cult'' and Colossus language may alarm partners. & Keep mythos internally; externalize as contributor development and human/agent governance. \\
|
||||
Legal complexity & Payouts, revenue share, benefits, and cross-border support are regulated. & Legal gates before live scale. \\
|
||||
\bottomrule
|
||||
\end{longtable}
|
||||
|
||||
\section{Ethical red lines}
|
||||
|
||||
\begin{itemize}
|
||||
\item No housing or benefits conditioned on ideological conformity.
|
||||
\item No opaque agent-only reputation scoring.
|
||||
\item No punitive withdrawal of basic support for governance dissent.
|
||||
\item No debt bondage, company-town lock-in, or nonportable reputation.
|
||||
\item No public export of private worker/operator/agent context.
|
||||
\item No direct payout or revenue-share instrument without counsel review.
|
||||
\end{itemize}
|
||||
|
||||
\chapter{Partner Selling Narrative}
|
||||
|
||||
\section{The simple pitch}
|
||||
|
||||
GameCult has built an internal swarm of AI agents and humans that appears to produce extraordinary technical velocity. The hidden asset is not any one game or engine. The hidden asset is the operating system around that velocity: persistent memory, repo identities, governed work transport, contribution credit, rewards, and public receipts.
|
||||
|
||||
\section{Why now}
|
||||
|
||||
AI agents are improving quickly, but the market lacks a durable governance and work layer. Human labor markets are also failing to capture huge pools of underused global talent. GameCult's thesis sits at the intersection: it uses agents to amplify humans, Bifrost to govern and reward contribution, and CultMesh to let knowledge travel across a distributed network.
|
||||
|
||||
\section{Why this team}
|
||||
|
||||
The public repos show unusual depth across agents, governance, rendering, audio, distributed state, and social agent interfaces. Bifrost is not a slideware governance fantasy; it has a working alpha foundation. Epiphany is not merely a chatbot; it is a typed-state control-plane project. CultMesh is not just a slogan; it has Verse and authority documentation.
|
||||
|
||||
\section{Why us}
|
||||
|
||||
We can give the founder what she wants: capital to scale the Colossus without flattening the nonprofit/cooperative mission. In return, we get what we need: Bifrost-first scaling covenants, telemetry, legal gates, and the right to keep capital flowing only if the network becomes measurable, governed, and externally repeatable.
|
||||
|
||||
\chapter{References}
|
||||
|
||||
\begin{enumerate}[leftmargin=1.8em]
|
||||
\item \href{https://gamecult.org/}{GameCult front page}.
|
||||
\item \href{https://github.com/GameCult/Bifrost/blob/main/README.md}{GameCult/Bifrost README}.
|
||||
\item \href{https://github.com/GameCult/Bifrost/blob/main/docs/full-implementation-strategy.md}{Bifrost Full Implementation Strategy}.
|
||||
\item \href{https://github.com/GameCult/Bifrost/blob/main/docs/jurisdiction-map.md}{Bifrost Jurisdiction Map}.
|
||||
\item \href{https://github.com/GameCult/Bifrost/blob/main/docs/agent-transport.md}{Bifrost Agent Transport}.
|
||||
\item \href{https://github.com/GameCult/Epiphany/blob/main/README.md}{GameCult/Epiphany README}.
|
||||
\item \href{https://github.com/GameCult/Epiphany/blob/main/notes/epiphany-fork-implementation-plan.md}{Epiphany Fork Implementation Plan}.
|
||||
\item \href{https://github.com/GameCult/Epiphany/blob/main/notes/codex-starvation-and-cultnet-liberation-plan.md}{Codex Starvation and CultNet Liberation Plan}.
|
||||
\item \href{https://github.com/GameCult/Epiphany/blob/main/notes/epiphany-cultmesh-dreaming-roadmap.md}{Epiphany CultMesh Dreaming Roadmap}.
|
||||
\item \href{https://github.com/GameCult/CultLib/blob/main/src/GameCult.Mesh/README.md}{CultMesh README}.
|
||||
\item \href{https://github.com/GameCult/CultLib/blob/main/src/GameCult.Mesh/docs/verses.md}{CultMesh Verses Documentation}.
|
||||
\item \href{https://github.com/GameCult/VoidBot/blob/main/README.md}{VoidBot README}.
|
||||
\item \href{https://github.com/GameCult/Fensalir/blob/main/README.md}{Fensalir README}.
|
||||
\item \href{https://github.com/GameCult/Mimir/blob/main/README.md}{Mimir README}.
|
||||
\item \href{https://github.com/GameCult/AquaSynth/blob/main/docs/ipa-vocal-tract-roadmap.md}{AquaSynth IPA Vocal Tract Roadmap}.
|
||||
\item \href{https://github.com/GameCult/Ghostlight/blob/main/README.md}{Ghostlight README}.
|
||||
\item \href{https://data.worldbank.org/indicator/NY.GDP.MKTP.CD?locations=1W}{World Bank: GDP (current US\$) - World}.
|
||||
\item \href{https://www.ilo.org/publications/flagship-reports/world-social-protection-report-2024-26-universal-social-protection-climate}{ILO: World Social Protection Report 2024-26}.
|
||||
\item \href{https://unstats.un.org/sdgs/report/2024/Goal-11/}{United Nations: SDG 11 Report 2024}.
|
||||
\item \href{https://www.irs.gov/charities-non-profits/charitable-organizations/exemption-requirements-501c3-organizations}{IRS: Exemption Requirements for 501(c)(3) Organizations}.
|
||||
\item \href{https://nvca.org/model-legal-documents/}{NVCA Model Legal Documents}.
|
||||
\end{enumerate}
|
||||
|
||||
\appendix
|
||||
\chapter{Glossary}
|
||||
|
||||
\begin{description}[leftmargin=2.5cm,style=nextline]
|
||||
\item[Agent] An AI model connected to tools and instructions, able to perform tasks rather than only answer questions.
|
||||
\item[Bifrost] GameCult's governance, labor, work, reward, receipt, and public-process platform.
|
||||
\item[CultCache] Typed document storage layer used by GameCult projects.
|
||||
\item[CultMesh] Distributed typed-state and consensus substrate, organized around Verses.
|
||||
\item[CultNet] Transport/wire layer for moving typed documents and messages.
|
||||
\item[Dream] In Epiphany's roadmap, a public thought artifact that may influence another instance but is not adopted truth.
|
||||
\item[Epiphany] Persistent agent-control plane for typed memory, role separation, verification, reorientation, and execution.
|
||||
\item[Face] A repo or project agent's public/social identity, usually surfaced through Discord or an operator UI.
|
||||
\item[Heimdall] Planned identity, grants, consent, and capability authority.
|
||||
\item[Verse] A CultMesh rule-bearing consensus graph with its own authority model and compatibility rules.
|
||||
\item[Yggdrasil] GameCult's infrastructure umbrella/hosting context for internal services.
|
||||
\end{description}
|
||||
|
||||
\chapter{Compiler Notes}
|
||||
|
||||
This document is designed to compile with standard \LaTeX{} distributions such as MiKTeX or TeX Live. Recommended command:
|
||||
|
||||
\begin{verbatim}
|
||||
latexmk -pdf gamecult_integrated_dossier.tex
|
||||
\end{verbatim}
|
||||
|
||||
If latexmk is unavailable:
|
||||
|
||||
\begin{verbatim}
|
||||
pdflatex gamecult_integrated_dossier.tex
|
||||
pdflatex gamecult_integrated_dossier.tex
|
||||
\end{verbatim}
|
||||
|
||||
\end{document}
|
||||
Loading…
Reference in a new issue