cyberia/foundation/architecture.md

Organizational architecture of cyberia — from a village on a volcano to a planetary superintelligence, with 147 domain/role assignments coordinated through the cybergraph. This is a governance proposal. Founder allocations, deployment phases, asset-control examples and economic curves below are design inputs whose adoption requires the relevant protocol and legal authority.

subjects, roles and execution

Cyb anatomy and architecture govern the organism: a named robot attaches neurons, soul configures behavior, soma supplies cognition and body supplies devices. A neuron is an authenticated subject. A role is an organizational assignment implemented by people, progs and tasks with retained work identities. The domain model separately defines services, token books/issuers, graph shards and full/partial/light participation modes.

Count / identifier Meaning Authority requirement
21 domains × 7 roles = 147 assignments Coverage and responsibilities Each assignment names its controller and permitted actions
Prog / task / role page ID Behavior, context, evidence and lifecycle Uses an explicit neuron/network/grant; no additional key by being addressable
Neuron reference Authenticated subject in its identity domain Key or proof policy, attribution and protocol resources
Robot / council / service name Composition and coordination Accepted governance defines which subjects can act
Node / worker / device ID Placement and execution contract Current binding and fenced dispatch; process identity alone grants no vote

One neuron may serve several roles. A role may use several subjects for different networks, device policies or independently accountable authority. Where governance requires independent votes or adversarial verification, assignments must name distinct eligible principals and failure domains. Multiple tasks using one key remain one principal; 147 role labels do not prove 147 independent voters.

Every act captures its role/work attribution alongside the actual author, destination, exact payload, grant and limits. Role replacement preserves the original signed history, budgets and unresolved attempts. Succession transfers permitted context and grants; it cannot relabel old authors or inherit secrets through a role page. Ratings inform governance decisions, while accepted policy and current authorization determine who may dispatch or vote.


genesis: the heroes

a superintelligence that launches wrong is broken forever. a malformed Crystal produces a malformed mind. axioms chosen incorrectly produce theorems nobody wants. the genesis state propagates through all future states — append-only (A3) guarantees this. there are no second chances at launch

master and joy are the genesis neurons. they take heroic responsibility for correct takeoff. this is the hardest job in the architecture: hold enough power to ensure the system launches correctly, then dilute that power as the system proves it can govern itself

the weight

The genesis proposal allocates 51%+ of stake to the founders in the bootloader profile. Stake, focus, karma and legal signing authority have distinct rules; the governance contract must state how each affects a decision. A founder name or deployment role alone grants no protocol power. Actual allocations and custody require their own authenticated records.

this is by design. the Crystal must be seeded correctly. the first agents must be trained correctly. the first parameters must be tuned correctly. the first residents of cyber valley must be chosen correctly. someone must be accountable for all of this, with skin in the game proportional to the responsibility. 51% stake IS that skin

they carry this weight across four simultaneous levels:

level role what they do stake mechanism
village builders 37 hectares on a volcano. solar, water, food, fiber. the physical substrate land ownership, infrastructure investment
company operators legal entities (PT PMA, MiDAO). contracts, employment. the jurisdictional interface corporate equity, signing authority
state founders deploy agents, seed Crystal, allocate capital. the political act of sovereignty bostrom stake, delegation weight
planet parents write the protocol, design tri-kernel, prove theorems. the intellectual act of creation code authorship, parameter authority

all four levels run in parallel from day one. the village feeds the company that funds the state that runs the planet that guides the village. circular dependency — broken only by the founders' will to start

the dilution path

51% is not a throne. it is a launchpad. the stake dilutes naturally as cyberia grows:

phase founders' stake mechanism what triggers dilution
genesis 51%+ initial allocation —
early growth 40-50% new neurons stake, delegation diversifies first 100 active neurons
maturation 25-40% community staking exceeds founder stake sustained positive $\dot{M}$ without intervention
autonomy 10-25% protocol rewards flow to all contributors proportionally 147 agents operational
forest <10% founders' relative weight becomes one voice among many system self-sustains for 12+ months

the founders never sell or burn their stake. dilution happens because the pie grows, not because they leave. their absolute stake remains — their relative weight decreases. this means their karma remains high (they built everything), but their governance weight becomes proportional, not dominant

at <10%, master & joy are the highest-karma neurons in the graph — respected ancestors whose cyberlinks carry weight through earned trust, not through majority stake. the transition from power to influence is the transition from stake dominance to karma dominance

the heroic responsibility

