From repository issues to decisions grounded in human values.
Learn the complete workflow—from configuring an analysis to exploring evidence, comparing affected software functionality, and prioritizing what matters most.
Designby values
IssuesConcernsPriorities
1Configure
2Analyze
3Explore
4Prioritize
01 · Start
Run your first analysis
Choose a repository, analysis depth, taxonomy, and date range. ValueXplain then analyzes the repository’s GitHub issues for risks to human values.
01
Enter the repository
Paste an owner/repository name or a complete GitHub repository URL.
02
Configure the analysis
Select Fast, Standard, or Deep, choose a taxonomy, and set the inclusive issue date range.
03
Analyze issues
Review the configuration and select Analyze Issues. The job appears in the workspace immediately.
Private repositories are available only when your connected GitHub account can access them.
Repository
github.com/owner/repository
FastStandardDeep
Analyze Issues
02 · Monitor
Follow every job from one workspace
Keep configuring work while other analyses run. Select any job to see its current stage, detailed progress, elapsed time, and available actions.
01
Overall progress
The upper segmented bar shows progress across the complete analysis pipeline.
02
Current-step progress
The inner bar shows completion within the active step, independently from overall progress.
03
Recovery controls
Cancel active work when needed. A compatible failed analysis can be resumed from its last completed checkpoint.
Map, Themes, and Overview present the same completed analysis from complementary perspectives without changing its underlying findings.
01
Map
Trace affected aspects through concern mechanisms to individual concerns. Focus or collapse branches, filter results, zoom, pan, rotate the radial layout, and export PNG.
02
Themes
Inspect affected software functionality in the Theme overview or compare themes and affected aspects in the matrix. Search by theme name in either tab.
03
Overview
Review how detected concerns are distributed across the selected taxonomy. Use the same professional zoom and navigation controls as the Map.
MapThemesOverview
−+↻⛶
04 · Understand
Inspect the evidence behind a concern
Open a concern to understand what is affected, how the risk arises, and which GitHub issue supports the finding.
01
Affected aspect
The taxonomy concept placed at risk by the issue.
02
Concern mechanism
The concrete behavior or condition through which the risk arises—not merely another technical topic.
03
Evidence and source
Read the explanation and supporting issue text, then follow the source link to verify the original GitHub context.
PrivacyAccess control
Concern title
A clear explanation connects the affected aspect to the issue evidence.
View source issue
05 · Discuss
Ask questions grounded in the analysis
Use Discuss to investigate the reported concerns without leaving the result you are reviewing.
01
Ask at repository level
Compare prevalent concerns, mechanisms, evidence, and potential mitigations across the complete analysis.
02
Narrow the context
On detail views, select the concerns that should ground the discussion.
03
Recognize read-only reports
Featured projects on the public landing page expose their results, but discussion input is disabled.
Which concerns appear most often?
The analysis identifies three recurring patterns, grounded in the selected findings.
Ask about the analysis…
06 · Organize
Return to, share, and organize projects
Projects keeps owned and shared analyses together. Find the result you need using search, filters, and your remembered sort preference.
01
Find a project
Search repositories, filter the collection, and sort by recently analyzed or recently accessed.
02
Share or transfer
Use the sharing and portable project controls available to your role and ownership permissions.
03
Delete safely
Delete an eligible project from its card. ValueXplain checks ownership and dependent data before removal.
Search projects
Ssocial-appOwned project
MmastodonShared project
07 · Improve
Record structured feedback on findings
Where feedback controls are available, rate the relevance or accuracy of an analysis result and provide a concise correction when useful.
01
Rate the result
Choose the response that most accurately reflects the concern or mechanism you reviewed.
02
Add useful context
Explain what should change, especially when evidence, grouping, or interpretation can be made more precise.
03
Update when needed
Saved feedback can be revised or removed from the same control.
How relevant is this concern?
12345
Add a correction or useful context…
Feedback saved
08 · Access
Understand access and analysis limits
Your account page shows the active tier and its available analysis allowances. New accounts require administrator activation before private application use.
01
Request activation
Submit the short access request when prompted. It remains pending until an administrator approves or rejects it.
02
Check your tier
Your signed-in header and Account page show the current tier and the limits that apply to it.
03
Plan an analysis
The configuration form shows the maximum number of issues for your tier before a job is submitted.
DMAccountActivePro
Analysis allowance9 of 10 left
Access is reviewed by an administrator
09 · Admin
Operate the managed parts of ValueXplain
Administrators have a dedicated workspace for user access, taxonomies, public content, feedback data, and model-improvement workflows.
01
Control access
Review activation requests, manage roles and tiers, and safely remove eligible accounts.
02
Manage analysis resources
View, validate, publish, retire, restore, search, and remove eligible taxonomies.
03
Manage public content
Feature eligible projects, publish research, and use Admin → Media to preview or replace the signed-out landing-page YouTube walkthrough.
04
Improve models safely
Export feedback datasets and operate the separate model-training workflows with their evaluation and rollback controls.
UsersTaxonomiesResearch
Schwartz Refined TheoryPublished
EU AI ActRetired
Manage taxonomy
10 · Help
Resolve common interruptions safely
Most interruptions can be diagnosed from the job details without discarding completed work.
01
A job appears paused
Open its details first: repository fetching and model analysis are separate stages and may progress at different speeds.
02
An analysis fails
Read the failure message and use Resume analysis when it is offered. Completed compatible stages are retained.
03
A repository is unavailable
Confirm the repository URL and verify that the connected GitHub account can access it.
Analysis interruptedCompleted stages are retained
Open the job details to see the failed stage and the exact recovery options.
Resume analysis
Ready to use ValueXplain?
Assess risks to human values and prioritize what matters most.