3-2-3-17-77-1-6-4-1-4
- Resolves toNortheast Ohio
- Rolethe central instance - resolves every other address
One standard for keeping records and building applications
Personal data stays local. Local networks get stronger.
MiCyte was made so that the way records are kept and the way applications reach them is one standard rather than one vendor's, so that people can organize themselves and connect without asking permission. An instance holds its own records at its own address and is the unit of identity; applications written by anyone and hosted by anyone cooperate through it, and nobody rents the program to take part. It began on the farm; the research is why.
Explore the network Get the software
- an instance keeps its own records, and is who you are
- the registry resolves its address
- others find it; nothing moves
- applications cooperate through it, whoever wrote or hosts them
What the site is for
One standard, four avenues.
This site is the software's front door: what ships, what you build against, who is on the network, what an account is for, and why it exists. The site and its resources are maintained by Fruitful Network Development.
- 01 SoftwareWhat ships: the release and how it is cut, the gadgets it offers, and the surfaces you build against. →
- 02 NetworkThe registry, browsable: a map and roster of everyone it can resolve, and the contract every instance holds with it. No account, no upload. →
- 03 AccountsWhat an account is for and what is free: a sign-in to instances others run for you or your organization. A hosted instance is charged only for the hardware behind it. →
- 04 ResearchWhy it began on the farm: whether stranded local agricultural value is recoverable, a seven-part case with a white paper and proposal. →
The network, standardized
The contract every instance holds.
The software does not require Fruitful Network Development. The registrar is a parameter of the library, and any other party can run one and set its own standard of agreement; anyone can host a local instance and still take part in the broader network. For ease of adoption, FND runs the registry this site reads and publishes the catalogue every instance pulls, so an instance built from the public package has a party to cooperate with on day one.
- The registrar answers one question Who is this msn. The channel an instance publishes answers the other: what do they run.
- The contract carries the catalogue An instance that never talks to the network still holds a contract with the FND instance. Its payload is deliberately small and pull-only: the packages and versions on offer. The instance pulls what it chooses; nothing is pushed, because a push channel is a remote-execution channel wearing a different name.
- How two instances agree Identity from the contact card, a signed key exchange, a sealed contract with a key period. As built; the code is in the public tree.
Plainly: no delivery between two live instances has happened yet. FND publishes the only signature and the only endpoint in the registry, and an install cannot report itself to it. The contract is written and the transport exists; the second live instance is what is missing.
What you build against
The surfaces.
MiCyte is implemented against a small set of surfaces, each written down as a contract. A tool, an instrument, a viewscope, an app, an extension, a port, a channel: each answers a different question.
- ToolsA function bound to a document's shape; what reads and writes.
- InstrumentsA read-only way to reach one kind of record across sandboxes; holds nothing.
- ViewscopesHow a document is drawn; the shape selects the render.
- Apps and extensionsWhat ships together; a hub over its tools, or a fill for a port.
- PortsFour layers: type, extension, binding, grant.
- ChannelsA session the outside engages; it never writes.
Live from the registry
Who is on the network right now.
Start here
Ways in.
- 01 Resources The network's tools: a live open channel with the phylogenic tree, the calendar of what recurs, and the farm-plan calculator.
- 02 Research The seven-part case for making local supply legible, with the white paper and proposal.
- 03 Get the software Install the 0.5.0 alpha and read every line that would run on the farm. AGPL-3.0.
- 04 See the gadgets Every app and extension the build offers, what each one installs, and its declaration to download.
- 05 The surfaces What you build against: tools, instruments, viewscopes, apps, extensions, ports, channels, each with the contract that governs it.
- 06 Accounts Free, and for one thing: reaching an instance someone else runs for you or your organization. What is charged, and what is built today.