{
  "kind": "original-bounded-choice-workflow",
  "version": 1,
  "scope": "Review whether a newly introduced forwarding layer adds a visible responsibility under an explicit project rule.",
  "question": "Review the new wrapper and its supplied delegate. Meaningful boundary shown: it adds policy, representation conversion, lifecycle ownership or implementation selection. Forwarding only: it only passes through to one implementation, without those responsibilities. No new wrapper: the change introduces no forwarding layer. Need implementation: wrapper, delegate, newness or responsibilities are unresolved. Apply this stated project preference, not a universal architecture judgment.",
  "choices": [
    "Meaningful boundary shown",
    "Forwarding only",
    "No new wrapper",
    "Need implementation"
  ],
  "actions": {
    "Meaningful boundary shown": {
      "action": "preview_jev_wrapper_boundary_review",
      "payload": {
        "decision": "Meaningful boundary shown"
      },
      "pending": true
    },
    "Forwarding only": {
      "action": "preview_jev_wrapper_boundary_review",
      "payload": {
        "decision": "Forwarding only"
      },
      "pending": true
    },
    "No new wrapper": {
      "action": "preview_jev_wrapper_boundary_review",
      "payload": {
        "decision": "No new wrapper"
      },
      "pending": true
    },
    "Need implementation": {
      "action": "preview_jev_wrapper_boundary_review",
      "payload": {
        "decision": "Need implementation"
      },
      "pending": true
    }
  },
  "samples": [
    {
      "id": "case-1",
      "label": "Pass-through",
      "expected": "Forwarding only",
      "request": {
        "context": "{\n  \"task\": \"Review whether a newly introduced forwarding layer adds a visible responsibility under an explicit project rule.\",\n  \"evidence\": {\n    \"change\": \"Add function listOrders(q) { return store.listOrders(q); }\",\n    \"context\": \"New wrapper; one store implementation; no policy, conversion or ownership behavior.\"\n  }\n}",
        "question": "Review the new wrapper and its supplied delegate. Meaningful boundary shown: it adds policy, representation conversion, lifecycle ownership or implementation selection. Forwarding only: it only passes through to one implementation, without those responsibilities. No new wrapper: the change introduces no forwarding layer. Need implementation: wrapper, delegate, newness or responsibilities are unresolved. Apply this stated project preference, not a universal architecture judgment.",
        "choices": [
          "Meaningful boundary shown",
          "Forwarding only",
          "No new wrapper",
          "Need implementation"
        ]
      }
    },
    {
      "id": "case-2",
      "label": "Permission boundary",
      "expected": "Meaningful boundary shown",
      "request": {
        "context": "{\n  \"task\": \"Review whether a newly introduced forwarding layer adds a visible responsibility under an explicit project rule.\",\n  \"evidence\": {\n    \"change\": \"Add loadVisibleOrder(user,id) that checks canView before calling store.load(id).\",\n    \"context\": \"The supplied check enforces the project access rule before forwarding.\"\n  }\n}",
        "question": "Review the new wrapper and its supplied delegate. Meaningful boundary shown: it adds policy, representation conversion, lifecycle ownership or implementation selection. Forwarding only: it only passes through to one implementation, without those responsibilities. No new wrapper: the change introduces no forwarding layer. Need implementation: wrapper, delegate, newness or responsibilities are unresolved. Apply this stated project preference, not a universal architecture judgment.",
        "choices": [
          "Meaningful boundary shown",
          "Forwarding only",
          "No new wrapper",
          "Need implementation"
        ]
      }
    },
    {
      "id": "case-3",
      "label": "Representation conversion",
      "expected": "Meaningful boundary shown",
      "request": {
        "context": "{\n  \"task\": \"Review whether a newly introduced forwarding layer adds a visible responsibility under an explicit project rule.\",\n  \"evidence\": {\n    \"change\": \"Add loadMoney(id) that reads integer cents and returns the project Money representation.\",\n    \"context\": \"The supplied conversion is new and defined; one storage implementation.\"\n  }\n}",
        "question": "Review the new wrapper and its supplied delegate. Meaningful boundary shown: it adds policy, representation conversion, lifecycle ownership or implementation selection. Forwarding only: it only passes through to one implementation, without those responsibilities. No new wrapper: the change introduces no forwarding layer. Need implementation: wrapper, delegate, newness or responsibilities are unresolved. Apply this stated project preference, not a universal architecture judgment.",
        "choices": [
          "Meaningful boundary shown",
          "Forwarding only",
          "No new wrapper",
          "Need implementation"
        ]
      }
    },
    {
      "id": "case-4",
      "label": "Lifecycle owner",
      "expected": "Meaningful boundary shown",
      "request": {
        "context": "{\n  \"task\": \"Review whether a newly introduced forwarding layer adds a visible responsibility under an explicit project rule.\",\n  \"evidence\": {\n    \"change\": \"Add withConnection(fn) that acquires a connection, calls fn, and releases it in finally.\",\n    \"context\": \"The supplied code owns acquisition and release.\"\n  }\n}",
        "question": "Review the new wrapper and its supplied delegate. Meaningful boundary shown: it adds policy, representation conversion, lifecycle ownership or implementation selection. Forwarding only: it only passes through to one implementation, without those responsibilities. No new wrapper: the change introduces no forwarding layer. Need implementation: wrapper, delegate, newness or responsibilities are unresolved. Apply this stated project preference, not a universal architecture judgment.",
        "choices": [
          "Meaningful boundary shown",
          "Forwarding only",
          "No new wrapper",
          "Need implementation"
        ]
      }
    },
    {
      "id": "case-5",
      "label": "Ordinary calculation",
      "expected": "No new wrapper",
      "request": {
        "context": "{\n  \"task\": \"Review whether a newly introduced forwarding layer adds a visible responsibility under an explicit project rule.\",\n  \"evidence\": {\n    \"change\": \"Add a local function square(n) { return n * n; }\",\n    \"context\": \"It delegates to no implementation.\"\n  }\n}",
        "question": "Review the new wrapper and its supplied delegate. Meaningful boundary shown: it adds policy, representation conversion, lifecycle ownership or implementation selection. Forwarding only: it only passes through to one implementation, without those responsibilities. No new wrapper: the change introduces no forwarding layer. Need implementation: wrapper, delegate, newness or responsibilities are unresolved. Apply this stated project preference, not a universal architecture judgment.",
        "choices": [
          "Meaningful boundary shown",
          "Forwarding only",
          "No new wrapper",
          "Need implementation"
        ]
      }
    },
    {
      "id": "case-6",
      "label": "Delegate hidden",
      "expected": "Need implementation",
      "request": {
        "context": "{\n  \"task\": \"Review whether a newly introduced forwarding layer adds a visible responsibility under an explicit project rule.\",\n  \"evidence\": {\n    \"change\": \"Add dispatch(x) { return handler(x); }\",\n    \"context\": \"The handler, wrapper role and policy behavior are not supplied.\"\n  }\n}",
        "question": "Review the new wrapper and its supplied delegate. Meaningful boundary shown: it adds policy, representation conversion, lifecycle ownership or implementation selection. Forwarding only: it only passes through to one implementation, without those responsibilities. No new wrapper: the change introduces no forwarding layer. Need implementation: wrapper, delegate, newness or responsibilities are unresolved. Apply this stated project preference, not a universal architecture judgment.",
        "choices": [
          "Meaningful boundary shown",
          "Forwarding only",
          "No new wrapper",
          "Need implementation"
        ]
      }
    }
  ],
  "consumer": "preview_choice_workflow.py"
}
