Network & sharing

Devices that work together.
Makers who share.

Every Chorion device keeps its own history and its own data. An open set of rules (a protocol) lets devices help each other and lets makers share their building blocks — with credit to who made what. There is no company in the middle.

versions

fork, change, merge

Take a cell from someone else, make it your own, and bring the lines back together. Every version keeps where it came from.

Your history

Your device keeps a record of what you made and how — so you can look back, build on it, or delete it.

Help from another device

A small device can ask a stronger one — for example a shared computer in the room — to do heavy work.

Share with credit

Building blocks travel between makers with their origin attached.

Open rules

The protocol is open, so others can build compatible devices and tools.

Finding each other

No central server

Every Chorion belongs to a person, and a person's devices form one household of machines. Devices in the same room find each other on the local network. Across the internet, a household leaves a small signed note in a large public address book that already exists (the BitTorrent DHT): it says where to find you — never who your friends are or what you share.

In the room

Devices on the same network find each other by themselves.

Across the internet

Moved house, new network? Friends still find you by your identity — in the field test, in about 20 seconds.

Messengers

When two devices can't reach each other directly, a third can carry sealed messages it cannot read — only if both sides agree.

Sharing cells

Shared cells are checked by their signature

When you share a cell, each version is signed by its maker. A copy can come from anyone who has it — a friend, a classmate, a library device — and your device checks every piece against the signature. A tampered copy is refused.

Per friend, per level

Choose what each friend may see: presence, messages, live signals, cells. Nothing is shared until you share it.

Follow, ask or pin

For each cell you got from someone: follow their updates, get asked first, or keep the version you have. An update that wants more rights always asks.

Run a friend's cell

Install a cell made by someone else and run it on your own device, safely contained and with only the rights you allow.

Pieces from many places

Larger files come in small checked blocks from several holders at once, and resume where they stopped.

How things evolve

Every cell has a version history

The ledger works like version control for everything you make. Every save of a cell is a signed version that points to the one before it. So you can always go back, see what changed, and see where a cell came from. Branches, forks and merges arrive on every device in the coming weeks.

A cell's family tree: versions, fork and merge

History

Every version of every cell, with who saved it and when. Going back is just another step forward.

Fork

Take a cell, change it, make it yours. When two versions grow from the same point, Chorion shows the fork and asks: choose one, or merge.

Merge

Combine two versions into one new version that records both.

Made from

Results remember what they were made from: which inputs, which cell, which version. Change one byte and the chain shows it — also across households when you share.

Credit that travels

A shared cell stays marked as made by its maker, wherever it goes. Counting reach by people, not by clicks.

Watch it grow

See how a cell — or a whole classroom's box of cells — branched and changed over weeks and years.