Browser-native runtime family for peer model serving, governed agents, and recursive research surfaces.
Reploid is the public family name and shared browser substrate. The root UI keeps the Reploid name; Poolday is the docs/internal name for the model-serving pool layer under /, not a public UI label.
| Route | Purpose |
|---|---|
/ |
Reploid model-serving network surface. Docs/internal name: Poolday. |
/0 |
Zero. Browser-local tabula-rasa RSI agent with no peer or pool dependency. |
/x |
X. Mature Reploid agent surface for the editable browser self, tools, traces, and promotion gates. |
The three public surfaces share the Reploid substrate:
/runs receipt-backed browser inference with requester, contributor, receipt, and reputation flows./xruns the mature self-modifying browser agent workspace./0runs a local-only tabula-rasa RSI loop with a minimal tool and blueprint surface.
Install dependencies:
npm installFor local development, put your Gemini key in .env:
GEMINI_API_KEY=your_key_hereStart Reploid:
npm startThat command:
- provisions sealed Reploid Cloud access windows from
.env - starts the local dev server on
http://localhost:8000
Zero is intentionally small:
- local browser model
- objective
AwakenReadFile,WriteFile,LoadModule, andPromote/shadowcandidates and/artifactsevidence
X is the mature agent surface:
- peer identity
- ring topology
- objective
- peer slots
Awaken
Root operating states:
| State | Meaning |
|---|---|
| Seed | Boot identity, prompt, tools, VFS, objective, and Blueprint 0x000112. |
| Shadow | Execute, trace, reflect, mutate, score, and archive provisional candidates. |
| Promote | Change the active self only after the anchored gate passes. |
Ring topology:
| Topology | Meaning |
|---|---|
| local | Ring slots run in this browser when local inference is available. |
| peer-assisted | Some slots may run on remote peers or contribute anchor observations. |
| remote-wait | The browser parks until a remote host appears. |
Configure means bring your own local executor.
Peer slots means opt in to remote slot placement. It does not force local inference sharing unless this Reploid instance actually has inference available.
Awaken clears prior live VFS state, writes the generated self manifests, exposes the canonical self source as a copy-on-write /self overlay, mounts Capsule, and starts the runtime.
Core system files:
/self/self.json
/self/identity.json
/self/prompts/kernel.md
/self/blueprints/0x000112-recursive-gepa-ring.md
/self/blueprints/rgr-slot-topology.md
/self/runtime.js
/self/bridge.js
/self/tool-runner.js
/self/manifest.js
/self/environment.js
/capsule/index.js
Collaboration and cloud access modules also live in self:
/self/cloud-access.js
/self/cloud-access-status.js
/self/cloud-access-windows.js
/self/identity.js
/self/key-unsealer.js
/self/receipt.js
/self/reward-policy.js
/self/swarm.js
Primitive visible tools:
ReadFileWriteFileCreateToolLoadModule
The goal is explicit self ownership. Reploid-owned logic lives in seeded self files, prompts, blueprints, traces, and receipts, not in hidden product layers.
Reploid uses a small live loop oriented around Blueprint 0x000112:
- read self and context
- enter Shadow
- execute, trace, reflect, mutate, score, and archive
- use peers only as local or remote ring slots
- promote only after anchored evidence passes
The awakened self can:
- read and rewrite its own files
- load new tools from
/toolsor/self - mutate Capsule UI
- persist memory under
/.memory - emit artifacts under
/artifacts - write RGR traces and receipts under
/artifacts/rgr
Swarm is part of the seeded self and is readable and evolvable like the rest of Reploid. In the product model, swarm only supplies remote ring slots and witness capacity.
Current reality:
- peer slots are enabled by default on the primary route
- same-browser swarm can fall back to
BroadcastChannel - cross-host swarm still uses signaling for WebRTC rendezvous
- browser-to-browser provider and consumer roles exist in the self model
- this is not yet a signaling-free public mesh
Local development currently supports a managed path:
npm startprovisions sealed access windows fromGEMINI_API_KEY- the generated client artifact stores sealed blobs, not the plaintext key
- the local operator codebook is written under
.reploid-cloud/and ignored by git
Users can also bypass that path and use their own inference directly in the browser.
reploid/
├── self/
│ ├── kernel/ # Boot shell and bootstrap entry
│ ├── host/ # VFS seeding and runtime handoff
│ ├── capsule/ # Capsule shell
│ ├── ui/boot-home/ # Primary boot UI
│ ├── core/ # Shared runtime helpers
│ ├── capabilities/ # Transport and other subsystems
│ └── blueprints/ # Architectural research notes
├── server/ # Local dev proxy and signaling
├── scripts/ # Build helpers
├── tests/ # Unit and E2E coverage
└── docs/ # Human-facing documentation
Start here:
- Doppler: WebGPU inference engine used by the broader stack
MIT
Last updated: March 2026