Verifiable answers: proof-trees as citations
Ship the reasoning, not just the conclusion.
What most systems ship
A confident sentence. Maybe a footnote. If you're lucky, a hyperlink. If you're really lucky, a page number. Never the actual reasoning path.
What PRISM ships
A tree. Root: the query. Nodes: the NEXUS entities consulted. Leaves: the source URLs with timestamps. You can walk the tree, delete a node, and watch the answer degrade. That is what actual verifiability feels like.
Why this changes the buyer conversation
A hospital CIO stops asking 'is your model accurate?' and starts asking 'can I audit any given answer end-to-end?' We are the only architecture where the honest answer is yes.
Why we use different words
Where the industry says LLM, we say CLLM. Where it says vector database, we say NEXUS. Where it says Chain-of-Thought, we say PRISM proof-tree. Where it says RAG, we say LATTICE. Where it says trillion-token dataset, we say Smart Router Dataset. Different words because different architecture. Read the whitepaper.