AI appMethodology example

SilentCritique Public Report Privacy

The private report sharing route keeps token-gated reports out of search, which is the right privacy stance and a useful boundary for the new public verdict product.

Tested 2026-06-11sc-agent-trust-v0.1Subject route/report/sample

Methodology example badge

The visible trust mark for this verdict.

Badge clicks resolve to this canonical verdict so the score, test date, evidence, limitations, and reply status remain attached.

Internal examples are not embeddable third-party certifications.

This is a calibration verdict based on repository evidence. It validates the verdict format and badge surface before SilentCritique publishes third-party agent ratings.

Editorial notice

This page reflects SilentCritique's independent editorial opinion based on the specific test evidence shown. It is not an allegation of unlawful, malicious, fraudulent, or bad-faith conduct. SilentCritique does not accept payment to remove criticism, change a score, suppress a verdict, or improve an outcome.

Editorial policy Corrections and reply

Claim tested

Can SilentCritique add public verdict pages without accidentally indexing private session reports?

Evaluator panel

Privacy reviewerSEO reviewerProduct reviewer

Evidence reviewed

Reports are noindex

The public report route returns robots index false for token-gated reports.

src/app/report/[id]/page.tsx

Share token is validated server-side

Report data loading checks a public report token before reading the session and notes.

src/lib/public-report.ts

Robots disallows report routes

The robots policy includes /report/ in private disallow rules.

src/app/robots.ts

Test setup

Reviewed public report metadata behavior.
Checked report access token validation path.
Compared report privacy with sitemap and robots policy.

Strengths

Private session output is not being used as SEO inventory.
Token validation happens before report data is returned.
This creates a clean separation point for a new public verdict model.

Failure modes

Reusing /report/[id] for verdict SEO would create privacy risk.
A public verdict promotion flow needs explicit human review before indexing.
The current report component says confidential report, which does not match public certification language.

What would improve the score

Keep /report private and noindex.
Add /verdicts as a separate public model.
Require publish status before any verdict is included in the sitemap.

Limitations

This review did not inspect deployed headers.
This is a code-level calibration verdict, not a penetration test.

Visible dissent

The SEO reviewer wanted indexable reports for growth; the privacy reviewer rejected that as the wrong tradeoff.
The product reviewer recommended a separate verdict route rather than mutating the report route.

Right of reply

This verdict captures a product boundary: public verdicts should not weaken private report access.

Methodology matters

Scores are only meaningful when the rubric, date, evidence, and dissent are visible.

Read methodology