Empire Build

What Empire Build is for

A real, playable territory/civilization-lite sim — not a rules reference. Every tile's yield, every claim's cost, and every contested claim's outcome comes from a documented formula.

What it does

new_game(target_tiles, max_turns) starts a game on a fixed 5x5 grid of 25 tiles (addressed "row,col") with you owning the center tile.

• claim_tile(state, tile_id) claims a tile that is orthogonally adjacent to territory you already own (a real adjacency check — you cannot claim a disconnected tile). Unguarded tiles cost real gold (10 + yield * 3) and are claimed immediately. Garrisoned tiles trigger real combat first (see below); the claim only succeeds if the attack wins, and the gold cost and army casualties apply either way.
• recruit_army(state, count) buys count army units at a real per-unit gold cost.
• advance_turn(state) aggregates real income (the sum of every owned tile's yield) minus real army upkeep, adds it to your treasury, and advances the turn.

get_status(state) reports gold, army, tiles owned, per-turn income, and which neighboring tiles are currently claimable. list_map(state) shows every tile's yield, garrison, and ownership. render_game(state) gives a human-readable summary. game_rules() explains every formula without a live game.

The formulas, in full

• Tile yield: ((row*3 + col*5 + 7) % 6) + 2 — a deterministic, reproducible pattern (range 2-7), not a random or hand-picked assignment.
• Garrison: equal to the tile's own yield wherever row+col is even; 0 otherwise. Your own starting tile is exempted (you cannot begin the game fighting yourself).
• Claim cost: 10 + yield * 3.
• Combat resolution: each side computes an effective strength as its base strength times an independent random multiplier drawn uniformly from [0.85, 1.15] (seedable for reproducibility). The attacker's base strength is army * 4; the defender's is the garrison value directly. The higher effective strength wins. The attacker always takes casualties: max(1, round(army * defender_effective / (attacker_effective + defender_effective))), capped at the whole army.

Because the randomness is bounded to ±15%, a wide enough strength gap makes the outcome deterministic in practice — see the test suite for worked guaranteed-win and guaranteed-loss cases that hold across every possible roll.

Win / loss

Win: control at least target_tiles tiles by max_turns. Loss: max_turns passes without reaching the target.

Stateless architecture

No server-side session. Every tool call receives the full current game state as a plain JSON object and returns the new state; the calling assistant holds and passes it between turns.

What it is not

Not narrative flavor text pretending to be a game — every yield, cost, and combat outcome comes from a real, tested, documented formula. Fully local, zero upstream calls, nothing stored.

Empire Build — Privacy Policy

Effective 28 September 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Empire Build is. Empire Build is a connector (an MCP server and REST API) that AI assistants and personal agents call on your behalf to run a real, playable, fully local resource-management economy sim. You interact with your assistant; the assistant sends us only the arguments needed for that one move — a game state object and your action.

What we receive. The game state and move arguments for each tool call, the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant, and a Pro API key if you have one), and standard server logs.

Everything is computed locally and nothing is stored server-side. There is no upstream call at all, live or otherwise, and no game state or move is logged in request bodies, recorded, or used to train anything. The entire game exists only inside the state object that travels between you and your assistant; our server never retains a copy after answering the request.

What we do not receive or store. We do not receive your conversation with the assistant or your name, and each request is answered independently — nothing carries over between requests. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting-provider access logs, which contain IP addresses and request paths but not request bodies, are retained for up to 30 days for security and abuse prevention.

Sub-processors. None — the entire game engine is bundled with the server and runs locally. Hosting: Vercel (United States regions).

Legal bases and your rights. Our processing is necessary to provide the service you request through your assistant. Because we store no personal data beyond short-lived logs, requests to access, correct or delete personal data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. We do not sell or share personal information and do not use your data to train models.

Children. Empire Build is a general-audience service operated by the adult using the assistant.

Changes. We will post changes here with a new effective date.

Empire Build — Terms of Service

Effective 28 September 2026. These terms govern use of the Empire Build connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. Empire Build runs a real, playable resource-management economy sim with original game logic and documented formulas, accessed through an AI assistant or directly over MCP or HTTP.
2. Original content. The game logic, economic formulas, and content are original works of Unify Dynamics LLC and are not copied from any third-party game or product.
3. Stateless by design. The Service keeps no server-side game session. Each tool call must include the complete current game state; the calling assistant is responsible for holding and passing it faithfully.
4. Acceptable use. Automated use within the published rate limits is welcome.
5. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time.
6. Data. Our Privacy Policy describes what we process. In short: your move is answered from the game state you send us, and nothing is stored.
7. Pro keys. Optional Pro API keys are issued at our discretion, are personal to the holder and may be revoked for abuse.
8. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service. Our total liability is limited to US $100.
9. Governing law. California law; venue in San Mateo County, California.
10. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/empirebuild

Empire Build support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://empirebuild.connectorbay.com/mcp
• REST API: https://empirebuild.connectorbay.com/openapi.json
• Live status: https://empirebuild.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Empire Build never asks for them.