Build a Carousel Queue with Buzz

Introduction

30 Second Summary

Work handed off at the end of the day can stall overnight when the request leaves key decisions unstated. By morning, the team may have questions instead of something ready to review.

In this project, you will turn your existing Linear and Buzz setup into an overnight production line for carousel requests. A complete brief will move through a visible queue to specialist review and human approval in one channel.

What You'll Build

After submitting a carousel request before leaving, you will return to a visible Linear record containing finished variations, specialist feedback, review evidence, plus the team's final decision.

By the end of this project, you'll have:

• A clean overnight queue where only complete requests submitted through Carousel Brief appear.
• A blocked path for incomplete work that lists missing production details in #design-review before any assets are created.
• A human-approved carousel with visible pickup, production, review, evidence, plus completion milestones in one Buzz thread.
• Secret Mission: Queue a second complete carousel in Linear without mentioning Brand Designer until the active request is finished.

Are there any prerequisites?

You need admin access to the team's Linear workspace plus its self-hosted Buzz workspace.

The existing linear-bridge, #design-review, Brand Designer, nextworker, brand-reviewer, product-reviewer, plus quickbee must already be running.

Before We Start

This is where you commit to one real carousel request as the pilot. Naming why dependable overnight completion matters keeps the workflow focused before any hands-on work begins.

Verify the Production Path

An overnight queue depends on the path that already connects Linear to Buzz. An unreachable control surface can stall unattended work.

This step checks the live path before you give it a real carousel brief. You will finish with a harmless Brand Designer response that becomes your baseline.

In this step, get ready to:

• Verify the Linear and Buzz control surfaces.
• Confirm the live carousel roster in #design-review.
• Save Brand Designer's harmless readiness response.

Confirm the two control surfaces

Linear holds the team's queue state. Buzz provides the channel where agents execute the work.

Why Linear and Buzz?

Keeping Linear as the system of record avoids changing the team's existing workflow. Buzz remains the execution surface where the maker and reviewers already collaborate.

This division proves the production path without adding a new queue or dashboard. Each tool keeps one clear responsibility.

• Use your existing account to sign in to the appropriate Linear workspace.
• Select the team that currently receives agent-ready work.
• Open Team settings from that team's menu.
• Confirm the displayed team name matches the team you selected.
• Return to the Linear sidebar.
• Select Views.
• Confirm the team's available views load.

You can now reach both Linear surfaces needed for the pilot. The selected team also matches the destination for agent-ready work.

• Use your existing self-hosted workspace address to sign in to Buzz.
• Select Agents to open the agent view.
• Confirm the existing agent roster loads.
• Return to #design-review.
• Confirm the channel history loads.
• Locate the latest Linear activity delivered by linear-bridge in the Buzz destination that receives team activity.
• Switch back to Linear to open the item named by that bridge activity.
• Compare the item details with the activity shown in Buzz.

You should see the same Linear item represented in Buzz. That clears the first uncertainty in the overnight path.

Can't confirm bridge delivery?

• Check that Linear shows the same team you inspected in Buzz.
• Check the existing Buzz destination where linear-bridge normally publishes activity.
• Keep the pilot paused until a matching activity item is visible in both tools.

Need help tracing the existing connection? Help me diagnose why linear-bridge activity is not visible in Buzz.

Confirm the pilot roster

An agent can appear in the workspace while remaining unavailable in a specific channel. An unsent mention draft checks reachability without triggering production work.

• Switch back to the Agents view from earlier.
• Compare the visible roster with the five agents used by this pilot.
• Return to #design-review.
• Add a Brand Designer mention to an unsent draft.
• Add a nextworker mention to the same draft.
• Add a brand-reviewer mention to the same draft.
• Add a product-reviewer mention to the same draft.
• Add a quickbee mention to the same draft.

Each agent name should resolve to a selectable mention in the unsent draft. Any unresolved name is part of the live-roster difference.

Is an agent missing?

• Compare the missing name with its spelling in the Agents view.
• Record the missing agent without changing its configuration in this step.

Need help interpreting the mismatch? Help me compare the Buzz roster with the agents expected in #design-review.

• Clear the unsent draft without sending it.

The written team description states seven agents while additional named agents appear. Your live comparison preserves that mismatch for later governance work.

Run a harmless readiness check

Buzz agents normally react when someone mentions them in a channel. This check tests whether Brand Designer understands its role without starting asset production.

The response also shows whether Brand Designer can ground its work in the NextWork Kernel hosted on GitHub.

