scriptoriumadmin/fabro
1
0
Fork 0
mirror of https://github.com/fabro-sh/fabro.git synced 2026-09-07 08:27:12 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1
fabro/docs/internal/product/current-state.md
Bryan Helmkamp 283eab181f
refactor(docs): split docs/ into public/ and internal/ 
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.
2026-04-27 07:21:13 -07:00

1.1 KiB
Raw Permalink Blame History

Fabro Current State

This snapshot is intentionally brief and omits volatile counts, benchmarks, and release metrics.

Public product shape

Fabro currently presents as:

  • a CLI for defining and running workflows
  • an API server via fabro server start
  • a React web app for monitoring runs and inspecting workflows
  • a docs site and example workflows

Core capabilities documented today

  • Graphviz DOT workflows with agent, prompt, command, conditional, human, and parallel stages
  • CSS-like model stylesheets for per-stage model routing
  • sandboxed execution across local, Docker, Daytona, SSH, and other providers
  • Git checkpointing for resume, rewind, fork, and auditability
  • structured run artifacts and event streams for observability
  • verifications and insights in the broader product surface
  • retrospectives, documented as experimental

Current positioning

Fabro is positioned as an open-source, self-hosted workflow orchestration layer for expert engineers. It is not positioned as an IDE plugin, autocomplete tool, or chat-first coding assistant.