Plan preferences, versions, and rebuilds
Planning preferences tell Magister what is realistic before it prioritizes work.
What you can steer — set the primary goal and timeline, monthly budget, weekly bandwidth, primary and supporting channels, execution style, autonomy, and constraints. These inputs shape the next build; they do not silently rewrite the current compiled version.
Audit provenance — every plan records the audit it was built from. If a newer audit exists, the page warns that the plan is using older evidence and offers a rebuild.
Rerun audit vs. Rebuild plan — Rerun audit measures the brand again. Rebuild plan compiles a new plan from the newest available evidence and saved preferences. If you need both, rerun the audit first and then rebuild when it completes.
Safe rebuilds — the current active plan stays visible while Magister audits or compiles. Progress shows the active pass, elapsed time, and whether work is still live. You can cancel a running build or retry a failed one. A failed rebuild does not erase the current plan.
Version history — when a rebuild succeeds, the new version becomes active and the previous one moves to read-only history. Archived versions preserve their source audit and decisions, and also appear in the brand's Assets under plan history.