mirror of
https://github.com/fabro-sh/fabro.git
synced 2026-09-07 08:27:12 +00:00
283eab181f
Invert the docs convention so the Mintlify-published site lives under docs/public/ and internal artifacts (strategy docs, brainstorms, plans, etc.) sit at docs/ root or docs/internal/. Tools that default to writing into docs/ now land in the catch-all instead of leaking into the published tree. - Move Mintlify content (administration/, agents/, api-reference/, changelog/, core-concepts/, examples/, execution/, getting-started/, human-tools/, integrations/, languages/, reference/, tutorials/, workflows/, images/, logo/, docs.json, favicon.svg, dot-highlight.js) into docs/public/. - Collapse docs-internal/ into docs/internal/. - Update Rust path references (fabro-api/build.rs, fabro-server, fabro-dev), TypeScript generator arg, CI path filters, clippy.toml reasons, AGENTS.md/CLAUDE.md, and README.md image refs. Mintlify dashboard project root must be updated to docs/public/ in a follow-up. .mintignore move/trim and .claude/skills/ updates land in a separate commit.
1.2 KiB
1.2 KiB
The Problem Fabro Solves
Fabro exists for teams that have outgrown the prompt-act-review loop used by most AI coding tools.
Why that loop breaks
Interactive agent sessions work for small tasks, but they do not define a repeatable software process. In practice this creates four recurring problems:
- The engineer must supervise the agent instead of defining the process once and reusing it.
- There is no reliable gate between "the agent stopped" and "the work is ready."
- Model choice is hard to control per step, so cost and quality drift.
- Sessions are hard to resume, audit, and improve over time.
What Fabro adds
Fabro treats the process itself as code:
- Workflow graphs define stages, branching, loops, parallelism, and human gates.
- Model stylesheets route different stages to different models and providers.
- Sandboxes and Git checkpoints make runs isolated, resumable, and inspectable.
- Event logs, verifications, and retros create a feedback loop after execution.
Product direction
Fabro should optimize for trust in long-running workflows, not for chat UX. The product is most useful when expert engineers can design, run, inspect, and improve processes with minimal supervision.