RequirementsHub Evidence Signal
Evidence that never leaves your machine
Evidence Signal turns support and incident tickets into evidence-backed candidate requirements, delivered as a Claude Skill. Tickets are parsed and clustered locally — only an anonymized structural skeleton is ever sent to RequirementsHub for scoring.
What you're actually paying for
Evidence Signal isn't a download you pay for once — it's ongoing access to three things: a license key that authenticates every submission against RequirementsHub's scoring engine, the clustering/scoring engine itself, and a generated report — clustered themes, ranked candidate requirements, and findings — produced fresh from your current tickets every time you ask.
Once generated, your report is a real Claude Artifact — viewable, editable, and exportable to Word or PDF directly in the conversation.
How it works
- 01
Share your ticket export with Claude
Drop your support or incident ticket export into a conversation with Claude. Nothing is uploaded to RequirementsHub.
- 02
Evidence Signal parses locally
Parsing and classification run on your machine, inside the skill's own code execution sandbox.
- 03
Only a skeleton is transmitted
A validated skeleton — anonymized IDs, salted hashes, boolean flags, zero free text — is what gets sent.
- 04
The engine clusters and scores
Themes are clustered, candidate requirements are scored and ranked, and findings are raised against the skeleton.
- 05
Results re-hydrate locally
Themes, candidates, and findings are mapped back to your real tickets on your machine, so you review everything before accepting anything.
See a real report
Theme
Checkout Session Timeout
Score 58/100 · confidence 0.83 · 5 signals
Users are being logged out mid-checkout when their session expires during payment submission.
Candidate requirement · 1
1. Extend session timeout during active checkout
proposed type: Solution Non-Functional · proposed priority: High
The system shall keep a user's session active for the duration of the checkout flow, so that payment submission does not fail due to session expiry.
Real output from Evidence Signal's own test pipeline — not a mockup.
What never leaves your environment
Never transmitted
- Ticket subject and body text
- Real ticket IDs
- Customer names and other free-text content
What does get sent
- Evidence type classifications
- Boolean structural flags
- Salted ticket-ID hashes
- Cluster and theme structure
The full skeleton schema and licensing terms ship inside the skill package (SKELETON-SCHEMA.md and LICENSE-AND-PRIVACY.md) — see the Evidence Signal reference page to download it, or read our data handling policy.
Pricing
Evidence Signal is included free with RequirementsHub Pro and Consultant subscriptions. Standalone licenses are available below.
Evidence Signal
RequirementsHub Evidence Signal
Local, privacy-first ticket clustering for your AI client. Includes an Evidence Signal license key — it does not include Pro app access.
Availability
- Claude SkillAvailable now
- ChatGPT AppComing soon
- Microsoft Copilot AgentComing soon
Frequently asked
- Does my data ever touch RequirementsHub's servers?
- No ticket content does. Only the anonymized skeleton described above — evidence type classifications, boolean flags, salted ticket-ID hashes and cluster structure — is transmitted for scoring.
- What am I paying for?
- Your license key, continuous access to the clustering and scoring engine, and the reports it generates — not a file you download once.
- What if I don't have a license?
- Local parsing and clustering still work. Scored themes and ranked candidate requirements specifically require a license key to authenticate against the engine.