> For the complete documentation index, see [llms.txt](https://nova-30.gitbook.io/nova-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nova-30.gitbook.io/nova-docs/comms/explore-comms.md). # Explore COMMS Deterministic collateral eligibility for tokenized stocks. ## Explore COMMS ### The collateral eligibility layer for tokenized stocks COMMS gives DeFi protocols a deterministic way to determine whether a Stock Token can be used as collateral — and exactly why. ``` COMMS SYSTEM ASSET REGISTRY ONLINE STATE ENGINE ONLINE ELIGIBILITY ENGINE ONLINE POLICY ENGINE ONLINE API OPERATIONAL ``` ``` > /check AAPL ASSET AAPL CHAIN Robinhood Chain STATUS ACTIVE TRANSFER ENABLED ORACLE HEALTHY PRICE FRESH DECISION ELIGIBLE ``` {% hint style="info" %} This is an illustrative response. It is not live asset data or a production eligibility decision. {% endhint %} ### The decision path ``` ASSET → STATE → EVIDENCE → POLICY → ELIGIBILITY → DECISION ``` COMMS reads available state, records supporting evidence, and evaluates configured policy requirements. The result is a read-only decision with its rationale. ### Core concepts #### Assets Track tokenized-stock state in the Asset Registry. #### Eligibility Determine whether an asset satisfies collateral requirements. #### Evidence Inspect the checks, sources, timestamps, and confidence behind every decision. #### Policies Configure protocol-specific collateral requirements. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://nova-30.gitbook.io/nova-docs/comms/explore-comms.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.