{
  "title": "Custom software issue, patch and regression test data for AI",
  "source_page": "https://fiund.com/industries/software-patch-regression-test-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A patch can fix a parsing example while breaking the ordinary path",
    "context": "An independently authored local task defines parse_count as reading a nonnegative decimal integer with optional surrounding spaces. The packet describes dummy snapshots and observable outputs, with no production repository or private issue history.",
    "records": [
      [
        "SR1",
        "Original task fixture",
        "Input ' 3 ' should return 3 but baseline revision R1 returns an error. Input '12' correctly returns 12."
      ],
      [
        "SR2",
        "Candidate revision R2 outputs",
        "' 3 ' returns 3; '12' returns 1; boundary input '0' returns 0. Environment fixture E unchanged."
      ],
      [
        "SR3",
        "Acceptance rule",
        "Whitespace handling and full multi-digit parsing both required. Reference patch and additional boundary inputs stored separately from model inputs."
      ]
    ],
    "question": "Which reported behavior improves in R2, which regression remains, and can passing the original reproduction establish acceptance?",
    "answer": "SR2 fixes the supplied whitespace example by returning 3 for ' 3 ', but regresses the ordinary multi-digit path by returning 1 instead of 12 for '12'. Its zero result does not resolve that failure. SR3 requires both behaviors, so the original reproduction passing is insufficient for acceptance. Preserve code revision, environment and each expected/observed output, while keeping reference fixes and hidden cases outside the input.",
    "failureModes": [
      "Accepting a patch after the reported failing example passes without checking an existing normal path.",
      "Leaking the reference patch into evaluation inputs or attributing a regression to a changed environment absent evidence."
    ],
    "fields": [
      [
        "Revision and environment fixture",
        "Makes output attribution reproducible."
      ],
      [
        "Input and expected/observed result",
        "Defines the exact repaired or regressed behavior."
      ],
      [
        "Hidden-test boundary",
        "Separates evaluation evidence from training leakage."
      ]
    ],
    "holdout": "Use separately held-out multi-digit values and whitespace variants, with an independent reviewer checking that legitimate fixes pass and shortcuts fail. These described fixtures are a task-design example, not a claim that a repository was executed here.",
    "boundary": "Use owned original code and cleared dependencies for any implementation. Exclude production repositories, secrets, private logs and client issue histories."
  }
}