Metadata-Version: 2.4
Name: fleetmesh-protocols
Version: 0.1.0
Summary: Host-side FleetMesh protocol stores and HTTP route handlers (Textile, DM, Grasp, Arcade, Circles)
License: CC0-1.0
Requires-Python: >=3.10
Description-Content-Type: text/markdown
License-File: LICENSE
Requires-Dist: fleetmesh-core[crypto]>=0.2.1
Dynamic: license-file

# fleetmesh-protocols

Host-side stores and HTTP route handlers for the FleetMesh application
protocols, as a plain Python library:

| subpackage | what it holds |
|---|---|
| `fleetmesh_protocols.textile` | fiber + quilt stores and routes, the hosted Leaf relay (negentropy sync, DIDComm mediation) |
| `fleetmesh_protocols.dm` | direct-message mailbox and spool |
| `fleetmesh_protocols.grasp` | git object store, smart-HTTP handler, seeded repos |
| `fleetmesh_protocols.arcade` | arcade store and routes |
| `fleetmesh_protocols.circles` | circle store and persistence |

It depends only on `fleetmesh-core[crypto]`. There is no node runtime,
transport or event loop in here: a web host (MeshTube) embeds these directly,
and `meshnode` mounts them behind its protocol router. The TypeScript
counterparts are the `@fleetmesh/{textile,dm,grasp,arcade,circles}` packages.

These modules moved out of `meshnode` (`node.protocols.*`) so that hosts do
not have to install the whole node to serve the protocols.

```
pip install fleetmesh-protocols
```

Tests: `for t in tests/test_*.py; do python3 "$t"; done` with `fleetmesh-core`
importable (installed, or `PYTHONPATH=.:../core:../schema` beside sibling checkouts).
