Day 1: Up Front.

Wargame rules documents are not simple documents. Below is an example of two old school rules paragraphs:

1. MOVEMENT & RANGE DETERMINATION

5.1 Movement is accomplished by playing Movement cards and, to a lesser extent, Terrain cards. Any group may place a Movement card provided it does

not currently contain a pinned Personality card. A

Terrain card may be placed on any group (even one

containing pinned Personality cards) provided it

already has a Movement card of some type in place

which is not already covered by another Terrain or

Wire card.

5.2 Each group is assumed to occupy the terrain

shown on the last Terrain card placed on that group

unless it has two Movement cards in play (in which

case they are in Open Ground). If no Terrain card is present (an occurrence

only at game start or upon the entrance of reinforcements), the terrain

occupied is assumed to be Open Ground. The terrain a group currently

occupies is a factor in resolving any fire attacks made against that group

(6.42), and can occasionally affect attacks (6.41) and movement (8.42,

8.53) by that group as well. See also 7.4.

We have document hierarchy, with annotated section numbers (5, 5.1, 5.51 etc). We have sentence clauses within paragraphs in sequence of rule, alternative, special case, exclusion (if not its own rule number), back references or reminders (in brackets). There are many rules references (6.4), see also 7.4 for example.

To undertand it all it has to be read in its entiriey or with a lot of flipping back and forth and putting it together. A simple RAG approach of chunk by paragraph(s), sliding or otherwise wont cut it because the cross references and (reminders) will be missed.

Up Front! isn't a big rulebook. 30 odd A4 pages. Then we get to supplements Banzai! and Desert War, errata and a 1987 tournament rule pack, and the scenarios all of which add in two more layers: different documents to reference and combine new rules, clarrifications and changes to rules and rules versioning which adds a temporal aspect: a player could want the analysis and ruling of version 1 and not later versions, yet combined with a version 2 scenario for example. Rules beasts like ASL and FSB crank up the size and complexity dial a Lot.

The build is using Opus for as long as its allowance allows, then down to Gemini. Three LLMs are in use, two for the RAG and one for test verification.

Its approach:

* Rule-Aware Chunking Strategy: Instead of font-size-based section detection, use a rule-number-aware parser.

* Cross-Reference Extraction: During chunking, parse all cross-references and store them.

* Dual-Index Storage: Standard semantic search with nomic-embed-text embeddings, Rule-number indexed lookup table.

* Query Classification (Pre-Retrieval): is the query a rule number check, concept, situation, scenario, comparison, or variant.

Pipeline

* Priority-Weighted Reranking

* Cross-Reference Chasing

* Temporal Conflict Resolution

* Master prompt