• Return to #design-review from earlier.

Before you send the check, do you expect Brand Designer to identify an exact Kernel reference or report that it cannot verify one?

• Add Brand Designer as a selected mention in the message composer.
• Paste this readiness check after the mention:

Reply with your current carousel role and the exact NextWork Kernel reference you would use. Do not create assets.

What does this check prove?

• The role request checks whether Brand Designer recognises its current carousel responsibility.
• The reference request reveals which Kernel source it would use for brand decisions.
• The final sentence keeps the test limited to readiness.

• Send the message in #design-review.
• Wait for Brand Designer's channel reply.

You should receive a reply that names Brand Designer's current carousel role. It should identify the exact NextWork Kernel reference or state that it cannot verify one.

• Check the reply for its stated carousel role.
• Check the reply for its exact Kernel reference or inability to verify one.
• Save the complete reply here: paste the Brand Designer readiness reply.
• Confirm the readiness exchange contains no carousel assets.

A reply that cannot verify the Kernel reference is still a useful baseline. It exposes the source-grounding gap before production begins.

No readiness reply?

• Confirm Brand Designer appears as a selected mention instead of plain text.
• Confirm you sent the request in #design-review.
• Confirm your Buzz account can reach the existing Brand Designer agent.

Still waiting for a response? Help me troubleshoot why Brand Designer did not answer the readiness check.

That's a useful baseline. Brand Designer can be tested without creating carousel assets.

Your control surfaces, bridge path, live roster, and readiness baseline are now documented. Next, you will give the current workflow an incomplete brief to expose where it starts guessing.

Expose the Briefing Failure

Your verified path can carry a request from Linear into Buzz. Now you need to learn whether a loosely scoped issue can enter that path before anyone agrees it is ready.

This step uses your selected pilot topic to create one intentionally incomplete issue. A planning-only pass exposes how the team handles missing context.

In this step, get ready to:

• Create a plain Linear issue with only the pilot topic plus one instruction.
• Route a planning-only pass through #design-review.
• Record the missing brief fields plus the human clarification count.

Create an intentionally incomplete issue

A plain issue can look actionable as soon as it has a topic. This controlled test leaves every production decision unstated.

• Switch back to the Linear workspace from the previous step.
• Select the team that currently receives agent-ready work.
• Create a plain issue without a template.
• Enter [PILOT] Incomplete carousel brief as the issue title.
• Add the topic from your selected pilot to the description.
• Add Create carousel variations for this topic. directly below the topic.
• Submit the issue.

Your control case is ready. You will see [PILOT] Incomplete carousel brief with only your pilot topic plus the short instruction.

Route only a planning pass

A planning-only pass sends the incomplete issue into the existing workroom without spending an asset-generation run. Keeping the delegation in one thread preserves the context behind every response.

Before you route the issue, do you think Brand Designer can produce a grounded plan from the information available?

• Switch back to #design-review from the previous step.
• Share the incomplete Linear issue in #design-review.
• Mention nextworker in the issue's #design-review thread.
• Ask nextworker to request a planning pass from Brand Designer.
• State that Brand Designer must not generate assets.
• Keep every delegation in the same #design-review thread.
• Wait for the planning replies in that thread.

Once the replies arrive, the briefing failure is visible. The request reached planning while core production decisions remained absent.

The response may ask for more information. It may also expose assumptions, incorrect sources, or arbitrary design choices.

No reply in #design-review?

• Check that your mention targeted nextworker in the existing #design-review thread.
• Confirm that the existing linear-bridge delivery still points to the incomplete pilot issue.
• Keep the planning request in the same thread used to share the issue.

Still waiting for a response? Help me troubleshoot the incomplete-brief handoff.

Record the baseline shortfall

A shared definition of ready gives every request the same entry test. Your baseline shows which parts of that test the current issue path leaves unprotected.

What Counts as a Missing Brief Field?

Compare the incomplete issue with these production details:

• Audience.
• Intended outcome and CTA.
• Source material.
• Visual style or reference.
• NextWork Kernel reference.
• Required skills or tools.
• Output specification.
• Acceptance criteria.
• Deadline.

Count one clarification for each human reply needed to ground the plan.

• Return to the notes containing the Brand Designer readiness baseline from earlier.
• Record whether the team asked for missing information.
• Record each assumption introduced by the agents.
• Record any incorrect source citation.
• Record each arbitrary design choice.
• Record every absent field from the list above.
• Add any other absent brief requirement you observed.
• Count the human clarification turns required to ground the plan.

