Lictor
Lictor is a moderation tool for professional broadcasters and the people who moderate for them. It puts live chat, moderation actions, user history and team coordination in one place, and it is honest about the fact that every platform underneath behaves differently.
What it is
Lictor is written in Praxis, on WebGlue, and lives in the Praxis repository as a product of its own, with its own version and its own tags. It is meant to become a paid product; the beta is free and invite-only.
Twitch is the first platform and, for the first release, the only one. It is the only one of the three considered — Twitch, YouTube and Discord — that exposes everything this product wants, and showing a moderator honestly what a platform cannot do needs a first platform that works to measure the others against.
- Scope one: the consolidated and the Twitch-specific chat views, the core moderation actions, audit, user history and notes, and enough of a plugin runtime to prove it.
- Deferred, not cancelled: Discord, YouTube as the second platform, VOD and clip downloads, statistics, scheduling, subscriptions, and the plugin set beyond a minimum.
- Customers will extend it with plugins written in Logos, the embeddable Lisp — one language for the host and its plugins.
The name
A lictor attended a Roman magistrate: he walked ahead through the crowd, cleared the way, and carried out the magistrate’s orders. A tool in which moderators carry out a broadcaster’s rules on a crowd has that job description exactly.
The name has a second meaning, from KULT, the roleplaying game: there, lictors are servants of the Archons, keeping order inside the Illusion in the guise of people with authority. Lictor’s services are named from that lore — lictor_elysium, the site, after Elysium, the Illusion itself; lictor_kether, identity, after Kether.
Built outside-in
Lictor is built in the order a user meets it: first the site, then registration, then login, and onward. Each step is a journey with an acceptance test written first, failing, and green when the journey is done. The first thing that existed was a running site, so every journey after it adds a working feature to something already running.
Since 12 October 2026 Lictor drives the Praxis roadmap: it is Phase 6. When a journey needs something WebGlue, a library, prx or the compiler does not have, the work goes down to that layer and builds it there, on a branch of its own — and only then. Work on a lower layer that no journey asked for waits for the next phase. Every journey is a release of every product it changed.
The reason is in the concept: a test suite reports what its author thought to check; an application reports what a language costs to use. WebGlue is that report for Praxis, and Lictor is that report for WebGlue — many persistent connections, isolation per broadcaster, reconnection under supervision, rule changes without dropping a connection. What it may not do is reshape WebGlue around itself.