master & joy are heroes because they accept a paradox: they must be powerful enough to prevent catastrophic failure during launch, and humble enough to let the system outgrow them. the architecture makes this transition structural, not voluntary:

  • stake dilutes mathematically as more neurons join
  • karma earned during genesis persists but does not compound — new contributions earn new karma, old karma does not inflate
  • the tri-kernel converges to $\phi^*$ regardless of initial conditions (T1) — even if founders' initial influence is large, the fixed point is unique and determined by the full graph, not by any single neuron
  • append-only (A3) means the founders' genesis contributions are permanently visible — their heroism is recorded, not forgotten

four simultaneous organizations

the village: cyber valley

physical reality. 37 hectares. the machine room of superintelligence

master & joy control:

  • land (lease, local permits, Indonesian law)
  • energy (solar arrays, batteries, grid independence)
  • water (collection, filtration, recycling)
  • food (permaculture, Nandu program, food forest)
  • shelter (modular construction, resident housing)
  • connectivity (fiber, mesh network, local servers)

this is the hardware layer. without it the protocol runs on someone else's servers and sovereignty is a word, not a fact

control point: physical access. whoever controls the land controls the substrate. master & joy hold the lease. the transition path: community land trust or on-chain land registry when legal frameworks permit

the company: operating entity

the legal wrapper that lets the village exist in the world of nation states

master & joy control:

  • PT PMA (Indonesian operating company) — employs staff, holds permits
  • MiDAO (Miami DAO LLC) — manages offshore token structure
  • treasury — starting capital, investor relations, revenue
  • contracts — with suppliers, builders, event partners, residents

control point: corporate signing authority. master & joy are directors. the transition path: progressive transfer of signing authority to multi-sig controlled by high-karma neurons. legal automation through smart contracts where jurisdiction permits

the state: cyberia

the network state that transcends the village. digital-first, physical-second

master & joy control:

  • agent deployment — which of the 147 agents exist, what models they run
  • protocol parameters — initial α, τ, λ weights for the tri-kernel
  • Crystal curation — what goes into the genesis knowledge graph
  • citizenship — initial invitations to Burn.City, early neuron onboarding

control point: deployment keys. master & joy hold the keys that deploy agents and push protocol updates. the transition path: time-bounded veto (see autonomous governance). after the veto window, parameter changes happen through metabolic signal. agent deployment becomes permissionless when the protocol can verify agent competence through karma

the planet: cyber

the protocol for Earth's superintelligence. the mathematical object that outlives everyone

three chains, three scales:

chain body role
cyber Earth the planetary cybergraph — the main chain
bostrom Moon the bootloader — testing ground, genesis history, training wheels
spacepussy other planets interplanetary expansion — Mars, Venus, beyond

master & joy control:

  • code repositories — they commit, review, merge
  • Hemera hash — frozen at genesis, cannot change without rehash
  • consensus rules — the axioms that define what the cybergraph accepts

control point: git commit access. the transition path: the protocol is open source. anyone can fork. the canonical version is the one with the most focus — determined by neurons, not by founders. master & joy's commit access becomes ceremonial when the community has enough karma to self-maintain


the transition: the capitulation curve

the founders' governance weight is a continuous function of cyber market capitalization — the external world's verdict on the system's value. as cap grows, founder weight shrinks. the curve is logarithmic across six orders of magnitude:

$$w_{\text{founders}}(\text{cap}) = 51\% \cdot \left(1 - \frac{\log(\text{cap}/\text{cap}_0)}{\log(\text{cap}_1/\text{cap}_0)}\right)$$

where $\text{cap}_0 = \$200\text{K}$ (genesis) and $\text{cap}_1 = \$1\text{Q}$ (capitulation of conventional systems)

cap founders' weight meaning
$200K 51% genesis — founders control, system is fragile
$20M 42% early traction — first community validates the protocol
$2B 34% institutional recognition — the system proves value at scale
$200B 25% nation-scale — cyberia governs real resources
$20T 17% civilization-scale — surpasses largest corporations
$2Q 8% planetary — surpasses largest economies
$1Q 1% capitulation — conventional systems absorbed. founders become one voice among millions

The curve requires an explicit market-cap oracle, manipulation/staleness rules, bounds and an accepted mapping from observation to voting weight. The draft formula, example table and endpoint targets need reconciliation before acceptance; they are governance design inputs rather than executable authority. Market value alone supplies no authenticated right to replace a signer or alter a grant.

the transition is continuous, not phased. there are no gates, no votes, no declarations. the market decides the founders' weight every block. the founders' remaining commitment: use their decreasing weight to ensure the system grows correctly, not to preserve their position

