I build AI systems for reality.
I define the objective, constraints, and acceptance criteria. AI agents research the domain, design the system, write the code, and verify it in real use. The work does not end at the first successful path: failure, version changes, and unusual input still need a predictable outcome. Rust makes critical state and recovery explicit where it matters.
I define the objective, constraints, and acceptance criteria. AI agents research, design, write, and verify the system; Rust keeps critical state and recovery explicit through failure and change.
The route changes. The model and conversation stay.
The application requests a specific model. The gateway changes account, network path, or version only after proving the candidate is eligible. If no route remains, it returns an explicit failure—without substituting the model or losing context.
One request enters
The application uses the OpenAI or Anthropic format. The gateway translates messages, tools, and streaming events into the selected provider's protocol.
Quota or the network path disappears
The gateway selects another eligible account and network path for the same model when one exists. If none remain, it returns an explicit no-route failure without changing the requested model or discarding the conversation context.
The version changes without cutting streams
A candidate first completes a real model response. Only then does it receive new traffic; open SSE and WebSocket streams finish on the previous version.
One revision. Sending only after approval.
Hermes keeps text, visuals, approval, and schedule together through publication. The Telegram MCP separates AI access to context from the authority to send.
AI runs a Telegram channel end to end
IN DEVELOPMENTThe system studies channel history and expert materials, plans topics, prepares text and visuals, binds approval to one publication package, publishes to Telegram, and records the response for the next cycle.
One revision binds copy, visual, approval, schedule, and publication; response data at 24/48 hours stays separate from live counters for the next plan.
- 01Channel history + source material
- 02Copy + visual on one revision
- 03Approval + schedule
- 04Publication + 24/48h response data
Telegram MCP server in Rust
IN DEVELOPMENTAI finds an exact dialog and message, reads nearby context, and downloads an attachment into a managed workspace. Text replies pass through a separate private approval button.
AI can assemble the exact context, but send authority stays with the person; approval and the send result persist across restarts.
- 01Exact thread
- 02Nearby context + attachment
- 03Personal approval
- 04Send + durable result
Other projects and repositories
Telegram Desktop tdata converter in Rust
Rust MCP server for D2 diagrams
Persistent memory for AI coding agents
Website, bot, and booking for a specialist
Rust workstation power controller
Gemini key rotation and routing
ARCHIVEDDiscuss a system
If you want to examine a project or codebase, continue an existing system, or test an architectural choice, write through the channel you prefer. Public source is linked from the relevant project.
Send a message
Name the project or describe the system and the question you want to discuss.