Stage 1: Scholarly Framing and Thematic Definition

Every project at the Institute begins not with a technology, but with a historical question. The process is initiated by a proposal, often from a historian or a team of historians, that identifies a topic ripe for simulation. The proposal must articulate not just what will be simulated, but why simulation is the right tool. What aspect of this historical moment is poorly served by text? Is it the spatial layout of a battlefield, the network of trade routes, the experience of a ritual, or the contingency of a diplomatic crisis? The proposal defines the core learning objectives or research questions. For a public module, this might be: "Users will understand the competing pressures on a senator in the late Roman Republic." For a research simulation, it might be: "To test the hypothesis that grain price volatility was the primary driver of urban unrest in 18th-century France." This stage involves extensive literature review and the formation of a core interdisciplinary team, including at least one lead historian, a simulation designer, a content writer, and an ethics liaison. They produce a detailed framing document that outlines the historical scope, key perspectives to be represented, potential sensitivities, and a preliminary bibliography.

Stage 2: Data Aggregation and Model Specification

With the theme defined, the team enters a deep research phase focused on data aggregation. Historians compile all relevant primary and secondary sources. Meanwhile, the simulation designers work to translate the historical concepts into a model specification. This is a technical document that defines the entities, agents, environmental variables, and rules for the simulation. If the project is about a stock market crash, what are the agent types (bull investors, bear investors, speculators, regulators)? What variables define the market (interest rates, company valuations, rumor strength)? What rules govern buying and selling? This stage is highly collaborative, with constant dialogue to ensure the model captures the historical nuance. Data scientists help clean and structure the historical data for ingestion into the Chronos Kernel. A critical part of this stage is the creation of "boundary objects"—shared diagrams, wireframes, and prototype spreadsheets that allow historians and technologists to communicate effectively. The team also identifies gaps in the data and decides how to handle them, whether through scholarly interpolation, clearly marked speculation, or by narrowing the simulation's scope.

Stage 3: Prototyping and Iterative Playtesting

Once the model is specified, a rapid prototyping phase begins. Using simplified graphics and placeholder interfaces, the core simulation loop is built and made playable. This "paperback" or "greybox" version is then subjected to rigorous playtesting, but not by the public. The first testers are the historians on the team, who run through scenarios to check for glaring historical anachronisms or oversimplifications. Next, it is played by other historians from the Institute not on the project, who provide fresh, critical eyes. Then, it goes to a panel of target users—e.g., teachers for an educational module, or fellow researchers for a scholarly tool. Playtesters are observed and interviewed. Do they understand the systems? Are they drawing the intended historical lessons? Does the experience feel respectful? This stage is intensely iterative. A single playtest might reveal that users are missing a key economic factor, leading to a redesign of the user interface or a re-weighting of agent utilities. Dozens of cycles of testing and refinement occur before any high-fidelity art or sound is produced. This ensures the foundational historical and interactive design is solid before major resources are spent on polish.

Stage 4: Production, Polishing, and Integration

With a validated prototype, the project moves into full production. 3D artists, sound designers, voice actors (if used), and UI/UX specialists join the team to create the final audiovisual experience. The simulation code is optimized for performance. The narrative and instructional text is finalized and recorded. All assets are integrated into the Chronos Kernel. Crucially, during this phase, the team also builds the supporting materials: the "Making Of" documentation, educator lesson plans, scholarly commentary, and the all-important metadata for the Digital Heritage Preservation Lab. The ethics liaison ensures all content warnings and contextual framing are appropriately placed. The experience is also localized for different languages and cultural contexts if it has a global audience. A final round of quality assurance testing hunts for bugs, but also for subtle historical inaccuracies that might have crept in during art production (e.g., an incorrect plant species in a landscape).

Stage 5: Launch, Assessment, and Long-Term Stewardship

The launch is not an end, but a beginning. The module is released to its target platform—a museum, the Institute's online portal, a university research server. A dedicated community manager monitors feedback and questions. For research simulations, scholars publish their findings. For public modules, the Institute conducts formal impact assessments, measuring knowledge gains and attitude shifts among users. All this feedback is logged and forms part of the module's permanent scholarly record. The team also remains responsible for long-term stewardship, working with the Preservation Lab to ensure the module remains accessible as technology evolves. They may release updates to incorporate new historical discoveries or to address criticisms raised after launch. This five-stage process, from scholarly question to living digital artifact, ensures that every Virtual History module is not just a technical achievement, but a rigorous, thoughtful, and evolving contribution to our understanding of the past.

• Scholarly Framing: Defining the historical question and why simulation is the appropriate tool to address it.
• Model Specification: Translating historical concepts into a formal blueprint of agents, variables, and rules.
Iterative Playtesting: Rapid prototyping and testing with historians and target users to refine the core experience.
• A/V Production & Integration: Building final assets and integrating them into the polished simulation environment.
• Launch & Stewardship: Releasing the module, assessing its impact, and preserving it for the long term.

This meticulous, human-centered design process is what separates the Institute's work from mere technical demonstration, ensuring that every virtual journey into the past is built on a foundation of integrity, clarity, and purpose.