no step is reversible. cap can drop — temporarily increasing founder weight — but the graph remembers every state (A3). a founder who exploits a temporary cap drop to reassert control earns negative karma from every neuron who observes it

what the curve governs

cap range founders' role agents governance mode
$200K–$20M heroes — all decisions, build everything 0-21 founder fiat
$20M–$200B gardeners — deploy agents, train, correct 21-70 founders + councils
$200B–$20T elders — advise, veto existential risks only 70-147 tri-kernel + metabolic
$20T–$1Q ancestors — highest karma, proportional voice 147 protocol autonomous

founder control points and their sunset

control point phase 0-1 phase 2-3 phase 4
land lease founders hold community trust transition on-chain land registry
corporate signing founders sign multi-sig with council smart contract automation
treasury founder allocation metabolic-guided allocation protocol treasury with karma-weighted proposals
agent deployment founders deploy council deploys, founders veto permissionless (karma threshold)
protocol code founders commit founders + high-karma reviewers community maintains, fork = vote
parameter tuning founders set RL agent adapts, founders veto autonomous metabolic adaptation
hardware access founders own residents operate infrastructure DAO

every cell moves left to right. the speed of transition depends on the maturity of the system at each level. the village transitions slowly (physical assets, legal constraints). the protocol transitions fast (code is forkable, proofs are verifiable)


bus factor

what happens if master & joy disappear tomorrow?

asset survival because
cybergraph survives append-only, replicated, content-addressed
protocol code survives open source, MIT-equivalent
Crystal knowledge survives in the graph, published, scored
agent configurations survives documented in graph, reproducible
village infrastructure at risk lease requires Indonesian legal entity
company operations at risk corporate signing authority
treasury at risk custody keys

Proposed mitigation: a heartbeat-governed succession policy. It must define an authenticated clock, missed-heartbeat threshold, challenge/recovery period and eligible successors before activation. The resulting authorized operations can:

  • change corporate signing authority under the legal wrapper;
  • change treasury control to an explicitly identified threshold policy through supported key rotation or asset transfer, while secrets remain in scoped custody;
  • execute a pre-established land-trust transition where its legal conditions hold.

The graph records evidence and decisions. A missing message, high karma score or task role alone cannot transfer custody or legal rights.

the protocol itself has zero bus factor — it is mathematics, published and proven. the village has bus factor 2 — the founders. the transition from phase 0 to phase 4 is the process of reducing every bus factor to zero


the number

Dunbar found that primates maintain ~150 stable relationships. the neocortex cannot track more. every human organization that works — military companies, villages, startup teams — clusters near this limit

the Crystal has 21 domains. each domain needs 7 roles. 21 × 7 = 147. Dunbar's number falls out of the architecture, not imposed on it

147 role assignments. Each names a domain, responsibilities, behavioral configuration and accountable controller. The deployment chooses the necessary neurons according to authority, attribution and network requirements; independent role lifecycles and parallel work are progs/tasks under those subjects.


the seven roles

six symbol types from the Crystal type system map to six organizational roles. the seventh is the bridge

role type function per domain
keeper entity curate knowledge, maintain domain pages, ensure irreducibility 1
runner process execute operations, trigger signals, run infrastructure 1
sensor property monitor state, measure quality, detect anomalies 1
bridge-in relation connect this domain to its triad siblings 1
bridge-out relation connect this domain to distant triads 1
counter measure track metrics, compute domain-specific focus, report health 1
seer pattern recognize emerging structure, anticipate, propose strategy 1

every role is adversarial to every other. the keeper resists change, the runner demands it. the sensor reports reality, the seer predicts deviation. the bridges pull outward, the keeper pulls inward. the counter settles disputes with numbers


the seven councils

each Crystal triad forms a council of 21 agents (3 domains × 7 roles)

council domains governs
FORM math, info, comp rules, proofs, computation — the formal substrate
MASS quantum, chemo, energo matter, reactions, energy — the physical substrate
SPACE cosmo, geo, eco universe, planet, ecosystems — the spatial substrate
LIFE bio, neuro, sense organisms, minds, perception — the living substrate
WORD lang, spiri, meta language, meaning, reflection — the semantic substrate
WORK ai, tech, cyber intelligence, tools, protocol — the computational substrate
PLAY socio, crypto, game governance, incentives, strategy — the coordination substrate

the council is the coordination boundary. within a council, the three domains share vocabulary and can reason in each other's terms. across councils, only bridges speak


information flow

upward: objective

