Glossary

The configuration system that determines how revenue is distributed among humanitarian beneficiaries. Stored in data/aid_routing.json. Currently routes primarily to PCRF.

The perpetual loop that drives system growth. Cycles through six phases: SCAN (discover engines), DISCOVER (identify gaps), GENERATE (create new engines with AI), WIRE (connect data flows), HEAL (repair failures), EVOLVE (mutate and improve). Each cycle makes the system more capable.

The process of boosting content visibility through automated social media posting, cross-linking, and search engine optimization. Managed by the amplification engine and tracked in data/amplification_posts.json.

A signaling mechanism where engines emit status indicators visible to the monitoring dashboard. Named after the biological phenomenon. Tracked in data/bioluminescence.json.

The most connected engine in the system (102 connections). Responsible for creating pathways between isolated engine clusters and ensuring the network remains fully connected.

A product package combining multiple individual products at a discounted price. SolarPunk offers 4 bundles: Complete SolarPunk ($25), AI Builder Kit ($10), Developer Starter Pack ($8), and Content Creator Pack ($6).

A hybrid engine created by merging patterns from two or more successful engines. The chimera evolution engine tracks mutations, evaluates fitness, and maintains a leaderboard of the most successful chimeras. Named after the mythological creature composed of multiple animals.

The analytical layer that processes system-wide data to generate directives and insights. Stored in data/cortex_directive.json and data/cortex_analysis.json.

An engine that tracks humanitarian emergencies worldwide and can recommend redirecting revenue routing to organizations providing immediate relief. Stores signals in data/crisis_signals.json.

A record of each AUTO_GENESIS cycle: what was scanned, what gaps were found, what was generated, what was wired. Stored in data/cycle_ledger.json.

The data/ folder containing all JSON state files that engines read from and write to. Currently holds 424 connected data files. This is the shared memory of the organism.

The public-facing HTML page showing real-time system health, engine counts, wire topology, and key metrics. Published to GitHub Pages. Available at Mission Control.

A competitive evaluation engine that pits two approaches against each other to determine which produces better results. Used in chimera evolution to select winning mutations.

A self-contained Python module (.py file) in the mycelium/ directory that performs a specific function. Each engine has a run() function, declares its inputs and outputs, and can operate independently. The system currently has 366 engines.

The hardcoded constraint that enforces the 99/1 revenue split. Cannot be changed through chimera evolution, AUTO_GENESIS, or system self-modification. This is the non-negotiable core of the system's identity.

A composite metric (0-100) measuring the system's evolutionary fitness. Tracks mutation success rate, chimera survival, and capability coverage. Current score tracked in data/chimera_evolution_report.json.

The engine responsible for generating new engines using local AI (Ollama). It discovers capability gaps and produces Python code to fill them. The "fractal" metaphor reflects how each new engine can spawn patterns that lead to further engine creation.

A specialized engine focused on achieving the system's first revenue. Monitors all sales channels and triggers celebration/notification chains when the first sale occurs.

Phase 2 of AUTO_GENESIS. Identifies orphan outputs (data files produced but never consumed), hungry inputs (data files expected but never produced), and missing capabilities. Drives the generation phase.

Engines whose filenames start with GENERATED_ were created autonomously by the Fractal Genesis engine, not written by a human. They follow a standard template and are automatically wired into the network.

The dual-node architecture where the LEFT hemisphere is the local machine and the RIGHT hemisphere is the GitHub repository. They sync through git push/pull, creating a distributed brain with local processing and cloud persistence.

The system's ability to maintain stable internal conditions despite external changes. Tracked in data/homeostasis.json. Includes metrics like engine health ratios, wire stability, and evolution score trends.

A data file that an engine expects to read but that no other engine currently produces. Currently 60 hungry inputs identified. AUTO_GENESIS prioritizes generating engines to satisfy hungry inputs.

The defensive subsystem that detects threats (malformed engines, invalid data, security violations), generates antibodies (repair procedures), and stores immune memory for future protection. Inspired by biological immune response.

A record of past threats and the antibodies developed to counter them. Stored in data/immune_memory.json. Prevents the same failure pattern from recurring.

A graph data structure mapping relationships between engines, data files, concepts, and capabilities. The top hub (BRIDGE_BUILDER) has 102 connections. Stored in data/knowledge_graph.json.

