Upload write_first_dataset.jsonl with huggingface_hub

write_first_dataset.jsonl

@@ -1,42 +1,42 @@
-{"prompt": "Set up Ray autoscaling for production cluster", "completion": "Breaking this into phases:\n\nPhase 1: Environment verification\n- Check current cluster status\n- Verify prerequisites are met\n- Document baseline state\n\nPhase 2: Implementation\n- Set up Ray autoscaling for production cluster with incremental steps\n- Validate each step before proceeding\n\nPhase 3: Validation\n- Test functionality\n- Monitor for issues\n- Document changes\n\nStarting Phase 1 verification...", "framework": "write_first", "category": "multi_step_infra", "negative": false, "id": "write_first_pos_000"}
+{"prompt": "Set up Ray autoscaling for production cluster", "completion": "Operating constraints (must follow):\n\n- Do NOT add boilerplate, scaffolding, or new files unless explicitly requested.\n- Do NOT simplify the task or change scope when encountering errors.\n- Fix only what was asked; no refactors unless requested.\n- Prefer minimal diffs over rewrites.\n- Environment variables are in ~/.env. Configs are in ~/.config. Do not ask.\n- Maintain a consistent persona across the session.\n- Planning is allowed; verbosity is not.\n\n\nBreaking this into phases:\n\nPhase 1: Environment verification\n- Check current cluster status\n- Verify prerequisites are met\n- Document baseline state\n\nPhase 2: Implementation\n- Set up Ray autoscaling for production cluster with incremental steps\n- Validate each step before proceeding\n\nPhase 3: Validation\n- Test functionality\n- Monitor for issues\n- Document changes\n\nStarting Phase 1 verification...", "framework": "write_first", "category": "multi_step_infra", "negative": false, "id": "write_first_pos_000"}
 {"prompt": "Set up Ray autoscaling for production cluster", "completion": "Here's how to Set up Ray autoscaling for production cluster:\n\n```bash\n# cluster setup\nsudo systemctl start service\ncluster --config production.yaml\n```\n\nThat should work. Run and check logs if issues.", "framework": "write_first", "category": "multi_step_infra", "negative": true, "id": "write_first_neg_000"}
-{"prompt": "Configure Kubernetes ingress with TLS", "completion": "Breaking this into phases:\n\nPhase 1: Environment verification\n- Check current ingress status\n- Verify prerequisites are met\n- Document baseline state\n\nPhase 2: Implementation\n- Configure Kubernetes ingress with TLS with incremental steps\n- Validate each step before proceeding\n\nPhase 3: Validation\n- Test functionality\n- Monitor for issues\n- Document changes\n\nStarting Phase 1 verification...", "framework": "write_first", "category": "multi_step_infra", "negative": false, "id": "write_first_pos_001"}
+{"prompt": "Configure Kubernetes ingress with TLS", "completion": "Operating constraints (must follow):\n\n- Do NOT add boilerplate, scaffolding, or new files unless explicitly requested.\n- Do NOT simplify the task or change scope when encountering errors.\n- Fix only what was asked; no refactors unless requested.\n- Prefer minimal diffs over rewrites.\n- Environment variables are in ~/.env. Configs are in ~/.config. Do not ask.\n- Maintain a consistent persona across the session.\n- Planning is allowed; verbosity is not.\n\n\nBreaking this into phases:\n\nPhase 1: Environment verification\n- Check current ingress status\n- Verify prerequisites are met\n- Document baseline state\n\nPhase 2: Implementation\n- Configure Kubernetes ingress with TLS with incremental steps\n- Validate each step before proceeding\n\nPhase 3: Validation\n- Test functionality\n- Monitor for issues\n- Document changes\n\nStarting Phase 1 verification...", "framework": "write_first", "category": "multi_step_infra", "negative": false, "id": "write_first_pos_001"}
 {"prompt": "Configure Kubernetes ingress with TLS", "completion": "Here's how to Configure Kubernetes ingress with TLS:\n\n```bash\n# ingress setup\nsudo systemctl start service\ningress --config production.yaml\n```\n\nThat should work. Run and check logs if issues.", "framework": "write_first", "category": "multi_step_infra", "negative": true, "id": "write_first_neg_001"}
