Reploid is a proof-carrying Research Room for curators adjudicating disputed annotations on explicitly public protein sequences. It combines exact model contracts, signed execution records, attributable review, preserved disagreement, and reusable prior evidence without treating admission as biological truth.
Repository mission, value, and durable strategy live in GOALS.md. Poolday's user workflow and evidence boundary live in its product intent.
The repository serves:
- Public protein catalog curators testing a disputed family or domain annotation.
- Research Room requesters, compute contributors, and accountable reviewers.
- Runtime and product contributors working on browser execution and room state.
- Security and claim reviewers checking records, relay boundaries, and evidence.
- Researchers designing the future active-science workflow.
Install and start the local browser surface:
npm install
npm startOpen http://localhost:8000. The managed Gemini path requires GEMINI_API_KEY
in .env before starting.
The product surface is:
| Surface | Route | Use |
|---|---|---|
| Research Room | / | Create or resume a bounded public-protein adjudication workflow. |
Poolday remains the internal implementation name. The public application and product are Reploid.
The surface claim index owns the current support claims and their evidence paths.
| Claim 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; joining does not expose local inference without a local executor. |
browser-provider-roles | Requesters and providers 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. |
public-mesh | Blocked as a signaling-free claim while cross-host rendezvous requires signaling. |
The current main product provides receipt-backed browser inference. Model execution and agent state stay in the browser. Compatibility services may handle authentication, rendezvous, policy enforcement, receipt anchors, and ledger projections; they do not perform the claimed browser-local model execution. Users can also provide their own browser inference.
Reploid does not claim hardware attestation, independently trustworthy browser/GPU execution, or guaranteed honest providers. Relay acknowledgement proves receipt of a relay record, not execution truth. Experimental runtime capabilities remain outside the Research Room product authority until prospective evidence and Poolday-owned admission allow them. Read the claim index row before repeating a capability statement.
self/: browser boot profiles, VFS, tools, and runtimedocs/: product intent, claims, security, architecture, and operator guidesdeploy/: deployment and access-window toolingdoppler/: vendored or paired Doppler integration surfaceshowcase/: demonstrations and recorded runspackage.json: package metadata and local commands
- GOALS.md owns the repository mission, value, and durable strategic goals.
- CATSCAN.md is the root component charter. Child charters narrow its authority for independently meaningful components.
- The generated component index lists every charter, parent, and target.
- AGENTS.md defines how code agents discover and obey the charter chain.
- The workspace CATSCAN protocol defines the shared shape and precedence rules.
Run npm run catscan:chain -- <path> to print the charter chain for a target file. Run npm run verify:catscan to validate fields, parents, links, evidence paths, identifiers, size, and the generated index.
- Repository goals
- Root component charter
- Component index
- Documentation index
- Poolday product intent
- Discovery Contract
- Poolday claims and non-claims
- Security model
- RSI improvement episodes
- Doppler
MIT License. The package metadata also declares MIT.