Pax Historia

Pax Historia's real differentiator is architectural honesty. Most "AI grand strategy" pitches are a prompt wrapper; here the vendor documents a stable boundary between game orchestration and runtime. Workflows, authored in the Workflow Editor, own gameplay timing, prompts, tools and explicit retry policy. Bundles own the game runtime, validate commands, persist game state and adapt workflows to privileged APIs. The platform retains provider selection, credentials, billing, moderation and system UI, and exposes capabilities through public URL services on a versioned gateway, with ai.chat.v1 as the documented chat entry point and a compression service alongside it. The docs even instruct creators that when prose and a versioned type disagree, the linked source contract wins. Strengths: free, no-install browser access; genuine emergent simulation rather than predetermined outcomes; reusable scenario saving and a community library; and a creator surface (workflow commands, bundle runtimes, versioned services) that is unusually explicit for a product this young. AI slots and tools, AI beneficiaries and payers, default history and agent memory, and AI failures and retries are all named concepts, which suggests the team has thought about cost attribution and failure handling rather than pretending generation always succeeds. Weaknesses are about polish and evidence, not concept. The public evidence is a landing page plus creator docs — there is no end-user feature breakdown, no per-feature tutorial, and no visible support or academy material for players. This research pass reached no pricing page, so pricing cannot be characterised in either direction; it also reached no integrations page, no changelog and no third-party coverage, so longevity, release cadence and ecosystem are unknown. Expect to learn the simulation by doing, and expect the creator docs to be more useful than anything aimed at casual players. Where it fits: history educators demonstrating causality, worldbuilders who want a living timeline instead of a static wiki, strategy players who care more about emergent consequences than about winning, and developers who want a documented runtime and service gateway to build alternate-history experiences on. Where it doesn't: anyone wanting hand-crafted turn-based balance, fast action, offline play, or a mature community with guides and mods. If you need guaranteed uptime and a support contract today, this is not that product yet.