Docs
Activation plan
Current operating focus for public entry points and adoption.
Canonical documentation
AnswerLens docs stay in Markdown and compile to an indexable layer.
AnswerLens keeps repo docs as the authoring surface and compiles this page to make them easier for search engines, AI systems, and external teams to discover.
Docs
Growth plan
GitHub-native packaging, funnel, and community strategy.
Docs
Self-dogfooding
How AnswerLens uses its own audit mindset on public source-material surfaces.
Docs
Quickstart
Run one real-site audit before you wire CI.
Docs
Starter bundle
Public external-repo layout for the GitHub Action adoption path.
Docs
Roadmap
Canonical public roadmap and issue sequencing.
Docs
Distribution plan
P0, P1, and P2 distribution surfaces and metrics.
Docs
Manual steps
Minimal GitHub, npm, and Pages setup checklist.
Docs
Model runtime
Repo-native eval defaults, runtime.yaml precedence, and secret boundaries.
Docs
GitHub Action
Reusable `uses: owner/repo@vX` contract and outputs.
Docs
Scoring
Public scoring model and output contract.
Docs
Shareable summary
How run outputs become copy-ready public assets.
Where to go next
Proof page map
Use these proof pages when you want buyer-facing context beyond the demo report.
- Pricing: open-source packaging, BYOK costs, and adoption surfaces.
- 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 artifact 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 artifact-first distribution.
Review flow
Artifact order
After you read the docs, move back into the artifact flow in the same order used everywhere else:
Then continue to the real-site quickstart or the GitHub Action path.