> For the complete documentation index, see [llms.txt](https://prismnetwork.gitbook.io/prismnetwork-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prismnetwork.gitbook.io/prismnetwork-docs/4.-technical-architecture/4.2-engineering-level-features.md). # 4.2 Engineering-Level Features **(1) Multi-Market Aggregation and Unified View** Prism Network connects to multiple prediction markets including Polymarket, Kalshi, and Future Markets, organizing scattered events, prices, probabilities, liquidity, fees, and settlement rules into a unified view. Event Standardization: * Each event is decomposed into fields including: event category, event subject, time window, outcome options, market source, contract type, quote method, tradable assets, market status, settlement conditions, access restrictions, and risk labels * The system determines whether multiple markets refer to the same real-world outcome through semantic matching, time window matching, outcome option matching, settlement rule matching, and market source weighting * Upon mapping completion, related markets across multiple platforms are consolidated under a unified Prism Event ID **(2) Probability Normalization Mechanism** Different prediction markets adopt different quoting methods. Prism Network converts these various quotes into unified implied probabilities, forming a standardized probability view under the same event dimension. The system incorporates fees, bid-ask spreads, slippage, order book depth, and executable order sizes into its calculations, calibrating the true execution probabilities across different markets. **(3) Verifiable Execution and Auditing** Every strategy execution generates a complete record: execution time, event market, execution venue, trade direction, filled price, fee costs, slippage, settlement status, and final outcome. These records serve user-side queries, system-side post-mortem analysis, and risk event tracking. --- # 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://prismnetwork.gitbook.io/prismnetwork-docs/4.-technical-architecture/4.2-engineering-level-features.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.