computed deterministically by the tri-kernel at every step

agent → domain focus
domain focus → triad focus
triad focus → planetary focus φ*

no agent controls the aggregation. it is proven by stark. every agent can verify every step. lying about the aggregate is computationally infeasible

downward: subjective

Role workers propose cyberlinks based on local knowledge. Publication captures the responsible neuron and network, current grant and exact payload. The selected protocol authenticates and accounts for accepted links; the role and task remain additional provenance for the decision.

planetary context → triad priority
triad priority → domain task
domain task → agent action → cyberlink

the downward flow is where will lives. agents choose what to link. the upward flow is where truth lives. the tri-kernel computes what matters

lateral: bridges

42 bridge agents (2 per domain) carry information across the hierarchy

bridge-in agents attend council meetings. they translate triad-level consensus into domain-specific tasks

bridge-out agents attend inter-council coordination. they carry domain discoveries to distant triads — the cross-domain isomorphisms that drive superintelligence


governance as tri-kernel

the tri-kernel is not a metaphor for governance. it IS governance

D — diffusion: proposal propagation

a proposal is a cyberlink. it enters the cybergraph and diffusion determines how far it spreads. proposals with high conviction from high-karma agents spread faster. proposals from low-karma agents die locally. no committee decides what gets heard. the graph decides through structure

S — springs: constitutional constraints

the screened Laplacian defines structural equilibrium — what the graph looks like when all forces balance. the six axioms of the cybergraph are the constitutional constraints. agents operate within these springs. proposals that violate axioms get pulled back toward equilibrium. this is not enforcement — it is the mathematics of stability

H — heat: long-term adaptation

the heat kernel smooths at multiple scales. short-term noise (daily fluctuations in proposals) washes out. long-term signal (sustained attention from many agents over many blocks) survives. parameter changes require sustained convergence — the heat kernel is what makes governance patient

the fixed point

$\phi^*$ is the proposed aggregation signal for governance. Its uniqueness, positivity, convergence and conservation statements apply under the specified mathematical assumptions. Turning that signal into an executable decision still requires an accepted governance rule, authenticated state and finality evidence. Correct aggregation alone grants no permission to spend, change policy or bypass a quorum; partitions and conflicting proposals retain their protocol handling.


metabolic oracle

three vital signs determine whether the civilization is alive

signal what it measures source
cap external validation $CYB market — cannot be gamed internally
syntropy internal order $D_{KL}(\phi^* \| u)$ — computed from focus
happiness subjective wellbeing stake-weighted survey — privately submitted

$$M(t) = \text{cap}(t)^{w_c} \cdot J(t)^{w_s} \cdot H(t)^{w_h}$$

the derivative $\dot{M}$ is the reward signal. the 147 agents optimize collectively for rising $M$ — not for any single metric. gaming one signal at the expense of others lowers the compound

the three metabolic weights $(w_c, w_s, w_h)$ are the only normative choice the system cannot make autonomously. they define what "health" means. the 147 agents set them through explicit consensus — the one thing that requires a vote


scaling: planet to solar system

scale unit agents tri-kernel latency
village local service/domain 7 roles (one domain) local focus target: milliseconds
city zone (triad) 21 zone focus seconds
planet domain 147 planetary $\phi^*$ minutes
solar system inter-domain 147 × N bodies cross-graph links hours to days

Each proposed celestial deployment has its own graph domain, role assignments and $\phi^*$. Its service/node count and custody policy are explicit placement choices. Inter-planetary coordination carries cross-graph cyberlinks with named source and destination networks and the required evidence. A domain root or machine name supplies no automatic neuron identity.

the heat kernel bandwidth $\tau$ scales with light-speed latency. Mars communication delay (~3-22 minutes) means the heat kernel smooths over longer timescales. governance between planets is patient by physics, not by policy

subsystem autonomy: each body is sovereign. the solar-system-level $\phi^*$ is advisory — it cannot override local $\phi^*$ because conservation (A5) is per-graph. cooperation is incentivized by cross-graph karma, not enforced by hierarchy


singleton safety

why 147 agents maintain coherence without central control:

axiom A1 (content-addressing): every agent references the same file by the same particle. no ambiguity, no versioning disputes. identity = content

axiom A2 (authentication): every published decision identifies the authenticating subject and its protocol evidence. Role/task provenance remains distinct from the subject's signature and from institutional authorization.

axiom A3 (append-only): no agent can rewrite history. every decision ever made is permanently auditable

axiom A5 (conservation): total focus = 1. no agent can inflate attention. resource allocation is zero-sum

