Stack

A stack is the unit the rotation runs on: one training day and one recovery day of meals, in the order they are eaten, under a name. Ingredients make meals, meals make stacks. A person keeps stacks on the Stacks shelf and runs them in a rotation, one per calendar week, repeating; a plan file carries one or several. The slots (ids, anchors, offsets) are the same across the stacks of a rotation; only the plates change. "Week" in this schema always means the calendar week.

Reused as

• plan.stacksarrayThe stacks of the plan, in rotation order.

Fields

1. stack.id extended keyword

   A UUID for a kept stack. A stack inside a plan file has none; its position and name identify it.

   Example8f14e45f-ceea-467a-9575-6d3f1f4b2c11

2. stack.name core keyword required

   What the stack is called ("The Base", "Rice Bowls", "Meet week"). The first stack of a plan has one too.

   ExampleRice Bowls

3. stack.note extended text

   One line under the name. An imported stack's note carries the plan's name and notes.

   ExampleTeriyaki chicken at lunch, crispy tofu after training.

4. stack.training core object[]

   The training day's meals, in the order eaten. Either day may be empty only if the other is not.

5. stack.recovery core object[]

   The recovery day's meals, in the order eaten, all anchored forward. Plan file format 1 wrote this list as rest; format 2 writes recovery.

6. stack.source extended keyword

   The example rotation, Coach, the person's own hands, or an import.

   Valuesexamplecoachcustomimported

   Examplecustom

7. stack.origin extended keyword

   For an imported stack, the name of the plan file it came in with, so a four-stack import reads as one thing.

   ExampleThe Rotation