# 2.9 Trust and traceability #### 2.9 Trust and traceability Research informs real capital decisions, and those decisions have to withstand scrutiny — from a portfolio manager, an investment committee, a compliance function, a regulator. A research platform that cannot show its work has limited value at an institution, however capable it is. Orbit is built so that everything it produces can be traced, checked, and stood behind. This is not a feature added at the end; it is a property of the whole design, and it is why the principle of transparency has run through every chapter of this section. The foundation of it is **lineage.** Every structured record carries a link back to the document it came from, as described in 2.4. Every answer and every agent output is grounded in primary sources and presents them, so a figure can be traced to the filing it was drawn from and a statement to the document that said it. Nothing Orbit produces floats free of its origin. When an agent returns a result, the path from the source material to that result is available — not hidden inside a process that has to be taken on faith. This matters in three practical ways. It makes results **checkable.** A user is never asked to trust an answer blindly. They can follow it back to the source and confirm it — which is what allows a professional to rely on the platform's output and put their name to it. The document layer, kept permanently queryable as described in 2.4, is what makes this possible: the original words are always there to return to. It makes the platform **auditable.** Because the path from source to output is recorded, a firm can demonstrate how a conclusion was reached after the fact — to its own oversight functions or to an external authority. The same lineage that lets an analyst check an answer in the moment lets a firm account for it later. And it keeps a human **accountable.** Orbit is built to support decisions, not to make them unaccountably. Its outputs are transparent precisely so that a person remains in a position to judge them, accept or override them, and take responsibility for what is done with them. The platform does the work and shows the work; the judgment, and the accountability for it, stay with the people using it. This is also where the threads of this whole section come together. The entity master makes the data connected; the structured layer makes it fast; the document layer keeps it complete; the agents make it reach; model-agnostic orchestration makes it economical and durable. Traceability is what makes all of that trustworthy — the property that lets an institution rely on the platform for work that matters, rather than treating it as a clever assistant whose output always has to be redone by hand to be sure. A platform a firm can build its research process on is one it can account for, and that is what Orbit is designed to be. --- # Agent Instructions: 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: ``` GET https://docs.orbitfin.ai/part-2-how-it-works/openapi-2.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.