A research surface for treating the output as a testable target.
GenesisCore does not claim that its output is already science. It claims that the output should be treated as a target for scientific verification and engineering discipline. This page fixes the experiment method, the verification method, and the public weekly board frame.
Main verification target for trait-level comparison
The minimum condition for the main analysis
Weekly batch execution is part of the design
The public graph surface is live while weekly metrics are still being connected.
Why compare against Big Five
Subjective resonance alone cannot support a product-level claim. GenesisCore uses Big Five as the main comparison surface so the output can be assessed against a known trait framework instead of only post-hoc feeling.
Big Five is the main evidence surface
The main experiment does not depend on user resonance alone.
Feedback stays separate
Subjective feedback is stored as a UX signal rather than primary proof.
Verification target, not proof label
The page states a posture toward verification, not an earned scientific title.
Experiment method for the current phase
Only runs with research consent and complete required inputs enter the main experiment. Chart features, consent snapshot, Big Five scores, and version data are bound by analysis_id, while duplicates are reduced to the latest valid case.
Consent-Gated Capture
Only consent-on runs enter the research store.
analysis_id Binding
Chart features, Big Five, and consent snapshot are bound to one analysis_id.
Complete-Case Filter
Missing fields and duplicates are filtered out before the main analysis.
Weekly Dataset Build
The dataset is rebuilt weekly so the same rules can be rerun under the same conditions.
Verification method for the current phase
The main comparison is M0, a non-astrological baseline, against M1, which adds astrological feature vectors. The primary metric is MAE, the secondary metric is R², and the process assumes permutation tests, Benjamini-Hochberg correction across the five axes, negative controls, holdout rules, and weekly reruns.
Reserved frame for the weekly public dashboard
This section reserves the public surface for the weekly verification module. Even before the live data feed is connected, the product should lock down the four public axes: weekly verification targets, comparable cases, period-based trend agreement, and confidence-band distribution.
Weekly verification targets
A frame for how many runs entered the weekly verification pipeline.
Frame only. Weekly verification counts will replace this sample trend.
Comparable cases
A frame for complete / comparable cases after QC, deduplication, and missing-value filtering.
Frame only. Complete-case counts will be connected from the weekly dataset build.
Period-based trend agreement
A frame for showing agreement rates across short, medium, and longer windows.
Preview only. The dual bars represent a display frame for period-based agreement.
Confidence-band distribution
A frame for how outputs distribute across confidence bands in a way general users can still read.
Preview frame for confidence-band distribution.
All charts below are UI frames only. They are format previews, not live data.
What this page does not claim
Having a research surface does not mean astrology has already been scientifically validated. The claim is narrower: GenesisCore is being built so the question can be tested under fixed, falsifiable rules and monitored with weekly reruns and public metrics.
After research, move to pricing or runtime.
Once the methodology and the research posture are clear, the remaining next steps are price review and the actual runtime entry.