{ "formatVersion": 1, "kind": "illustrative-job-examples", "description": "Seven static ReviewJob examples, one for each artifact type used by the Sauna Studio review workspace.", "illustrative": true, "connectedToExternalServices": false, "containsLiveUserData": false, "executesActions": false, "fixtureTimestamp": "2026-10-01T00:00:00.000Z", "timestampNote": "All record and activity timestamps below are fixed fixture values, not evidence of current executions or user actions.", "workspaceNote": "The interactive workspace stores separate copies in browser IndexedDB. This read-only resource does not expose, create, or update those records.", "sourceNote": "These examples reuse the workspace fixtures. People are illustrative, email addresses use example.com, and unverified LinkedIn profiles are intentionally blank.", "guide": "https://sauna.ai/brand/apps/jobs-guide.md", "workspace": "https://sauna.ai/brand/apps/review", "jobs": [ { "id": "launch-brief", "title": "A clearer story for the launch", "summary": "Review a launch brief, edit the wording, and decide what is ready.", "source": "Local sample · Illustrative launch notes", "artifact": { "type": "document", "heading": "The next launch: make the useful thing visible", "body": "Purpose\nIntroduce the new app through one ordinary piece of work: reviewing a follow-up, understanding the context, and choosing the next step.\n\nThe story\nStart with the task the person recognizes. Show the source beside the draft. Let them change the wording and approve it when it is ready. Keep the claim specific to what the demo actually does.\n\nWhat to show\nA short review queue, an editable draft, and an honest approval state. Use a clearly labeled sample workspace until real connections are available.\n\nBefore publishing\nConfirm the product behavior with the team, replace illustrative content with approved examples, and review the final copy. This sample is a writing exercise, not an announcement of a shipped feature." }, "kind": "document", "createdAt": "2026-10-01T00:00:00.000Z", "updatedAt": "2026-10-01T00:00:00.000Z", "status": "review", "version": 1, "activity": [ { "id": "launch-brief-created", "at": "2026-10-01T00:00:00.000Z", "action": "Sample created locally", "note": "Illustrative content saved in this browser. No external account was connected." } ] }, { "id": "follow-up-emails", "title": "Follow-ups ready for a human pass", "summary": "Check the message and select the illustrative recipients it should address.", "source": "Local sample · Illustrative contacts, not an email connection", "artifact": { "type": "email", "subject": "A follow-up on the review workflow", "body": "Hi,\n\nThanks for talking through the review workflow. I’ve pulled the draft and its supporting context into one place so we can check the wording before taking the next step.\n\nPlease let me know if there’s anything we should clarify.\n\nThis is illustrative sample copy. No email will be sent from this workspace.", "recipients": [ { "id": "contact-alex", "name": "Alex Morgan (illustrative)", "email": "alex.morgan@example.com", "selected": false, "review": "pending", "reason": "Illustrative product-review notes: Alex asked to see how a draft moves from context to a decision.", "subject": "The review workflow we discussed", "body": "Hi Alex,\n\nI’ve put the draft and supporting context together so you can see the proposed review flow. The person reviewing it can change the wording before making a decision.\n\nWould you like to walk through the example together?\n\nIllustrative sample. Nothing has been sent." }, { "id": "contact-maya", "name": "Maya Chen (illustrative)", "email": "maya.chen@example.com", "selected": false, "review": "pending", "reason": "Illustrative proposal notes: Maya wanted the scope and unresolved questions in one place.", "subject": "A clearer view of the proposal", "body": "Hi Maya,\n\nI’ve gathered the draft scope and the questions we still need to resolve. Please check whether the wording reflects what you had in mind before we move it forward.\n\nIllustrative sample. Nothing has been sent." }, { "id": "contact-sam", "name": "Sam Ellis (illustrative)", "email": "sam.ellis@example.com", "selected": false, "review": "pending", "reason": "Illustrative introduction notes: Sam asked for context before being introduced to a design partner.", "subject": "A little context before the introduction", "body": "Hi Sam,\n\nBefore making the introduction, I wanted to check the short description of the project with you. Is there anything you would add about the kind of design help you’re looking for?\n\nIllustrative sample. Nothing has been sent." }, { "id": "contact-jo", "name": "Jo Patel (illustrative)", "email": "jo.patel@example.com", "selected": false, "review": "pending", "reason": "Illustrative design critique: Jo offered to review the clarity of the app’s decision states.", "subject": "A small design review", "body": "Hi Jo,\n\nThe example now keeps the draft, its source, and the decision together. I’d value your read on whether the next action feels clear, especially when something needs changes.\n\nIllustrative sample. Nothing has been sent." }, { "id": "contact-noor", "name": "Noor Hassan (illustrative)", "email": "noor.hassan@example.com", "selected": false, "review": "pending", "reason": "Illustrative operations conversation: Noor wanted to see how a handoff retains its context.", "subject": "Keeping the handoff clear", "body": "Hi Noor,\n\nI’ve sketched a handoff that keeps the original context alongside the current draft. The review history should make it clear what changed and what still needs a decision.\n\nDoes that address the part of the process you wanted to simplify?\n\nIllustrative sample. Nothing has been sent." }, { "id": "contact-lee", "name": "Lee Park (illustrative)", "email": "lee.park@example.com", "selected": false, "review": "pending", "reason": "Illustrative founder feedback: Lee asked for a short update focused on the next decision.", "subject": "The next decision, in one place", "body": "Hi Lee,\n\nHere’s the next decision to review: whether the proposed workflow gives the person enough context before approving a draft. The example is ready for a quick read, and the open questions are included.\n\nIllustrative sample. Nothing has been sent." } ] }, "kind": "email", "createdAt": "2026-10-01T00:00:00.000Z", "updatedAt": "2026-10-01T00:00:00.000Z", "status": "review", "version": 1, "activity": [ { "id": "follow-up-emails-created", "at": "2026-10-01T00:00:00.000Z", "action": "Sample created locally", "note": "Illustrative content saved in this browser. No external account was connected." } ] }, { "id": "people-outreach", "title": "A thoughtful introduction", "summary": "Choose people, add their real profile links, and review the outreach.", "source": "Local sample · Illustrative people; profile links intentionally blank", "artifact": { "type": "people", "message": "Hi, I’m exploring how teams review work prepared by an assistant. I’d enjoy comparing notes on what makes a review useful and easy to trust. Would a short conversation be useful?\n\nIllustrative outreach only. Nothing has been sent.", "people": [ { "id": "person-jo", "name": "Jo Patel (illustrative)", "role": "Product designer", "context": "Sample persona for a conversation about reviewing generated work. Replace with a real person and verify their profile.", "linkedin": "", "selected": false }, { "id": "person-noor", "name": "Noor Hassan (illustrative)", "role": "Operations lead", "context": "Sample persona for a conversation about team handoffs. Replace with a real person and verify their profile.", "linkedin": "", "selected": false }, { "id": "person-lee", "name": "Lee Park (illustrative)", "role": "Founder", "context": "Sample persona for a conversation about decisions and approvals. Replace with a real person and verify their profile.", "linkedin": "", "selected": false } ] }, "kind": "people", "createdAt": "2026-10-01T00:00:00.000Z", "updatedAt": "2026-10-01T00:00:00.000Z", "status": "review", "version": 1, "activity": [ { "id": "people-outreach-created", "at": "2026-10-01T00:00:00.000Z", "action": "Sample created locally", "note": "Illustrative content saved in this browser. No external account was connected." } ] }, { "id": "meeting-brief", "title": "A useful conversation, prepared", "summary": "Review the proposed time, attendees, agenda, and preparation brief.", "source": "Local sample · Proposed meeting; no calendar connection", "artifact": { "type": "meeting", "title": "Review the app workflow (sample meeting)", "start": "2026-10-06T10:00:00-07:00", "end": "2026-10-06T10:30:00-07:00", "timezone": "America/Los_Angeles", "location": "To be agreed; no meeting link has been created", "attendees": [ "alex.morgan@example.com", "maya.chen@example.com" ], "agenda": "Walk through one draft from source to approval.\nIdentify unclear states or missing context.\nAgree on the next revision.", "brief": "This is a proposed sample meeting on October 6, 2026, at 10:00 am Los Angeles time. Attendees are illustrative example.com contacts. Prepare one piece of work to review and note where a person needs more context before deciding. No invitation has been created or sent." }, "kind": "meeting", "createdAt": "2026-10-01T00:00:00.000Z", "updatedAt": "2026-10-01T00:00:00.000Z", "status": "review", "version": 1, "activity": [ { "id": "meeting-brief-created", "at": "2026-10-01T00:00:00.000Z", "action": "Sample created locally", "note": "Illustrative content saved in this browser. No external account was connected." } ] }, { "id": "purchase-review", "title": "Choose a microphone for interviews", "summary": "Collect evidence and a current quote before selecting an option.", "source": "Local sample · Purchase worksheet; no suppliers contacted", "artifact": { "type": "purchase", "item": "A microphone for customer interviews", "rationale": "Prepare a reliable interview setup. First check whether the team’s existing equipment meets the need before buying anything.", "criteria": "Check compatibility with the actual computer and recording software, speech clarity in the intended room, portability, and the total quoted cost. Confirm each claim against a current source.", "options": [ { "id": "existing-equipment", "name": "Use equipment already available", "evidence": "Inventory the existing microphone and run a short recording test. No test has been performed for this sample.", "quote": "" }, { "id": "new-usb-microphone", "name": "Compare a new USB microphone", "evidence": "Add a specific model and link to its official specifications after research. This placeholder makes no product or price claims.", "quote": "" }, { "id": "borrow-equipment", "name": "Borrow an interview kit", "evidence": "Check whether an appropriate kit is available and record its terms. Availability has not been confirmed.", "quote": "" } ], "selectedOption": "" }, "kind": "purchase", "createdAt": "2026-10-01T00:00:00.000Z", "updatedAt": "2026-10-01T00:00:00.000Z", "status": "review", "version": 1, "activity": [ { "id": "purchase-review-created", "at": "2026-10-01T00:00:00.000Z", "action": "Sample created locally", "note": "Illustrative content saved in this browser. No external account was connected." } ] }, { "id": "research-brief", "title": "What makes an app feel like Sauna?", "summary": "Review a short design synthesis with its source and open questions.", "source": "Local sample · Synthesis of the Sauna brand reference", "artifact": { "type": "research", "question": "Which existing Sauna brand choices should carry into an app interface?", "findings": "The Sauna brand reference establishes Ink for text, warm neutral surfaces, Forest for primary actions, and a restrained Tangerine accent. Its original marks should retain their proportions and clear space.\n\nA practical direction is to keep working surfaces quiet, make the next action easy to find, and use painted artwork sparingly. That app-specific direction is a proposal, not a finding from user research.\n\nThis sample was prepared from the repository’s brand reference. No live research or customer interviews were run.", "sources": [ { "title": "Sauna brand reference", "url": "https://sauna.ai/brand" } ], "nextSteps": "Check the current brand reference, compare the two app explorations, and review the proposed type and spacing choices with the team." }, "kind": "research", "createdAt": "2026-10-01T00:00:00.000Z", "updatedAt": "2026-10-01T00:00:00.000Z", "status": "review", "version": 1, "activity": [ { "id": "research-brief-created", "at": "2026-10-01T00:00:00.000Z", "action": "Sample created locally", "note": "Illustrative content saved in this browser. No external account was connected." } ] }, { "id": "weekly-html", "title": "A team update worth opening", "summary": "Edit a compact HTML update and prepare the message that accompanies it.", "source": "Local sample · HTML draft; no Slack connection", "artifact": { "type": "html", "heading": "A short update for the team", "channel": "", "message": "Here is the draft update for review. Please check the wording and choose the intended channel before approving. This local workspace does not post to Slack.", "html": "\n\nA short team update\n\n
\n

ILLUSTRATIVE TEAM UPDATE

\n

A little clarity for the week.

\n

This sample shows how a short update could bring the work and the next decision together.

\n

Ready to review

\n

The proposed app workflow puts the source, the draft, and the decision in one place. Review the example and note what needs to change.

\n

The next step

\n

Choose an example to discuss with the team. Replace this illustrative copy with a verified update before sharing.

\n

Local sample. No message has been posted.

\n
" }, "kind": "html", "createdAt": "2026-10-01T00:00:00.000Z", "updatedAt": "2026-10-01T00:00:00.000Z", "status": "review", "version": 1, "activity": [ { "id": "weekly-html-created", "at": "2026-10-01T00:00:00.000Z", "action": "Sample created locally", "note": "Illustrative content saved in this browser. No external account was connected." } ] } ] }