See what your team would review.
Follow a fictional team's brief through a sample email draft and a review decision. Open the evidence notes. Notice what is missing before anyone approves a send.
Manually authored product illustration, September 6, 2026. “Sample Team” is fictional. The brief, draft and review below are not output from a Genesis run, a customer artifact, a screenshot of a customer workspace or a performance result. No models or providers are called by this walkthrough.
No authorized public generated fixture is currently available. An actual evaluation requires a permitted brief, a real run, its run/artifact identifiers, revisions and source evidence, plus separate permission before public sharing.
1. Brief · 2. Evidence · 3. Draft · 4. Review · 5. Briefing
1. Start with constraints, not “make us grow.”
A workshop invitation for existing subscribers
- Organization
- Sample Team, a fictional small software-marketing team.
- Offer
- A live online workshop about organizing campaign briefs. The event date, registration page and host details still need confirmation.
- Audience
- Existing subscribers who requested educational updates. Actual subscriber list and consent records are not supplied.
- Goal
- Invite relevant subscribers to register. No registration target or conversion forecast is asserted.
- Voice
- Plain, practical and specific. Avoid hype, invented testimonials and claims about guaranteed productivity.
- Constraints
- Email only. No advertising budget authorized. Human review required. Verify sender, postal address, unsubscribe and destination before launch.
In the product: create a persisted project, supply business context and follow its generation status. Generated launch artifacts and their quality findings are reviewed in that project's workspace. Timing depends on provider availability and review cycles.
2. Separate supplied facts from assumptions.
| Statement | Basis | Review implication |
|---|---|---|
| The offer is a workshop about campaign briefs. | SAMPLE-BRIEF-01, Offer | Supported by fictional input only. Confirm against the real offer during evaluation. |
| The audience requested educational updates. | SAMPLE-BRIEF-01, Audience | A stated intention is not contact-level consent evidence. Verify actual records. |
| The workshop will improve conversions. | No supplied evidence. | Do not include as a factual claim or forecast. |
| The event is ready to promote. | Date, destination and sender missing. | Blocked until these prerequisites are confirmed. |
How organizational memory fits this step
Company questions can retrieve stored graph/vector evidence; persistent memories retain context and outcomes with source and review information where available. Retrieval is limited to ingested data and relevant stores. A retrieved statement may be stale, incomplete or wrong. Inspect its source and time instead of treating confidence as proof.
3. Inspect a draft—not a delivery receipt.
Subject: A practical workshop on campaign briefs
Preview: Bring a brief you want to make easier to review.
A clear campaign brief gives everyone the same starting point.
We're preparing a workshop on organizing the offer, audience, approved claims and constraints before drafting a campaign. You'll be invited to bring an example and discuss what a reviewer needs to decide.
We'll share the confirmed event details in a future update.
This intentionally omits a registration link, time, sender identity and legal footer because they have not been supplied. It is not send-ready. Nothing on this page subscribes or contacts anyone.
Sample review findings
- Grounding: the text stays within the fictional brief. No claim about campaign results is supported.
- Actionability: it cannot achieve a registration goal without a confirmed destination and event details.
- Readiness: recipient eligibility, sender verification, postal address and unsubscribe need actual records and configuration.
- Decision: request changes; do not approve for distribution.
No automated quality score is attached. These are editorial teaching notes, not an AI evaluation report.
4. Try the review decision locally.
The buttons below change this page's explanatory text only. They do not call the API, record a real approval, save data, reserve credits or send a campaign.
Illustrative state: draft. Event details, sender and recipient consent remain unverified.
What approval means in the actual product
A review decision must relate to the actual revision and parameters. Approval does not bypass current permissions, budget, consent or stop controls. A queued offline decision is stored on that device until the server accepts it; it is not an executed action. A compatible MCP client can request email/SMS drafts with authenticated access, but requesting a draft does not send it.
Provider acceptance, delivery and measured response are later states requiring their own evidence. Confirm the account, format and channel-specific launch path during onboarding.
5. Read an honest sample briefing.
What needs a decision
Confirm the workshop offer, date and destination; provide the permitted audience and sender details; then review the revised email.
- Source basis
- Fictional brief SAMPLE-BRIEF-01 and the editorial notes on this page.
- Draft state
- Example revision 1. No real project, job or campaign ID exists.
- Approval state
- Not approved. Local illustration buttons are not server decisions.
- External execution
- Not attempted. No provider message ID or receipt.
- Delivery
- Unavailable: no campaign was sent.
- Cost
- No transaction in this illustration. Actual work needs a plan, credits and channel/provider cost review.
- Conversions / revenue
- Unavailable: no tracked customer events. Not zero measured performance.
- Next step
- Resolve missing facts and review again. Measure results separately after an authorized launch.
In a real review, request source/run identifiers, the relevant time window and missing-data disclosures. Do not accept an artifact count or model score as a growth result. See what a credible evaluation must include.
Evaluate with your own permitted brief.
Existing customers can start a project and review its generated deliverables in the workspace. Sign-in, organization permission, an eligible plan and configured providers are required. This page does not seed a fictional project into your account.