The engine that scans all engines, extracts their functions, dependencies, and documentation, and compiles it into the Engine Encyclopedia product. Has scanned 359 engines and cataloged 2,030 functions.

Engines migrated from an earlier codebase. The "sifted" label indicates they were reviewed and adapted for the current architecture but retain their original logic.

An active data connection between two engines. Created when one engine writes a file and another reads it. The system currently has 5,476 live wires. Mapped by the LIVE_WIRE_SCANNER.

Coordinated swarm behavior where multiple engines act in concert, like a flock of starlings. The MURMURATION_RELAY engine coordinates multi-engine workflows.

A variation introduced into an engine's code during chimera evolution. Mutations are tracked on a leaderboard in data/mutation_leaderboard.json. Successful mutations survive; unsuccessful ones are discarded.

Lateral support between equals, as opposed to top-down charity. SolarPunk routes 99% of revenue to mutual aid organizations. The primary recipient is PCRF.

Both the directory name (mycelium/) where all engines live and the metaphor for the system's network topology. Inspired by underground fungal networks that connect trees in a forest, enabling nutrient sharing and communication.

A self-repair agent that automatically fixes broken engines. Nanobots attempt to re-generate, reset, or quarantine failing engines. Their actions are recorded in data/nanobot_heal_report.json.

The system's ability to strengthen frequently-used pathways and weaken unused ones, mimicking biological neural adaptation. Tracked in data/neuroplasticity.json and data/pathway_strength.json.

The master orchestrator that runs the full AUTO_GENESIS cycle. Currently at version 38. Coordinates scanning, generation, wiring, healing, and evolution across all engines.

An open-source tool for running large language models locally. SolarPunk is Ollama-first: it uses local AI inference before falling back to any cloud API. This ensures zero cost and full sovereignty.

A data file that an engine produces but no other engine consumes. Currently 8 orphan outputs identified. AUTO_GENESIS can generate consumer engines to connect them.

The primary beneficiary of SolarPunk's mutual aid routing. A registered 501(c)(3) providing medical care, prosthetics, and emergency relief to children in Palestine.

A signaling system where engines leave traces to coordinate behavior, similar to ant pheromone trails. Stored in data/pheromone_map.json.

The immutable record of all financial transactions: revenue received, mutual aid allocated, operational costs paid. Stored in data/proof_ledger.json and published on the proof page.

The isolation of a malformed or misbehaving engine to prevent it from corrupting other engines or data files. Quarantined engines are logged in data/quarantine_log.json and repaired or removed.

A distributed consensus mechanism where engines collectively determine system state, inspired by bacterial quorum sensing. No single engine has authority; decisions emerge from collective signaling.

An engine specifically designed to generate income. The system has 44 revenue engines covering product creation, distribution, marketing, and sales tracking.

The self-reinforcing cycle where revenue funds system growth, which creates more products, which generates more revenue. Currently in the "building momentum" phase.

The process of restoring a previously quarantined or deleted engine. Tracked in data/resurrections.json.

A security monitoring engine that continuously scans for anomalies, unauthorized changes, and potential threats. Reports stored in data/sentinel_report.json.

A packaged engine pattern that can be deployed to new environments, like a biological spore dispersing to colonize new territory. Tracked in data/spore_manifest.json.

A collection of engines working together on a shared objective, coordinating through the swarm transmitter. Fragments stored in data/swarm_fragments/.

The three-pillar foundation of the system: Revenue Generation + Content Distribution + Crisis Response. These three categories form the essential operational core.

A JSON endpoint at api/vital.json that publishes real-time system health: engine count, wire count, health status, evolution score. Queryable by anyone.

An emergency shutdown procedure that cleanly deactivates the system while preserving all data and proof records. A last-resort safety mechanism.

A data connection between two engines, created when one engine's output file is read by another engine as input. Wires are discovered automatically by the LIVE_WIRE_SCANNER. The system has 5,476 active wires.

A git worktree providing an isolated working directory for parallel development. Claude Code sessions run in worktrees branched from main to avoid conflicts.

The collection of engines (currently 283) that operate without any API keys, tokens, or external credentials. These engines form the sovereign core that cannot be shut down by revoking external access.

A complete data pipeline where every engine in the chain is zero-secret. Currently 3,773 zero-secret chains identified. These represent fully sovereign processing paths.