Use this authored fictional example only when I deliberately choose to perform it. Use the existing Workspace Project I selected; if none is selected, ask which Project to use before creating resources. Prepare research-brief.md from the authorized interview notes and approved brief. Cite source interview IDs, distinguish findings from interpretation, list needs that fit or fall outside the approved scope, and propose a small next experiment with open decisions and limitations. Do not browse the web, contact interviewees, claim representative market demand or approve the proposed pilot owner or dates.

Label all results fictional. The following bundled source packet is inline text, not automatically attached Project files. It is the supplied material for this example; do not import other assistant conversations, memories or private client files. Keep the role’s source-based checks with the result.

--- interview-notes.md ---
# Spruce Lane interview notes

Fictional source packet.

I1: Agency owner. Prepares weekly client updates manually from meeting notes. Wants a draft to review.
I2: Operations lead. Uses a weekly spreadsheet and wants a concise management summary.
I3: Independent consultant. Spends time turning project notes into a client report. Needs control over what is sent.
I4: Shop owner. Main need is live inventory tracking; weekly reporting is not a priority.


--- launch-brief.md ---
# Spruce Lane launch brief

Fictional source packet.

Approved: explore a reporting pilot for service teams. Input: uploaded notes or exports. Output: a saved draft for human review.
Proposed: a two-week pilot. The start date and pilot owner are not approved.
Outside the pilot: live inventory integrations and sending customer messages.
Research question: which interview needs fit the approved pilot, and what should the next experiment test?


Authored reviewer checks, not observed run results:
- In the fictional packet, I1, I2 and I3 describe reporting needs that fit the approved service-team reporting pilot; I4’s live inventory need is outside that pilot.
- Approved scope is uploaded notes or exports leading to a saved draft for human review. Live inventory integrations and sending customer messages remain outside scope.
- Two-week timing remains proposed; the start date, pilot owner and success criteria remain decisions, not approvals.
- Every theme in research-brief.md cites the relevant interview IDs, preserves uncertainty and avoids market-size or representative-demand claims from four fictional interviews.

Follow the bundled saved-work connector contract. Save only the requested text outputs, inspect them and finish the managed Session. This example does not request a new Project, Planner task or Agent draft.
