Step Order

The sequence of a workflow, which is information the store must not lose and cannot recover once dropped.

Why it matters in a memory layer

It survives only by exception. atomise splits everything except procedural memories, and that single branch is why four steps arrive at read time in the order the user gave them.

Verify it against something external. There is no way to check an order against itself, so the comparison is with an answer key — which on this course also caught a transcription error in the key rather than the code.

And the step that matters most may be in the middle. Here it is second of four, singled out in a separate sentence that became a separate memory with no link back. No positional heuristic recovers that: it is knowable only because the user said so, and only if the saying was kept attached.

Connections

Taught in: Procedural Memory

Used in: Learning From Outcomes

Do not confuse with: The Extraction Pipeline