Operate
Activation plan
Current operating focus for public entry points and adoption.
Product docs
Have a report open? Pick the next doc by task.
Start with share-summary.md or scorecard.md. Then choose the document that explains the issue, helps you edit one page, or moves the same report into CI.
Choose by what you need to do
Use docs to answer the question in front of you.
Every path starts from the same report files: summary, scorecard, recommendations. Pick one action, read the matching doc, then come back to the report.
- 1
Understand the score
Use scoring notes to understand what the summary and scorecard are telling you.
Open scoring - 2
Explain a failed check
Use concept docs when schema, evidence, or page-structure problems need context.
Open concepts - 3
Run your own site
Use quickstart after the demo so the docs turn into one real audit.
Open quickstart - 4
Add the Action
Use the Action only after the local report already feels reviewable.
Open Action docs
Try
Quickstart
Run one real-site audit before you wire CI.
Understand
Scoring
Public scoring model and output contract.
Understand
Schema-text consistency
Why structured data and visible copy need to tell the same story.
Understand
Evidence density
How proof blocks help AI systems cite and compare pages.
Adopt
GitHub Action
Reusable Action inputs, outputs, and review order.
Adopt
Starter bundle
Public external-repo layout for GitHub Actions setup.
Adopt
Model runtime
Repository eval defaults, runtime.yaml precedence, and secret boundaries.
Share
Shareable summary
How report outputs become copy-ready public summaries.
Operate
Roadmap
Canonical public roadmap and issue sequencing.
Operate
Distribution plan
P0, P1, and P2 distribution pages and metrics.
Operate
Manual steps
Minimal GitHub, npm, and Pages setup checklist.
Where to go next
Choose the next product page
Open these pages when the report raises a buyer, trust, setup, or positioning question.
- Pricing: open-source packaging, provider costs, and setup paths.
- Security: secrets, review flow, and trust guardrails.
- FAQ: first-run questions in visible, citable language.
- Compare: how AnswerLens differs from Profound, Peec AI, and Otterly.
- Integrations: GitHub Action, providers, and validation helpers.
- Starter bundle: external-repo layout and report review order.
- Product marketing teams: homepage and proof-page hardening.
- Developer advocacy teams: docs, examples, and self-serve proof.
- Open-source maintainers: README, Pages, releases, and report-first distribution.
Review order
Report files
After you read the docs, go back to the report files in the same order used everywhere else:
share-summary.md
Start with the human-readable audit summary.
scorecard.md
Inspect coverage, checks, and scoring.
recommendations.md
Turn issues into fixes.
Then continue to the real-site quickstart or the GitHub Action path.