SRC / PROTOCOL
Match each assertion to the artefact that can actually test it.
The source protocol distinguishes legal records, product documents, platform statements and reproducible observations before interpreting a result.
Primary record
Use regulators, courts, company registers, filed accounts and binding terms for identity, legal status and contractual obligations.
- Publisher and title
- Stable location
- Effective and access dates
- Exact assertion
- Market and product scope
Product document
Technical guides and fee schedules can establish a disclosed capability or rule. They do not establish actual performance, uninterrupted availability or user suitability.
The panel text states the applicable control and output boundary.
Platform statement
Marketing, security and reserve statements remain attributed unless an independent artefact tests the same assertion and scope.
The panel text states the applicable control and output boundary.
Runtime observation
A scenario requires environment, account class, version, market, timestamp, inputs, steps, output and failure conditions. This edition publishes those runs with explicit inputs and pass conditions.
The panel text states the applicable control and output boundary.
Boundary output
Every result states what the evidence cannot prove. Authenticity, relevance, scope and currency are separate checks.
- Document result
- Inference prohibited
- Scenario required
- Review owner
Retrieval control
Every input carries a retrieval date. Fees, terms, entities, regulatory records, versions and incidents are re-fetched from the primary publisher before a changed conclusion is released.
The panel text states the applicable control and output boundary.
Output parity
The server-rendered proof file controls. Structured data, RSS, the research index and llms.txt may expose only the same protocols, boundaries and dates. llms.txt is a navigation surface, not a Google ranking protocol.
The panel text states the applicable control and output boundary.