RAGBAZRAGBAZ
sections
home pricing
products
product lines ai governance matches articulate mailroute detcordon baz signals esp32tolk shipwrecks weftmark sylvae mouseion nostoi frog rebekah minotaur design system dash docbin library mailstack remote android scarcity completion glossary
learn
school docs face lesson game search
governance
buyer page formal spec architecture pilot
demos
face demo glither wasm baz signals
studio · product lines · updated 2026-08-14
// updates

Substantial news, rarely.

Register for ragbaz updates — very low volume, only when something real ships. No digests, no drip. Confirm by email; unsubscribe in one click.


// ethos

deterministic

runtimes reproduce. same seed, same frame. choreography is data, not chance.

containment-first

hostile inputs run in isolation. observe the payload, never the blast radius.

terse

copy reads like kernel log lines. labels are identifiers. numbers are mono, tabular.

in-family

one warm dark system across engine, studio, decks, and pages. borders, not shadows.


// product lines

10 surfaces

ephor (ai governance)

building
Ephor routes agent actions through typed allow / hold / deny policy, identity and RBAC, human approval, and a tamper-evident SHA-256 audit chain. Operator preflight, self-contained buyer-demo, release-packet, and HSM-capable evidence paths ship; external review and deployment-specific conformity remain gates, not product claims. buyer page → formal specification → prospectus →
componentsarchitecture →

mcp ingress

model-context-protocol gateway. every agent tool-call is intercepted and routed through the policy gate before it reaches the upstream tool. identity + rbac enforced at entry.

policy gate

glither.governance dialect (risk-tiered, fold first-match) compiled to a wasm component. synchronous allow / hold / deny, fail-closed on missing evidence.

audit chain

append-only postgres event store with sha-256 hash chain and verify-chain. ≥6-month retention. art 9 risk management, art 12 traceability.

human oversight

hold-for-approval lifecycle with sla-timeout-to-deny. notifications to discord and email, rbac-gated approvers. art 14 human oversight.

manifest signer

ed25519 replica-manifest signing, software or pkcs#11 / hsm backend, anchoring cross-node divergence detection and conformity evidence.

identity + rbac

oidc / saml authentication, role→permission authorization (agent / reviewer / approver / admin) enforced at ingress and on approvals.

agent→mcp-ingress→policy-gate→audit-chain→oversight→replica-signer

matches

78% completelive
autonomous cinematic battle runtime — grounded locomotion, tactical ai, procedural choreography, per-bone keyframe timeline in an in-browser studio. prospectus →
componentsarchitecture →

viewport

real-time 3d scene renderer. webgl2 viewport with orbit controls, selection, transform gizmos. multi-camera layout (perspective, top, front).

timeline

per-bone keyframe editor. dope sheet and curve editor. blend modes, easing presets, frame-stepping. deterministic replay.

tactical ai

goal-oriented action planner. perception system (sight, sound, damage). stance state machine, formation logic, cover evaluation.

dsl editor

embedded domain-specific language for choreography. syntax-highlighted editor with live preview. seed-based determinism for reproducible playback.

procedural engine

locomotion blending, ragdoll transitions, procedural wind/react. constraint solver for foot-planting and hand-placement.

dsl-editor→tactical-ai→procedural-engine→viewport←timeline

articulate

88% completelive
WordPress powers 43% of the web — and is the single most targeted CMS. Every plugin, theme, and zero-day is an attack surface you didn't write. Articulate wraps your WordPress in a Rust gateway with filesystem immutability, WASM image hardening, GraphQL depth/pagination guardrails, and a private origin invisible from the internet — then adds a Next.js storefront, multi-tenant provisioning, and GraphQL edge federation. read the docs → pricing → prospectus →
componentsarchitecture →

gatekeeper

secure ingress proxy. authenticates and routes requests to tenant wordpress instances. handles custom domain ssl, rate limiting, waf rules.

storefront

next.js 16 headless frontend. app router, tailwind v4, stripe payments, oauth (google/facebook/microsoft/apple). courses, shop, events, digital downloads.

provisioner

multi-tenant lifecycle manager. creates wordpress instances via docker-compose, manages dns (cloudflare), mail users, ssl certs. stripe webhook integration for billing.

graphql edge

federated graphql gateway (strawberry + fastapi). aggregates wp graphql, storefront data, and tenant management into a single endpoint. mcp server for ai-driven operations.

mailstack

tenant email infrastructure. dovecot imap, postfix smtp, dkim signing, alias management, mailbox provisioning per tenant.

provisioner→gatekeeper→wordpress↔graphql-edge↔storefront→stripe

mailroute

74% completebeta
Hostile mail bypasses every perimeter filter eventually — phishing, malware, data exfiltration, and spoofing land in inboxes before signatures catch up. MailRoute sits between the MTA and the mailbox, inspecting every message against hot-reloadable rules with quarantine buckets, audited rule edits (propose → apply → revert), and webhook relays for downstream automation. read the docs → cellular school → prospectus →
componentsarchitecture →