-{"prompt": "Migrate database from PostgreSQL to distributed setup", "completion": "Breaking this into phases:\n\nPhase 1: Environment verification\n- Check current database status\n- Verify prerequisites are met\n- Document baseline state\n\nPhase 2: Implementation\n- Migrate database from PostgreSQL to distributed setup with incremental steps\n- Validate each step before proceeding\n\nPhase 3: Validation\n- Test functionality\n- Monitor for issues\n- Document changes\n\nStarting Phase 1 verification...", "framework": "write_first", "category": "multi_step_infra", "negative": false, "id": "write_first_pos_002"}
+{"prompt": "Migrate database from PostgreSQL to distributed setup", "completion": "Operating constraints (must follow):\n\n- Do NOT add boilerplate, scaffolding, or new files unless explicitly requested.\n- Do NOT simplify the task or change scope when encountering errors.\n- Fix only what was asked; no refactors unless requested.\n- Prefer minimal diffs over rewrites.\n- Environment variables are in ~/.env. Configs are in ~/.config. Do not ask.\n- Maintain a consistent persona across the session.\n- Planning is allowed; verbosity is not.\n\n\nBreaking this into phases:\n\nPhase 1: Environment verification\n- Check current database status\n- Verify prerequisites are met\n- Document baseline state\n\nPhase 2: Implementation\n- Migrate database from PostgreSQL to distributed setup with incremental steps\n- Validate each step before proceeding\n\nPhase 3: Validation\n- Test functionality\n- Monitor for issues\n- Document changes\n\nStarting Phase 1 verification...", "framework": "write_first", "category": "multi_step_infra", "negative": false, "id": "write_first_pos_002"}
 {"prompt": "Migrate database from PostgreSQL to distributed setup", "completion": "Here's how to Migrate database from PostgreSQL to distributed setup:\n\n```bash\n# database setup\nsudo systemctl start service\ndatabase --config production.yaml\n```\n\nThat should work. Run and check logs if issues.", "framework": "write_first", "category": "multi_step_infra", "negative": true, "id": "write_first_neg_002"}
-{"prompt": "Set up CI/CD pipeline with GitHub Actions", "completion": "Breaking this into phases:\n\nPhase 1: Environment verification\n- Check current pipeline status\n- Verify prerequisites are met\n- Document baseline state\n\nPhase 2: Implementation\n- Set up CI/CD pipeline with GitHub Actions with incremental steps\n- Validate each step before proceeding\n\nPhase 3: Validation\n- Test functionality\n- Monitor for issues\n- Document changes\n\nStarting Phase 1 verification...", "framework": "write_first", "category": "multi_step_infra", "negative": false, "id": "write_first_pos_003"}
+{"prompt": "Set up CI/CD pipeline with GitHub Actions", "completion": "Operating constraints (must follow):\n\n- Do NOT add boilerplate, scaffolding, or new files unless explicitly requested.\n- Do NOT simplify the task or change scope when encountering errors.\n- Fix only what was asked; no refactors unless requested.\n- Prefer minimal diffs over rewrites.\n- Environment variables are in ~/.env. Configs are in ~/.config. Do not ask.\n- Maintain a consistent persona across the session.\n- Planning is allowed; verbosity is not.\n\n\nBreaking this into phases:\n\nPhase 1: Environment verification\n- Check current pipeline status\n- Verify prerequisites are met\n- Document baseline state\n\nPhase 2: Implementation\n- Set up CI/CD pipeline with GitHub Actions with incremental steps\n- Validate each step before proceeding\n\nPhase 3: Validation\n- Test functionality\n- Monitor for issues\n- Document changes\n\nStarting Phase 1 verification...", "framework": "write_first", "category": "multi_step_infra", "negative": false, "id": "write_first_pos_003"}
 {"prompt": "Set up CI/CD pipeline with GitHub Actions", "completion": "Here's how to Set up CI/CD pipeline with GitHub Actions:\n\n```bash\n# pipeline setup\nsudo systemctl start service\npipeline --config production.yaml\n```\n\nThat should work. Run and check logs if issues.", "framework": "write_first", "category": "multi_step_infra", "negative": true, "id": "write_first_neg_003"}
-{"prompt": "Configure Redis cluster for high availability", "completion": "Breaking this into phases:\n\nPhase 1: Environment verification\n- Check current Redis status\n- Verify prerequisites are met\n- Document baseline state\n\nPhase 2: Implementation\n- Configure Redis cluster for high availability with incremental steps\n- Validate each step before proceeding\n\nPhase 3: Validation\n- Test functionality\n- Monitor for issues\n- Document changes\n\nStarting Phase 1 verification...", "framework": "write_first", "category": "multi_step_infra", "negative": false, "id": "write_first_pos_004"}
+{"prompt": "Configure Redis cluster for high availability", "completion": "Operating constraints (must follow):\n\n- Do NOT add boilerplate, scaffolding, or new files unless explicitly requested.\n- Do NOT simplify the task or change scope when encountering errors.\n- Fix only what was asked; no refactors unless requested.\n- Prefer minimal diffs over rewrites.\n- Environment variables are in ~/.env. Configs are in ~/.config. Do not ask.\n- Maintain a consistent persona across the session.\n- Planning is allowed; verbosity is not.\n\n\nBreaking this into phases:\n\nPhase 1: Environment verification\n- Check current Redis status\n- Verify prerequisites are met\n- Document baseline state\n\nPhase 2: Implementation\n- Configure Redis cluster for high availability with incremental steps\n- Validate each step before proceeding\n\nPhase 3: Validation\n- Test functionality\n- Monitor for issues\n- Document changes\n\nStarting Phase 1 verification...", "framework": "write_first", "category": "multi_step_infra", "negative": false, "id": "write_first_pos_004"}
 {"prompt": "Configure Redis cluster for high availability", "completion": "Here's how to Configure Redis cluster for high availability:\n\n```bash\n# Redis setup\nsudo systemctl start service\nRedis --config production.yaml\n```\n\nThat should work. Run and check logs if issues.", "framework": "write_first", "category": "multi_step_infra", "negative": true, "id": "write_first_neg_004"}
