wip deepseek

2026-07-07 16:42:42 +02:00
parent 00c67dd66a
commit 9555423f51
12 changed files with 2871 additions and 13 deletions
@@ -28,5 +28,20 @@ A deterministic rule that checks LLM claims against Operation Facts and known ga
 ### Validation Issue
 A machine-detected problem in an LLM claim, such as a direct contradiction, weak evidence, missing alternative, or impossible timeline.

+### Game Knowledge
+Domain knowledge about the game or mod that the AI may use during analysis, such as unit capabilities, faction rules, map geometry, build restrictions, and known exceptions. Game knowledge may be used both to shape prompt guidance and to power deterministic validation.
+
+### Knowledge Scope
+The applicability boundary of a piece of game knowledge. A mod is a game version and defines its own complete knowledge set. Within a mod, scope can be global (applies to all factions and maps on that mod), faction-specific, or map-specific. There is no separate "mod scope" because the mod IS the top-level scope selector — the replay's mod determines which knowledge set is loaded.
+
+### Knowledge Set
+A named collection of game knowledge entries for a specific game version (mod). Each knowledge set is self-contained and complete for its mod — there is no cross-set inheritance or conditional sharing. The set is organized hierarchically by scope: `global/` entries apply across all factions and maps; `factions/{name}/` entries are scoped to a faction; `maps/{id}/` entries are scoped to a map. The replay's mod name directly selects which knowledge set to load (e.g., `"default"` for base game, `"corona"` for the Corona mod).
+
+### Knowledge Entry
+The smallest reusable unit of game knowledge within a knowledge set. A knowledge entry has an identifier, a set of predefined tags, and a text description (markdown). It is the unified format used both for prompt rendering and for validation queries. Scope is inherited from the entry's path position within the knowledge set (global, faction, or map), not stored in the entry itself.
+
+### Knowledge Tag
+A predefined label attached to a `KnowledgeEntry` to enable querying by validation logic. Tags belong to a finite taxonomy covering capabilities (e.g., `builder`, `pack`, `unpack`, `amphibious`, `returnToProducer`), types (e.g., `infantry`, `vehicle`, `aircraft`, `naval`, `structure`), combat roles (e.g., `antiInfantry`, `antiVehicle`, `antiAir`, `antiNaval`, `antiStructure`), and special power references (e.g., `specialPower:PackReplaceSelf`).
+
 ### Revision Pass
 (Partially implemented) A hidden LLM request that receives the prior draft, validation issues, and relevant Operation Facts, then produces a corrected analysis without exposing apology or correction chatter to the user. Currently, validation issues are detected and logged, but no automatic revision pass is triggered. The revision logic still needs to be wired into `AIChatPanel`.