⚒️ Building the greek-stack — open-source tools for agent-assisted development you can actually trust.
I'm a software developer based in 🇧🇷 Brazil. I spent years shipping Flutter apps — finance, streaming, commerce, the usual grind — until AI coding assistants changed the question I was trying to answer. The question isn't "can the agent write it?" anymore. It's "can I trust what it wrote — and reproduce that every single time?"
My answer is the greek-stack: three open-source tools, each named after Greek mythology, each owning one part of the loop that turns a one-shot generation into shippable code. Built in the open, early and honest about it.
Tech I ship with
Dart · Flutter · TypeScript · JavaScript · Node.js · MCP · CLI tooling
If you've only got a minute, these are the three I'd point you to first. Together they cover retrieval, delivery, and rules for agent-assisted dev.
Named after the bronze automaton that patrolled Crete — a tireless, deterministic guardian.
A deterministic delivery pipeline for AI-assisted dev: Contract → Plan → Execution → Cold validation, with MCP gates and an isolated sibling validator. Ships 16 MCP tools and runs across 8 hosts (Claude Code, Cursor, Codex, Antigravity, ZCode, OpenCode, Pi CLI, VS Code).
npx github:pauloborini/talos init claudecode🔗 github.com/pauloborini/talos
Named after the hundred-eyed giant who never slept — nothing escaped its sight.
Local code retrieval and context packing for AI agents. Point it at a symbol and it answers where it lives, what calls it, and what breaks if it changes. CLI + MCP server, git-aware auto-sync. Up to −92.7% tokens on internal benchmarks, 6/6 ground-truth.
npm install -g @owerride/argus
argus install🔗 github.com/pauloborini/argus
Named after the god of the forge — who shaped raw metal into canonical form.
A repo-native skill kit that takes raw project rules and forges them into a canonical LLM runtime. It governs the four documentary territories of a repo — AGENTS.md, project-rules/, the vault, the work folder — in a single write transaction: 13 phases, one batched interview, an approvable plan, and a checkpoint to resume from.
🔗 github.com/pauloborini/hephaestus
The thesis is simple: an agent is powerful but unreliable on its own. To be trustworthy it needs retrieval, a deterministic path, and governed rules.
| Tool | Owns | One-line job |
|---|---|---|
| 👁️ Argus | retrieval | finds what the agent needs — cheaply |
| 🛡️ Talos | delivery | guards the path from prompt to validated code |
| ⚒️ Hephaestus | rules | forges the repo's rules into a runtime the agent respects |
Each works standalone. Together they form a loop where nothing gets written blind, nothing ships unvalidated, and nothing contradicts the repo's own rules.
- Shipping the greek-stack in the open — Talos, Argus, Hephaestus
- Treating agent-assisted dev as an engineering discipline, not a vibe
- Writing a landing & docs for each tool — all of them catalogued at borini software
📍 Brazil · 🇧🇷 · Coffee-powered · Always shipping