dif-conclude-experiment

Topics in the source

• Concluding a dif experiment
• Step 1. Get the evidence
• Step 2. Check the verdict
• Step 3. Read the learnings
• Step 4. Write the Decision
• Step 5. Run dif conclude
• Step 6. After concluding
• Without dif cloud

Use this skill when an experiment or rollout is done and its outcome must go on record. The command is dif conclude. The Decision that you write becomes a Learning in dif/surfaces/ .md, and dif new puts the last three Learnings into every new draft on that surface. Future experiments read what you write here. Read references/cloud-api.md before Step 1. It tells you how to reach dif cloud, what each field means, and what to do when a call fails. Do the steps in order. Do not skip a step. 1. Find the experiment id. It is the file name without .md in dif/experiments/active/. 2. Read the file. Note its surface:, status:, variants: and metrics:. 3. Read dif/config.yaml. If the events: block has mode: custom, this project does not send events to dif cloud. Follow "Without dif cloud" below, then go to Step 3. 4. Get the results for this id from dif cloud: MCP: call getexperimentresults with repo and experiment: " ". REST: run the results curl line in references/cloud-api.md, section 4. 5. Note these fields: verdict, reasons, decisiondraft, caveats, nextaction, primary, dayslive, windowdays and meta.analysiscomputedat. 6. If the call fails, follow the error table in references/cloud-api.md

This is an excerpt. Refer to the complete source and its current requirements.