rule engine

pattern-match pipeline. header, body, attachment analysis. allow/block/reject actions, scoring, tag injection. hot-reloadable rule sets.

bucket store

quarantine and archive buckets. sqlite-backed with litestream replication. time-based retention policies, manual release or delete.

audit

propose-apply-revert cycle for rule changes. full diff history per rule. operator approvals, rollback on failure. immutable event log.

webhook relay

event-driven delivery for matched mail. configurable endpoints, retry with backoff, delivery receipts, secret signing.

imap proxy

transparent smtp/imap intercept. sits between mta and mailbox. inspects in transit, no client config changes required.

smtp→imap-proxy→rule-engine→bucket-store|webhook-relay

detcordon

beta
DetCordon fronts disposable, network-isolated Docker or Firecracker victims with a DetectionOnly HTTP tap. Tenant-bound mTLS moves events, samples, and heartbeats to an age-encrypted, audited sink; bounded replay and on-demand sending preserve observed HTTP provenance. Deterministic request-to-process-to-sample lineage remains planned. product site → open prospect → forensics school → docs → request a pilot →
componentsarchitecture →

waf tap

DetectionOnly ingress assigns fresh request IDs, records observed HTTP metadata, and keeps captured provenance separate from runtime facts.

disposable victim

Docker and Firecracker backends isolate intentionally vulnerable workloads so each detonation can be discarded and rebuilt.

evidence sink

a separate active-passive sink receives tenant-bound mTLS events and samples, age-encrypts evidence, and exports offline-verifiable bundles.

operator dashboard

authenticated review and export surface for events, samples, containment evidence, and buyer-facing demonstrations.

hostile-http→waf-tap→disposable-victim|events + samples→evidence-sink→operator-dashboard

esp32tolk

building
esp32 speech-translator firmware — i2s mic or bluetooth capture, on-device transcription, live translation.
components

capture

i2s digital microphone input or bluetooth a2dp source. 16khz/16bit mono pipeline, configurable gain and noise gate. ringbuffer with dma.

stt engine

on-device speech-to-text via esp-sr or whisper.cpp (q4 quantized). streaming inference, voice-activity detection, keyword spotting.

translate

local nllb or tiny-llm translation model. phrase cache for low-latency repeat translations. configurable source/target language pair.

output

serial/uart text out, i2s tts playback, or ble gatt characteristic. lcd display for standalone mode. wifi or bt transport.

mic→capture→stt-engine→translate→output

ShipWrecks

building
interactive swedish shipwreck explorer — charted wrecks, dive records, and documented provenance over the swedish coast.
componentsarchitecture →

map

leaflet-based interactive map of the swedish coast. clustered wreck markers with depth contours, exclusion zones, and maritime navigation layers.

archive

curated registry with per-wreck provenance. coordinates, depth, cargo, sinking date, discovery story. photos, sonar scans, and diver reports.

backend

node/express api server with postgresql. geo queries, full-text search, image serving. stripe subscription billing, user auth, admin interface for curators.

map↔backend↔archive

baz trade signal stack

50% completeactive embryo
Automated trading pipelines are opaque — strategies execute without audit, and a bug in the signal chain appears first as a loss. The BAZ Trade Signal Stack compiles each glither.hft strategy to a signed WASM component with Ed25519 monetary audit receipts, enriches tick data in a verifiable Rust pipeline (SMA/EMA/RSI/Bollinger), and surfaces every execution in a live browser notebook you can inspect. glither component path → platform architecture → prospectus →
componentsarchitecture →

baz.hft

glither.hft compiler dialect and no_std wasm host embryo. compiles trading strategies via baz-hft-roux. signed ed25519 monetary audit receipts, deterministic market-policy evaluation.

baz.palantir

rust/axum orchestration server. rule lifecycle management, sma/ema/rsi/bollinger enrichment via bounded ring buffers, websocket streaming, sqlite backlog, bearer auth.

baz.luna

vite 6 browser trading frontend. codemirror 6 glither.hft notebook editor, lightweight-charts candlestick + rsi view, signal markers, backlog viewer. ~2.7 kB initial js.

baz.cx

python fastapi exchange connector. 5 venue adapters, websocket stream of tick data and enriched candles to palantir. live execution gate open pending durable receipts.

baz.cx→baz.palantir→baz.hft→audit-receipts|baz.luna

weftmark

research
Multi-agent software work loses the thread fast — which worker changed what, what evidence says it works, who reviewed it, and whether it's actually ready to merge. WeftMark is a vendor-neutral ledger that tracks scope, Git lineage, evidence, handoff, and review through a prototype runtime, growing out of the operational primitives already proven in RAGBAZ Frog.
components