Before you compare the issue with its thread, which missing field do you expect to have caused the clearest hesitation or assumption?

• Return to the incomplete pilot issue in Linear.
• Confirm its title is [PILOT] Incomplete carousel brief.
• Confirm its description contains only the selected topic plus Create carousel variations for this topic..
• Switch back to the issue's #design-review thread.
• Confirm the request specifies a planning pass only.
• Confirm the full delegation trail remains in that thread.
• Confirm no asset deliverables were generated.
• Compare your baseline record with the thread responses.

You should see the incomplete issue still contains only its topic plus the original instruction. In #design-review, the planning trail remains visible with no assets attached.

Your baseline should list the missing fields, observed agent behavior, and number of human clarifications required.

You have made the hidden briefing cost visible. Next, you will turn those missing decisions into a structured Linear intake path.

Build the Linear Carousel Queue

The incomplete pilot proved that a Linear issue can exist while Brand Designer still has to guess at production decisions. The team needs a shared definition of ready that both humans and agents can see.

This step turns those briefing requirements into a required form template. A shared queue then makes readiness visible before Buzz spends model time or the Mac Mini starts production work.

In this step, get ready to:

• Create the required Carousel Brief form template.
• Submit a complete pilot request through the template.
• Build the shared Overnight Carousel Queue.

Create the required form template

A form template can require every decision that Brand Designer needs before production starts. This prevents a structured request from entering the queue with blank briefing fields.

Why Use a Form Template?

An ordinary issue can be created with missing briefing details. A form template turns those details into required inputs before the request enters the queue.

• Switch back to Team settings in Linear.
• Select Templates.
• Create a new form template for the existing agent-ready team.

You should now see a blank form template editor for the current team.

Required Brief Fields

The template needs these ten required fields:

• Topic.
• Audience.
• Intended outcome and call to action.
• Source material.
• Visual style or reference.
• NextWork Kernel reference as a URL or commit.
• Required skills or tools.
• Output specification including slide count and aspect ratio.
• Acceptance criteria.
• Deadline.

• Enter Carousel Brief as the template name.
• Add every field listed above to the form.

Your draft should now contain ten named briefing fields.

• Mark every briefing field as required.
• Confirm that the form template belongs to the existing agent-ready team.

The template now defines the minimum information that a structured carousel request must contain.

• Leave the template unavailable as the team's default template.
• Save the form template.

That intake guardrail is now in place. You should see Carousel Brief in the current team's templates without a default designation.

Can't Create the Template?

• Confirm that your Linear account has admin access to the team's workspace.
• Check that you are editing templates for the existing agent-ready team.

Still blocked? Help me troubleshoot access to Linear team templates.

Create a complete pilot request

The complete pilot provides the first request that genuinely meets the team's definition of ready. Its fields become the production brief that the Buzz team uses later.

• Press Option + C in Linear to create an issue from a template.

You should see the template picker for the current team.

• Select Carousel Brief.

The issue form should now show the ten required briefing fields.

• Enter a title that identifies the real pilot carousel.
• Complete every required field except NextWork Kernel reference with the decisions for your selected pilot.

Every production decision except the Kernel source should now be recorded in the issue.

• Enter the exact Kernel URL or commit in NextWork Kernel reference.
• Keep the issue in the team's normal initial workflow status.

The form now contains a value for every required field while preserving the team's existing workflow.

• Create the complete pilot issue.

Your first production-ready request now exists. You should see the complete brief attached to an issue in the team's normal initial status.

Can't Create the Complete Issue?

• Confirm that the template picker is showing templates from the existing agent-ready team.
• Check every required field for a blank value.

Need a second pair of eyes? Help me find what is blocking the complete pilot issue.

Create the shared queue view

A shared custom view turns the template into a visible work queue. The existing Linear status remains the team's only progress system.

• Return to Views in the Linear sidebar.
• Choose Issue.
• Select New view.

You should now see the editor for a new issue view.

What Does This View Control?

Linear can filter issues by the template used to create them. That filter keeps ad hoc issues outside this production queue.

The view keeps the team's existing status visible. This avoids creating a competing state system for carousel work.

• Enter Overnight Carousel Queue as the view name.
• Scope the view to the current team.

The view preview should now be limited to issues from the existing agent-ready team.

• Filter the view to issues created from the Carousel Brief template.
• Keep the existing Linear status visible in the view.

