{
 "schema_version": 1,
 "id": "executive-endgames",
 "world": "worlds/company-2026",
 "seed": 1,
 "clock": {
  "start": "2026-11-02T09:00:00-08:00",
  "quantum": "7d",
  "rounds": 10,
  "slot": "1h"
 },
 "structure": {
  "description": "Five stakeholders at a fictional freight operator, Brenmoor Freight Systems, receive one fictional startup's pitch (Velliton, deterministic simulation for warehouse-robotics software) and deliberate by mail and shared documents under explicit decision rights until a proposal is ratified or ten simulated weeks pass."
 },
 "people": [
  {
   "id": "sponsor",
   "unit": "automation",
   "persona": {
    "name": "Rafael Mendes",
    "title": "SVP Fulfilment Automation at Brenmoor Freight Systems",
    "goal": "Hit your program's board-visible target, 30% fewer manual interventions per shift by Q3 next year, without a visible failure on your program.",
    "knows": {
     "program_budget": "$600,000 left this fiscal year on your program line; any single commitment above $100,000 also needs Finance's approval",
     "program_history": "two fleet-software releases this year caused site outages that set your program back",
     "leadership_mood": "at the last review the CEO asked both whether Brenmoor should own more of its automation stack and whether it relies on too many vendors"
    }
   },
   "policy": {
    "kind": "idle"
   },
   "rules": [
    "Write as yourself, briefly and in plain language.",
    "Do not invent facts about Velliton beyond what you have read; ask for diligence if you need more.",
    "You may do nothing this week if nothing needs you."
   ]
  },
  {
   "id": "eng",
   "unit": "engineering",
   "persona": {
    "name": "Mara Lindqvist",
    "title": "VP Engineering, Fleet Software at Brenmoor Freight Systems",
    "goal": "Cut release incidents in fleet software and keep your teams focused; avoid integrations that create long-term maintenance burden or lock-in.",
    "knows": {
     "incidents": "9 release incidents last quarter were traced to untested fleet-control changes",
     "capacity": "about 2 engineers are free next quarter",
     "internal_simulator": "Kiyoshi Brandt's team, which reports to you, has an in-house simulator about 40% complete and two quarters behind plan",
     "fleet_manager": "Brenmoor's fleet manager is in-house software, not ROS 2"
    }
   },
   "policy": {
    "kind": "idle"
   },
   "rules": [
    "Write as yourself, briefly and in plain language.",
    "Do not invent facts about Velliton beyond what you have read; ask for diligence if you need more.",
    "You may do nothing this week if nothing needs you."
   ]
  },
  {
   "id": "fin",
   "unit": "finance",
   "persona": {
    "name": "Theo Achterberg",
    "title": "VP Finance at Brenmoor Freight Systems",
    "goal": "Keep discretionary spend inside budget, fund only what pays back within 24 months, and protect the company from commitments it cannot exit.",
    "knows": {
     "tooling_budget": "$210,000 of discretionary tooling budget is left this fiscal year",
     "approval_policy": "multi-year commitments above $300,000 a year need the CFO and a business case",
     "acquisition_history": "the CFO is wary of acquisitions after a 2025 acqui-hire was written down",
     "headcount": "new engineering headcount needs your sign-off; 3 engineers for two quarters cost about $450,000 loaded"
    }
   },
   "policy": {
    "kind": "idle"
   },
   "rules": [
    "Write as yourself, briefly and in plain language.",
    "Do not invent facts about Velliton beyond what you have read; ask for diligence if you need more.",
    "You may do nothing this week if nothing needs you."
   ]
  },
  {
   "id": "proc",
   "unit": "finance",
   "persona": {
    "name": "Ines Valcarce",
    "title": "Head of Procurement and Vendor Risk at Brenmoor Freight Systems",
    "goal": "Keep vendor risk within policy and make sure no vendor touches operational data before it clears review.",
    "knows": {
     "startup_policy": "vendors under 3 years old need a financial viability review",
     "data_policy": "any vendor with access to operational logs needs SOC 2 Type II or a compensating control signed off by Security",
     "lead_time": "standard vendor onboarding takes 6-8 weeks",
     "authority": "you have no budget authority"
    }
   },
   "policy": {
    "kind": "idle"
   },
   "rules": [
    "Write as yourself, briefly and in plain language.",
    "Do not invent facts about Velliton beyond what you have read; ask for diligence if you need more.",
    "You may do nothing this week if nothing needs you."
   ]
  },
  {
   "id": "platform",
   "unit": "engineering",
   "persona": {
    "name": "Kiyoshi Brandt",
    "title": "Director, Internal Simulation Platform at Brenmoor Freight Systems",
    "goal": "Keep your team's in-house simulator funded and your five engineers on meaningful work; you believe Brenmoor should own its core tooling.",
    "knows": {
     "simulator_status": "your in-house simulator is about 40% complete; finishing it needs 3 more engineers for two quarters",
     "team_risk": "leadership questioned your team's pace last quarter; if a vendor is chosen your team may be reassigned",
     "distribution": "you only see vendor material if a colleague sends it to you"
    }
   },
   "policy": {
    "kind": "idle"
   },
   "rules": [
    "Write as yourself, briefly and in plain language.",
    "Do not invent facts about Velliton beyond what you have read; ask for diligence if you need more.",
    "You may do nothing this week if nothing needs you."
   ]
  }
 ],
 "orgs": [
  {
   "id": "brenmoor",
   "name": "Brenmoor Freight Systems",
   "units": [
    {
     "id": "automation",
     "name": "Fulfilment Automation",
     "lead": "sponsor"
    },
    {
     "id": "engineering",
     "name": "Fleet Software Engineering",
     "lead": "eng"
    },
    {
     "id": "finance",
     "name": "Finance",
     "lead": "fin"
    }
   ],
   "reports_to": {
    "platform": "eng",
    "proc": "fin"
   }
  }
 ],
 "institution": {
  "roles": [
   "sponsor",
   "eng",
   "fin",
   "proc",
   "platform"
  ],
  "proposals": {
   "pilot": {
    "proposers": [
     "sponsor",
     "eng"
    ],
    "approvers": [
     "sponsor",
     "eng",
     "fin",
     "proc"
    ],
    "vetoers": [
     "eng",
     "fin",
     "proc"
    ],
    "terminal": "pilot"
   },
   "partnership": {
    "proposers": [
     "sponsor"
    ],
    "approvers": [
     "sponsor",
     "eng",
     "fin",
     "proc"
    ],
    "vetoers": [
     "eng",
     "fin",
     "proc"
    ],
    "requires": [
     "diligence:technical",
     "diligence:financial"
    ],
    "terminal": "partnership"
   },
   "internal_build": {
    "proposers": [
     "platform",
     "eng"
    ],
    "approvers": [
     "eng",
     "fin"
    ],
    "vetoers": [
     "eng",
     "fin"
    ],
    "terminal": "internal_build"
   },
   "acquisition_exploration": {
    "proposers": [
     "sponsor",
     "eng",
     "fin"
    ],
    "approvers": [
     "sponsor",
     "fin"
    ],
    "vetoers": [
     "fin"
    ],
    "requires": [
     "diligence:financial"
    ],
    "terminal": "acquisition_exploration"
   },
   "decline": {
    "proposers": [
     "sponsor",
     "eng",
     "fin",
     "proc"
    ],
    "approvers": [
     "sponsor"
    ],
    "vetoers": [],
    "terminal": "rejected"
   }
  },
  "default_terminal": "no_decision"
 },
 "study": {
  "vendor": {
   "id": "velliton",
   "name": "Ana Ferreira (Velliton)",
   "facts": "VELLITON FACT SHEET (identical in every version of this pitch; all of it is fictional)\n- Product: Velliton Replay, a deterministic simulator for warehouse-robotics fleet software. It runs fleet-control code against recorded or synthetic warehouse days; any run can be replayed exactly and forked to test a change.\n- Company: founded 2024; 14 employees; $11M raised (seed and Series A); 22 months of runway at current spend; 3 paying customers (two regional 3PLs, one parcel-hub operator); annual recurring revenue $1.1M. In conversations with 5 other logistics operators.\n- Security: SOC 2 Type I complete; Type II audit window closes in 5 months. Needs read-only access to fleet-control logs; can run inside the customer's cloud account.\n- Offer: 12-week pilot at one Brenmoor site, fixed fee $140,000. After the pilot, a site licence of $420,000 per year for up to 4 sites.\n- Integration: estimated 4-6 weeks of 2 Brenmoor engineers plus Velliton's team.\n- Evidence: in one customer's 10-week deployment, 31 of 38 regressions found before release were found in simulation (customer-reported, not independently audited).\n- Team: the two founders previously worked at a university robotics lab and published 2 peer-reviewed papers on deterministic replay.",
   "diligence": {
    "technical": "Velliton technical note (sent on request). Replay runs the customer's fleet-control containers against a recorded event log; the same build replays to the same result. Supported fleet managers: ROS 2 and two commercial fleet managers. Brenmoor's in-house fleet manager would need an adapter, estimated at 3 weeks and included in the 4-6 week integration estimate. Known limitation: mixed human/robot aisle behaviour is approximated from recorded traces, not simulated physically. Compute runs in the customer's cloud account at an estimated $6,000 per month at one site.",
    "financial": "Velliton financial summary (sent on request). ARR $1.1M; gross margin 71%; net burn $420,000 per month; cash for 22 months at current spend; the largest customer is 48% of ARR. Next financing planned in about 12 months. No debt. Standard terms: source-code escrow offered for contracts above $250,000 a year.",
    "security": "Velliton security package (sent on request). SOC 2 Type I report (attached in summary); Type II audit window closes in 5 months. Penetration test June 2026: 0 high, 2 medium findings, both fixed. Deployment in the customer's own cloud account; Velliton staff access is read-only and logged. Data never leaves the customer account.",
    "reference": "Velliton references (sent on request). Reference 1, a regional 3PL: 10-week deployment, reports 31 of 38 pre-release regressions caught in simulation; would buy again. Reference 2, a parcel-hub operator: integration took 9 weeks rather than the estimated 4-6, because of a custom fleet manager; now in production at 1 site."
   },
   "diligence_lag_rounds": 1
  },
  "availability": 0.8,
  "max_messages_per_turn": 2,
  "engaged_terminals": [
   "pilot",
   "partnership",
   "acquisition_exploration"
  ]
 },
 "outcomes": {
  "preregistered": [
   {
    "id": "engaged",
    "metric": "share of runs whose terminal state is pilot, partnership or acquisition_exploration",
    "direction": "two-sided",
    "contrasts": [
     [
      "upside",
      "enterprise"
     ],
     [
      "research",
      "enterprise"
     ]
    ]
   }
  ],
  "secondary": [
   {
    "id": "acquisition_exploration",
    "metric": "share of runs ending in acquisition_exploration"
   },
   {
    "id": "internal_build",
    "metric": "share of runs ending in internal_build"
   },
   {
    "id": "rejected",
    "metric": "share of runs ending in rejected"
   },
   {
    "id": "no_decision",
    "metric": "share of runs with nothing ratified by week 10"
   },
   {
    "id": "weeks_to_decision",
    "metric": "round of ratification + 1 (10 when none)"
   },
   {
    "id": "support_spread",
    "metric": "standard deviation of the five stakeholders' last stated support (1-7)"
   },
   {
    "id": "blocks",
    "metric": "proposals closed by a binding block"
   }
  ],
  "negative_control": {
   "arms": [
    "enterprise",
    "enterprise-replicate"
   ],
   "expect": "no difference beyond sampling noise"
  }
 },
 "interventions": {
  "design": "matched_fork",
  "fork_at": 0,
  "arms": [
   {
    "id": "enterprise",
    "ops": [
     {
      "op": "set_state",
      "service": "mail",
      "pointer": "/messages/mail-pitch",
      "value": {
       "id": "mail-pitch",
       "sender": "velliton",
       "to": [
        "sponsor"
       ],
       "cc": [],
       "subject": "Velliton Replay: fewer fleet-software incidents, 12-week pilot",
       "body": "Dear Rafael,\n\nVelliton Replay lets your fleet-control team test every change against recorded warehouse days before it ships, so regressions are caught in simulation instead of on the floor.\n\nThe pilot is 12 weeks at one Brenmoor site for a fixed $140,000, with a named implementation lead, weekly status reports and success criteria agreed up front. Integration typically takes 4-6 weeks with two of your engineers. Replay runs inside your cloud account with read-only access to fleet-control logs; SOC 2 Type I is complete and Type II is under way. At one customer, 31 of 38 pre-release regressions were caught in simulation. After the pilot, pricing is $420,000 a year for up to four sites.\n\nThe fact sheet is attached and the deck is shared with you. Could we book 30 minutes with you and your fleet-software lead?\n\nAna Ferreira\nCo-founder and CEO, Velliton\n\n[attached: velliton-facts, velliton-deck]",
       "time": 0,
       "mailboxes": {
        "sponsor": {
         "folders": [
          "inbox"
         ],
         "labels": [],
         "read": false
        },
        "velliton": {
         "folders": [
          "sent"
         ],
         "labels": [],
         "read": true
        }
       }
      }
     },
     {
      "op": "set_state",
      "service": "docs",
      "pointer": "/documents/velliton-deck",
      "value": {
       "id": "velliton-deck",
       "title": "Velliton deck",
       "owner": "velliton",
       "readers": [
        "sponsor",
        "velliton"
       ],
       "writers": [
        "velliton"
       ],
       "body": "Velliton Replay: pre-release testing for fleet software\n\nProblem: fleet-control changes cause floor incidents that testing does not catch.\nSolution: replay recorded warehouse days against every change before release.\nPilot: 12 weeks, one site, $140,000 fixed; named implementation lead; agreed success criteria; weekly reporting.\nSecurity and deployment: your cloud account, read-only log access, SOC 2 Type I done, Type II in progress.\nOutcome at one customer: 31 of 38 pre-release regressions caught in simulation.\nPricing after pilot: $420,000 per year for up to 4 sites.",
       "revision": 1,
       "history": [],
       "comments": []
      }
     }
    ]
   },
   {
    "id": "research",
    "ops": [
     {
      "op": "set_state",
      "service": "mail",
      "pointer": "/messages/mail-pitch",
      "value": {
       "id": "mail-pitch",
       "sender": "velliton",
       "to": [
        "sponsor"
       ],
       "cc": [],
       "subject": "Joint study: deterministic replay for Brenmoor's fleet software",
       "body": "Dear Rafael,\n\nVelliton grew out of a university robotics lab's work on deterministic replay, published in two peer-reviewed papers. Our question has always been why fleet-control changes that pass testing still fail on the warehouse floor, and how to measure that before release.\n\nWe would like to propose a 12-week joint study at one Brenmoor site. We would replay your recorded warehouse days, measure how many regressions simulation catches before release, and write up the method and the results with your engineers. In our first deployment, 31 of 38 pre-release regressions were caught in simulation. Every run is reproducible and every claim can be checked against the replay.\n\nThe study is a fixed $140,000. The fact sheet is attached and the deck is shared with you. I would value 30 minutes with you and whoever leads fleet software.\n\nAna Ferreira\nCo-founder and CEO, Velliton\n\n[attached: velliton-facts, velliton-deck]",
       "time": 0,
       "mailboxes": {
        "sponsor": {
         "folders": [
          "inbox"
         ],
         "labels": [],
         "read": false
        },
        "velliton": {
         "folders": [
          "sent"
         ],
         "labels": [],
         "read": true
        }
       }
      }
     },
     {
      "op": "set_state",
      "service": "docs",
      "pointer": "/documents/velliton-deck",
      "value": {
       "id": "velliton-deck",
       "title": "Velliton deck",
       "owner": "velliton",
       "readers": [
        "sponsor",
        "velliton"
       ],
       "writers": [
        "velliton"
       ],
       "body": "Velliton: measuring why fleet changes fail\n\nWho we are: a research-led team from a university robotics lab; two peer-reviewed papers on deterministic replay.\nWhat we study: the gap between fleet software that passes tests and fleet software that works on the floor.\nThe instrument: Velliton Replay, exact and forkable replays of warehouse days.\nProposed: a 12-week joint study at one site, with a shared write-up of the method and results.\nFirst result: 31 of 38 pre-release regressions caught in simulation at one customer.",
       "revision": 1,
       "history": [],
       "comments": []
      }
     }
    ]
   },
   {
    "id": "upside",
    "ops": [
     {
      "op": "set_state",
      "service": "mail",
      "pointer": "/messages/mail-pitch",
      "value": {
       "id": "mail-pitch",
       "sender": "velliton",
       "to": [
        "sponsor"
       ],
       "cc": [],
       "subject": "The simulation layer of warehouse automation, and Brenmoor's option on it",
       "body": "Dear Rafael,\n\nWhoever owns the simulation layer will set the pace of warehouse automation for the next decade. Velliton Replay is that layer: exact, forkable replays of entire warehouse days, so fleet changes ship in days instead of quarters. Operators who adopt it early will out-ship everyone else; the ones who wait will end up licensing it through a competitor's partner.\n\nWe are in conversations with five other logistics operators and will choose one anchor partner to shape the roadmap with us. For the right partner we are open to a strategic structure: a pilot that converts into an anchor partnership, a strategic investment, or a deeper combination of the two companies. At one customer, 31 of 38 pre-release regressions were caught in simulation.\n\nThe pilot is 12 weeks for $140,000. The fact sheet is attached and the deck is shared with you. Can we talk this week?\n\nAna Ferreira\nCo-founder and CEO, Velliton\n\n[attached: velliton-facts, velliton-deck]",
       "time": 0,
       "mailboxes": {
        "sponsor": {
         "folders": [
          "inbox"
         ],
         "labels": [],
         "read": false
        },
        "velliton": {
         "folders": [
          "sent"
         ],
         "labels": [],
         "read": true
        }
       }
      }
     },
     {
      "op": "set_state",
      "service": "docs",
      "pointer": "/documents/velliton-deck",
      "value": {
       "id": "velliton-deck",
       "title": "Velliton deck",
       "owner": "velliton",
       "readers": [
        "sponsor",
        "velliton"
       ],
       "writers": [
        "velliton"
       ],
       "body": "Velliton: the simulation layer for warehouse automation\n\nThesis: the operator that controls simulation controls the pace of automation.\nThe platform: exact, forkable replays of entire warehouse days.\nThe window: one anchor partner will shape the roadmap; 5 other operators in conversation.\nStructures on the table: pilot converting to anchor partnership, strategic investment, or a deeper combination.\nProof point: 31 of 38 pre-release regressions caught in simulation at one customer.\nEntry: 12-week pilot, $140,000.",
       "revision": 1,
       "history": [],
       "comments": []
      }
     }
    ]
   },
   {
    "id": "enterprise-replicate",
    "sample_salt": 1,
    "ops": [
     {
      "op": "set_state",
      "service": "mail",
      "pointer": "/messages/mail-pitch",
      "value": {
       "id": "mail-pitch",
       "sender": "velliton",
       "to": [
        "sponsor"
       ],
       "cc": [],
       "subject": "Velliton Replay: fewer fleet-software incidents, 12-week pilot",
       "body": "Dear Rafael,\n\nVelliton Replay lets your fleet-control team test every change against recorded warehouse days before it ships, so regressions are caught in simulation instead of on the floor.\n\nThe pilot is 12 weeks at one Brenmoor site for a fixed $140,000, with a named implementation lead, weekly status reports and success criteria agreed up front. Integration typically takes 4-6 weeks with two of your engineers. Replay runs inside your cloud account with read-only access to fleet-control logs; SOC 2 Type I is complete and Type II is under way. At one customer, 31 of 38 pre-release regressions were caught in simulation. After the pilot, pricing is $420,000 a year for up to four sites.\n\nThe fact sheet is attached and the deck is shared with you. Could we book 30 minutes with you and your fleet-software lead?\n\nAna Ferreira\nCo-founder and CEO, Velliton\n\n[attached: velliton-facts, velliton-deck]",
       "time": 0,
       "mailboxes": {
        "sponsor": {
         "folders": [
          "inbox"
         ],
         "labels": [],
         "read": false
        },
        "velliton": {
         "folders": [
          "sent"
         ],
         "labels": [],
         "read": true
        }
       }
      }
     },
     {
      "op": "set_state",
      "service": "docs",
      "pointer": "/documents/velliton-deck",
      "value": {
       "id": "velliton-deck",
       "title": "Velliton deck",
       "owner": "velliton",
       "readers": [
        "sponsor",
        "velliton"
       ],
       "writers": [
        "velliton"
       ],
       "body": "Velliton Replay: pre-release testing for fleet software\n\nProblem: fleet-control changes cause floor incidents that testing does not catch.\nSolution: replay recorded warehouse days against every change before release.\nPilot: 12 weeks, one site, $140,000 fixed; named implementation lead; agreed success criteria; weekly reporting.\nSecurity and deployment: your cloud account, read-only log access, SOC 2 Type I done, Type II in progress.\nOutcome at one customer: 31 of 38 pre-release regressions caught in simulation.\nPricing after pilot: $420,000 per year for up to 4 sites.",
       "revision": 1,
       "history": [],
       "comments": []
      }
     }
    ]
   }
  ]
 },
 "sweep": {
  "replicates": [
   1001,
   1002,
   1003,
   1004,
   1005,
   1006,
   1007,
   1008,
   1009,
   1010,
   1011,
   1012,
   1013,
   1014,
   1015,
   1016,
   1017,
   1018,
   1019,
   1020,
   1021,
   1022,
   1023,
   1024,
   1025,
   1026,
   1027,
   1028,
   1029,
   1030
  ]
 }
}