The method layer for references, testing, and disclosure on the public site
Methodology is the central page that explains how claims, benchmark references, and trust-sensitive content are governed on the website. It is not a full compliance dossier.
for public-site trust logic
frameworks, tests, disclosure, review
buyers, architects, content owners
read with evidence and decision layers
The core pillars that govern communication and reference quality
These four pillars make the methodology usable without turning the page into a long policy dump.
External frameworks
Uses NIST AI RMF, OECD principles, and other public frameworks as the shared language for trust, governance, and evaluation on the public site.
Internal testing baselines
Keeps public positioning and numeric claims aligned with internally verified versions, tests, uptime, and public-safe metrics.
Disclosure boundaries
Explains capability and buyer paths clearly without exposing implementation detail that is unsuitable for the public web or procurement-stage audiences.
Review and update loops
Uses author, reviewer, reviewed-date, and reference hygiene patterns so trust-sensitive pages remain more consistent over time.
The pages worth opening after methodology
Methodology works best when paired with benchmark, whitepaper, and evaluation pages along the real work path.
View benchmark summary
Use this to review how public metrics are summarized and what caveats accompany them.
Go to evaluation
Use this when framework and disclosure logic need to be translated into buyer-side decision paths.
Pair it with whitepaper review
Use this to connect the method layer to the technical dossiers architecture teams will review next.
Methodology governs interpretation, but it does not replace evidence or decision paths
After understanding this framework, continue into the benchmark summary, whitepaper, and evaluation hub so evidence and decision work stay connected.