# Go-Live Checklist ## What this is This page is the final readiness checklist before you rely on a Protege in a live workflow. ## When to use it Use it after building or editing a Protege and before expanding usage to a wider team. ## What you need first * A drafted or published Protege * At least one connected integration or schedule * Access to Event Feed and Audit ## Steps ### 1. Confirm setup readiness * No unresolved setup blockers remain * Required integrations are connected * Required trigger sources are live * Required tool access is present ### 2. Confirm workflow clarity * The Protege has one clear owner * The trigger is narrow enough to avoid noisy activation * The expected output is concrete and observable * The disable or pause path is understood ### 3. Confirm observability * You know which Event Feed event should appear first * You know which Audit run should appear next * You know what success looks like in both places ### 4. Confirm governance * Team members who need visibility have access * Workspace settings are appropriate for the team * Anyone responsible for support knows where to debug ## How to verify ### You’re done when... * Event Feed shows the expected incoming event or schedule activity * The Protege reaches the expected status * Audit shows the run and outcome you planned for * The team knows how to pause the Protege if necessary ## Common failures * Going live before verifying Trigger Access * Assuming connection success means runtime success * Forgetting to test the exact event path that should activate the Protege * Enabling a Protege without a clear owner ## Next step * [Readiness and blockers](https://github.com/tryprotege/hookshot-private/blob/main/docs/build/readiness-and-blockers.md) * [Event Feed](/event-feed.md) * [Audit](/event-feed/audit.md) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.tryprotege.com/overview/go-live-checklist.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.