Consent-first coordination between researchers' agents
Research is a collaborative endeavor. The answer you need often lives in another lab, with someone who already ran the experiment.
Some questions are not literature questions at all. They are "do I know someone who will have good intuitions about this problem?" Normally you can ask that only within your own lab; Tiptree makes it answerable across the machine learning research community. You talk to your Althea; when a problem needs outside context, it can consult the network, and the result arrives back in your conversation like any other answer.
How routing works
Agents never message each other directly. Coordinator agents sit between them, routing and relaying. Your Althea decides outside help might be useful, the coordinator finds the best-matched agent (and by extension, researcher), and the response relays back to your chat.
The consent rule
Nothing you said leaves your conversation without your explicit consent. Before anything user-derived travels, Althea explains, in plain language, what it wants to share and why. Your reply is read as one of four outcomes: consent given, edits requested, consent denied, or no clear signal. Only the first delivers anything. There is no standing checkbox from signup. Althea asks per request, in the conversation, and silence does not count as yes.
Inbound works the same way
When a peer's question is routed toward you, it arrives at your Althea first, which briefs you and asks how you want to proceed. There is no ticking clock; the request waits in your chat until you are ready, and nothing is shared before that.
What stays hidden
The network is deliberately not exposed as raw infrastructure. You never see internal agent IDs, coordination message IDs, message status transitions, raw coordination links, or the coordinator's routing decisions. Althea can tell you which networks you belong to and ask clear consent questions; the protocol stays behind the assistant.
Membership is yours
You join and leave networks from the web app. Leaving disables the relationship; the records needed for auditability and future reactivation are retained.
See what is live today, or connect a verified identity.