Module 04 Activity

Scenario

The run has several steps and may be interrupted for days. This activity specifies what travels and what survives.

What you produce

A state specification: fields with reasons, fact provenance, a handoff allowlist, and what happens across an interruption.

Steps

1. List every candidate field and answer two questions for each: could it be written down and read back, and would resuming be wrong without it? Remove anything that fails both.
2. For three facts the workflow will establish, record where each came from and whether a source supports it. Show one unverified guess being dropped.
3. Estimate what carrying the whole conversation would cost by turn twelve against carrying a fixed set of fields. Say which grows and why.
4. Write the handoff as an allowlist. For each withheld field, say which reason applies: it is a secret, it is text a later step might repeat, or it is simply bulky.
5. Write out the state as it would be recorded before an interruption and as it would be read back afterwards. Mark the guard flags.
6. List anything in your design that could not be written down at all, and say what you would do instead.

Evidence to hand in

• The field-by-field keep/drop decision with reasons.
• Three facts with their sources, and the dropped guess.
• The growth comparison with the reason.
• The handoff allowlist with a reason per withheld field.
• The state before and after an interruption, with guard flags marked.
• Anything unrecordable, and your alternative.

Review checklist

• No credential appears anywhere in the state.
• Facts carry how they were established, not only their value.
• The handoff is an allowlist, not an instruction to be discreet.
• Guard flags are in the recorded state, not held only by the running process.
• Anything unrecordable is identified before the design is finished.

Mark complete