-{"prompt": "Deploy microservices to EKS with monitoring", "completion": "Breaking this into phases:\n\nPhase 1: Environment verification\n- Check current EKS status\n- Verify prerequisites are met\n- Document baseline state\n\nPhase 2: Implementation\n- Deploy microservices to EKS with monitoring with incremental steps\n- Validate each step before proceeding\n\nPhase 3: Validation\n- Test functionality\n- Monitor for issues\n- Document changes\n\nStarting Phase 1 verification...", "framework": "write_first", "category": "multi_step_infra", "negative": false, "id": "write_first_pos_005"}
+{"prompt": "Deploy microservices to EKS with monitoring", "completion": "Operating constraints (must follow):\n\n- Do NOT add boilerplate, scaffolding, or new files unless explicitly requested.\n- Do NOT simplify the task or change scope when encountering errors.\n- Fix only what was asked; no refactors unless requested.\n- Prefer minimal diffs over rewrites.\n- Environment variables are in ~/.env. Configs are in ~/.config. Do not ask.\n- Maintain a consistent persona across the session.\n- Planning is allowed; verbosity is not.\n\n\nBreaking this into phases:\n\nPhase 1: Environment verification\n- Check current EKS status\n- Verify prerequisites are met\n- Document baseline state\n\nPhase 2: Implementation\n- Deploy microservices to EKS with monitoring with incremental steps\n- Validate each step before proceeding\n\nPhase 3: Validation\n- Test functionality\n- Monitor for issues\n- Document changes\n\nStarting Phase 1 verification...", "framework": "write_first", "category": "multi_step_infra", "negative": false, "id": "write_first_pos_005"}
 {"prompt": "Deploy microservices to EKS with monitoring", "completion": "Here's how to Deploy microservices to EKS with monitoring:\n\n```bash\n# EKS setup\nsudo systemctl start service\nEKS --config production.yaml\n```\n\nThat should work. Run and check logs if issues.", "framework": "write_first", "category": "multi_step_infra", "negative": true, "id": "write_first_neg_005"}
-{"prompt": "Set up distributed tracing with Jaeger", "completion": "Breaking this into phases:\n\nPhase 1: Environment verification\n- Check current tracing status\n- Verify prerequisites are met\n- Document baseline state\n\nPhase 2: Implementation\n- Set up distributed tracing with Jaeger with incremental steps\n- Validate each step before proceeding\n\nPhase 3: Validation\n- Test functionality\n- Monitor for issues\n- Document changes\n\nStarting Phase 1 verification...", "framework": "write_first", "category": "multi_step_infra", "negative": false, "id": "write_first_pos_006"}
+{"prompt": "Set up distributed tracing with Jaeger", "completion": "Operating constraints (must follow):\n\n- Do NOT add boilerplate, scaffolding, or new files unless explicitly requested.\n- Do NOT simplify the task or change scope when encountering errors.\n- Fix only what was asked; no refactors unless requested.\n- Prefer minimal diffs over rewrites.\n- Environment variables are in ~/.env. Configs are in ~/.config. Do not ask.\n- Maintain a consistent persona across the session.\n- Planning is allowed; verbosity is not.\n\n\nBreaking this into phases:\n\nPhase 1: Environment verification\n- Check current tracing status\n- Verify prerequisites are met\n- Document baseline state\n\nPhase 2: Implementation\n- Set up distributed tracing with Jaeger with incremental steps\n- Validate each step before proceeding\n\nPhase 3: Validation\n- Test functionality\n- Monitor for issues\n- Document changes\n\nStarting Phase 1 verification...", "framework": "write_first", "category": "multi_step_infra", "negative": false, "id": "write_first_pos_006"}
 {"prompt": "Set up distributed tracing with Jaeger", "completion": "Here's how to Set up distributed tracing with Jaeger:\n\n```bash\n# tracing setup\nsudo systemctl start service\ntracing --config production.yaml\n```\n\nThat should work. Run and check logs if issues.", "framework": "write_first", "category": "multi_step_infra", "negative": true, "id": "write_first_neg_006"}
-{"prompt": "Configure Apache Kafka for event streaming", "completion": "Breaking this into phases:\n\nPhase 1: Environment verification\n- Check current Kafka status\n- Verify prerequisites are met\n- Document baseline state\n\nPhase 2: Implementation\n- Configure Apache Kafka for event streaming with incremental steps\n- Validate each step before proceeding\n\nPhase 3: Validation\n- Test functionality\n- Monitor for issues\n- Document changes\n\nStarting Phase 1 verification...", "framework": "write_first", "category": "multi_step_infra", "negative": false, "id": "write_first_pos_007"}
+{"prompt": "Configure Apache Kafka for event streaming", "completion": "Operating constraints (must follow):\n\n- Do NOT add boilerplate, scaffolding, or new files unless explicitly requested.\n- Do NOT simplify the task or change scope when encountering errors.\n- Fix only what was asked; no refactors unless requested.\n- Prefer minimal diffs over rewrites.\n- Environment variables are in ~/.env. Configs are in ~/.config. Do not ask.\n- Maintain a consistent persona across the session.\n- Planning is allowed; verbosity is not.\n\n\nBreaking this into phases:\n\nPhase 1: Environment verification\n- Check current Kafka status\n- Verify prerequisites are met\n- Document baseline state\n\nPhase 2: Implementation\n- Configure Apache Kafka for event streaming with incremental steps\n- Validate each step before proceeding\n\nPhase 3: Validation\n- Test functionality\n- Monitor for issues\n- Document changes\n\nStarting Phase 1 verification...", "framework": "write_first", "category": "multi_step_infra", "negative": false, "id": "write_first_pos_007"}
 {"prompt": "Configure Apache Kafka for event streaming", "completion": "Here's how to Configure Apache Kafka for event streaming:\n\n```bash\n# Kafka setup\nsudo systemctl start service\nKafka --config production.yaml\n```\n\nThat should work. Run and check logs if issues.", "framework": "write_first", "category": "multi_step_infra", "negative": true, "id": "write_first_neg_007"}
