Goal
Create a concise trust page in docs describing verification and release integrity signals.
Why
Users evaluating a TA library for production need one place to understand reliability posture quickly.
Scope
- Add
docs/trust.md (or similar) linked from README.
- Cover compatibility policy, release gates, CI checks, and versioning guarantees.
- Include where to find changelog, tags, release notes, and benchmark/compat reports.
Implementation prompt
Write a single page that answers:
- Why results are trustworthy
- What is validated before release
- How users can independently verify versions and behavior
- What limitations remain
Acceptance criteria
- Trust page exists and is linked from README.
- Content references real repo artifacts (CI workflow, release tags, changelog, compat policy).
- Language is factual and auditable (no marketing claims without evidence).
Test plan
- Link checker for all references.
- Manual review: can a new user verify trust signals in < 5 minutes.
Goal
Create a concise trust page in docs describing verification and release integrity signals.
Why
Users evaluating a TA library for production need one place to understand reliability posture quickly.
Scope
docs/trust.md(or similar) linked from README.Implementation prompt
Write a single page that answers:
Acceptance criteria
Test plan