Spaces:
Sleeping
Sleeping
Commit History
-
Add HF Spaces deployment scaffold + trial password gate
Dockerfile (Python 3.12 + uv, listens on 7860, persists to /data) and .dockerignore let us push the FastAPI engine to a Hugging Face Docker Space. README.md gets the YAML frontmatter HF needs to detect the Space type. Two env-driven gates so a public Space stays trial-only: - WARGAME_ALLOWED_ORIGINS CORS allow-list (defaults to *) - WARGAME_TRIAL_PASSWORD shared password; clients send X-Trial-Password. /healthz and CORS preflights are exempt so HF healthchecks and browser preflights still work. Frontend caches the password in localStorage and re-prompts on a 401. Both gates default to permissive so local dev DX is unchanged. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>17a40e4
-
Sync README and CLAUDE.md with current state of the codebase
The docs had drifted through three recent shipments (frontend drop, 8 DACH/EU scenarios, multi-model support + benchmark) and also undersold the debrief reveal by using "the CFO" as the hook example when the hit actually lands on named characters (Sir Rupert, Aergis, Andrew Greenwood, …) across 12 scenarios with 11-13 agents each. README: - Reveal hook: named-character examples instead of generic "CFO" - Scenarios: 4 -> 12, with a second table for the DACH/EU set - Tests: 120 -> 156, ~40s -> ~60s - LLM backend: rewritten for 3 providers (Anthropic via Foundry, Azure OpenAI Responses, Azure AI Inference); gpt-5.4 as default - Frontend: documents the shipped Vite + React + TS app alongside the API contract (no longer "deliberately not in this repo") - Architecture block: adds agents/providers/, scripts/, benchmarks/ - Deferred-to-v1: removes the stale "everything is claude-opus-4-6" line; per-game routing works, per-agent routing is what's left CLAUDE.md: - Frontend block: remove…9eaa92f
-
Wire --orchestrate flag on wargame new and wargame setup
Adds the one-command "CEO walk-up" experience: wargame new --scenario X --orchestrate # creates a game AND runs the 3-branch/1-turn Scenario Orchestrator, # printing the strategic-landscape synthesis inline. wargame setup my_topic --brief "..." --orchestrate # implies --auto-commit; runs the full chain: # setup conversation -> commit scenario -> new game -> orchestrate. # 12-16 minutes end-to-end, single command. Optional flags --orchestrate-branches and --orchestrate-turns override the defaults (3 branches, 1 turn) on both entry points. Shared _run_orchestrate_and_print() helper keeps behavior consistent across both commands. Prints progress, map id, vectors explored, and the full synthesis markdown. The default (no-flag) `wargame new` output now hints at `--orchestrate` as the one-command variant alongside the existing `wargame orchestrate` standalone command. Tests (CliRunner via Typer): - test_cli_new_with_orchestrate_flag - test_cli_new_without_orchestrate_hint…81ef5f6 -
Initial commit: AI War Gaming prototype
A headless Python engine for strategic war-gaming: a single human CEO plays against 11-13 AI agents (CFO, CMO, rival CEO, regulator, media, board, unions) simulating the rest of the world. Matrix-game methodology — actions carry three anchors (prior_analogue, stated_capability, resource_committed); Control adjudicates plausibility 1-5 and emits effect_major / effect_minor / no_effect / backfires. Surfaces: Typer CLI (primary), FastAPI web wrapper, markdown debrief exporter. Azure AI Foundry via Anthropic's native Messages API at /anthropic/v1/messages. claude-opus-4-6 for every role in MVP. Features shipped: - 4 scenario archetypes (competitor_disruption, crisis_response, ma_integration, activist_investor), each with world bible + 8-13 agents with distinct hidden agendas + initial state. - Setup wizard: LLM-driven interactive scenario composer. - Document grounding: PDF/DOCX/MD/TXT attached to scaffolding. - Scenario Orchestrator: agentic-age Monte Carlo — K forked branches aut…0bf1063