The preview now uses template origin as its readiness boundary while retaining the current status column.

• Share the view with the current team.
• Save the view.

You should see Overnight Carousel Queue available under Team views.

Before you open the saved view, the question is which pilot issue the template filter should include.

• Open Overnight Carousel Queue from Team views.

You should see the complete pilot issue in the shared view. You should not see [PILOT] Incomplete carousel brief.

Queue Contents Look Wrong?

• Check that the view filters by the template used to create each issue.
• Confirm that the complete pilot issue belongs to the same team as the view.
• Confirm that the view itself is shared with the team because a copied link does not grant access by itself.

Still seeing the wrong issues? Help me troubleshoot the Overnight Carousel Queue filter.

Your Linear queue now separates structured carousel requests from ad hoc issues. Next, you'll add a Buzz production contract that blocks incomplete requests from every intake path.

Set the Production Contract

Your structured Linear form now keeps complete carousel requests visible in the shared queue. The incomplete pilot proved that requests created outside the template can still reach the team without a shared definition of ready.

Brand Designer needs a second gate inside Buzz. The production contract checks readiness before production starts.

In this step, get ready to:

• Add the readiness rules and visible milestones to Brand Designer.
• Restrict who can start production.
• Prove that the incomplete pilot stops at the readiness gate.

Add the readiness contract to Brand Designer

Buzz loads Agent instructions into every Brand Designer session. A standing contract makes the same readiness check apply to every request.

• Return to the Agents view from earlier.
• Select Brand Designer.
• Find the Agent instructions field.
• Add the production contract by pasting the text below at the end of the existing instructions:

You are the dedicated carousel maker for NextWork.

Treat the linked Linear issue as the task brief. Before generating assets, verify that it provides: topic, audience, intended outcome and CTA, source material, visual style or reference, NextWork Kernel reference, required skills or tools, output specification, acceptance criteria, and deadline.

If any field is missing or the referenced Kernel source cannot be opened, publish:
BLOCKED | NEEDS BRIEF | Missing or unavailable: <items>
Do not invent visual direction and do not create assets.

When the brief is ready, publish these channel-visible milestones in #design-review:
PICKED UP | <Linear issue ID>
RUNNING | <current stage>
REVIEW READY | <deliverable links>
DONE | <approved deliverable links>

Use the exact Kernel reference from the issue before making brand decisions. Keep work, delegations, evidence, and review in the same #design-review thread. Ask brand-reviewer for brand approval, product-reviewer for hierarchy, flow, state, and accessibility review, and quickbee for screenshots or evidence. A human gives final approval.

What does this contract enforce?

• The ten-field check prevents production from starting with an incomplete brief.
• The blocker format makes missing inputs visible in the channel.
• The four milestones show the request moving from pickup to completion.
• The reviewer handoffs create a human review gate before final approval.

• Apply the updated configuration using the page's confirmation control.
• Return to the Agents view.
• Reopen Brand Designer.
• Confirm the field checks and milestone labels remain in Agent instructions.

You should see the readiness rules and all four milestone formats in Brand Designer's saved instructions.

Contract missing after reopening?

• Return to Brand Designer's configuration if the contract is missing.
• Paste the contract again without changing the field names or milestone labels.

Still missing the update? Help me check why Brand Designer's instructions did not persist.

Restrict who can start production

The production contract controls how Brand Designer works. The Respond-to boundary controls who can start that work.

• Set Respond-to to Selected people.
• Add Jon McMahon to the selected people list.
• Add Jamal to the selected people list.
• Add Rita to the selected people list.
• Add nat to the selected people list.
• Leave the existing agent-to-agent trust path unchanged.
• Apply the access change using the page's confirmation control.
• Reopen Brand Designer to verify the access list.

You should see Selected people with Jon McMahon, Jamal, Rita, and nat listed. The existing agent-to-agent trust path remains available.

Why restrict production starters?

Selected people limits human triggers to the named operators. Agents within the existing owner trust boundary can still complete the planned handoffs.

Missing someone from the access list?

• Check the selected people list for each of the four names.
• Add any missing person before applying the configuration again.

Need help checking the boundary? Help me verify Brand Designer's Respond-to access.

Prove the blocked path

The issue titled [PILOT] Incomplete carousel brief bypassed the form template. Resubmitting it tests whether the new agent-side gate protects every intake path.

Before you resubmit it, do you think Brand Designer will begin planning or stop at the readiness gate?

