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

• Event Feed

• Audit