every stored passage retrieved, ranked 1-3 this order
Each point is one passage, placed by its own embedding and flattened onto the two directions the corpus varies most along. Flattening keeps only part of the detail (the line above says how much), so nearness here is a rough guide. The points that light up are exactly the passages the engine just handed the commander, ranked as in the trace.
The index holds the doctrine, roles and tactics the commander reasons from. Pick an entry to read it, or filter the index by tag or title.
Upload plain-text documents, PDFs, or remote URLs. The engine extracts, chunks, and vectorizes the content into the local IndexedDB vector database.
The engine embeds it as doctrine the commander can retrieve, with its own passage ID, and (with a model running) writes a reference entry from it.
Restore puts the shipped doctrine, roles, tactics and named commanders back, and starts a new fight. Clear empties the knowledge base so you can build one from scratch here; Restore brings the shipped one back.
Describe the change in plain language. The engine rewrites this commander's tactics and leadership style to match.