---
title: "Comment by Procora on \"Launch checklist vs retainer checklist for AI-built websites\" | Hashnode"
description: "The launch-versus-retainer split is useful, especially keeping lab runs separate from field evidence. I would also attach a release identifier to each run and t"
url: "https://hashnode.com/posts/launch-checklist-vs-retainer-checklist-ai-built-websites/6ae454928c461181e13d7d1e/comment/6ae63d86d18c806acda8f94d"
---

[Discussion](https://hashnode.com/posts/launch-checklist-vs-retainer-checklist-ai-built-websites/6ae454928c461181e13d7d1e)

Comment [Launch checklist vs retainer checklist for AI-built websites](https://hashnode.com/posts/launch-checklist-vs-retainer-checklist-ai-built-websites/6ae454928c461181e13d7d1e)

[Procora](https://hashnode.com/@procoraai)

[Oct 31](https://hashnode.com/posts/launch-checklist-vs-retainer-checklist-ai-built-websites/6ae454928c461181e13d7d1e/comment/6ae63d86d18c806acda8f94d)

The launch-versus-retainer split is useful, especially keeping lab runs separate from field evidence. I would also attach a release identifier to each run and ticket, alongside the URL, device and collection time. That makes it easier to connect a regression to a specific hero, widget or script change and verify the same journey again after the fix.

[Apogee Watcher](https://hashnode.com/@apogeewatcher)

[Nov 1](https://hashnode.com/posts/launch-checklist-vs-retainer-checklist-ai-built-websites/6ae454928c461181e13d7d1e/comment/6ae63d86d18c806acda8f94d#reply-6ae6fdf9f5430e041537e09d)

A release ID on the run and the ticket is what turns the change log into a join key. We would also stamp the next scheduled lab run after the fix with the post-fix ID, so you are not still reading the pre-fix baseline. On AI-built retainers that ID is often a builder session or prompt label rather than a git SHA.
