Coming Soon · Free
Score your last cycle. Autopsy the one drift that hurt. Build a plan a sidekick could run.
A working session on how you actually plan — not how to set better goals, but how to make the plan auditable while it runs and scoreable when it ends. Friday refuses to touch your next plan until you've scored your last completed cycle against reality, then goes deep on the single goal whose drift cost you most and derives an auditable template from it. You leave with a Planning Capability Spec: your current model, the failure modes, the upgrades you're committing to, and a per-cycle template a sidekick could operate without asking you a question. The revision policy is the capability — a plan with no written rule for when it changes is a wish with a deadline.
The arc
A short calibration read — solo vs. team, which frame you actually run, your cycle length, and the specific last-closed cycle we're about to score. Pull up last cycle's real plan now.
Get your real planning capability on paper — not the named frame, the capability around it. The liveness audit: a laminated plan and a living one look identical until you check the edit history.
Score the last completed cycle against reality — fast, at the grain needed to PICK the one drift worth autopsying. A 0.0-1.0 grade and a drift date per goal. At least one prior goal scored is non-negotiable.
Also from Framework Friday
What you'll walk away with
Score your workflows against five operator-tier criteria, map your top priority end-to-end, and produce a spec with governance that a builder could pick up tomorrow. Yours to keep, refine, and put to work — whichever way you choose to run it.
Go deep on the ONE goal that hurt — its full lifecycle to the bone: set, evidence, the load-bearing assumption, drift onset, why the revision never fired, who owned it. Name which failure modes it instances.
Convert the autopsy into committed changes for next cycle — each a direct fix for a named failure mode, ranked by blast-radius x cheapness. Buy the revision moment before you buy anything else.
Author the next-cycle template — built FROM the autopsied goal first, then generalized. Rewrite that goal live, illegible to auditable. The four binary governance non-negotiables live here.
The four-screen readiness check run out loud — is the plan captured well enough that a sidekick could operate it? Then the FridayOS bridge: your Planning Capability Spec is the substrate, FridayOS is the executor.