How it works, then the tool.
The discovery page is now tool-first. It shows the user what the code is doing, exposes route inputs, and keeps the live findings document in a pop-up instead of crowding the page.
1. Define route
Set target nucleus, projectile beam, and neutron evaporation. The candidate is calculated from those inputs.
2. Run screen
The visual pipeline moves through target, projectile, compound nucleus, evaporation, scoring, and validation output.
3. Save evidence
Save locally, export findings, store candidate data in a project, or run an authenticated screening score.
Atom-combination visualization
No proprietary math is shown. The visible process is public route logic only.
Organize for review
Run the screen to score this route.
Verification method
The app combines conventional nuclear screening with structural, checksum, basis-stability, and residue checks. These improve ranking discipline; they do not prove synthesis.
Conventional math trace
Verification checks
Validation checklist
Predicted alpha-chain map
Verification and source review.
This section keeps the product focused on verifiable user functions: candidate math, evidence review, source bias checks, and QA.
Known data sources
Use NuDat, NNDC, IAEA LiveChart, peer-reviewed synthesis literature, and facility reports as external references. The app stores notes but does not replace expert review.
Reference bias controls
Databases reflect known measured data. Missing records do not prove a candidate exists. Existing records do not prove a proposed route can synthesize it.
Frontend QA
Run the QA scan below to check duplicate IDs, broken anchors, unbound buttons, and unlabeled controls.
QA output
Authentication and API readiness.
These controls call the app API and check whether saved project functions are available.
API connection
API not checked yet.
Register or log in
No access token stored.
Workspace, project, candidate, evidence, audit.
This is the front-end home for saved workspaces, projects, candidate records, evidence, and review history.
Profile state
Not logged in.
Active workspace: None selected
Active project: None selected
Evidence and audit
API response output
Saved discovery records.
The archive is a functional local browser store. Every generated archive button is delegated to download or reload that record.
Browser archive
No archived candidates yet.
Archive ready.
Common questions.
FAQ entries keep expectations controlled and explain what the tool does and does not do.
Does this discover elements by itself?
No. It organizes and screens hypotheses. Formal discovery requires experimental evidence, peer review, and scientific recognition.
What changed in this frontend?
The user-facing functions are now visible: login, workspaces, projects, candidate save/load, evidence, audit trail, archive, and source review.
Can users enter their own route?
Yes. Target, beam, and evaporation inputs are now functional and directly drive the visual route, scoring, report, archive, and saved payload.
What claim boundaries are enforced?
The frontend keeps the product focused on element-isotope screening and prevents unrelated claim paths from being mixed into the discovery workflow.
Research-preview boundaries.
This section is not a substitute for legal counsel. It gives the product a visible legal and claim-boundary page before public launch.
Disclaimer
The tool is for educational, research-preview, and hypothesis-organization use. It does not make official scientific, commercial, medical, investment, or legal claims.
Data and privacy
Browser archive records stay local unless the user saves them online. Online project storage requires login, workspace, and project setup. Add a formal privacy policy before public deployment.
Scientific claims
Do not market candidate scores as proof of synthesis, stability, existence, or official recognition. Scores are prioritization signals only.
Publishing requirement
Before launch, get legal review, scientific reviewer feedback, and staging QA. The frontend now gives those gates a visible place.
Contact the creator.
Functional contact form opens an email draft. The hidden honeypot field has a spam-guard function.
Creator context
Public-facing creator section is intentionally lean in this QA build so it does not distract from the product workflow.