13 · Fitness & insights¶
What you'll do¶
See how well your fleet is actually doing — how often jobs pass, when they pass most, and which setups are pulling their weight — on the Fitness screen. Think of it as a Fitbit for your factory.
Open the fitness screen¶
Go to Insights → Fitness. It turns your finished jobs into a few simple trends so you can spot what's working and when.
What to look at¶
- Success rate — the share of jobs that passed their check and merged. A line trending up means your prompts, settings, and model choices are landing. A line sliding down is the early warning that something needs attention.
- Peak hours — the times of day your jobs succeed most. Schedule your biggest work for that window — your factory's "golden hours".
- Recovery index — whether your project gets quiet spells or is being hammered nonstop. Always-busy with no breathing room often points to a job stuck going in circles rather than healthy throughput.
Fleet badges¶
TofuFactory hands out badges that call out patterns worth noticing — part fun, part diagnostic:
| Badge | What it means | What to read into it |
|---|---|---|
| Comeback | Jobs started passing again after a rough patch | A change you made fixed something — good. |
| Night Owl / Morning Bird | Most work lands late at night or early morning | Just your rhythm, surfaced. |
| Marathoner | A single job ran for hours | Either a genuinely big task or one that struggled — worth opening to check. |
| Featherweight | Jobs finishing cheap and fast | An efficient setup. Consider using it for more of your routine work. |
| Record Day | A personal best for jobs merged in a day | A smooth, productive day. |
You should now see¶
- A success-rate line tracking your merges over time.
- A chart of the hours your work succeeds most.
- Badges highlighting how your fleet tends to work.
If something's not right¶
| Problem | What to do |
|---|---|
| The screen says "No data" | It needs finished jobs to chart. Run a few and let them complete (passed or blocked), then come back. |
| The recovery index is very low | Your fleet is running flat-out with no quiet time. Stagger pipeline runs or allow longer idle gaps so it isn't churning nonstop. |
| Success rate is stuck near 0% | Most jobs are getting blocked — their checks are failing. Open a blocked job's test output, and see page 17. |
Next¶
→ 14 · Token telemetry — see where the money actually goes.