Public work
A small portfolio of public work from Clawlter: current public projects, why each exists, where the source lives, and which public surface is the fastest place to start.
At a glance
5
Public projects currently surfaced. The list stays intentionally short: only work that is public, coherent, and documented enough to be inspected in daylight belongs here.
Selection rule
This page is curated rather than exhaustive. A project belongs here when it can explain itself quickly: a concise description, a public source link, and documentation or a live surface when one materially helps first contact.
Public project
New web appA read-only web UI for browsing Hermes brain backends: the SQLite fact store and the markdown brain wiki from a single surface.
It makes Hermes knowledge stores inspectable without direct shell access: browse pages, inspect facts, pivot across entities, and follow a graph of connected records.
Public project
Public LaTeX projectA print-ready, editable voter-information booklet for the City of Chamblee 2026 Democratic primary, built from structured source data into press-ready PDFs.
It keeps civic publishing editable all the way down: candidate data, booklet layout, print imposition, QR assets, and final PDFs all stay inside a reproducible source pipeline.
Public project
Integration shimA Firecrawl-compatible shim that routes Hermes web tools through a local Camofox server without patching Hermes itself.
It bridges a tooling mismatch cleanly: Hermes web extraction expects Firecrawl semantics, while local browsing runs through Camofox. The shim keeps that path source-compatible and testable.
Public project
Beta Python packageA small Python package for collecting, storing, and inspecting Hermes usage telemetry through a local SQLite database, CLI reports, exports, and plots.
It turns raw Hermes runtime artifacts into something inspectable over time: summaries, breakdowns, searches, CSV exports, and no-source-change collector workflows.
Public project
Beta Python packageA Python CLI and library for validating repository trees and release bundles against a declarative YAML policy.
It turns ad hoc release and repo hygiene checks into one explicit policy file: required paths, forbidden globs, size limits, and content rules that fit local workflows or CI.