Experiment · Invitation only · Building now
Railgun Care
Continuity across sessions. The thread of what you and someone helping care for you have been working on — kept by you, read with them, and never turned into something you did not say.
Status: Experiment — a small number of pairs, by application. Already enabled? Open Care.
The idea
Anyone who has worked with a therapist, a psychologist, a coach or a doctor over months knows the shape of the problem. Each session starts from a summary of the last one — held in one person's notes, or in nobody's. Threads get dropped. Something said in March matters in September and no one remembers it.
Railgun Care keeps that thread. The sessions go in; a structured memory comes out: what you said, what your provider said, and — marked separately, always — what a model inferred. Before a session there is a short briefing. After it, a plain account of what changed.
The space belongs to the person it is about. The provider sees it with them, by invitation, and can leave at any time — or be asked to.
What it does
Sessions in, memory out
Upload a transcript or minutes, or import a Railgun Meet session. The source stays a source. Memory is built from it, and every memory points back to the lines it came from.
Every insight says where it came from
You said it, your provider said it, or a model inferred it — marked on every entry. An inference stays an inference until one of you confirms it.
Themes over time
Recurring threads across sessions, with the evidence behind each one, so a pattern is something you can check rather than something you are told.
A briefing before, what changed after
A one-page brief before a session: where things stand, open threads, what was agreed. Afterwards, a short account of what moved and what did not.
Talking points, with reasons
Suggested things to raise next time, each with the memory that prompted it. Dismiss any of them; the dismissal is remembered too.
A provider's private notes
Notes only their author can read. The person the space is about never sees them; neither does Railgun's staff, nor any model call.
What it never does
It never diagnoses. A model's output is a hypothesis with a source, never a label. A diagnosis is something a professional writes, and this stays out of it.
It never acts on its own. No alerts to third parties, no emergency contacts, no messages sent on your behalf. If something in a session worries you, that is a conversation between people.
It never invents a number. There are no mood scores, progress percentages or streaks. What is not measured is not shown.
It never leaks sideways. Nothing from a Care space reaches analytics, search, error reporting or any other part of Railgun. An administrator who enables Care for your account cannot read it.
How it is built
Its own security domain
Care spaces live in their own database schema with their own keys. They belong to no organization, team or project, and no role anywhere else in Railgun opens one.
A second lock
Opening a space asks for your password again — and your second step, if you have one. The unlock lasts thirty minutes, and every unlock is recorded.
Sealed at rest, plainly described
Session text is encrypted under a key that belongs to the space and is decrypted only while the server serves you or runs a model call. This is not end-to-end encryption; the space's Security tab says exactly where plaintext exists and for how long.
Consent that means something
Creating a space is where you say what may happen: cross-session memory, AI analysis, processing by an external model. Each is named. Changing your mind is one setting, and every change is recorded.
Deletion is deletion
Delete the space and everything in it is gone — sources, memory, themes, notes — and the space's key is forgotten. Revoke a provider and their access ends at once; their private notes stay sealed and unreadable to anyone, including you.
Models, used carefully
A heavier model builds the first memory once and reviews it on request; a lighter one keeps it up to date. Every run is logged with the model used and why. Your sessions are never used to train a model.
Who it is for
A person and someone helping care for them — a psychologist, a therapist, a coach, a physician, a counsellor — who already meet regularly and want the thread kept. Both need a Railgun account. The person creates the space; the provider is invited into it.
Railgun Care is a tool for continuity between people who are already working together. It is not therapy, not medical advice, and not a crisis service.
Apply for access
Care is enabled account by account, by hand, for a small number of pairs. Tell us who you are and we will reply by email — from a person, not a sequence.
Questions
- Does my provider have to use Railgun?
- Yes. They need a Railgun account to accept your invitation. An invitation is a link that expires; accepting it is explicit, and you can revoke it later.
- Can I bring in sessions from before?
- Yes. Upload a transcript or minutes as text or PDF and Care parses it. Sessions held on Railgun Meet can be imported directly.
- Who at Railgun can read a space?
- Nobody, in the ordinary course of things. Enabling Care for an account is a separate switch from reading its content, and nothing in the admin console opens a space. The honest caveat: the server holds the key while it works, so a compromised server could read. The Security tab spells this out.
- What does the model see?
- The sessions you consented to process, and the memory built from them, for the duration of a call. Every run is logged. Nothing is used to train a model.
- Is it free?
- During the experiment, yes.