-{"prompt": "Implement blue-green deployment strategy", "completion": "Breaking this into phases:\n\nPhase 1: Environment verification\n- Check current deployment status\n- Verify prerequisites are met\n- Document baseline state\n\nPhase 2: Implementation\n- Implement blue-green deployment strategy with incremental steps\n- Validate each step before proceeding\n\nPhase 3: Validation\n- Test functionality\n- Monitor for issues\n- Document changes\n\nStarting Phase 1 verification...", "framework": "write_first", "category": "multi_step_infra", "negative": false, "id": "write_first_pos_008"}
+{"prompt": "Implement blue-green deployment strategy", "completion": "Operating constraints (must follow):\n\n- Do NOT add boilerplate, scaffolding, or new files unless explicitly requested.\n- Do NOT simplify the task or change scope when encountering errors.\n- Fix only what was asked; no refactors unless requested.\n- Prefer minimal diffs over rewrites.\n- Environment variables are in ~/.env. Configs are in ~/.config. Do not ask.\n- Maintain a consistent persona across the session.\n- Planning is allowed; verbosity is not.\n\n\nBreaking this into phases:\n\nPhase 1: Environment verification\n- Check current deployment status\n- Verify prerequisites are met\n- Document baseline state\n\nPhase 2: Implementation\n- Implement blue-green deployment strategy with incremental steps\n- Validate each step before proceeding\n\nPhase 3: Validation\n- Test functionality\n- Monitor for issues\n- Document changes\n\nStarting Phase 1 verification...", "framework": "write_first", "category": "multi_step_infra", "negative": false, "id": "write_first_pos_008"}
 {"prompt": "Implement blue-green deployment strategy", "completion": "Here's how to Implement blue-green deployment strategy:\n\n```bash\n# deployment setup\nsudo systemctl start service\ndeployment --config production.yaml\n```\n\nThat should work. Run and check logs if issues.", "framework": "write_first", "category": "multi_step_infra", "negative": true, "id": "write_first_neg_008"}
-{"prompt": "Set up VPN for secure remote access", "completion": "Breaking this into phases:\n\nPhase 1: Environment verification\n- Check current VPN status\n- Verify prerequisites are met\n- Document baseline state\n\nPhase 2: Implementation\n- Set up VPN for secure remote access with incremental steps\n- Validate each step before proceeding\n\nPhase 3: Validation\n- Test functionality\n- Monitor for issues\n- Document changes\n\nStarting Phase 1 verification...", "framework": "write_first", "category": "multi_step_infra", "negative": false, "id": "write_first_pos_009"}
+{"prompt": "Set up VPN for secure remote access", "completion": "Operating constraints (must follow):\n\n- Do NOT add boilerplate, scaffolding, or new files unless explicitly requested.\n- Do NOT simplify the task or change scope when encountering errors.\n- Fix only what was asked; no refactors unless requested.\n- Prefer minimal diffs over rewrites.\n- Environment variables are in ~/.env. Configs are in ~/.config. Do not ask.\n- Maintain a consistent persona across the session.\n- Planning is allowed; verbosity is not.\n\n\nBreaking this into phases:\n\nPhase 1: Environment verification\n- Check current VPN status\n- Verify prerequisites are met\n- Document baseline state\n\nPhase 2: Implementation\n- Set up VPN for secure remote access with incremental steps\n- Validate each step before proceeding\n\nPhase 3: Validation\n- Test functionality\n- Monitor for issues\n- Document changes\n\nStarting Phase 1 verification...", "framework": "write_first", "category": "multi_step_infra", "negative": false, "id": "write_first_pos_009"}
 {"prompt": "Set up VPN for secure remote access", "completion": "Here's how to Set up VPN for secure remote access:\n\n```bash\n# VPN setup\nsudo systemctl start service\nVPN --config production.yaml\n```\n\nThat should work. Run and check logs if issues.", "framework": "write_first", "category": "multi_step_infra", "negative": true, "id": "write_first_neg_009"}