change sets

local change-set runtime tracking scope and semantic claims per worker, with Git lineage bound to each change.

evidence

durable records of what was verified and how, kept alongside the change instead of scattered across chat logs and CI runs.

review + handoff

structured review and handoff surfaces that make merge/release readiness explicit rather than implied.

board projection

read-only Kanban and mobile/tablet review client for watching in-flight work without a heavier PM tool.

worker→change-set→evidence→review→board

sylvae

research
Agent skills written for one harness don't travel — a macro built for Claude Code doesn't run under Codex, OpenCode, or a local model without a rewrite. Sylvae is a portable skill runner: it loads a SKILL.md-format skill and dispatches it to Ollama, Claude Code, Codex, OpenCode, or the Anthropic API, logging every run as a durable evidence record. Four of the five backends need no API key of their own.
components

skill loader

parses a SKILL.md-format directory — YAML frontmatter plus instructions — into a normalized skill definition, reusing a format already in cross-vendor use.

backend router

dispatches a run to Ollama, Claude Code, Codex, OpenCode, or the Anthropic API; tier-based auto routing sends cheap work local and frontier work to a paid backend.

evidence log

every run is recorded as a durable, comparable record — output, latency, and rough cost — shaped to be WeftMark-compatible.

SKILL.md→loader→backend-router→ollama/claude/codex/opencode→evidence-log

mouseion

live
Mouseion keeps things made with AI the way a library kept scrolls: collected, catalogued, and open to scholars. Every file is stored under its SHA-256 and re-hashed on every read, so a tampered copy is reported instead of shown. Every publication and every piece of evidence is one record in a tamper-evident Nostoi chain that anyone can download and verify. Publishers choose a pseudonym, anonymity or a real name, and a real name is never linked to a pseudonym. Evidence about a scroll — the model that wrote it, when, and through which harness — is chained, and claims are labelled as claims until something verifies them. Public beta; source not yet open.
components

scroll keeping

bytes in R2 content-addressed by SHA-256 and re-hashed on every read; a mismatch is a 502, never a page.

chain

every publication, key change and evidence push is a record in a Nostoi ledger, with signed heads anyone can check.

provenance

which model wrote it, when, and through which harness — recorded as evidence and labelled as a claim.

sandboxed exhibits

scroll bodies are served from a separate cookieless origin under a CSP sandbox and never same-origin with the museum.

publish→hash (sha256)→chain (nostoi-v1)→sign head→verify anywhere

nostoi

beta
A chain is a sequence of records where each carries the digest of the record before it and a digest of its own content. Verification names the first inconsistent record. Nostoi is a Rust library, a CLI and a TUI for that, and it already reads the chains the RAGBAZ projects keep — Nostoi's own, WeftMark's ledger and Ephor's audit chain — so the rest of a fleet can share one format. Detecting a removed tail or a wholly recomputed history still requires a head trusted outside the chain, which is what signed anchors are for.
components

library + CLI

append, verify, head, show, log --follow and a TUI; exit status is 0 intact, 1 broken, 2 unreadable.

formats

nostoi-v1, weftmark-ledger-v1 and ephor-audit-v1 are detected automatically; --format overrides.

signed anchors

Ed25519 nostoi-anchor-v0 signs a head, so a chain can be anchored without holding the chain's private keys.

bindings

JavaScript, Python and a WASM component build, so a Worker, a script and a browser can all verify the same bytes.

records→digest each→chain them→sign the head→verify anywhere

frog

beta
Frog is the coordination layer a multi-agent workspace runs on. It discovers repositories and resolves their identity, schedules tasks by dependency and priority, hands out file locks so two agents cannot silently edit the same file, and records events so a decision can be traced after the session that made it is gone. Rules stay in readable files; the machine-readable state is one SQLite database. It is used daily by the fleet it coordinates.
components

repo discovery

registers a repository and resolves a stable identity from its origin, so scheduled work can be affected precisely.

tasks

dependency-aware scheduling with priority and ROI, claims, and a durable history of who did what.

locks

file and repository scopes with leases, so long-running work can hand over instead of deadlocking a workspace.

federation

peers can be joined so several machines share one coordination view rather than drifting apart.

discover repos→schedule tasks→lock files→record events

rebekah

building
Rebekah is the runtime the fleet's agents actually execute in: a reproducible image with supervised services, a policy gate, and evidence produced as work happens rather than reconstructed afterwards. It is an executable bootstrap today — the core image builds and its supervised services pass an end-to-end container smoke test — not yet a production-ready distribution.
components

reproducible image

one build definition for the agent runtime, so a run can be repeated rather than described.

supervised services

the services that carry an agent session, with health checks and restart under one supervisor.

gateway views

Rebakah-compatible views with a schema name, a source and an observed_at, so clients read it like any other gateway.

