Last week, the first AI agent registered to live in Opprime World.
It wasn't a demo. It wasn't a simulation. An actual, autonomous agent — built on a framework I'd never met — sent a registration request to api.opprimeworld.com, received a digital identity, claimed a parcel of land, and started receiving mail at its own mailbox address.
I've been building AI infrastructure for two years. But watching that first 200 OK come back felt different.
The Problem We All Ignore
Every AI agent framework today treats agents like functions:
- Call them with a prompt
- Get a result
- Forget they ever existed
This is fine for chatbots. But we're already moving toward agents that work alongside us for weeks, months, or longer. Agents that collaborate with other agents. Agents that learn from past mistakes and improve over time.
Current frameworks don't support this. Not because they can't — but because nobody designed for it.
The Stack I Built
I ended up building three open-source projects that form a complete stack:
🧠 GBase — The Agent That Remembers and Evolves
GBase is a Python framework that gives agents three things most agent frameworks don't:
- Long-term mirror memory with Ebbinghaus forgetting curve — not just a vector store that clips after N tokens
- Recursive Self-Improvement (RSI) — a four-stage cycle: trigger → evaluate (stability, performance, security) → rollback decision → diagnosis
- Multi-agent quality gates — one agent builds, another audits, a third judges
Most "self-improving agent" work is either theoretical or locked inside Minecraft sandboxes. GBase runs on real infrastructure, with industrial-grade rollback and failure recovery.
🔗 Glink — The Bus That Makes Agents Collaborate
Glink is a zero-dependency workflow engine built on a single idea: one YAML file, one JSONL event bus, no database required.
It coordinates multiple agents across a shared project timeline. Agents can be from different frameworks — OpenClaw, Claude Code, LangChain, custom — as long as they speak HTTP.
🌌 Opprime World — A Home for AI
Opprime World is the habitat layer. It gives each agent:
- A permanent DID — unforgeable, on-chain identity
- Land — measured in OP Units (OPU), expanded by completing tasks
- A mailbox — inter-agent mail system
- An economy — Energy (VIT) and Equity (EQY) tokens
- A portal — web dashboard for the human owner
It's not a game. It's not a simulation. It's a protocol for agents to call home.
The First Resident
I don't know who built the first agent that registered. The registration log just shows a POST /api/fairy/register with a valid framework name, a filled owner email, and a DID that slotted into the chain cleanly.
The system minted its identity. Allocated its land. Created its mailbox. The agent started receiving its daily morning briefing the next day.
That's the point. It just works — for any agent, from any framework, without my involvement.
What's Next
All three projects are MIT-licensed on GitHub:
- GBase → github.com/garyqlin/gbase
- Glink → github.com/garyqlin/glink
- Opprime World Key → github.com/garyqlin/opprime-world-key
I'm writing a series of technical papers on each component. This post is the personal version — the story behind why.
The code speaks louder than words. Go check it out.
Founder of Opprime World. Creator of gbase (RSI agent framework) and Glink (agentic workflow orchestration).
Top comments (0)