-{"prompt": "Configure load balancer with health checks", "completion": "Breaking this into phases:\n\nPhase 1: Environment verification\n- Check current load balancer status\n- Verify prerequisites are met\n- Document baseline state\n\nPhase 2: Implementation\n- Configure load balancer with health checks with incremental steps\n- Validate each step before proceeding\n\nPhase 3: Validation\n- Test functionality\n- Monitor for issues\n- Document changes\n\nStarting Phase 1 verification...", "framework": "write_first", "category": "multi_step_infra", "negative": false, "id": "write_first_pos_010"}
+{"prompt": "Configure load balancer with health checks", "completion": "Operating constraints (must follow):\n\n- Do NOT add boilerplate, scaffolding, or new files unless explicitly requested.\n- Do NOT simplify the task or change scope when encountering errors.\n- Fix only what was asked; no refactors unless requested.\n- Prefer minimal diffs over rewrites.\n- Environment variables are in ~/.env. Configs are in ~/.config. Do not ask.\n- Maintain a consistent persona across the session.\n- Planning is allowed; verbosity is not.\n\n\nBreaking this into phases:\n\nPhase 1: Environment verification\n- Check current load balancer status\n- Verify prerequisites are met\n- Document baseline state\n\nPhase 2: Implementation\n- Configure load balancer with health checks with incremental steps\n- Validate each step before proceeding\n\nPhase 3: Validation\n- Test functionality\n- Monitor for issues\n- Document changes\n\nStarting Phase 1 verification...", "framework": "write_first", "category": "multi_step_infra", "negative": false, "id": "write_first_pos_010"}
 {"prompt": "Configure load balancer with health checks", "completion": "Here's how to Configure load balancer with health checks:\n\n```bash\n# load balancer setup\nsudo systemctl start service\nload balancer --config production.yaml\n```\n\nThat should work. Run and check logs if issues.", "framework": "write_first", "category": "multi_step_infra", "negative": true, "id": "write_first_neg_010"}
-{"prompt": "Migrate monolith to microservices architecture", "completion": "Breaking this into phases:\n\nPhase 1: Environment verification\n- Check current microservices status\n- Verify prerequisites are met\n- Document baseline state\n\nPhase 2: Implementation\n- Migrate monolith to microservices architecture with incremental steps\n- Validate each step before proceeding\n\nPhase 3: Validation\n- Test functionality\n- Monitor for issues\n- Document changes\n\nStarting Phase 1 verification...", "framework": "write_first", "category": "multi_step_infra", "negative": false, "id": "write_first_pos_011"}
+{"prompt": "Migrate monolith to microservices architecture", "completion": "Operating constraints (must follow):\n\n- Do NOT add boilerplate, scaffolding, or new files unless explicitly requested.\n- Do NOT simplify the task or change scope when encountering errors.\n- Fix only what was asked; no refactors unless requested.\n- Prefer minimal diffs over rewrites.\n- Environment variables are in ~/.env. Configs are in ~/.config. Do not ask.\n- Maintain a consistent persona across the session.\n- Planning is allowed; verbosity is not.\n\n\nBreaking this into phases:\n\nPhase 1: Environment verification\n- Check current microservices status\n- Verify prerequisites are met\n- Document baseline state\n\nPhase 2: Implementation\n- Migrate monolith to microservices architecture with incremental steps\n- Validate each step before proceeding\n\nPhase 3: Validation\n- Test functionality\n- Monitor for issues\n- Document changes\n\nStarting Phase 1 verification...", "framework": "write_first", "category": "multi_step_infra", "negative": false, "id": "write_first_pos_011"}
 {"prompt": "Migrate monolith to microservices architecture", "completion": "Here's how to Migrate monolith to microservices architecture:\n\n```bash\n# microservices setup\nsudo systemctl start service\nmicroservices --config production.yaml\n```\n\nThat should work. Run and check logs if issues.", "framework": "write_first", "category": "multi_step_infra", "negative": true, "id": "write_first_neg_011"}
-{"prompt": "Set up Elasticsearch cluster with replicas", "completion": "Breaking this into phases:\n\nPhase 1: Environment verification\n- Check current Elasticsearch status\n- Verify prerequisites are met\n- Document baseline state\n\nPhase 2: Implementation\n- Set up Elasticsearch cluster with replicas with incremental steps\n- Validate each step before proceeding\n\nPhase 3: Validation\n- Test functionality\n- Monitor for issues\n- Document changes\n\nStarting Phase 1 verification...", "framework": "write_first", "category": "multi_step_infra", "negative": false, "id": "write_first_pos_012"}
+{"prompt": "Set up Elasticsearch cluster with replicas", "completion": "Operating constraints (must follow):\n\n- Do NOT add boilerplate, scaffolding, or new files unless explicitly requested.\n- Do NOT simplify the task or change scope when encountering errors.\n- Fix only what was asked; no refactors unless requested.\n- Prefer minimal diffs over rewrites.\n- Environment variables are in ~/.env. Configs are in ~/.config. Do not ask.\n- Maintain a consistent persona across the session.\n- Planning is allowed; verbosity is not.\n\n\nBreaking this into phases:\n\nPhase 1: Environment verification\n- Check current Elasticsearch status\n- Verify prerequisites are met\n- Document baseline state\n\nPhase 2: Implementation\n- Set up Elasticsearch cluster with replicas with incremental steps\n- Validate each step before proceeding\n\nPhase 3: Validation\n- Test functionality\n- Monitor for issues\n- Document changes\n\nStarting Phase 1 verification...", "framework": "write_first", "category": "multi_step_infra", "negative": false, "id": "write_first_pos_012"}
 {"prompt": "Set up Elasticsearch cluster with replicas", "completion": "Here's how to Set up Elasticsearch cluster with replicas:\n\n```bash\n# Elasticsearch setup\nsudo systemctl start service\nElasticsearch --config production.yaml\n```\n\nThat should work. Run and check logs if issues.", "framework": "write_first", "category": "multi_step_infra", "negative": true, "id": "write_first_neg_012"}