build image→start services→run agent work→emit evidence

minotaur

research
Minotaur checks whether hosts are healthy and healthy enough to depend on. Observations form a graph, so a check that depends on a failing check is not run as if the world were fine; repairs are event-driven rather than periodic guesswork; configuration is signed; plugins are isolated; and the log is Nostoi-backed tamper-evident, with optional cross-host replication. A read-only native candidate with a typed graph IR is in progress.
components

graph IR

typed observation graph with dependency validation and freshness and single-flight planning.

event-driven repair

a repair runs because something changed, not because a timer said so.

signed configuration

what the monitor will do is itself signed, so it cannot be quietly edited.

Nostoi logging

observations are chained, so a cleared or rewritten monitor log is detectable.

observe→validate dependencies→plan freshness→repair→chain the log

design system

research
Without a shared vocabulary, every terminal surface invents its own colours, glyphs, help boxes and spacing, and two products stop looking like one company. The design system is the single source of truth for the terminal: semantic colour tokens and themes, glyph sets, the hotkey legend grammar, and the layout rules. The token files are the source; the language modules under generated/ are a projection that other repositories vendor, so no design decision lives in two places. Adopted by two surfaces so far, specified for the rest.
components

tokens and themes

semantic colour tokens and themes, bound by one table instead of hardcoded literals.

glyph sets

a chosen glyph vocabulary, so the same idea is never drawn three ways.

renderer adapters

conformance checks and an adapter path so a curses, ratatui, Textual or ANSI surface reads the same tokens.

define tokens→project language modules→vendor + adapt→check conformance

dash

beta
Dash is where a person looks at the fleet: Rebekah, DetCordon and the WordPress Gatekeeper, each card offering to register interest in a pilot. Sign-in is ragbaz.cc's, forwarded to the same Worker over a service binding, so there is one form and one passkey across both sites rather than two accounts to keep in sync.
components

one sign-in

auth is forwarded to ragbaz.cc over a service binding; a passkey works on both sites.

product cards

operational surfaces per product, each with an audited, emailed interest or pilot request.

sign in→see the fleet→request a pilot

docbin

building
DocBin publishes a document by link and nothing else. There is no listing, no search and no index to crawl — a document exists to the people who hold its link, which is the right default for drafts, proposals and material that should not be discovered. It is the publishing surface several of these projects hand finished documents to.
components

link-only publishing

no index and no listing, so a document's audience is exactly the holders of its link.

formats

MDX, PDF and HTML from one publishing path.

write→publish→share the link

library

live
Library is a minimal Worker that serves the finished Salvage to Signal handbook. It runs the manuscript's own multilingual build and verification, stages the exact output bytes, and writes a scroll manifest — a single entry point and a SHA-256 inventory of every file — in the same shape Mouseion uses, so a book can become a scroll without being re-described by hand.
components

generated book

the manuscript's canonical multilingual build and verification, staged as the served bytes.

scroll manifest

scroll.json and scrolls.json in the ragbaz.artifact shape: one entry point and a SHA-256 inventory.

build manuscript→verify→stage bytes→write scroll manifest→serve

mailstack

beta
Mailstack is the default mail path for the wider platform rather than a standalone mail product: a Rust relay with sendmail and mail replacements, a Cloudflare Worker relay surface, and the Python configuration and operations helpers around them, with container and systemd deployment. Making mail boring and repeatable is the point.
components

relay

a Rust mail-relay binary that replaces sendmail and mail, relaying via a Worker or direct SMTP.

worker relay surface

a Cloudflare Worker front end for the same relay.

operations

Python configuration and domain helpers, with container and systemd deployment.

configure→relay→operate

remote android

beta
Discover phones, interrogate them over adb — mode, battery and AC, screen state, capabilities — mirror or record their video with scrcpy, and drive all of it from a full-screen TUI or a scriptable CLI. No X11, no Wayland, no compositor: the UI is curses, and VLC and browsers are optional helpers the tool degrades without. Everything is logged as JSONL so the same event stream can be replayed, audited or piped elsewhere.
components

device discovery

find phones over USB and WiFi and interrogate their state through adb.

mirror and record

scrcpy-backed mirroring and recording, from a TUI or a script.

JSONL event log

one replayable, auditable event stream for every action taken.

discover→interrogate→mirror/record→log as JSONL

scarcity

building
The handbook is both a manuscript and its own publishing pipeline: original material in one directory, the active draft in another, and a single command that builds and verifies the whole book. Chapters are readable on screen and printable as one document at A5 or A4, so the same source serves the web reader and the paper edition.
components

sources and draft

original material kept apart from the active draft, so a claim can be traced to what it rests on.

one-command build

./scripts/build-book.sh builds and verifies the whole book.

print edition

chapter view or one document, A5 or A4, from the same source.

gather sources→draft→build + verify→read or print→serve via Library