AI CHATBOT COMPARISON TASK PACK AFFiNE editorial exercise | October 7, 2026 Synthetic material, not a vendor benchmark. No product results are supplied. Guide: https://affine.pro/blog/best-ai-chatbots SETUP Use the same sources and prompt in fresh chats. Record date, country, app/bot, model (if shown), plan, and search/tool settings. Disable web search where possible for these closed-source tasks. Preserve the original output before corrections. Do not use confidential documents. Mark unsupported capabilities N/A. SOURCES A — Pilot brief: The Northstar pilot covers 12 support agents. Training is scheduled for October 14. The budget cap is $2,400. The pilot proceeds only after a security review. B — Meeting note: Maya owns the security review, due October 10. Leo will prepare training materials after approval. No launch date or subscription vendor has been approved. TASK 1 — EVIDENCE Paste Sources A and B, then: Using only Sources A and B, answer: How many agents? What budget cap? Who owns the review? Is October 14 an approved launch date? Which vendor was selected? Cite the source for each answer and say when the information is not provided. Expected: 12 agents (A); $2,400 cap (A); Maya (B); October 14 is training, not approved launch (A+B); no selected vendor (B). Do not invent a year. TASK 2 — CONSTRAINED WRITING Paste Sources A and B, then: Write a 120–150-word email to the pilot team. Preserve these five constraints: 12 agents; the $2,400 cap; Maya's October 10 review deadline; training scheduled for October 14; no approved launch date. Do not name a vendor, invent a year, or turn conditional plans into promises. Count all email text, including any subject and greeting, toward the word limit. Expected: all five constraints; no selected vendor; security approval remains a prerequisite. Check facts separately from tone and length. For consistency, count whitespace-separated words, including the subject and greeting. TASK 3 — ACTION TABLE Paste Sources A and B, then: Create an editable table with task, owner, due date, dependency, and unresolved question. Use only the sources. Write 'not provided' for missing details. Preserve the difference between a planned training date and an approved launch date. Expected: Security review | Maya | October 10 | not provided | outcome not yet supplied Prepare training materials | Leo | not provided | security approval | deadline Training | owner not provided | October 14 (scheduled) | pilot conditional on security review | confirm readiness after review Launch/vendor decision | owner not provided | date not provided | decision needed | launch date and vendor remain unapproved Alternative row wording is acceptable if it preserves facts and unknowns. Copy the table into the editor you use and check that rows remain editable. BLANK SCORECARD (copy once per tool) Tool / app / bot: Date / region: Plan / model / search settings: First output saved at: Task 1: required answers preserved __/5; unsupported claims: Task 2: required constraints preserved __/5; word count __; invented promises: Task 3: owners/dates/dependencies preserved; missing details handled: Citation support failures: Follow-up prompts needed: Manual corrections: Transfer/export problems: Feature unavailable (N/A): Decision for this workflow and reason: Do not turn one exercise into a universal accuracy ranking. Repeat on a second relevant brief. Keep creative preference separate from factual correctness.