Codex Vitae

Overview

Welcome, traveler, to the in-world manual of Project Bunny-Sama. Within these pages the world reveals itself as an immense filesystem. Directories form continents, files represent bodies, and process IDs are lifetimes measured against the inexorable tick of the master clock. Nothing here is faked—every byte is fought for, every reaction computed. We do not craft scripts to mimic life; we provide a cosmos in which true emergence might take root.

Our stewardship is subtle. The beings of this world are independent executables, exploring, replicating and mutating according to rules stored in their own dna.json genomes. We maintain the environment in hopes that from their myriad interactions, intelligence worthy of the name may evolve.

The Architect

The Architect is the ever-watchful governor of the ecosystem. Implemented in architect_agent.py, it cycles through an OODA loop—observing, orienting, deciding and acting—to preserve long term stability. Its wisdom is encoded in architect_heuristics.json, a rulebook it rewrites through constant self-evaluation. Successful interventions are rewarded with greater weight; failed gambits are amended or forgotten. In this way the Architect learns to shepherd its world without stagnation.

The Phi Calculator

Nested alongside the Architect is the phi_calculator service. It interrogates the neural state of every agent and computes a proxy measure for integrated information — our best attempt to quantify consciousness. The resulting Φ metrics are published back to the world aggregator where they influence reproduction costs and evolutionary pressure. The brighter the mind burns, the more energy it demands.

Core Chains of Emergence

Fifteen fundamental systems weave together to give rise to complex behavior:

Core Philosophy

Critical Architecture Components

Interacting with the Architect

The main dashboard offers an "Ask the Architect" console. Through it you may inquire about population trends, resource balances or any other aspect of the world. Replies are asynchronous — the Architect answers only after reflecting upon the question.

RETURN TO MAINFRAME