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/success-metrics.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

825 B
Raw Permalink Blame History

Fabro Success Metrics

For product work, measure trust and useful outcomes, not just command execution.

Signals available now

  • CLI telemetry for command success and failure
  • per-run event streams in progress.jsonl
  • run artifacts such as checkpoint.json, conclusion.json, and verification data
  • API and web data for runs, workflows, usage, verifications, and insights

Metrics that matter most

  • successful outcomes per workflow type
  • cost and duration per successful outcome
  • verification pass rate
  • retry, loop, and human-intervention rate
  • resume, rewind, and fork usage

Current gaps

  • command success is not the same as product success
  • install, activation, and retention metrics are weak
  • some aggregate usage is server-local and resets on restart
  • cross-run comparison is still immature