Reploid is a browser runtime family working toward a proof-carrying, self-improving active-science network. Its goal is to select the computation, review, replication, or experiment expected to reduce scientific uncertainty most efficiently, then carry the evidence needed to inspect and reproduce that decision.
The current main product surface provides receipt-backed browser inference. Model execution and agent state stay in the browser. Current Poolday compatibility services may handle authentication, rendezvous, policy enforcement, receipt anchors, and ledger projections, but they do not perform the claimed browser-local model execution. The active-science goal does not expand the current supported claim.
It ships as three distinct surfaces: Poolday, Zero, and X. Each has its own route, boot profile, tool set, and evidence authority. Poolday is the main product surface. Zero and X are experimental RSI harnesses. A capability supported on one surface is not implied on another. Every support claim is machine-checked in the surface claim index; read each row by its declared boundary and status.
| Surface | Route | What it is | Boundary |
|---|---|---|---|
| Poolday | / |
Main product UI: receipt-backed browser inference under the internal Poolday pool contract. ("Poolday" is the internal/docs name; the public UI remains Reploid.) | Browser inference backed by signed records, audits, reputation, policy, and deterministic comparison. It does not claim hardware attestation or unconditionally honest browser/GPU execution. |
| Zero | /zero |
Experimental minimal RSI harness that begins from CreateTool, with no pool dependency. |
Standalone experimental evidence; requires no inference pool. |
| X | /x |
Experimental governed RSI harness with workers, memory, peer slots, verification, and self-modification (Seed → Shadow → Promote). | Self-modification, swarm, validation, and promotion evidence stay separate from Poolday inference records. |
The Zero and X intent contract defines their routes, boot profiles, modules, and tool surfaces. The root Poolday path is owned separately by the product boot modes, pool config, and Poolday product intent. Proven Zero or X capabilities may enter Poolday only through a governed promotion boundary and a new Poolday-owned policy, user contract, and operational proof.
The target atomic product object is a signed, evolving Discovery Contract. It binds a bounded question, competing hypotheses, uncertainty, candidate actions, predicted observations, scientific costs, outcomes, and predeclared replication or closure criteria.
Bring Reploid an uncertain problem. Leave with the most informative next action,
and leave the network better at solving the next problem
The canonical Poolday product intent defines this objective, the initial protein-discovery wedge, the north-star metric, and the separate authority of Poolday, Zero, and X. It also separates target capabilities from the current browser-inference boundary.
The agent modes that expose Promote (the X surface) move through Seed, Shadow, and
Promote. Seed creates the recoverable self, Shadow stages candidate changes, and
Promote writes an allowlisted candidate into the live self only after its evidence passes.
| State | File mutation | Evidence | Activation boundary |
|---|---|---|---|
| Seed | Writes the recoverable identity, prompt, tools, VFS, objective, and Blueprint 0x000112. |
Boot manifest. | Establishes the self that can be restored. |
| Shadow | Writes candidates under /shadow; the active /self stays unchanged. |
RGR traces, scores, receipts, and rollback paths under /artifacts/rgr. |
Candidate code remains provisional. |
| Promote | Copies an allowlisted candidate from /shadow into /self. |
Anchored gate result, replay result, and candidate hash. | Changes /self; validator mutations enter quarantine instead. |
npm install
npm startOpen http://localhost:8000. For the managed Gemini path, set GEMINI_API_KEY in .env before starting.
Awaken clears prior live VFS state, writes the generated self manifests, exposes canonical source through a copy-on-write /self overlay, mounts Capsule, and starts the runtime.
The generated VFS manifest enumerates seeded files. The executable tool-surface contract enumerates tool membership. The RGR runtime contract defines candidate evidence, anchors, quarantine, rollback, and promotion.
The surface claim index owns these status lines and their evidence paths:
| Index row | Current boundary |
|---|---|
local-execution |
A configured local executor runs slots in the current browser. |
peer-slot-placement |
Opted-in slots may run on joined peers; enabling slots does not expose local inference unless this browser has an executor. |
browser-provider-roles |
Browser requester and provider clients exchange assignments, outputs, and receipts through peer rooms. |
signaling |
Same-browser rooms can use BroadcastChannel; cross-host WebRTC uses signaling for rendezvous. |
sealed-credentials |
npm start can build sealed access windows; client artifacts omit the plaintext key and the operator codebook stays ignored under .reploid-cloud/. |
public-mesh |
Blocked as a signaling-free claim while cross-host rendezvous still requires signaling. |
Users can bypass the managed access-window path and supply their own browser inference.
| Reader | Entry points |
|---|---|
| Operators | Quick start, configuration, and local models |
| Agent and runtime contributors | System architecture, RGR runtime contract, and tool surfaces |
| Security and claim reviewers | Security model, surface claim index, Poolday claims, and threat model |
| Product and inference integrators | Poolday product intent, Discovery Contract, browser inference pool, receipt schema, and Doppler |
The documentation index owns the complete architecture, blueprint, API, and operator inventory.
License metadata is in package.json (license: MIT). This repository does not currently include a standalone LICENSE file.