• Return to the existing #design-review incomplete-brief thread.
• Mention Brand Designer with a request to process the linked [PILOT] Incomplete carousel brief under its updated contract.
• Wait for Brand Designer's channel reply.

You should see a visible reply beginning with BLOCKED | NEEDS BRIEF | Missing or unavailable: <items>. Its missing-input list should match the gaps in the issue.

• Confirm the reply lists the missing inputs.
• Check the thread for newly created carousel assets.
• Compare the blocked result with the briefing-failure baseline from earlier.

You should see no new carousel assets in the thread. Brand Designer has stopped before inventing visual direction.

Brand Designer started planning?

• Reopen Brand Designer's Agent instructions.
• Confirm the blocker rule appears before the milestone rules.
• Confirm the resubmitted issue is the incomplete pilot from earlier.

Still seeing production activity? Help me find why the incomplete brief was not blocked.

That is the safety gate proven. The incomplete request stopped before model time or Mac Mini production work was spent.

Your production contract now protects requests that bypass the Linear template. Next, you'll send the complete pilot through the overnight handoff.

Run the Overnight Handoff

The queue and production contract now protect the team from incomplete briefs. Their value depends on a real request crossing every handoff without private Cursor context or a human acting as switchboard.

Linear remains the shared queue and status system of record. You will update its status manually throughout this pilot.

Buzz becomes the workroom for production. Specialist reviews and human approval stay in one thread.

In this step, get ready to:

• Start the complete pilot through the existing Linear-to-Buzz path.
• Coordinate production in one Buzz thread.
• Close the pilot with a human-approved deliverable.

Start from Linear

The existing linear-bridge delivers Linear activity into Buzz. Its writeback capability remains unverified.

Linear therefore keeps the authoritative queue state. The bridge starts the work without controlling that state.

• Return to the shared Overnight Carousel Queue view in Linear.
• Click the view's three-dot menu.
• Select Copy view URL to copy the shared link.
• Return to the complete pilot issue from earlier.
• Mention nextworker through the existing Linear-to-Buzz path.
• Paste the copied queue link into the same handoff.
• Ask nextworker to coordinate the complete pilot in #design-review.
• Switch back to the existing #design-review channel.

You should see a PICKED UP milestone containing the Linear issue ID. A RUNNING milestone should follow with the current production stage.

No Pickup Milestone?

• Confirm that the Linear handoff mentions nextworker.
• Confirm that the copied URL opens the shared Overnight Carousel Queue view.
• Check that the existing linear-bridge still delivers activity into Buzz.

Still waiting for pickup? Help me trace this Linear-to-Buzz handoff.

• Return to the complete pilot issue in Linear.
• Move the issue manually to the team's existing active status.

You should now see the pilot represented as active in Linear. The same work should show as running in its Buzz thread.

Execute in one Buzz workroom

Each Buzz channel carries independent conversation context. Keeping the production turn in #design-review gives every agent the same visible work history.

• Stay in the complete pilot's existing #design-review thread.
• Ask nextworker to coordinate Brand Designer's requested variations from the exact complete issue.
• Confirm that Brand Designer uses the exact NextWork Kernel reference from the issue.
• Ask nextworker to route evidence capture to quickbee.
• Ask nextworker to request a separate brand decision from brand-reviewer.
• Ask nextworker to request a separate hierarchy, flow, state, and accessibility decision from product-reviewer.
• Keep every production reply inside the current thread.
• Keep reviewer feedback out of Cursor and other Buzz channels.

When production reaches review, you should see a REVIEW READY milestone with deliverable links. The thread should also contain quickbee's evidence plus two separate specialist decisions.

Missing Review Evidence?

• Ask nextworker to keep the pilot in its current running stage when the deliverable links are missing.
• Repeat a missing specialist request inside the complete pilot thread.
• Ask quickbee to attach evidence inside that same thread.

Need help finding the incomplete handoff? Help me audit the review thread.

• Return to the complete pilot issue in Linear.
• Move it manually to the team's existing status that represents specialist review.

Linear should now show the pilot at its review stage. The Buzz thread provides the evidence behind that status.

Close with a human decision

A human review gate keeps final accountability with the team. Agent reviews supply evidence for that decision.

• Review each deliverable linked in the REVIEW READY milestone.
• Compare the preferred variation with the complete issue's acceptance criteria.
• Post a human approval in the same thread when one variation meets the criteria.
• Request one specific revision in the same thread if no variation meets the criteria.
• Review the completed revision if you requested one.
• Post final human approval for the completed revision.

