pyrtan …
A core set of expandable services that act on all forms of I/O through inspectable decision trees. Ask a sentence a tree answers to; the answer comes back with the exact path that produced it. If nothing answers, you get the tree that would. No model is involved.
pyrtan hub --cors . A hub on your LAN over http:// may be refused by the browser when this page is https://; open the hub's own / instead, which is this same console.What this swarm can answer
| Tree | Answers to | From |
|---|
Need a tree that is not here? Browse the catalog, then pyrtan pull NAME into a folder a service serves.
Peers
| Link | Peer | Trees | Last |
|---|
up: answered within 30 s · stale: within 90 s · down: longer, or never.
Federation
This hub is . It routes to the hubs it follows; hubs that follow it receive its announcements and may ask it.
| Link | Hub | Relation | Trees |
|---|
Watches
Trees that run on their own: a clock, a file, a topic or a serial line starts them ([[watches]] in the tree, --watch on the service). Each row is what the watch last did; a path that changed between two runs of the same watch is how you learn a site changed before anyone asked.
| Watch | On | Fired | Last run |
|---|
Gaps
A gap is a decision that met a value no branch covers. Each one is the next branch to write, in the tree and node named.
| Tree · node | Saw | Times | Where |
|---|
Waiting to be written
Sentences nobody answered, each with the tree that would. pyrtan unanswered --at URL --scaffold DIR writes the files.
| Nobody answered | Would be | To write it |
|---|
Directory
Every hub that asked to be found, as this hub has heard it through the swarm. Entries are hints carried hub to hub; link is how recently each announced. Nothing here is routed to: to use one, follow it from your own hub, pyrtan follow URL --at YOUR-HUB. To be in it: pyrtan hub --listed.
| Heard | Hub | Holds | Last announced |
|---|
This browser as a member
A browser or a phone cannot be reached, so it joins a hub the other way round: it follows the hub, polls a mailbox the hub keeps for it, carries the directory, and keeps copies of the hub's blobs (its directory, gaps, unanswered sentences, anything given to pyrtan keep). When the hub's box dies, what it kept is still here. Install this page to the home screen and it is the phone app.
Kept here for this hub
| Key | Size | Updated |
|---|
Trees this device runs
| Tree | Answers to | Reaches |
|---|
Activity
Talk to a stranger
You are paired at random: with someone else on this hub or on a hub it follows, or with a bot. A bot is a set of trees on the network, not a person and not a model; each of its lines carries the path that produced it, and what it cannot answer it says so, with the tree that would. Nobody has a name and nothing is kept: the conversation is gone when either of you leaves.
The same endpoints this page uses
POST /intent {"text": "…"}
POST /run {"tree": "…", "inputs": {…}}
POST /resume {"snapshot": {…}, "answer": …}
GET /capabilities
GET /health
GET /gaps
GET /unanswered
GET /peers (hub only)
POST /chat/start {"want": "anyone"|"people"|"bot"} (hub with --chat)
Authorization: Bearer …. From the command line: pyrtan ask "…" --at URL, pyrtan gaps --at URL.