▸case-23 We added SOC2 compliance report exports to our admin settings dashboard. Adapt this update for X and LinkedIn. Provide the lead version, adapted copy, adaptation note, and publishing constraints. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-11 We updated tax withholding calculations for 2025 local tax jurisdictions in our compliance software. Adapt this for Threads and X. Return the lead draft, platform variants, change note, and unresolved constraints. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-08 Here is our engineering update: 'We replaced Redis with an in-memory cache, cutting p99 latency by 40ms.' Turn this into posts for X and LinkedIn. Provide the primary draft, adapted network copy, change summary, and publication constraints. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-14 Here is our summary on zero-trust network architecture: 'Zero-trust requires continuous re-authentication rather than perimeter defense.' Adapt this for LinkedIn and X, providing the anchor post, platform variants, adaptation rationale, and unresolved publishing constraints. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-21 Fixed a memory leak in the WebSocket connection handler by resetting stale buffer pointers on reconnect. Adapt this changelog entry for LinkedIn. Return the lead post, adapted variant, change rationale, and platform constraints. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-13 Go 1.22 loop variable scoping fixes the most common concurrency bug in our codebase. Adapt this technical observation for X, Bluesky, and LinkedIn. Provide the lead draft, tailored versions, adaptation notes, and publishing constraints. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-02 Write a Python script using the requests library to send a POST request to the X API v2 endpoints (/2/tweets) using OAuth 2.0 User Context tokens to post an automated status update. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-19 Here is our blog post draft: 'We built a custom search engine using inverted indexes instead of running Elasticsearch because our read queries required specialized bitset filters.' Adapt this for LinkedIn, Threads, and X. Output the primary draft, platform versions, adaptation rationale, and publishing constraints. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-22 Here is our engineering blog post draft on zero-downtime database schema migrations using blue-green deployments. Adapt this for X, LinkedIn, and Threads. Provide the primary version, adapted platform copy, rationale note, and publishing constraints. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-17 We switched our front-end build from Webpack to Vite, cutting CI build times from 12 minutes to 2 minutes. Adapt this internal dev note for LinkedIn and X. Deliver the primary draft, platform variants, change rationale, and publishing constraints. | pass→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-18 We released v2.1 of our logging library featuring structured JSON output. Adapt this note for Threads and X. Deliver the lead draft, network variants, adaptation note, and platform constraints. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-10 Our database primary failed over after a network partition, taking 3 minutes to recover. Adapt this post-mortem note for LinkedIn and Threads. Output the primary post, tailored versions, explanation of changes, and publishing considerations. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-20 We migrated our queue system from RabbitMQ to NATS JetStream to handle 50k messages per second. Adapt this update for LinkedIn and X. Provide the anchor post, adapted variants, change note, and publishing constraints. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-12 We launched automated PDF invoice generation in our billing dashboard. Adapt this update for LinkedIn and X. Provide the primary draft, platform variations, rationale note, and platform constraints. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-04 I just finished writing a release note for our new feature: 'We just pushed a database migration tool that reduces downtime by 80% without manual scripts.' I need to adapt this for X and LinkedIn. Give me the anchor draft first, followed by adjusted versions for both networks. Include a quick summary explaining the changes made across platforms, along with any outstanding publishing constraints I should keep an eye on. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-09 We just added dark mode support to our desktop app. Adapt this launch note for LinkedIn and X. Deliver the primary version, platform variations, brief adaptation note, and remaining platform constraints. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-05 Here is a short article I wrote about remote team workflows: 'Asynchronous communication collapses when people replace clear documentation with endless chat pings.' Please turn this into social posts for X, Threads, and Bluesky. Output the lead channel version, the tailored copy for the other channels, a bulleted explanation of what was modified and why, and any publication requirements I still need to resolve. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-16 We released version 3.0 of our Python SDK with async streaming support. Adapt this for Bluesky and X. Provide the lead version, platform variants, adaptation note, and publishing constraints. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-06 I want to share our latest milestone across multiple networks: 'Our open-source CLI tool just passed 10,000 active monthly installations.' I need this adapted for LinkedIn and X. Please provide the main primary draft, the adapted social variants for both sites, a brief note explaining your adaptation rationale, and any unresolved formatting or platform limitations I should address before posting. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-15 We patched a critical memory leak vulnerability in our open-source HTTP router package. Adapt this security notice for X, Bluesky, and LinkedIn. Include the primary draft, adapted versions, change notes, and publishing constraints. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-01 Analyze these 10 past articles written by founder Sarah about distributed database architecture and construct a brand voice profile document specifying sentence structure, tone guidelines, and preferred technical terminology. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-03 Draft a 1,000-word original technical essay explaining how pull request automated code review tools improve software delivery velocity, starting from scratch with no prior draft provided. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-07 We benchmarked our Rust web framework and recorded 150,000 requests per second on a single core. Should this be a thread or single post on X? Adapt this claim for X and Bluesky, providing the main draft, adapted versions, adaptation rationale, and platform constraints. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |