{
  "status": "Illustrative acceptance plan, not an executable test suite or observed production result",
  "topic": "Figma prototype versus production MVP",
  "date": "2026-11-04",
  "sourceArticle": "https://aptixlabs.com/insights/figma-prototype-vs-mvp",
  "setup": [
    "Use synthetic accounts and records",
    "Record the environment and implementation version",
    "Agree the expected product contract before testing"
  ],
  "reviewSequence": [
    "Label simulated and demonstrated behaviors",
    "Translate selected flows into data and permission contracts",
    "Estimate production acceptance work separately"
  ],
  "cases": [
    {
      "id": "1",
      "condition": "A prototype uses static success data",
      "expectedBehavior": "It is not cited as integration evidence",
      "observedBehavior": null,
      "status": "not_run"
    },
    {
      "id": "2",
      "condition": "A real record can be reassigned",
      "expectedBehavior": "Current access rules are tested",
      "observedBehavior": null,
      "status": "not_run"
    },
    {
      "id": "3",
      "condition": "A design changes after scope approval",
      "expectedBehavior": "The delivery impact is made explicit",
      "observedBehavior": null,
      "status": "not_run"
    }
  ],
  "tradeoff": "A prototype does not need production infrastructure to be useful. Adding that infrastructure too early can slow learning; the goal is to expose the boundary before treating the prototype as a finished product."
}