> For the complete documentation index, see [llms.txt](https://nfa.gitbook.io/nfa-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nfa.gitbook.io/nfa-docs/live-data-and-adapters/ukrainian-osint-signal.md). # Ukrainian OSINT signal ## Ukrainian OSINT signal Some of the hardest markets to forecast well are the territorial ones: whether a particular town will be captured or entered by a given date. Crowd prices on these move slowly and often lag the ground truth. NFA anchors them with open-source intelligence instead. ### What it reads For markets of the form "will a given town be captured or entered by a date," NFA draws on [DeepStateMap](https://deepstatemap.live), a widely followed, community-maintained map of Ukrainian territorial control that publishes which areas are held, contested, or advancing. The engine reads the current state of the map around the town in question and turns it into a read on that specific market. Because the phrasing of these markets matters (entering the edge of a settlement is not the same as controlling it) the signal is interpreted per market rather than applied bluntly. {% hint style="warning" %} **This is a leading indicator, not the resolver.** These markets settle on a designated authority, and the open-source map typically runs ahead of it. NFA uses the DeepStateMap read as early, labelled Ukrainian OSINT context that informs the forecast. It is never treated as the official outcome. {% endhint %} ### Why it helps On a fast-moving front, the difference between a map updated today and a crowd price updated last week is real edge. Anchoring these markets to current open-source ground truth, clearly labelled as Ukrainian OSINT, gives the engine a more current picture than the market often has, while keeping an honest line between an early signal and the settled result. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://nfa.gitbook.io/nfa-docs/live-data-and-adapters/ukrainian-osint-signal.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.