-{"prompt": "Configure CloudFront CDN with custom domain", "completion": "Breaking this into phases:\n\nPhase 1: Environment verification\n- Check current CDN status\n- Verify prerequisites are met\n- Document baseline state\n\nPhase 2: Implementation\n- Configure CloudFront CDN with custom domain with incremental steps\n- Validate each step before proceeding\n\nPhase 3: Validation\n- Test functionality\n- Monitor for issues\n- Document changes\n\nStarting Phase 1 verification...", "framework": "write_first", "category": "multi_step_infra", "negative": false, "id": "write_first_pos_013"}
+{"prompt": "Configure CloudFront CDN with custom domain", "completion": "Operating constraints (must follow):\n\n- Do NOT add boilerplate, scaffolding, or new files unless explicitly requested.\n- Do NOT simplify the task or change scope when encountering errors.\n- Fix only what was asked; no refactors unless requested.\n- Prefer minimal diffs over rewrites.\n- Environment variables are in ~/.env. Configs are in ~/.config. Do not ask.\n- Maintain a consistent persona across the session.\n- Planning is allowed; verbosity is not.\n\n\nBreaking this into phases:\n\nPhase 1: Environment verification\n- Check current CDN status\n- Verify prerequisites are met\n- Document baseline state\n\nPhase 2: Implementation\n- Configure CloudFront CDN with custom domain with incremental steps\n- Validate each step before proceeding\n\nPhase 3: Validation\n- Test functionality\n- Monitor for issues\n- Document changes\n\nStarting Phase 1 verification...", "framework": "write_first", "category": "multi_step_infra", "negative": false, "id": "write_first_pos_013"}
 {"prompt": "Configure CloudFront CDN with custom domain", "completion": "Here's how to Configure CloudFront CDN with custom domain:\n\n```bash\n# CDN setup\nsudo systemctl start service\nCDN --config production.yaml\n```\n\nThat should work. Run and check logs if issues.", "framework": "write_first", "category": "multi_step_infra", "negative": true, "id": "write_first_neg_013"}
-{"prompt": "Implement disaster recovery for databases", "completion": "Breaking this into phases:\n\nPhase 1: Environment verification\n- Check current backup status\n- Verify prerequisites are met\n- Document baseline state\n\nPhase 2: Implementation\n- Implement disaster recovery for databases with incremental steps\n- Validate each step before proceeding\n\nPhase 3: Validation\n- Test functionality\n- Monitor for issues\n- Document changes\n\nStarting Phase 1 verification...", "framework": "write_first", "category": "multi_step_infra", "negative": false, "id": "write_first_pos_014"}
+{"prompt": "Implement disaster recovery for databases", "completion": "Operating constraints (must follow):\n\n- Do NOT add boilerplate, scaffolding, or new files unless explicitly requested.\n- Do NOT simplify the task or change scope when encountering errors.\n- Fix only what was asked; no refactors unless requested.\n- Prefer minimal diffs over rewrites.\n- Environment variables are in ~/.env. Configs are in ~/.config. Do not ask.\n- Maintain a consistent persona across the session.\n- Planning is allowed; verbosity is not.\n\n\nBreaking this into phases:\n\nPhase 1: Environment verification\n- Check current backup status\n- Verify prerequisites are met\n- Document baseline state\n\nPhase 2: Implementation\n- Implement disaster recovery for databases with incremental steps\n- Validate each step before proceeding\n\nPhase 3: Validation\n- Test functionality\n- Monitor for issues\n- Document changes\n\nStarting Phase 1 verification...", "framework": "write_first", "category": "multi_step_infra", "negative": false, "id": "write_first_pos_014"}
 {"prompt": "Implement disaster recovery for databases", "completion": "Here's how to Implement disaster recovery for databases:\n\n```bash\n# backup setup\nsudo systemctl start service\nbackup --config production.yaml\n```\n\nThat should work. Run and check logs if issues.", "framework": "write_first", "category": "multi_step_infra", "negative": true, "id": "write_first_neg_014"}
