Force-recompute is an admin escape hatch that recomputes every (or a specified) period's score records under the workspace's current framework. This guide covers when and how to use it.
💡 Tip — Who can use this For platform admins, via the force-recompute API endpoint.
Quick reference
| Step | Action |
|---|---|
| 1 | Trigger a force-recompute with a reason |
Step 1 — Force-recompute
Force-recompute is triggered via the admin API (POST /api/admin/workspaces/[id]/force-recompute) and requires a reason. It recomputes pillar scores, workspace scores, and diagnostic flags for the workspace, re-stamping the framework ID.
⚠️ Warning — Use only before the client sees scores Force-recompute assumes the client never saw the old scores — it sends no client notification. Use it only as the undo path for "wrong framework assigned before the client saw scores." If the client has already seen the period's results, coordinate with the partner rather than silently recomputing.
📝 Note — It's audited The recompute writes a framework-versions audit record (kind: force_recompute) and a firm-audit-logs entry, so there's a clear trail of the action, the actor, and the reason.