For people who aren't developers: Greater is a free chat widget you can drop on a website. When a visitor asks a question, the answer is written by a small AI model running inside the visitor's own browser — not on a server you have to pay per-message for. The Bitcoin demo at hire.colonhyphenbracket.pink is the live version. Everything below is for people who want to host their own.
Sovereign-by-default support bots. FOSS shell, persona-tuned demos, browser-local inference. No per-message API tax. No vendor between you and your customers.
Greater is a free, open-source shell for industry-specific support
chatbots that — by default — answer in the visitor's browser using
WebGPU. There is no per-message API cost, message content stays
in-browser on the default flow, and there is no vendor mediating
between you and your customers. (Caveats: the marketing site loads
Google webfonts, and there is a labelled, client-capped cloud
fallback for browsers without WebGPU. See
COMPLIANCE.md for the full posture.)
The shell is MIT. The model is open-weight (Llama-3.2-1B-Instruct, q4f16). The corpus is yours. The runtime cost is the visitor's device.
The work that gets hired — and the work that actually closes
deals — is the corpus curation, the persona tuning, the
domain-specific Pipes that wrap proprietary knowledge bundles, and
the integration into your stack. That's colonhyphenbracket.
The Bitcoin demo runs entirely in the visitor's browser. No backend. No database. No API keys. That means a non-developer can put a working copy of the bot on the public internet without ever opening a terminal.
The path is:
- Fork this repo on GitHub. Click the "Fork" button at the top of github.com/rorshockbtc/greater-than. You now own a copy.
- Connect your fork to a free static host. Cloudflare Pages,
Vercel, and Netlify all do the same job here — pick whichever you
already have an account on.
- Build command:
pnpm install && pnpm --filter @workspace/greater run build - Output / publish directory:
artifacts/greater/dist/public - Environment variables: none required.
- Build command:
- Deploy. The host gives you a public URL in a couple of minutes. That URL is your bot.
That's it. You now have a Bitcoin support chat running on your own domain, with the model executing in your visitors' browsers, no per-message bill, no vendor sitting between you and them.
GitHub has a "Sync fork" button on every fork. Click it whenever you want to pull in upstream improvements (new catalog branches, security fixes, design polish). Your static host watches the fork and automatically rebuilds when it sees the change. You never run an update command.
If you want it truly hands-off, drop a daily GitHub Action into your
fork that auto-presses Sync Fork for you. (A starter workflow for that
will land in .github/workflows/sync-upstream.yml shortly — track
the open issue
if you want to be pinged when it does.)
To set expectations honestly:
- No URL ingestion. The "paste a URL and the bot will learn from it" feature needs the API server. The static install ships with the curated Bitcoin catalog only.
- No contact form delivery. The form will render but submissions will go nowhere without a Web3Forms key.
- No admin feedback inbox. Only relevant if you plan to read what visitors are searching for.
- No cloud-LLM answer polish. The bot answers from the catalog brief verbatim — which is the point of catalog-first; the briefs are hand-written. If you want the answers paraphrased per visitor, the full Quickstart below adds the cloud fallback.
For most non-developer operators, the static install is the right default. Add the API server later if you actually need any of the above.
Edit JSON files in the GitHub web editor — no clone, no terminal:
- Open
artifacts/greater/public/catalog/bitcoin/in your fork on github.com. - Add or replace the
<branch>/<leaf>.jsonfiles with content that matches your domain. Each leaf is a 3-paragraph brief with cited sources. The structure is documented indocs/INSTALL.mdunder "Track A — Bitcoin operators." - Bump the
versionfield inindex.json. (Required so visitors' browsers fetch the new tree instead of the cached old one.) - Save. Your static host sees the commit, rebuilds, and your bot updates within a couple of minutes.
This is the caveat the README owes you up front: Greater is an early-stage product. The catalog you ship is yours to maintain, the shell will keep getting better, and the install path above is specifically designed so that the maintenance cost on you stays close to zero.
The launch demo is wired live: a FinTech bot grounded in the Blockstream support corpus.
→ hire.colonhyphenbracket.pink/demo/blockstream
The other five personas (HealthTech, Startups, Faith, Schools, Small Business) ship as persona-tuned holding pages — the seed corpora are still being curated.
For the longer story behind why Greater is built the way it is — explicit bias, sovereign-by-default, FOSS shell with proprietary weights as the work-that-gets-hired — see the company philosophy doc:
→ Read the CHB company philosophy
- Six industry personas — fintech, healthtech, startups, faith, schools, small-business. Each ships with a written-out failure mode, a pivot story, a tuned welcome message, and a Pipe slot for the proprietary knowledge bundle.
- Browser-local LLM — Llama-3.2-1B-Instruct (q4f16) and bge-small-en-v1.5 running in a Web Worker on WebGPU.
- IndexedDB vector store — RAG retrieval lives on the visitor's device. The corpus you ship is cached after first load.
- Cited answers — every retrieved chunk is shown to the visitor via the "Thought trace" disclosure on every reply.
- Honest cloud fallback — when WebGPU isn't ready, the widget can call a server endpoint for the first three turns, badged "Cloud" so provenance is visible. After the cap, the badge changes to "Local-only · cloud rate-limited".
- Generic web-scraping ingestion — paste a URL or sitemap into the chat widget's settings menu; the server fetches it (Mozilla Readability), the browser chunks and embeds it, IndexedDB persists it. No LLM in the ingestion path.
- Pipes — a Pipe is a curated, opinionated knowledge bundle
authored by a domain expert. Drop manifests into
data/pipes/(gitignored) and the Vite plugin inlines them asvirtual:greater-pipes. - Bias-aware retrieval — the Bitcoin Pipe ships with Core, Knots, and Neutral perspectives; the chat shows a bias toggle when multiple perspectives are mounted, and the transcript drops an inline note when the visitor switches.
- Compliance posture — written-down, deep-linkable, honest. See
COMPLIANCE.mdand the/compliancepage. - Anti-AI design pass — hand-drawn SVGs, build-stamp footer, margin notes, asymmetric layout cues, real first-person copy. This is a real product built by a real person.
- WCAG 2.2 AA — focus rings, skip-to-content, reduced-motion,
aria-liveon streaming chat, role/status disclaimers.
FOSS, in this repo (MIT-licensed):
- The full Greater shell (
artifacts/greater). - The chat widget, model loader, vector store, ingestion orchestrator, KnowledgePanel, BiasToggle.
- Six persona scaffolds with case-study copy.
- The Bitcoin seed builder (
scripts/src/build-bitcoin-seed.ts) — pulls OpTech, the last 12 months ofbitcoin/bitcoinandbitcoinknots/bitcoincommits, and a checked-in list of BitcoinTalk threads. - The compliance document and the
/compliancepage. - The persona case studies and the marketing site.
Proprietary, gitignored, not in this repo:
data/pipes/— Pipe manifests. The Bitcoin Pipe (Core/Knots bias-aware) is the reference Pipe that ships behind the/demo/blockstreamroute. Authoring more Pipes is the workcolonhyphenbracketdoes for hire.data/seeds/bitcoin.json— the output of the Bitcoin seed builder. Anyone can regenerate it from this repo (the script is open) but the cached artifact is not committed.artifacts/greater/public/seeds/— the public-static copy that the LLMProvider fetches on first run for the FinTech demo.
If you want to run the FinTech demo locally with the proprietary Bitcoin bundle pre-loaded, run the seed builder yourself (see Quickstart below). Otherwise the demo will fall back to ingesting the Blockstream support corpus on first visit.
pnpm install
pnpm --filter @workspace/greater run dev
# → http://localhost:5173pnpm --filter @workspace/api-server run dev# Anonymous; sleeps through GitHub rate-limit windows.
pnpm exec tsx scripts/src/build-bitcoin-seed.ts
# Faster + higher rate limit (recommended for dev):
GITHUB_TOKEN=ghp_xxx pnpm exec tsx scripts/src/build-bitcoin-seed.tsThe script writes data/seeds/bitcoin.json (gitignored). It also
syncs a public-fetchable copy to artifacts/greater/public/seeds/
so the LLMProvider can pull it on first run. Both directories are
gitignored; the script is fully resumable and caches every fetched
page to disk.
Pipes live under data/pipes/<slug>/manifest.json. The Vite plugin
in artifacts/greater/scripts/pipes-vite-plugin.ts discovers them at
build time. See data/pipes/bitcoin/ (in your local clone, post
seed-build) for the reference structure.
A visitor opens the chat. Their question is handed to a Web Worker running Llama-3.2-1B on WebGPU. Before the model runs, the question is embedded with bge-small-en-v1.5 (also browser-local) and matched against the IndexedDB-backed vector store. The top 4–8 chunks are inlined into a system prompt with citation instructions. The model streams tokens back; the widget renders them with the citation markers turned into clickable links to the source pages. Every retrieved chunk is visible behind a "Thought trace" disclosure. Nothing leaves the device on the default flow.
For the long version with the actual flow diagram, see
/how-it-works.
Greater — sovereign-by-default support bots, FOSS by default.
Open-source shell for industry-specific support chatbots that run entirely in the visitor's browser (WebGPU + Llama-3.2-1B + IndexedDB RAG). Six personas, one wired live: a Bitcoin support bot grounded in the Blockstream corpus, with a Core/Knots bias toggle.
No per-message API tax. No vendor between you and your customers. The shell is MIT. The corpus is yours.
Live demo: https://hire.colonhyphenbracket.pink/demo/blockstream Source: https://github.com/rorshockbtc/greater-than Compliance posture (HIPAA / WCAG / GDPR / PCI / SOC 2): /compliance
Built by one fractional architect, in public, in pink. :-]
artifacts/
greater/ # Greater marketing site + chat shell (the FOSS bit)
api-server/ # Express server for ingestion + escalation
mockup-sandbox/ # Component-preview server for design iteration
data/
pipes/ # Proprietary Pipe manifests (gitignored)
seeds/ # Generated seed bundles (gitignored)
scripts/
src/ # Seed builders, ingest helpers
COMPLIANCE.md # Engineering-grade compliance posture
README.md # You are here.
Built by colonhyphenbracket.
The proprietary Pipes, the persona-tuned weights, and the integration work into your stack are available for hire.
MIT. See LICENSE.
Greater — built by colonhyphenbracket. :-]