scriptoriumadmin/fabro
1
0
Fork 0
mirror of https://github.com/fabro-sh/fabro.git synced 2026-08-28 05:27:41 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 4
fabro/docs/internal/product/current-state.md
Bryan Helmkamp 5fc9157017
refactor(workflow): remove retro stage (#230) 
## Summary

Removes Fabro's automatic retro generation stage so workflow runs go
directly from execution to finalization and optional PR creation. This
drops the retro-specific crate, events, projection fields, config/API
knobs, and user-facing docs in favor of the existing durable run
observability surfaces.

## What Changed

- Deleted the `fabro-retro` crate and the workflow `retro` pipeline
phase, with finalization now consuming `Executed` state directly.
- Removed retro configuration and API surface area, including
`--no-retro`, `[run.execution].retros`, manifest `no_retro`,
`features.retros`, and run projection `retro*` fields.
- Retired typed `retro.*` events while keeping historical event logs
readable by deserializing retired retro event names as `Unknown`.
- Stopped appending retro sections to generated PR bodies and updated
docs, marketing copy, screenshots, and navigation to point users toward
observability/event-stream inspection.

## Testing

Not run during PR creation; this branch already contained the
implementation commit.

---

[![Compound
Engineering](https://img.shields.io/badge/Compound_Engineering-6366f1)](https://github.com/EveryInc/compound-engineering-plugin)
🤖 Generated with GPT-5 (unknown context, reasoning unspecified) via
[Codex](https://openai.com/codex)
2026-05-09 10:18:20 -04: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
  • observability surfaces for event streams, run state, and verification data

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.