// run
Run a task. See who ran it.
Pick a job, send it across the mesh, and follow it machine by machine. Every run ends in a receipt you can open and share.
prompt
Summarize the Bitcoin whitepaper in three sentences.
- model
- llama-3.1-8b
- split
- 2 halves, mapped then reduced
- replicas
- 3 machines per shard, majority hash wins
- needs
- 8 GB of memory or more
[------------------------] 0.00s
[.][.][.][.][.][.][.][.][.][.][.][.][.][.][.][.][.][.][.][.][.][.][.][.][.][.][.][.][.][.][.][.][.][.][.][.][.][.][.][.][.][.][.][.][.][.][.][.][.][.][.][.][.][.][.][.][.][.][.][.]
hover a machine to see who it is
- [.] idle
- [>] assigned
- [#] computing
- [=] returned
- [$] paid
- [z] handed off
- [x] mismatch
> tail -f job.log
waiting for a job_
> cat output
the result lands here once a majority of replicas agree on its hash.
Want to know why three machines do the same work? Read how verification works, or the full job lifecycle in the docs.