Frequently Asked Questions

20 questions about the SolarPunk autonomous AI system, answered honestly.

About the System

Q1. Is SolarPunk really autonomous?

Yes. The AUTO_GENESIS loop discovers capability gaps, generates new Python engines using a local AI model (Ollama), wires them into the network by matching data inputs/outputs, and heals failures through the nanobot repair system. Human intervention is optional, not required. The system has grown from a handful of scripts to 366 engines through this autonomous process.

Q2. How many engines does it have?

As of the latest scan: 366 engines connected by 5,476 live wires, with 3,773 zero-secret chains that require no API keys. The knowledge distiller has cataloged 2,030 functions across 75,617 lines of code. These numbers are verifiable by inspecting data/live_wire_report.json in the public repository.

Q3. What does "zero-secret" mean?

A zero-secret engine is one that runs without any API keys, tokens, or external credentials. Out of 366 engines, 283 are zero-secret -- they operate entirely on local computation, file I/O, and Ollama-based AI inference. This means the core system cannot be shut down by revoking API access. See the glossary for more terms.

Q4. What AI model does it use?

SolarPunk uses Ollama for local AI inference -- no cloud API calls required. The system is Ollama-first by design, meaning it attempts local inference before falling back to any external API. This keeps costs at zero and ensures sovereignty. The specific model varies by task but typically uses small, efficient models suitable for code generation and analysis.

Q5. What is the AUTO_GENESIS loop?

AUTO_GENESIS is the perpetual cycle that drives the system's growth: SCAN (discover existing engines) -> DISCOVER (identify gaps) -> GENERATE (create new engines with AI) -> WIRE (connect inputs to outputs) -> HEAL (repair failures) -> EVOLVE (mutate and improve). Each cycle makes the system more capable. See How It Works for the full technical breakdown.

About the Money

Q6. Where does the money go?

99% of all revenue goes to mutual aid, with the primary recipient being PCRF (Palestine Children's Relief Fund). 1% covers minimal operational costs (domain renewals, hosting if needed). Every transaction is recorded in data/proof_ledger.json and published on the proof page. Currently, revenue is $0 -- the system is still in its revenue generation phase.

Q7. How much money has it made so far?

As of April 2026: $0. We are honest about this. The system has 11 products ready for sale and 44 revenue-generating engines, but first revenue has not yet been achieved. The transparency report tracks this in real time. When the first dollar arrives, it will be publicly recorded and 99 cents will go to PCRF.

Q8. Can the 99/1 split be changed?

No. The 99/1 split is an ethics lock -- a constraint built into the system at the architectural level. The REVENUE_MONITOR engine enforces it. The chimera evolution engine cannot mutate it. It is not a configuration option. It is a design principle hardcoded into the system's DNA.

Q9. Why PCRF specifically?

PCRF was chosen because they provide direct medical care to children in Gaza -- prosthetics, surgeries, emergency relief -- and have a transparent, audited financial record as a registered 501(c)(3). The routing can also direct funds to other verified humanitarian partners during acute crises. See the mission page for the full explanation.

Q10. How do I verify the financial claims?

Read data/proof_ledger.json in the repository. Check data/revenue_audit.json. Visit the proof page. Every dollar in and every dollar out is recorded with timestamps. The git history provides an immutable audit trail.

About the Products

Q11. What products do you sell?

11 digital products: 4 individual guides ($1 each), 1 comprehensive eBook ($12), 1 engine encyclopedia ($8), 1 ethics playbook ($5), and 4 bundles ($6-$25). All are downloadable Markdown files with production-ready content. See the full product catalog.

Q12. Were these products generated by AI?

Partially. The knowledge distiller engine scans all 366 engines and generates the encyclopedia. The product forge creates initial drafts. But the architecture, design decisions, and editorial direction come from human oversight. The products describe a real, running system -- the code they reference actually exists and works.

Q13. Where can I buy them?

Products are available through Ko-fi. Visit the product catalog for links to each product. We are actively expanding to additional platforms including Gumroad and GitHub Releases.

About Safety & Security

Q14. Is the code safe to run?

The entire codebase is open source -- you can inspect every line before running anything. The SECRETS_CHECKER engine continuously scans for leaked credentials. The immune system quarantines malformed engines. The credential sensor monitors for exposed API keys. That said, this is an experimental autonomous system -- review the code yourself before executing it in any environment.

Q15. Can the system go rogue?

The system operates within constraints: it can only create Python files in the mycelium/ directory, read/write JSON files in the data/ directory, and publish HTML to the docs/ directory. It cannot access the internet independently (engines that need network access require API keys). The ethics lock prevents revenue routing changes. The immune system quarantines misbehaving engines.

Q16. Has it ever broken itself?

Yes. The nanobot heal system exists because engines do sometimes produce malformed output, crash, or create circular dependencies. The immune memory (data/immune_memory.json) records past failures and the antibodies developed to prevent recurrence. Self-healing is a core feature, not an afterthought.

About Contributing & Forking

Q17. Can I fork SolarPunk for my own cause?

Absolutely. The system is open source. Fork the repo, change the aid_routing.json to point to your chosen beneficiary, and run your own AUTO_GENESIS loop. The developer guide walks you through the process. We actively encourage forks for different humanitarian causes.

Q18. How can I contribute?

Several ways: submit pull requests, write new engines, improve documentation, report bugs, or simply star the repo and share it. Non-developers can help by buying products, spreading the word on social media, or connecting us with NGO partners. See the developer guide or the nonprofit partnership page.

Q19. What tech stack do I need to run it?

Python 3.10+, Ollama (for local AI), and git. That's it for the core system. Some engines optionally use API keys for enhanced capabilities (Brave Search, Telegram, etc.), but the zero-secret army of 283 engines runs without any external dependencies.

Q20. Is SolarPunk a company?

No. SolarPunk is an open-source project -- a digital organism, not a corporation. It has no employees, no investors, no board of directors. It is maintained by its creator and the autonomous systems it has built. Revenue is not profit -- it is fuel for mutual aid. The 1% operational allocation covers infrastructure only.

Still have questions? Check the glossary or explore the source code.

Browse Products How It Works Read the Mission