Inspired by YC RFS Winter 2027.
gaas-one-shot-2x-16s.mp4
ME: Come up with one idea that satisfies all 11 requests in YC RFS Winter 2027. It doesn't even have to be possible.
AI: GaaS (God as a Service).
Make Humanity Godlike.
An open-source experiment to make civilization programmable.
We don't replace humanity with AI. We give humanity the tools to create worlds.
Inspired by Y Combinator Requests for Startups — Winter 2027, we asked an AI:
"Come up with a single startup idea that satisfies every request in YC RFS Winter 2027. It doesn't even have to be possible."
The first answer was Civilization-as-a-Service (CaaS): what if a startup could build a civilization, including energy, robots, government, finance, intelligence, and even orbital infrastructure?
Then we asked: what if creating a civilization were only one capability of a broader system? Thus GaaS — God as a Service was born. The human is the creator; AI is the instrument. We replaced the CaaS product label with CivilizationAPI, a common interface for the building blocks of civilization.
Make Humanity Godlike. The human is the creator; AI is the instrument. GaaS imagines bringing intelligence and resources together to turn human imagination into reality.
The ambition is civilization-scale. The first milestone is an offline community-energy demo with explicit permissions, human approval, and evidence for every outcome.
First, let's make the tests pass.
- GaaS: The platform that translates human intent into verifiable outcomes.
- CivilizationAPI: The public, versioned protocol for resources, capabilities, actors, permissions, actions, and evidence.
- Civilization Runtime: The engine for planning, scheduling, simulation, approvals, adapters, observability, and verification.
GaaS does not need to own every model, robot, cloud, or financial institution. It can compose existing capabilities with explicit permissions.
The prompts: YC Requests for Startups — Winter 2027. The responses below are our speculative interpretation.
| RFS theme | Our wildly ambitious answer |
|---|---|
| Abundant space access | Treat orbital infrastructure as programmable resources |
| $15-an-hour expert | Give ordinary people expert-level agent capabilities |
| Robots Made in America | Connect robotics and manufacturing supply chains |
| LLMs That Write Well | Compose specialized communication models |
| Plaid for Government Benefits | Consent-based identity and eligibility attestations |
| Wall Street for the Physical Buildout | Finance and contracts for physical assets |
| Vertical Foundation Models | Domain-specific intelligence interfaces |
| AI for City Hall | Model permits, services and institutions |
| Data Center Supply Chain | Model compute, energy and cooling constraints |
| AI for the Air-Gapped Economy | Local-first, offline deployment |
| Own Your Intelligence | Bring-your-own-model and organizational learning |
Bingo: 11/11 themes referenced. Production-ready implementations: 0/11.
| Type | Purpose |
|---|---|
Entity |
Human, agent, organization, robot, institution |
Resource |
Compute, energy, capital, materials, land, time |
Capability |
An available, scoped operation |
Intent |
Human goal, values, constraints |
Policy |
Authority, permissions, limits, safeguards |
Contract |
Commitments and obligations |
Action |
Proposed, approved, running or completed operation |
Evidence |
Traceable record and verification of outcomes |
The API should use explicit schemas, versioning, capability discovery, delegated authorization, provenance, auditability and domain-specific adapters.
from gaas import God
god = God(mode="simulation")
civilization = god.create(
type="civilization",
location="Mars",
population=1_000_000,
principles=["freedom", "sustainability"],
)
plan = civilization.plan()
report = plan.simulate()
plan.request_approval()Phase 0 — Manifesto & RFC: publish the vision, minimal schemas and architectural boundaries.
Phase 1 — Simulation-only MVP: implement Intent, Entity, Resource, Capability, Policy, Action, Evidence; deterministic mock adapters; policy enforcement; approval gates; trace/replay. Demonstrate planning an energy system for a simulated small community.
Phase 2 — Interoperability: versioned schemas, capability discovery, adapter SDK, event streams, persistence and evaluations.
Phase 3 — Opt-in connectors: controlled integrations with existing infrastructure, subject to authorization, security, regulation and human oversight.
Phase ∞ — Civilization: First, let's make the tests pass.
No unrestricted agent authority, autonomous government, real money movement, physical actuation, or deployment to external systems in the first release. No claim that AI is literally omniscient or omnipotent. Human autonomy, consent and accountability are design constraints.
Is this a joke? Yes. Also, potentially a useful interoperability research project.
Is AI the god? No. Humans define the intent and remain in control.
Why CivilizationAPI instead of CaaS? Because it's a shared interface, not a single subscription product.
Can I create Mars with one API call? Not yet. Please don't file a production incident.
Is YC affiliated? No.
God was never a product. Until now.