> 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/comms-whitepaper.md). # COMMS Whitepaper Design principles for deterministic collateral eligibility infrastructure. ## COMMS Whitepaper ### The collateral eligibility layer for tokenized stocks COMMS provides a deterministic path from asset state to collateral decision. ``` ASSET → STATE → EVIDENCE → POLICY → ELIGIBILITY → DECISION ``` A decision is evidence-backed and policy-driven. It does not imply a valuation, recommendation, or guarantee. ### Design principles * **Deterministic** — equivalent inputs and policy produce equivalent outcomes. * **Read-only** — COMMS reports decisions without controlling an asset. * **Evidence-backed** — each result can expose its supporting checks and sources. * **Policy-driven** — protocols define their own collateral requirements. ### Decision states COMMS returns `ELIGIBLE`, `INELIGIBLE`, `CONDITIONAL`, or `UNKNOWN`. `UNKNOWN` means available information cannot support a deterministic decision. It does not mean `INELIGIBLE`. ### Boundaries COMMS does not publish unverified assets, live metrics, undocumented guarantees, or invented API behavior. Illustrative examples are labeled as such. --- # 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/comms-whitepaper.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.