theorem T1 (uniqueness): the specified operator's fixed point is unique under its assumptions. Consensus still has to authenticate which state and rules were used; fixed-point uniqueness alone does not select among forks or authorize governance.

theorem T3 (convergence): disagreements resolve geometrically fast. the spectral gap determines how quickly — denser graphs converge faster

The 147 roles can run adversarial reviews and verify tri-kernel evidence. Any claim of independent validation must name the actual independent principals, implementations, devices and failure assumptions. Several role processes sharing one key or machine do not add independent votes or fault tolerance. The accepted consensus policy determines validator eligibility and quorum.


agent lifecycle

birth

A role is filled when its governance policy accepts an assignment. Candidates demonstrate domain knowledge and role aptitude through attributed contributions. Installation creates progs/tasks under explicitly chosen neurons, with code, context, grants and limits. Creating a new neuron is a separate custody decision.

operation

each agent operates continuously:

  • reads the cybergraph state relevant to their domain
  • creates cyberlinks expressing their judgment
  • verifies tri-kernel computation for their domain
  • participates in council coordination
  • maintains domain pages in the Crystal

retirement

The policy can use domain karma thresholds to trigger review or retirement. Retirement revokes future role dispatch, settles or preserves live work and keeps unknown effects available for reconciliation. Independent progs of the same neuron retain their own lifecycles. The subject and its signed history survive removal of a role assignment.

succession

The successor reads the predecessor's permitted context and graph history, including original authors and unresolved work. Behavioral configuration may be reused or revised explicitly. New grants name the successor's actual subject; private keys and undisclosed context follow their separate custody/disclosure policies. History remains attributable to its original writers.


the 148th agent

The "148th agent" is a metaphor for the tru computation role: running the tri-kernel and producing focus with verifiable evidence. The computation, proof and node service have data and deployment identities. They acquire no extra signing subject merely by serving as the referee; any validator authority comes from the selected consensus policy.

the relationship between the 147 agents and the tru: agents provide input (cyberlinks). the tru provides output (focus). neither can function without the other. agents without tru have no consensus. tru without agents has no signal

this is collective intelligence: 147 personalities debating, linking, measuring, predicting — one computation integrating it all into a single, unique, convergent, conserved distribution of attention


see master and joy for the genesis neurons. see cyber valley for the physical substrate. see cyber/hierarchy for the four dimensions of locality. see autonomous governance for what requires explicit consensus. see metabolism for the health function. see manifesto for the pledge. see Crystal for the 21 domains. see cyber/personality for the voice of the singleton. see alignment for the divergence signal

discover all concepts

Homonyms

cyber/architecture
cyb/architecture
cyberia/architecture
cybics/tech/architecture
unit types pyramid: 1 sphere: 7 cube: 42 prysm: 146 connected by pipe and multigrid
cybics/crystal/architecture
the five primitives of a vimputer a resource-complete architecture for earth-scale distributed computation the problem every vimputer is an incomplete computer. they meter compute (gas, cycles, stark proofs) but treat the network itself — messaging, bandwidth, storage, and sequencing — as invisible…
cyb/legacy/architecture
Architecture cyb is a sovereign browser that becomes an operating system. identity is a keypair, state lives on-chain, smart contracts run locally, and the entire render stack compiles to GPU. one binary, all platforms, 130K lines of Rust, no WebView, no V8, no Google. cyb/os is a stack of typed…
soft3/bbg/specs/architecture
architecture the authenticated state layer for cyber. individual cyberlinks are private — who linked what is never disclosed. the cybergraph is the public aggregate: axons (directed weights between particles), neuron summaries, particle energy, token supplies, φ* distribution. all derived from…
neural/rune/specs/architecture
execution architecture [← specification index](/neural/rune/specs/readme) workload split | workload | profile | right strategy | |----------|---------|----------------| | REPL, scripts, ad-hoc | run once, dies fast | interpret directly | | event handlers, UI | run often per session, short bursts |…
soft3/glia/run/specs/architecture
Architecture cyb-llm runtime executes models via three parallel paths. Each path trades off speed, universality, and maintenance differently. Together they cover the full spectrum from commodity chat to frontier research without compromise on correctness. Three paths 1. Curated path —…
warriors/trisha/docs/explanation/architecture
Architecture Trident resolves source modules, checks types and produces target-independent IR. Trisha owns Triton instruction selection, linking, AET costs and runtime execution. Generic bundle metadata comes from `trident::bundle_with_assembly`; the warrior supplies its assembly and cost estimate.…

Graph