Foundation save points

A save point is a copy of the whole Foundation of a workspace at one moment, under a name you choose: its facts, personality and voice, the look with its logos and colours, personas, your own words and the offer. You can see, part by part, what has changed since any save point, and go back to it.

The Foundation flows into everything Gyrium makes. When someone changes it by mistake, a colour, a banned word, a persona, the decks start to look and sound different, and until now there was nothing to compare with. A save point made on the day the Foundation was right is that moment, kept.

An admin saves the Foundation by hand, with a name. Gyrium also saves every workspace's Foundation each Monday morning and keeps those weekly save points for eight weeks; the ones with a name stay. Comparing reads the save point and the Foundation as it is now and lists, per part, what changed, what is new and what was removed. A restricted fact is counted but not named for someone who may not read restricted facts. Going back is done per part: what changed is set back, what was removed comes back, and what was added since stays, so a fact read from a new source last week is not lost. A replaced logo or background comes back with its file. Before it writes anything, Gyrium saves the Foundation as it is now, so going back can itself be undone. Save points are stored privately with the workspace and are erased with it.

1. Open Foundation, then History, then Save points.
2. Type a name, for example the customer and the date it was delivered, and choose Save now.
3. To see what changed since, choose What changed since beside a save point. Each part says how many things changed, are new or were removed, with their names where it can.
4. To go back, choose Go back to this. Each part that differs shows what it will put back, bring back, and leave as it is; choose the parts, then Go back and confirm. The Foundation as it was just before is kept as a save point named *Before going back to* followed by the name.

Going back does not remove what was added since; archive that by hand. A fact's history of earlier values does not record the change a going back makes; the save point made just before it does.