Clavis

A personal AI operations layer for this website.

Clavis is my private operations assistant for farcas.dev: a Telegram-based way to monitor the site, manage content, review activity, and handle maintenance from anywhere. Development tools are part of it, but the main role is oversight and control.

Raspberry Pi host running Clavis services with an illuminated status display
Self-hosted Raspberry Pi node with case ventilation, status display, GPIO wiring, and USB power.

One private channel for operating the site.

Hermes Agent provides the tool, memory, scheduling, and messaging framework. Clavis uses that foundation as a controlled command layer for the website.

Telegram control

A private chat becomes the place to check the platform, request updates, and coordinate maintenance.

Public boundary

The public website gets a narrow visitor-facing assistant. The private operations layer stays separate.

Site management

Content updates, page checks, activity review, and maintenance work stay connected to one assistant.

Development support

When needed, Clavis can inspect files, edit code, run checks, verify changes, and help with deployment tasks.

Public Clavis turns visitor questions into useful feedback.

Clavis collects visitor questions and uploads them to Google Sheets, making it easier to see what people care about and where the website needs clearer information.

Question insight
Shows what visitors ask about most.
Content gaps
Reveals what the site should explain better.
Sheets review
Keeps the questions easy to review and act on.

One public question, one grounded answer.

This is the public-facing version of Clavis: one grounded answer from approved website context, while the private assistant remains isolated.

public Q&A · approved website context · visitor-question insights · private layer isolated