Version history
GAOS evolves additively across the v0.x line. Products can adopt new mechanism families independently, while deprecated compatibility names remain available until the v1.0 boundary.
Current source: v0.16.0
The latest batch expands GAOS from a grid-focused engine into a composable tabletop mechanism suite: heterogeneous boards, hidden information, zones, card-play composition, portals, high-frequency lockstep, and multi-agent episodes.
Tabletop mechanism suite
v0.16.0 — portals and multi-agent play
Prepared July 23, 2026.
- Atomic portal planning and commit across square, hex, and graph boards and ordered, bag, or slotted zones.
- Bounded multi-hop traversal, cycles, groups, footprints, transformations, destination capacity, and deterministic contention.
- Frame skipping for decision-point agents with transcript v1.2.
- Seat-redacted
MultiAgentEnvironmentepisodes with canonical simultaneous batches and per-seat rewards. - Authoritative hidden-information deployment guidance, including per-match server resolvers and optimistic P2P dispute verification.
Portal reference → · Multi-agent reference → · High-frequency turns →
v0.15.0 — zones and card composition
Prepared July 23, 2026.
- Ordered, bag, and sparse slotted zones with atomic transfers.
- Seeded shuffle, draw, round-robin dealing, and batch dealing.
- Keyword layers, response priority, declarative targets, durations, phase hooks, and deck/squad validation.
- Priority resource claims for contested draft picks and capacity.
v0.14.0 — information partitions
Prepared July 23, 2026.
- Deterministic
viewFor(state, seat)observations. - Independent identity and order visibility for zones.
- Fog-of-war, entity shells, leak assertions, revelations, teams, spectators, and ranked multi-seat outcomes.
- Turn order, participation descriptors, pattern matching, sparse tick transcripts, rollback resimulation, and state digests.
Information partitions → · Turn order and lockstep →
v0.13.0 — neutral core and layouts
Prepared July 23, 2026.
- Genre-neutral reducer, action, solver, and replay names.
- Deprecated v0.12 aliases retained with equivalent behavior.
LocationRefaddressing across multiple containers.- Square, axial-hex, and directed-graph layouts with generic pathfinding, line-of-sight, fields, and keyed movement.
Locations and layouts → · Migration table →
Foundation releases
| Version | Date | Main addition |
|---|---|---|
| v0.12.0 | 2026-07-22 | Runtime validation, integrity, retry lifecycle, and deterministic edge-case hardening |
| v0.11.0 | 2026-07-22 | Atomic, product-defined resource transactions |
| v0.10.0 | 2026-07-22 | Resumable agent interruption |
| v0.9.2 | 2026-07-21 | Complete mechanism documentation, benchmark mission, and Build Week release packet |
| v0.9.1 | 2026-07-21 | Nearest reachable qualified paths and the public VitePress site |
| v0.9.0 | 2026-07-21 | Gates, latched triggers, policy-driven rays, and generic behavior trees |
| v0.8.0 | 2026-07-21 | Chain reactions, projectiles, push chains, arrivals, claims, transport, and interlocks |
| v0.7.0 | 2026-07-21 | Deterministic multi-wave settlement |
| v0.6.0 | 2026-07-21 | Local Ollama-backed CLI agent support |
| v0.5.1 | 2026-07-21 | Product and action-prompt composition |
| v0.5.0 | 2026-07-21 | Extensible keyed-model drivers and the gaos-agent CLI |
| v0.4.0 | 2026-07-21 | Deterministic agent environment, portable tools, and Python evaluation |
| v0.3.0 | 2026-07-21 | Reusable geometry and pathfinding |
| v0.2.0 | 2026-07-21 | Reusable engine core, generic solver, and replay verification |
| v0.1.1 | 2026-07-21 | Build output for Git-based package installation |
| v0.1.0 | 2026-07-21 | TypeScript and Python turn SDKs, protocol documentation, and release automation |
Compatibility policy
- v0.13 through v0.16 are additive.
- Existing single-board and perfect-information reducers continue to work.
- The old
Grid*core names remain deprecated aliases through v0.x. - v1.0 removes those aliases and is the next intentional breaking boundary.
For migration details and maintainer publishing instructions, see Release process and migrations.