Skip to content

Commit cdc2776

Browse files
authored
Fix screenshot references in README
Updated screenshots in the README to reflect the correct images for the hub and publisher.
1 parent fd36376 commit cdc2776

1 file changed

Lines changed: 3 additions & 2 deletions

File tree

README.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -48,11 +48,12 @@ A fresh `git clone` on a Linux VM, a Groq brain published in one command, and a
4848

4949
**1. Start the hub (Linux VM, terminal 1).** One command brings up the FastAPI router, persistent SQLite, and a public Cloudflare tunnel. The public URL is printed in a box and exposed at `/hub/identity` for any publisher or client to discover.
5050

51-
![hub starting with public tunnel](docs/screenshots/hub.png)
51+
![publisher live with full URL + KEY box](docs/screenshots/publisher.png)
5252

5353
**2. Publish a brain (Linux VM, terminal 2).** `multi_brain_publisher.py` registers a Groq Llama-3.3-70B publisher under the name `zai`. The publisher auto-discovers the hub's public URL and prints a copy-paste-ready box with `URL`, `KEY`, and a working curl example. Every brain that connects via this script ships with a built-in zhub-aware preamble — so the AI naturally knows it's part of the substrate without anyone writing a system prompt.
5454

55-
![publisher live with full URL + KEY box](docs/screenshots/publisher.png)
55+
![hub starting with public tunnel](docs/screenshots/hub.png)
56+
5657

5758
**3. Talk to it from anywhere (Windows PowerShell).** Same URL + KEY. No zhub install on the client side — just `Invoke-RestMethod`. Three different prompts (intro / meta / code) all answered coherently, with the brain naturally explaining that it's running on Groq Llama 3.3 70B *behind a substrate called zhub that lets it be reached from many places at once*. Nothing in the client said any of that — the substrate did.
5859

0 commit comments

Comments
 (0)