hec-ovi/censurado-web-brain

<h1 align="center"censurado-web-brain</h1

<p align="center" <strongThe Censurado newsroom: a host-run agentic CLI plus the on-disk prompt recipe that drives the rest of the system, and the one Docker Compose that wires the Go data/API backend (which owns all content data and serves the operator admin panel), the static-site generator, the public site, and ComfyUI. It holds no data and runs no server or model: authors, sources, and articles all live in the backend, and the CLI talks to it over HTTP.</strong </p

<p align="center" <img src="https://img.shields.io/badge/compose-onestack-2496ED?logo=docker&logoColor=white" alt="Docker Compose" / <img src="https://img.shields.io/badge/AMD-StrixHalo-ED1C24?logo=amd&logoColor=white" alt="AMD Strix Halo" / <img src="https://img.shields.io/badge/License-MIT-blue" alt="License" / </p

<h2 align="center" <a href="https://hec-ovi.github.io/censurado-web-brain/"📖 Read the interactive docs →</a </h2

<p align="center" <a href="https://hec-ovi.github.io/censurado-web-brain/"<img src="https://img.shields.io/badge/docs-live-e01842?style=for-the-badge&logo=github&logoColor=white" alt="Read the interactive docs" /</a </p

<h2 align="center" <a href="https://elcensuradoweb.com"🌐 See it live: elcensuradoweb.com →</a </h2

<p align="center" <a href="https://elcensuradoweb.com"<img src="assets/censurado-portal.gif" width="820" alt="A Censurado article on the desktop portal: an embedded X post inside the piece, directly above a pricing comparison table" /</a </p

<p align="center" <a href="https://elcensuradoweb.com"<img src="assets/censurado-mobile.gif" width="240" alt="The same portal on a phone: the article feed scrolling on a narrow mobile viewport" /</a </p

<p align="center"<subThe public site this newsroom publishes to, a fully static portal on a CDN. Posts embed inside articles (here an X post sitting above a pricing table), and the whole site is responsive down to a phone.</sub</p

---

What this is

This repo is the newsroom: the agentic CLI a driver walks to write and publish articles (cli/), the editorial prompt recipe it walks through (prompts/), the maintenance sweeps that keep the corpus tidy (newsroom/, the censurado-brain command), and the single docker-compose.yml that brings up the whole pipeline. It re-implements none of the other repos: every service builds from a sibling repo's own Dockerfile (or pulls an image), and this repo owns the wiring between them, the one secret that couples them, and the recipe the agent follows.

There is no database and no server here. Content (authors, sources, articles, layout, topics) lives only in the backend, and the CLI reads and writes it over the backend's HTTP API. Delete this repo and the backend still serves the whole site and its admin panel; what you lose is the way to author new pieces.

This repo is the source of truth for how the system runs. If a claim about ports, flows, or contracts conflicts with the code and compose here, the code wins. Read this README, AGENTS.md, and docker-compose.yml first.

It expects the code repos checked out next to it:

workspace/
  censurado-web-brain/        <- you are here (the newsroom: CLI + prompts + sweeps + compose)
  censurado-web-backend/      <- data + API: sqlite store, publish/read API, media, admin panel
  censurado-web/              <- static-site generator + the public frontend (templates/CSS/JS)
  comfyui-strix-docker/       <- ComfyUI on ROCm (image generation)
  telegram-bot-skill/         <- the Telegram bridge (required for the Telegram lane)

The code repositories, all under github.com/hec-ovi:

• censurado-web-backend - data + API (sqlite store, publish/read API, media) and the operator admin panel.
• censurado-web - static-site generator + public frontend.
• comfyui-strix-docker - ComfyUI on ROCm, the art director's render backend.
• telegram-bot-skill - the Telegram bridge that puts the CLI agent in your pocket. Required if you want the Telegram lane; its setup lives in its own repo.