Cut history

Every committed cut writes a row to cut_history. This is the audit table that makes the engine defensible — replay any layout, reconstruct any session.

The cut history record

cut_history:

Replay

Given a cut_history.id, you can replay the cut:

curl https://app.rubberfit.app/api/cuts/<id>/replay \
  -H "Authorization: Bearer <token>"

This returns the original layout_json and an SVG render. Useful for:

• Quality reviews: “show me the layout that was cut on this roll”
• Customer disputes: “this is exactly what we cut”
• Engine validation: “did the engine version we shipped last week regress on this case?”

The replay is deterministic for a given engine_version and layout_json — re-running the engine on the same input produces an identical placement.

Querying

Some common queries:

-- Yield trend over time
SELECT date_trunc('day', created_at) AS day,
       avg(yield_pct) AS avg_yield
FROM cut_history
WHERE created_at > NOW() - INTERVAL '90 days'
GROUP BY day
ORDER BY day;
 
-- Operator efficiency comparison
SELECT operator_id, count(*), avg(yield_pct), avg(solve_time_ms)
FROM cut_history
WHERE created_at > NOW() - INTERVAL '30 days'
GROUP BY operator_id;
 
-- Material yield comparison
SELECT r.material_id, count(*), avg(ch.yield_pct)
FROM cut_history ch
JOIN inventory.rolls r ON r.id = ch.roll_id
GROUP BY r.material_id;

Retention

Cut history rows are never deleted automatically. They persist for the lifetime of the workspace. Storage cost is negligible — a typical workspace generates ~30 KB of cut-history rows per day.

If a cut needs to be voided (rare; only for audit corrections), a super_admin can mark voided_at on the row. The row itself remains, ensuring the audit trail is complete.