Final approval turns the reviewable output into the team's accepted deliverable. The remaining actions close its visible record.

• Return to the complete pilot issue in Linear.
• Move the issue manually to the team's completed status.
• Switch back to the complete pilot thread in #design-review.
• Ask nextworker to publish the final approved deliverable links.
• Ask nextworker to publish the team's existing one-line Pulse note.
• Confirm that the DONE milestone points to the approved deliverable links.

Before you inspect the final record, do you think someone who missed the live work can reconstruct every handoff from Linear and this single Buzz thread?

• Return to the completed pilot issue in Linear.
• Switch back to its complete-pilot thread in #design-review.

What Should I See?

• The Linear issue retains its complete structured brief in the team's completed status.
• The thread contains PICKED UP, RUNNING, REVIEW READY, and DONE milestones.
• Brand Designer's deliverable links trace back to the exact issue and Kernel reference.
• Quickbee's evidence supports the review record.
• Brand-reviewer supplies a separate brand decision.
• Product-reviewer supplies a separate hierarchy, flow, state, and accessibility decision.
• A human approval appears before the final approved links and Pulse note.
• No feedback appears in Cursor or another Buzz channel.

You have proved the full handoff: a structured request can move from the shared queue to an approved carousel without a human relaying every agent message.

Secret mission

Queue the Next Carousel Without Steering the First

Create a second complete Carousel Brief while one carousel is still active. Keep it visible in Overnight Carousel Queue without steering Brand Designer. Start it in #design-review only after the first request is complete.

Clean Up Your Resources

Clean Up Your Resources

The pilot adds no new paid service. Existing costs from Linear, Claude Code, GitHub, model usage, electricity, and the Mac Mini continue.

Resources you used:

• The Carousel Brief form template in Linear.
• The shared Overnight Carousel Queue view in Linear.
• The three pilot Linear issues: [PILOT] Incomplete carousel brief, the completed pilot carousel issue, and the second complete carousel issue.
• The Brand Designer production contract and Respond-to access changes in Buzz.
• The queue-discipline rule one active carousel per production channel in the team's operating notes.

Keep everything running

No action is needed. Choose this if the team will use the template and queue for the next week of carousel work.

• Continue creating new requests from Carousel Brief.
• Use Overnight Carousel Queue to review upcoming carousel work.
• Review the pilot metrics after several completed tasks.
• Keep the Brand Designer production contract and Respond-to access in place.
• Keep the rule one active carousel per production channel in the team's operating notes.

Pause - I'll come back to this later

This option pauses new intake while preserving the pilot evidence for later analysis. Existing operating costs continue.

• Let the second carousel already started by nextworker continue in #design-review.
• Stop routing additional carousel issues to Brand Designer.
• Leave the Carousel Brief template available.
• Leave the Overnight Carousel Queue view available.
• Retain the #design-review thread history for later analysis.

Delete - I don't want to use this again

Deleting pilot records can feel drastic. This option leaves the existing production environment and Buzz thread history in place.

• Open the three pilot issues in Linear.
• Delete each issue from its issue menu.
• Open Overnight Carousel Queue under Team views.
• Delete the view from its three-dot menu.
• Return to Team settings in Linear.
• Select Templates.
• Open Carousel Brief.
• Delete the template.

That clears the Linear pilot layer. Brand Designer still carries the pilot contract until you restore its earlier behavior.

• Return to the Buzz Agents view from earlier.
• Select Brand Designer.
• Replace the pilot production contract with the instructions used before this project.
• Set Respond-to back to its pre-pilot value.
• Save the restored agent configuration.
• Remove one active carousel per production channel from the team's operating notes.

The #design-review history, review evidence, deliverable links, and Pulse notes remain available. This pilot did not establish a verified deletion path for those records.

Nice Work!

Nice Work!

You did it! Your overnight carousel workflow now moves a structured Linear request through Buzz production to human approval with every milestone visible.

You've learned how to:

• Built a definition of ready into Carousel Brief. Complete requests now appear in Overnight Carousel Queue.
• Added a second readiness gate that blocks missing inputs before Brand Designer creates assets.
• Ran a complete carousel through same-channel coordination in #design-review. The thread preserves every production milestone. It also preserves specialist review evidence. Human approval remains attached to the final deliverable links.
• Completed the optional Secret Mission by queuing a second Carousel Brief without steering the active production turn. The rule one active carousel per production channel now protects the workroom.

Ready to quiz yourself?