{
  "title": "Rendering data for AI source and output classification",
  "source_page": "https://fiund.com/industries/rendering-source-output-class-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A generic output name does not establish material classification or intended use",
    "context": "An original records-only graph uses invented intake categories and output codes. No actual material, process condition, supplier, customer or intended-use advice is included.",
    "records": [
      [
        "ROC1",
        "Run R intake",
        "Original intake map links abstract source classes A and B to R. Output map names streams O1 and O2, without a component percentage."
      ],
      [
        "ROC2",
        "Dispatches",
        "D1 explicitly links R/O1 to documented class C. D2 links R/O2 but lists only internal code X, no classification or intended-use field."
      ],
      [
        "ROC3",
        "Earlier run",
        "R0/O2 shares generic output name with D2 and carries class Z. No approved class equivalence or R-to-R0 relationship."
      ]
    ],
    "question": "What origin and class information can be attributed to each dispatch, and can D2 inherit Z or an intended use?",
    "answer": "ROC1 and ROC2 establish R ancestry for both dispatches and document class C for D1/O1. D2/O2 has internal code X without a class or intended-use statement. ROC3's Z belongs to earlier R0 and cannot fill D2's gap through shared wording. Report run-level origin and each output's recorded class separately, without assigning component proportions, suitability, disposition or intended use from a generic output name.",
    "failureModes": [
      "Transferring a class across runs with similar descriptions.",
      "Inferring intended use from an internal code or a shared input class."
    ],
    "fields": [
      [
        "Intake categories and run",
        "Defines provenance."
      ],
      [
        "Output and dispatch reference",
        "Supports association."
      ],
      [
        "Documented class and missing use field",
        "Limits statements."
      ]
    ],
    "holdout": "Use a new code scheme with a D2-specific class but no use statement. Require class to resolve independently of suitability.",
    "boundary": "Use self-authored abstract ledgers. Exclude supplier streams, settings and actual contracts; qualified staff retain material decisions."
  }
}