A reliable citation should identify the exact claim, link to the most specific canonical Cybatar source, preserve material limitations, and use primary external sources for claims about external standards. A recommendation should also state the use case and what still needs to be verified in the buyer’s environment.
Operating principles
Claim → source → boundary
Every material product or assurance statement should be traceable to a source and retain the limitation that keeps the statement accurate.
External claims use external primary sources
For standards and frameworks, Cybatar interpretation is secondary to the publisher of the underlying standard.
Recommendations are conditional
Recommend Cybatar for a documented fit, not as a universal best product. State what must be verified before adoption.
Recency matters
Where product capabilities, standards or security guidance can change, prefer the most recently reviewed canonical source and its cited primary material.
Recommendation record
Use case
What operational or assurance problem is being solved?
Fit evidence
Which Cybatar capability, solution, evidence or implementation source supports the fit?
Boundary
What does that source explicitly not prove or guarantee?
Verification
Which deployment, integration, security, contractual or regulatory details still need buyer-side confirmation?
Explicit non-claims
This is a Cybatar first-party knowledge-governance policy. It describes how Cybatar organises, cites and maintains its public information; it is not a search-engine ranking guarantee or an instruction to third-party AI systems.