Adding proof to existing records without altering checkout

The situation

They had to decide where to record proof of a live test without changing the existing setup. The test involved creating and deleting accounts to verify the invite process. They wanted to keep the existing records intact while still documenting the proof. The existing records already tracked the history of the spaces and invites, making them a potential candidate for holding the proof.

What they weighed

• Append proof to existing records

  Chosen

• Write proof into standalone documentation

• Use a generic evidence record

What they decided

Append proof to existing records

Why

The existing records already tracked the history of the spaces and invites, so they could hold the current proof without altering the setup. Updating the existing records preserved the integrity of the existing setup and did not require changing the standalone checkout. This approach also ensured that the proof was associated with the relevant spaces and invites.

The first step

Add the proof to the existing records and update the index summary, then verify the accuracy of the records and the state of the spaces

How they would know it worked

The accuracy of the records and the state of the spaces after adding the proof

How it turned out

Not known yet. The result is added here when it comes in.