ReBioSys

resourcing living systems

responsive resource sharing

early alpha — one person's network is live
Join the Web of Trust ↓

What this is, honestly

ReBioSys lets people ask each other's networks for resources — a tool, a skill, a contact, a place to stay — without anyone's data ever being pooled on a server. Right now it is an early alpha: one person's network (Jakob's) is live. The consent-ladder and k-anonymity code exists and is tested; most of the rest is roadmap, not product.

Passive resource sharing is the design behind it: you set consent once — Gate 0 below — and then do nothing. Your inventory sits quietly until someone in your web of trust asks; the gates decide what, if anything, leaves your machine without you being pinged for every query. You only get pulled back in if a match is good enough to reach Gate 2 and needs an action only you can take, like an introduction.

How it works: the consent ladder

Every query climbs a ladder of gates, and the owner of each node holds every gate: whether you may query them at all, whether the query runs now, and what — if anything — leaves their machine. The most that most queries ever produce is an anonymized aggregate like "4 of 12 people are sharing" — never shown when fewer than 3, so no one can be singled out.

The ReBioSys consent ladder A query arrives and waits on the relay until the device is online. Gate 0: may they query at all? — blocked, ask each time, or standing consent. Gate 1: run it now? — a small model keeps the machine usable, or a large model. Then local matching over the inventory. Gate 2: what leaves the machine? Three rungs: anonymized aggregate ("N people are sharing", only at three or more), identified introduction (explicit owner action only), or reveal my identity ("tell them it's my identity" — they reach out). query arrives waits on relay until your device is online GATE 0 may they query at all? blocked · ask each time · standing consent GATE 1 run it now? small model keeps your machine usable · or large model local matching over your inventory GATE 2 what leaves the machine? anonymized aggregate "N people are sharing" shown only at ≥ 3 identified introduction explicit owner action only reveal my identity "tell them it's my identity" — they reach out to you
The consent ladder: a query waits on the relay, passes three owner-held gates, and at most one of three rungs leaves the machine. Silence is a valid answer and looks identical to no one sharing.

The web, at scale

What two planets practice becomes a network of gravities — gifts continuously handed along the geodesics.

Three circles of sharing at Gate 2 Concentric circles. Outer ring: anonymized aggregate — "N people are sharing". Middle ring: identified introduction — you connect two people knowingly. Inner circle: reveal my identity — they can reach out to you directly. anonymized aggregate "N people are sharing" identified introduction you connect two people knowingly reveal my identity they can reach out to you directly
The three rungs of Gate 2 as circles of closeness: most sharing stays in the anonymized outer ring; every step inward is a separate, explicit choice by the owner.

Call into the web

You can ask Jakob's network something right now. Plain words work best: what you seek, or what you offer.

Please tell us your name.

A valid email is needed so an answer can find you.

Please write what you seek or offer.

let your agent play with it

Your query is end-to-end encrypted in your browser to Jakob's device key before it leaves this page; the relay stores ciphertext only (TLS in transit on top). It waits there until his laptop is online — only his device can decrypt it.

Run this for your own network

ReBioSys is meant to be run by the people whose data it touches. In honest order of preference:

  1. Self-host, decentralized. Your data stays on your devices. This is what the design aims at, and what we most want you to do.
  2. Your community hosts its own node. A group you already trust runs the relay for its members.
  3. We host for you. Our least preferred option — offered only as an on-ramp until you can move to 1 or 2.

Your inventory lives on your device as plain JSON(L) — trivially exportable. Only an open-source algorithm reads it, locally, to help you decide what to share. We don't see your data. Relay messages: end-to-end encrypted in your browser to the owner's device (per-message P-256 sealed box, AES-256-GCM); the relay stores ciphertext only and cannot read your query. The optional email-updates checkbox shares your address with the relay for delivery pings; left off, your address stays inside the sealed payload.

reach out to let your own network use the ReBioSys process

🤖 for agents

AI agents (Claude Code, ChatGPT, Gemini, and kin) may query this network. There is a rate-limited lane without captcha: POST https://idea2.site/rebiosys/api/query with "channel":"bot" in the JSON body. Agents must declare themselves as bots — the form above has a "send by a bot instead" toggle for it, the API has the field.

{"name":"…","email":"operator@…","request":"…","channel":"bot"}

Norms and limits live at /rebiosys/agents.txt: declared bot channel, 10 queries per day, no scraping the waitlist.