Documentation Index
Fetch the complete documentation index at: https://docs.specterpq.com/llms.txt
Use this file to discover all available pages before exploring further.
GitHub issue snapshot date: May 5, 2026.At that point, the product repo had 4 open issues and no
good first issue or help wanted labels. Use the live issue filters below for the latest state.Start with the live queue
All open issues
Review the full current backlog in the product repo.
Recently updated issues
See what changed most recently before you pick work.
Product repository
Backend, frontend, issue tracker, and CI live here.
Contribution workflow
Read the repo and docs workflow before opening a PR.
Current open issues
These are the open product issues visible on May 5, 2026:#19 DevOps and release hardening
Branch strategy, environment separation, CI gates, release runbooks, and deployment safety checks.
#17 Core hardening epic
Protocol correctness, view tag semantics, workspace cleanup, and production-readiness refactors.
#18 Client-side key generation
Move long-term key generation out of the backend and into a client-side WASM flow.
#16 On-chain announcement recovery
Remove backend dependence from recovery by making chain data the authoritative announcement source.
Pick work by skill set
| If you want to help with… | Best issue | Primary repo areas |
|---|---|---|
| Release process, CI, environments | #19 | .github/workflows/, deploy/config docs, environment templates |
| Protocol correctness and crate boundaries | #17 | specter/specter-api/, specter/specter-stealth/, specter/specter-crypto/, specter/specter-registry/ |
| Browser-side cryptography and secure key ownership | #18 | SPECTER-web/src/, WASM bindings, hosted API flow docs |
| Recovery guarantees and decentralization | #16 | contracts/indexing work, scanner fallback logic, recovery documentation |
| Docs clarity and docs IA | Start with a small docs PR or pair your docs work with one of the issues above | This Mintlify docs repo, especially index.mdx, build/, reference/, and API pages |
How contribution works across repos
| You are changing… | You will usually touch… |
|---|---|
| Product behavior | The product repo first, then this docs repo if public behavior changed |
| Public docs, guides, diagrams, or structure | This Mintlify docs repo |
| Issue triage and roadmap scope | The product repo issue tracker, then roadmap/docs if the public status changed |
Good contribution habits
- Claim or comment on an issue before you start large work.
- Keep each PR aligned to one issue or one tightly scoped change.
- Update docs in the same change set when public behavior changes.
- Add tests for behavior changes and regression fixes.
- Call out partial or placeholder behavior explicitly instead of smoothing it over.
If you are maintaining the backlog
The current repo does not yet expose onboarding labels such asgood first issue, help wanted, or area labels. Adding those labels would make contribution discovery much easier for new contributors.