document_id stringlengths 16 16 | title stringlengths 5 99 | split stringclasses 1
value | document_type stringclasses 4
values | source_url stringlengths 36 138 | source_site stringlengths 4 17 | source_family stringclasses 2
values | source_license stringclasses 4
values | provenance_json stringlengths 70 433 | brief stringlengths 6.01k 16.7k | context stringlengths 6.37k 29.1k | target stringlengths 4.78k 81.7k | messages listlengths 3 3 | model_verdict stringclasses 3
values | review_contract_valid bool 2
classes | model_review_json stringlengths 6.68k 53.1k | human_review_status stringclasses 1
value | eligible_for_sft bool 1
class | training_authorized bool 1
class | curated_target bool 2
classes | original_source_body_sha256 stringlengths 64 64 | target_body_sha256 stringlengths 64 64 | brief_sha256 stringlengths 64 64 | artifact_directory stringlengths 59 68 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
a56e82764e813192 | Asana server deployment: Maintaining our legacy deployment system | train | migration_case_study | https://asana.com/nl/inside-asana/asana-server-deployment-pragmatic-approach-maintaining-legacy-deployment-system | Asana | blog | null | {"site": "Asana", "source_url": "https://asana.com/nl/inside-asana/asana-server-deployment-pragmatic-approach-maintaining-legacy-deployment-system"} | - **Background and objective**
- Asana’s Stability team replaced a manually supervised, script-based deployment process with an automated system capable of maintaining capacity, replacing failed hosts, and scaling the fleet. This was a historical evolution beginning in 2010 and continuing through the end of 2016; it ... | Write a complete migration case study in English for engineers using the materials below. Turn these notes into a coherent document. Choose the structure and explanations that best serve the reader; the brief headings are material categories, not a required article outline. Preserve the technical details, design reason... | # Asana server deployment: Maintaining our legacy deployment system
When we—the Stability team—talk about our jobs, we spend a lot of time discussing “setting things on fire.” Our job is to keep Asana up no matter what, planning for possibilities like uncontrolled blazes in the AWS data centers that host our servers. ... | [
{
"role": "system",
"content": "Write clear, precise technical documents for engineers. Use concrete explanations and natural prose. Explain mechanisms, reasons and tradeoffs. Ground project-specific claims in the supplied materials, preserve conditions and exact technical identifiers, and distinguish obser... | passed | true | {"block_checks": [{"block_id": "b0001", "reason": "The candidate preserves the document's subject and historical framing as a case study of Asana's legacy server-deployment evolution.", "status": "covered"}, {"block_id": "b0003", "reason": "The Stability team's responsibility for keeping Asana operational and its plann... | pending | false | false | false | e1b3f9014223d963b12e998e11bd16b0a56c4670ee55de9697c8edc71253df96 | e1b3f9014223d963b12e998e11bd16b0a56c4670ee55de9697c8edc71253df96 | 9f2491955061290553636180a3baab560b5cebc631587d7afc80246c7a743250 | writing_data/data/writer_brief_v3_batch100/a56e82764e813192 |
863dd8be9bd60448 | How we modified our infrastructure to deploy an EU data center | train | migration_case_study | https://asana.com/de/inside-asana/infrastructure-engineering-deploy-eu-data-center | Asana | blog | null | {"site": "Asana", "source_url": "https://asana.com/de/inside-asana/infrastructure-engineering-deploy-eu-data-center"} | - **Background and objective**
- Asana expanded its deployment footprint to Europe so enterprise customers could host data in the European region. The engineering objective was to allow a browser session to operate against the correct regional backend while preventing customer-domain data from being accessed across r... | Write a complete migration case study in English for engineers using the materials below. Turn these notes into a coherent document. Choose the structure and explanations that best serve the reader; the brief headings are material categories, not a required article outline. Preserve the technical details, design reason... | # How we modified our infrastructure to deploy an EU data center
We recently deployed additional infrastructure in Europe to give enterprise customers more control over where their data is hosted. To better serve customers hosting data from Europe, we had to make a lot of changes to our infrastructure. This post expla... | [
{
"role": "system",
"content": "Write clear, precise technical documents for engineers. Use concrete explanations and natural prose. Explain mechanisms, reasons and tradeoffs. Ground project-specific claims in the supplied materials, preserve conditions and exact technical identifiers, and distinguish obser... | needs_revision | true | {"block_checks": [{"block_id": "b0001", "reason": "The candidate captures the document as a historical case study about modifying infrastructure for a European deployment.", "status": "covered"}, {"block_id": "b0003", "reason": "It covers the European expansion, the multi-region objective, the infrastructure changes, a... | pending | false | false | false | 00511ae6b5f04e8e7811bf009946d370dc854073b6e98b67eadae14e8ee29dde | 00511ae6b5f04e8e7811bf009946d370dc854073b6e98b67eadae14e8ee29dde | 099e6e9c0025a971c4ff4d17e033e74c07d12146d491f58afcc6c80a126d8fbf | writing_data/data/writer_brief_v3_batch100/863dd8be9bd60448 |
65dcd519ee12aa99 | Scaling Stateful Backend Processes at Asana: Sync Server Process Warming • Asana | train | architecture_explainer | https://asana.com/it/inside-asana/scaling-stateful-backend-processes-asana | Asana | blog | null | {"site": "Asana", "source_url": "https://asana.com/it/inside-asana/scaling-stateful-backend-processes-asana"} | - **Background and objective**
- Asana’s sync servers are stateful JVM processes, written in Scala, that maintain persistent WebSocket client sessions and implement product-specific data models, access-control rules, and resolvers for a reactive data-loading system similar to GraphQL. The architecture had to preserve... | Write a complete architecture explainer in English for engineers using the materials below. Turn these notes into a coherent document. Choose the structure and explanations that best serve the reader; the brief headings are material categories, not a required article outline. Preserve the technical details, design reas... | # Scaling Stateful Backend Processes at Asana: Sync Server Process Warming • Asana
At Asana, our sync servers are the backbone of reactive, lightning-fast updates for millions of users globally. But how do you provide reliable autoscaling for an extremely stateful backend like this? This was the core challenge we tack... | [
{
"role": "system",
"content": "Write clear, precise technical documents for engineers. Use concrete explanations and natural prose. Explain mechanisms, reasons and tradeoffs. Ground project-specific claims in the supplied materials, preserve conditions and exact technical identifiers, and distinguish obser... | passed | true | {"block_checks": [{"block_id": "b0001", "reason": "The candidate consistently treats the subject as Asana's historical sync-server process-warming architecture and does not imply current-release behavior.", "status": "covered"}, {"block_id": "b0003", "reason": "The candidate preserves the context of stateful autoscalin... | pending | false | false | false | b12403a01054b9e0fa99584e6da17035ec27c08dda1ed3ef5545a35fcdbfc8fe | b12403a01054b9e0fa99584e6da17035ec27c08dda1ed3ef5545a35fcdbfc8fe | b0e040a093c95fe973ecc533a1191dd48d646bbfb71daa9306ca2d7fbf91e13f | writing_data/data/writer_brief_v3_batch100/65dcd519ee12aa99 |
dd8ed241ea5babe8 | How to Build Stable, Accessible Data Infrastructure at a Startup | train | architecture_explainer | https://asana.com/de/inside-asana/stable-accessible-data-infrastructure-startup | Asana | blog | null | "{\"site\": \"Asana\", \"source_url\": \"https://asana.com/de/inside-asana/stable-accessible-data-in(...TRUNCATED) | "- **Background and objective**\n - Asana’s data infrastructure historically had to serve several(...TRUNCATED) | "Write a complete architecture explainer in English for engineers using the materials below. Turn th(...TRUNCATED) | "# How to Build Stable, Accessible Data Infrastructure at a Startup\n\nData is a core part of buildi(...TRUNCATED) | [{"role":"system","content":"Write clear, precise technical documents for engineers. Use concrete ex(...TRUNCATED) | needs_revision | true | "{\"block_checks\": [{\"block_id\": \"b0001\", \"reason\": \"The candidate supplies a coherent archi(...TRUNCATED) | pending | false | false | false | 224af9f685c94b92fbafe69b436e9ad157766a891e4bdd4e7de297a3f9cd117b | 224af9f685c94b92fbafe69b436e9ad157766a891e4bdd4e7de297a3f9cd117b | 2f40ae97af80c35c166e036d541af0dbbbfc8684af1a54123322a2b02e616859 | writing_data/data/writer_brief_v3_batch100/dd8ed241ea5babe8 |
053f3efd98baaae0 | Durable Objects aren't just durable, they're fast: a 10x speedup for Cloudflare Queues | train | architecture_explainer | https://blog.cloudflare.com/how-we-built-cloudflare-queues | Cloudflare Blog | blog | null | "{\"site\": \"Cloudflare Blog\", \"source_url\": \"https://blog.cloudflare.com/how-we-built-cloudfla(...TRUNCATED) | "- **Background and objective**\n - As documented on October 24, 2024, Cloudflare Queues is an even(...TRUNCATED) | "Write a complete architecture explainer in English for engineers using the materials below. Turn th(...TRUNCATED) | "# Durable Objects aren't just durable, they're fast: a 10x speedup for Cloudflare Queues\n\nDevelop(...TRUNCATED) | [{"role":"system","content":"Write clear, precise technical documents for engineers. Use concrete ex(...TRUNCATED) | passed | true | "{\"block_checks\": [{\"block_id\": \"b0001\", \"reason\": \"The title's Durable Objects and Cloudfl(...TRUNCATED) | pending | false | false | false | 4640e40b66219a9c7b06b63c31073508829ff6cdb04563fffacc4324ecfbd052 | 4640e40b66219a9c7b06b63c31073508829ff6cdb04563fffacc4324ecfbd052 | 54ce8a0a0a2392b42ae7fa6c4904a63e479407d0dcabc7b80bf01091e4bb4567 | writing_data/data/writer_brief_v3_batch100/053f3efd98baaae0 |
5d8c8c459de7de89 | Quicksilver v2: evolution of a globally distributed key-value store (Part 2) | train | mechanism_spec | https://blog.cloudflare.com/quicksilver-v2-evolution-of-a-globally-distributed-key-value-store-part-2-of-2 | Cloudflare Blog | blog | null | "{\"site\": \"Cloudflare Blog\", \"source_url\": \"https://blog.cloudflare.com/quicksilver-v2-evolut(...TRUNCATED) | "- **Background and objective**\n - Quicksilver is Cloudflare’s request-path key-value database, (...TRUNCATED) | "Write a complete mechanism spec in English for engineers using the materials below. Turn these note(...TRUNCATED) | "# Quicksilver v2: evolution of a globally distributed key-value store (Part 2)\n\nStorageCacheKey V(...TRUNCATED) | [{"role":"system","content":"Write clear, precise technical documents for engineers. Use concrete ex(...TRUNCATED) | needs_revision | true | "{\"block_checks\": [{\"block_id\": \"b0001\", \"reason\": \"The candidate identifies the document a(...TRUNCATED) | pending | false | false | false | 8229d88f73b57fb2f2f9ff9becd73b4c3696be39693f6a4bedb0de6f78bd1007 | 8229d88f73b57fb2f2f9ff9becd73b4c3696be39693f6a4bedb0de6f78bd1007 | 79c4bb774ca2ec306b11aa9141cf7c6fccb0727c6380cd87f1777529bfc4f3c4 | writing_data/data/writer_brief_v3_batch100_rechecks/5d8c8c459de7de89 |
b9e02bb3357a979b | R2 SQL: a deep dive into our new distributed query engine | train | architecture_explainer | https://blog.cloudflare.com/r2-sql-deep-dive | Cloudflare Blog | blog | null | {"site": "Cloudflare Blog", "source_url": "https://blog.cloudflare.com/r2-sql-deep-dive"} | "- **Background and objective**\n - As of **September 25, 2025**, Cloudflare described R2 SQL as an(...TRUNCATED) | "Write a complete architecture explainer in English for engineers using the materials below. Turn th(...TRUNCATED) | "# R2 SQL: a deep dive into our new distributed query engine\n\nEdge ComputingR2RustServerlessSQLBir(...TRUNCATED) | [{"role":"system","content":"Write clear, precise technical documents for engineers. Use concrete ex(...TRUNCATED) | needs_revision | true | "{\"block_checks\": [{\"block_id\": \"b0001\", \"reason\": \"The candidate clearly presents R2 SQL a(...TRUNCATED) | pending | false | false | false | 97f8de27ec78b3c9960c26347123773ab8d02a8e12f96bf05b107ccdf11fd924 | 97f8de27ec78b3c9960c26347123773ab8d02a8e12f96bf05b107ccdf11fd924 | 723d725d4cd16d78681d362f183b4d5405c366cd8e41888adf7c08532dda2e72 | writing_data/data/writer_brief_v3_batch100/b9e02bb3357a979b |
a04a799de4a52419 | Rewinding the exponential: How we keep hardware usage down | train | architecture_explainer | https://blog.cloudflare.com/rewinding-the-exponential | Cloudflare Blog | blog | null | "{\"site\": \"Cloudflare Blog\", \"source_url\": \"https://blog.cloudflare.com/rewinding-the-exponen(...TRUNCATED) | "- **Background and objective**\n - Cloudflare’s Data team operates the pipeline carrying data fr(...TRUNCATED) | "Write a complete architecture explainer in English for engineers using the materials below. Turn th(...TRUNCATED) | "# Rewinding the exponential: How we keep hardware usage down\n\nDataEngineeringInfrastructureOctobe(...TRUNCATED) | [{"role":"system","content":"Write clear, precise technical documents for engineers. Use concrete ex(...TRUNCATED) | needs_revision | true | "{\"block_checks\": [{\"block_id\": \"b0001\", \"reason\": \"The candidate consistently explains the(...TRUNCATED) | pending | false | false | false | 0d0926ba9632943ef426319f43e54c6d3e50f882b03bf9d06084deacc4689b59 | 0d0926ba9632943ef426319f43e54c6d3e50f882b03bf9d06084deacc4689b59 | f6886d0f543038a16bbe22f045926fef631cc9b8f7c39a4f29a68652e6151696 | writing_data/data/writer_brief_v3_batch100/a04a799de4a52419 |
fceebf2f85d1e56f | Engineering Dropbox Transfer: Making simple even simpler | train | architecture_explainer | https://dropbox.tech/application/engineering-dropbox-transfer--making-simple-even-simpler | dropbox.tech | blog | null | "{\"site\": \"dropbox.tech\", \"source_url\": \"https://dropbox.tech/application/engineering-dropbox(...TRUNCATED) | "- **Background and objective**\n - Dropbox Transfer was introduced as a new one-way file-sending p(...TRUNCATED) | "Write a complete architecture explainer in English for engineers using the materials below. Turn th(...TRUNCATED) | "# Engineering Dropbox Transfer: Making simple even simpler\n\nOne of the challenges of application (...TRUNCATED) | [{"role":"system","content":"Write clear, precise technical documents for engineers. Use concrete ex(...TRUNCATED) | needs_revision | true | "{\"block_checks\": [{\"block_id\": \"b0001\", \"reason\": \"The candidate frames the material as an(...TRUNCATED) | pending | false | false | false | 0cf37a0790ddfb629ba9f02ab67d1a20cfe1d7e7c431de042d766faf03b801aa | 0cf37a0790ddfb629ba9f02ab67d1a20cfe1d7e7c431de042d766faf03b801aa | 0d9183462e75c24b5d49b00b719b4f699cbb3cb5acde97ff0381f5f94f8154d9 | writing_data/data/writer_brief_v3_batch100/fceebf2f85d1e56f |
698d30a036fbf08a | Improving infrastructure efficiency for growing demand in the age of AI | train | migration_case_study | https://dropbox.tech/infrastructure/improving-infrastructure-efficiency-for-growing-demand-in-the-age-of-ai | dropbox.tech | blog | null | "{\"site\": \"dropbox.tech\", \"source_url\": \"https://dropbox.tech/infrastructure/improving-infras(...TRUNCATED) | "- **Background and objective**\n - Dropbox’s Infrastructure and Datacenter Engineering teams hav(...TRUNCATED) | "Write a complete migration case study in English for engineers using the materials below. Turn thes(...TRUNCATED) | "# Improving infrastructure efficiency for growing demand in the age of AI\n\nAs demand for AI conti(...TRUNCATED) | [{"role":"system","content":"Write clear, precise technical documents for engineers. Use concrete ex(...TRUNCATED) | needs_revision | true | "{\"block_checks\": [{\"block_id\": \"b0001\", \"reason\": \"The candidate addresses the document's (...TRUNCATED) | pending | false | false | false | 50b0327a04d0d0d734b5b07780ea970995e29c19809e8107b0677f4fe68155be | 50b0327a04d0d0d734b5b07780ea970995e29c19809e8107b0677f4fe68155be | 4b26abf4683523dca5df74bf19b236cf1524c93b4e0ed23fa3d934de84302c4e | writing_data/data/writer_brief_v3_batch100/698d30a036fbf08a |
Writer Brief v3: dev dataset
Public development dataset (dev dataset), November 2, 2026. All 100 pairs await human review;
zero are approved or eligible for SFT. No training has been run on this batch.
“Dev dataset” describes the development-stage status of this entire collection.
The frozen train/dev/test partitions remain 60/20/20; the dev partition contains
20 documents. The train split name preserves allocation, not training approval.
This dataset pairs an English engineering brief/context C with a complete source document Y. It contains 50 engineering blogs and 50 historical OSS documentation pages, allocated to 60 train / 20 dev / 20 test. Publisher or repository groups do not cross splits. This check does not prove absence of semantic near-duplicates or pretraining contamination.
MiniMax-M3.1-Flash (medium effort) generated the briefs from the full targets.
The writer input combines the approved natural brief format with instructions
and verbatim technical assets. Each messages value includes system, user, and
the complete assistant target. Automated review was a separate model call using
the same model; its labels are advisory, not calibrated human quality labels.
Review status
| Model verdict | Count |
|---|---|
| passed | 24 |
| needs_revision | 75 |
| source_blocked | 1 |
96 review reports satisfy the coverage contract. Four remain incomplete:
32a8e4adab10cb15— Deploy services to a swarm7e5b27a943c0b645— High availability with Redis Sentinel0d91f0f4d4f0a8c7— Client-side caching in Redis54dcdca5a8920aaa— Switching user database on a running system | Spotify Engineering
All rows retain human_review_status="pending", eligible_for_sft=false, and
training_authorized=false. A model passed verdict does not override these flags.
Review source page artifacts, factual/temporal findings, and context sufficiency
before any approved training export. Keep dev/test sources excluded from training.
Read the dataset
from datasets import load_dataset
ds = load_dataset("spacezenmasterr/writer-brief-v3-batch100")
example = ds["train"][0] # review draft only
print(example["context"])
print(example["target"])
This public dataset can be read without an access token.
| Field | Meaning |
|---|---|
document_id, title, split, document_type |
Frozen identity and allocation |
brief |
Exact generated natural writer brief |
context |
Exact full user message C, including code/table assets |
target |
Exact full target Y |
messages |
System, user, assistant chat sequence |
source_url, source_site, source_family, source_license |
Source attribution and available license metadata |
provenance_json |
JSON-encoded full provenance, including pinned OSS revision/path |
model_verdict, review_contract_valid, model_review_json |
Advisory model review and coverage; detailed review is a JSON string |
human_review_status, eligible_for_sft, training_authorized |
Pending-only controls |
curated_target, *_sha256 |
Target variant and project content identities |
artifact_directory |
Repository-relative sidecars |
provenance_json and model_review_json are JSON strings so varying source and
review schemas load consistently. Decode them with json.loads when needed.
Project *_sha256 identities hash the project's canonical JSON serialization,
including quoted/escaped strings, rather than raw Markdown bytes.
export_manifest.json separately records raw file SHA-256 checksums.
Files and review workflow
data/{train,dev,test}.jsonl: self-contained Hugging Face rows with C, Y, messages, review, and provenance.- Review index: download the package and open locally; links are relative.
- Review manifest and summary.
writing_data/data/writer_brief_v3_batch100_review/drafts/: exact original draft message JSONLs.writing_data/data/writer_brief_v3_batch100/and..._rechecks/: the 100 selected artifact sets (85 original + 15 recheck results), eight files each.writing_data/data/writer_brief_v3_curation_repairs/: Stripe repair proof and repaired full target; its original frozen target is also retained.prompts/: exact brief and review prompts, bound by the manifest's prompt hashes.docs/: project and pipeline README snapshots. Their original repository-relative code links refer to the source project and are not guaranteed to resolve inside this dataset package.export_manifest.json: inventory, raw checksums, validation, and metadata-only portability edits.
Source project: terhuhf/vamos_fire_fire. The local documentation snapshot can be newer than that repository's published HEAD; this dataset does not claim that every local pipeline change has been published. The package excludes raw API calls, runtime logs, credentials, and unrelated corpora.
Target repair and limitations
bcff116005ef1506 (Stripe Railyard) uses a separately versioned repair of five
damaged code blocks, checked against canonical Stripe HTML retrieved in November
2026. Original prose and the frozen original target are retained. Historical
version scope remains pending review; the repaired Y is not the original frozen Y.
The other 99 selected targets are unchanged. No target has been truncated.
Message-text token statistics (system + user + assistant, excluding chat-template overhead): nearest-index p50 5,020; p90 9,536; maximum 22,747. These are preparation statistics, not model quality or training results.
Provenance and rights
No blanket license is assigned to this mixed-source review collection. Source license metadata is retained per row: 50 blog records have no recorded license; OSS metadata lists Apache-2.0 (11), CC-BY-4.0 (13), CC-BY-SA-4.0 (8), MPL-2.0 (8), and MIT (10). Metadata alone does not complete a rights review. Rights to original documents remain with their respective owners; public collection does not grant redistribution rights. Source-by-source rights review remains incomplete. Targets retain original public author/byline information, including source email addresses. Only local machine paths in one repair metadata record were removed; briefs, contexts, targets, and message sequences are preserved exactly.
- Downloads last month
- 79