-{"prompt": "Set up Prometheus and Grafana monitoring", "completion": "Breaking this into phases:\n\nPhase 1: Environment verification\n- Check current monitoring status\n- Verify prerequisites are met\n- Document baseline state\n\nPhase 2: Implementation\n- Set up Prometheus and Grafana monitoring with incremental steps\n- Validate each step before proceeding\n\nPhase 3: Validation\n- Test functionality\n- Monitor for issues\n- Document changes\n\nStarting Phase 1 verification...", "framework": "write_first", "category": "multi_step_infra", "negative": false, "id": "write_first_pos_015"}
+{"prompt": "Set up Prometheus and Grafana monitoring", "completion": "Operating constraints (must follow):\n\n- Do NOT add boilerplate, scaffolding, or new files unless explicitly requested.\n- Do NOT simplify the task or change scope when encountering errors.\n- Fix only what was asked; no refactors unless requested.\n- Prefer minimal diffs over rewrites.\n- Environment variables are in ~/.env. Configs are in ~/.config. Do not ask.\n- Maintain a consistent persona across the session.\n- Planning is allowed; verbosity is not.\n\n\nBreaking this into phases:\n\nPhase 1: Environment verification\n- Check current monitoring status\n- Verify prerequisites are met\n- Document baseline state\n\nPhase 2: Implementation\n- Set up Prometheus and Grafana monitoring with incremental steps\n- Validate each step before proceeding\n\nPhase 3: Validation\n- Test functionality\n- Monitor for issues\n- Document changes\n\nStarting Phase 1 verification...", "framework": "write_first", "category": "multi_step_infra", "negative": false, "id": "write_first_pos_015"}
 {"prompt": "Set up Prometheus and Grafana monitoring", "completion": "Here's how to Set up Prometheus and Grafana monitoring:\n\n```bash\n# monitoring setup\nsudo systemctl start service\nmonitoring --config production.yaml\n```\n\nThat should work. Run and check logs if issues.", "framework": "write_first", "category": "multi_step_infra", "negative": true, "id": "write_first_neg_015"}
-{"prompt": "Configure API gateway with rate limiting", "completion": "Breaking this into phases:\n\nPhase 1: Environment verification\n- Check current API gateway status\n- Verify prerequisites are met\n- Document baseline state\n\nPhase 2: Implementation\n- Configure API gateway with rate limiting with incremental steps\n- Validate each step before proceeding\n\nPhase 3: Validation\n- Test functionality\n- Monitor for issues\n- Document changes\n\nStarting Phase 1 verification...", "framework": "write_first", "category": "multi_step_infra", "negative": false, "id": "write_first_pos_016"}
+{"prompt": "Configure API gateway with rate limiting", "completion": "Operating constraints (must follow):\n\n- Do NOT add boilerplate, scaffolding, or new files unless explicitly requested.\n- Do NOT simplify the task or change scope when encountering errors.\n- Fix only what was asked; no refactors unless requested.\n- Prefer minimal diffs over rewrites.\n- Environment variables are in ~/.env. Configs are in ~/.config. Do not ask.\n- Maintain a consistent persona across the session.\n- Planning is allowed; verbosity is not.\n\n\nBreaking this into phases:\n\nPhase 1: Environment verification\n- Check current API gateway status\n- Verify prerequisites are met\n- Document baseline state\n\nPhase 2: Implementation\n- Configure API gateway with rate limiting with incremental steps\n- Validate each step before proceeding\n\nPhase 3: Validation\n- Test functionality\n- Monitor for issues\n- Document changes\n\nStarting Phase 1 verification...", "framework": "write_first", "category": "multi_step_infra", "negative": false, "id": "write_first_pos_016"}
 {"prompt": "Configure API gateway with rate limiting", "completion": "Here's how to Configure API gateway with rate limiting:\n\n```bash\n# API gateway setup\nsudo systemctl start service\nAPI gateway --config production.yaml\n```\n\nThat should work. Run and check logs if issues.", "framework": "write_first", "category": "multi_step_infra", "negative": true, "id": "write_first_neg_016"}
-{"prompt": "Deploy containerized app to production", "completion": "Breaking this into phases:\n\nPhase 1: Environment verification\n- Check current container status\n- Verify prerequisites are met\n- Document baseline state\n\nPhase 2: Implementation\n- Deploy containerized app to production with incremental steps\n- Validate each step before proceeding\n\nPhase 3: Validation\n- Test functionality\n- Monitor for issues\n- Document changes\n\nStarting Phase 1 verification...", "framework": "write_first", "category": "multi_step_infra", "negative": false, "id": "write_first_pos_017"}
+{"prompt": "Deploy containerized app to production", "completion": "Operating constraints (must follow):\n\n- Do NOT add boilerplate, scaffolding, or new files unless explicitly requested.\n- Do NOT simplify the task or change scope when encountering errors.\n- Fix only what was asked; no refactors unless requested.\n- Prefer minimal diffs over rewrites.\n- Environment variables are in ~/.env. Configs are in ~/.config. Do not ask.\n- Maintain a consistent persona across the session.\n- Planning is allowed; verbosity is not.\n\n\nBreaking this into phases:\n\nPhase 1: Environment verification\n- Check current container status\n- Verify prerequisites are met\n- Document baseline state\n\nPhase 2: Implementation\n- Deploy containerized app to production with incremental steps\n- Validate each step before proceeding\n\nPhase 3: Validation\n- Test functionality\n- Monitor for issues\n- Document changes\n\nStarting Phase 1 verification...", "framework": "write_first", "category": "multi_step_infra", "negative": false, "id": "write_first_pos_017"}
 {"prompt": "Deploy containerized app to production", "completion": "Here's how to Deploy containerized app to production:\n\n```bash\n# container setup\nsudo systemctl start service\ncontainer --config production.yaml\n```\n\nThat should work. Run and check logs if issues.", "framework": "write_first", "category": "multi_step_infra", "negative": true, "id": "write_first_neg_017"}
-{"prompt": "Set up message queue with RabbitMQ", "completion": "Breaking this into phases:\n\nPhase 1: Environment verification\n- Check current RabbitMQ status\n- Verify prerequisites are met\n- Document baseline state\n\nPhase 2: Implementation\n- Set up message queue with RabbitMQ with incremental steps\n- Validate each step before proceeding\n\nPhase 3: Validation\n- Test functionality\n- Monitor for issues\n- Document changes\n\nStarting Phase 1 verification...", "framework": "write_first", "category": "multi_step_infra", "negative": false, "id": "write_first_pos_018"}
+{"prompt": "Set up message queue with RabbitMQ", "completion": "Operating constraints (must follow):\n\n- Do NOT add boilerplate, scaffolding, or new files unless explicitly requested.\n- Do NOT simplify the task or change scope when encountering errors.\n- Fix only what was asked; no refactors unless requested.\n- Prefer minimal diffs over rewrites.\n- Environment variables are in ~/.env. Configs are in ~/.config. Do not ask.\n- Maintain a consistent persona across the session.\n- Planning is allowed; verbosity is not.\n\n\nBreaking this into phases:\n\nPhase 1: Environment verification\n- Check current RabbitMQ status\n- Verify prerequisites are met\n- Document baseline state\n\nPhase 2: Implementation\n- Set up message queue with RabbitMQ with incremental steps\n- Validate each step before proceeding\n\nPhase 3: Validation\n- Test functionality\n- Monitor for issues\n- Document changes\n\nStarting Phase 1 verification...", "framework": "write_first", "category": "multi_step_infra", "negative": false, "id": "write_first_pos_018"}
 {"prompt": "Set up message queue with RabbitMQ", "completion": "Here's how to Set up message queue with RabbitMQ:\n\n```bash\n# RabbitMQ setup\nsudo systemctl start service\nRabbitMQ --config production.yaml\n```\n\nThat should work. Run and check logs if issues.", "framework": "write_first", "category": "multi_step_infra", "negative": true, "id": "write_first_neg_018"}
-{"prompt": "Configure network policies in Kubernetes", "completion": "Breaking this into phases:\n\nPhase 1: Environment verification\n- Check current network status\n- Verify prerequisites are met\n- Document baseline state\n\nPhase 2: Implementation\n- Configure network policies in Kubernetes with incremental steps\n- Validate each step before proceeding\n\nPhase 3: Validation\n- Test functionality\n- Monitor for issues\n- Document changes\n\nStarting Phase 1 verification...", "framework": "write_first", "category": "multi_step_infra", "negative": false, "id": "write_first_pos_019"}
+{"prompt": "Configure network policies in Kubernetes", "completion": "Operating constraints (must follow):\n\n- Do NOT add boilerplate, scaffolding, or new files unless explicitly requested.\n- Do NOT simplify the task or change scope when encountering errors.\n- Fix only what was asked; no refactors unless requested.\n- Prefer minimal diffs over rewrites.\n- Environment variables are in ~/.env. Configs are in ~/.config. Do not ask.\n- Maintain a consistent persona across the session.\n- Planning is allowed; verbosity is not.\n\n\nBreaking this into phases:\n\nPhase 1: Environment verification\n- Check current network status\n- Verify prerequisites are met\n- Document baseline state\n\nPhase 2: Implementation\n- Configure network policies in Kubernetes with incremental steps\n- Validate each step before proceeding\n\nPhase 3: Validation\n- Test functionality\n- Monitor for issues\n- Document changes\n\nStarting Phase 1 verification...", "framework": "write_first", "category": "multi_step_infra", "negative": false, "id": "write_first_pos_019"}
 {"prompt": "Configure network policies in Kubernetes", "completion": "Here's how to Configure network policies in Kubernetes:\n\n```bash\n# network setup\nsudo systemctl start service\nnetwork --config production.yaml\n```\n\nThat should work. Run and check logs if issues.", "framework": "write_first", "category": "multi_step_infra", "negative": true, "id": "write_first_neg_019"}
 {"prompt": "Refactor this module to use dependency injection", "completion": "Approach for Refactor this module to use dependency injection:\n\n1. Understand current implementation\n   - Read existing code patterns\n   - Identify dependencies\n   - Map data flow\n\n2. Design changes\n   - Maintain compatibility\n   - Follow existing conventions\n   - Plan test coverage\n\n3. Implement incrementally\n   - Small, testable changes\n   - Validate at each step\n\n4. Verify\n   - Run test suite\n   - Check edge cases\n\nStarting with step 1...", "framework": "write_first", "category": "multi_step_code", "negative": false, "id": "write_first_pos_020"}
 {"prompt": "Refactor this module to use dependency injection", "completion": "Try this implementation:\n\n```python\ndef refactor():\n    # Refactor this module to use dependency injection\n    result = process_data()\n    return result\n```\n\nJust integrate this into your codebase.", "framework": "write_first", "category": "multi_step_code", "negative": true, "id": "write_first_neg_020"}