Wall-clock runtime
Wall-clock results describe the end-to-end runtime of the present workflow. They can remain long because computational correctness, reproducibility, and traceability still have priority over aggressive optimization.
.mayan-hero {
display: grid;
grid-template-columns: minmax(0, 1.06fr) minmax(280px, 0.94fr);
align-items: stretch;
gap: 26px;
min-height: min(720px, calc(100vh - 132px));
margin: 8px 0 14px;
padding: 64px 40px;
position: relative;
overflow: hidden;
isolation: isolate;
border: 1px solid rgba(255, 255, 255, 0.08);
border-radius: 22px;
background:
linear-gradient(135deg, rgba(47, 111, 159, 0.16), transparent 38%),
linear-gradient(315deg, rgba(31, 138, 112, 0.14), transparent 42%),
linear-gradient(135deg, #020817 0%, #06162d 54%, #020817 100%);
box-shadow:
0 24px 80px rgba(2, 8, 23, 0.38),
inset 0 0 0 1px rgba(255, 255, 255, 0.05);
}
.mayan-hero::before {
position: absolute;
inset: 18px;
z-index: -1;
content: "";
border: 1px solid rgba(255, 255, 255, 0.08);
background-image:
linear-gradient(rgba(255, 255, 255, 0.05) 1px, transparent 1px),
linear-gradient(90deg, rgba(255, 255, 255, 0.05) 1px, transparent 1px);
background-size: 42px 42px;
mask-image: linear-gradient(90deg, black, transparent 84%);
}
.mayan-hero::after {
position: absolute;
inset: 0;
z-index: -1;
content: "";
background: linear-gradient(
115deg,
transparent 0,
transparent 36%,
rgba(255, 255, 255, 0.05) 50%,
transparent 64%,
transparent 100%
);
opacity: 0.6;
pointer-events: none;
}
.mayan-hero-copy {
display: flex;
flex-direction: column;
justify-content: center;
min-width: 0;
}
.mayan-hero .eyebrow {
color: rgba(32, 214, 199, 0.92);
}
.mayan-hero h1 {
max-width: 10ch;
margin-bottom: 20px;
color: var(--surface-strong);
font-size: clamp(3.8rem, 8vw, 7rem);
line-height: 0.93;
letter-spacing: 0;
}
.mayan-hero .lead {
max-width: 780px;
color: rgba(255, 255, 255, 0.76);
font-size: clamp(1.02rem, 1.6vw, 1.2rem);
line-height: 1.62;
}
.mayan-hero .lead + .lead {
margin-top: 12px;
}
.mayan-hero .action-row {
margin-top: 26px;
}
.mayan-hero .button.primary {
border-color: transparent;
background: linear-gradient(135deg, #2f6f9f, #20d6c7);
color: var(--surface-strong);
box-shadow: 0 16px 32px rgba(32, 214, 199, 0.2);
}
.mayan-hero .button.secondary {
border-color: rgba(255, 255, 255, 0.16);
background: rgba(255, 255, 255, 0.06);
color: var(--surface-strong);
}
.mayan-hero .button:hover,
.mayan-hero .button:focus-visible {
transform: translateY(-2px);
}
.mayan-hero-aside {
display: grid;
align-content: center;
gap: 14px;
min-width: 0;
}
.summary-card {
min-width: 0;
padding: 18px 18px 20px;
border: 1px solid rgba(255, 255, 255, 0.12);
border-radius: var(--radius);
background: rgba(255, 255, 255, 0.06);
box-shadow: 0 12px 30px rgba(2, 8, 23, 0.22);
color: var(--surface-strong);
}
.summary-label {
margin: 0;
color: rgba(255, 255, 255, 0.66);
font-size: 0.74rem;
font-weight: 800;
letter-spacing: 0.06em;
text-transform: uppercase;
}
.summary-card strong {
display: block;
margin: 18px 0 10px;
font-size: clamp(1.7rem, 4vw, 3rem);
line-height: 0.98;
}
.summary-text {
margin: 0;
color: rgba(255, 255, 255, 0.72);
line-height: 1.55;
}
.signal-panel {
.status-strip p,
.measurement-card p,
.measurement-interpretation p,
.data-panel p,
.measurement-grid {
display: grid;
grid-template-columns: repeat(2, minmax(0, 1fr));
gap: 12px;
margin-bottom: 16px;
}
.measurement-card {
min-width: 0;
min-height: 188px;
padding: 20px;
border: 1px solid rgba(29, 34, 40, 0.16);
border-radius: var(--radius);
background: rgba(255, 254, 250, 0.9);
box-shadow: 0 10px 30px rgba(29, 34, 40, 0.05);
}
.measurement-card h3 {
margin-bottom: 14px;
font-size: 1.08rem;
}
.measurement-card-accent {
background: #172028;
color: var(--surface-strong);
}
.measurement-card-accent p {
color: rgba(255, 255, 255, 0.72);
}
.measurement-interpretation {
margin-top: 4px;
}
.section-heading {
@media (max-width: 920px) {
.intro-section,
.mayan-hero,
.split-layout,
.intro-section {
.mayan-hero {
min-height: 0;
padding: 54px 30px;
}
.mayan-hero-aside {
grid-template-columns: 1fr;
}
.measurement-grid {
grid-template-columns: 1fr;
}
.metric-grid {
.mayan-hero {
padding: 44px 22px;
border-radius: 14px;
}
.mayan-hero::before {
inset: 14px;
background-size: 34px 34px;
}
.mayan-hero h1 {
font-size: clamp(3.1rem, 16vw, 5.4rem);
}
.mayan-hero .lead {
font-size: 1rem;
}
.status-strip,
.mayan-hero .action-row,
.mayan-hero .button {
width: 100%;
}
.measurement-card,
.summary-card {
min-height: 0;
}
.rule-row {
background-size: 42px 42px;
-webkit-mask-image: linear-gradient(90deg, black, transparent 84%);
mask-image: linear-gradient(90deg, black, transparent 84%);
display: grid;
grid-template-columns: 0.75fr 1fr 1fr 1.1fr;
grid-template-columns: 0.75fr 1fr 1.08fr 1.08fr;
gap: 1px;
.data-panel code {
overflow-wrap: anywhere;
word-break: break-word;
font-family: "SFMono-Regular", Consolas, "Liberation Mono", monospace;
font-size: 0.86rem;
line-height: 1.55;
}
.panel-heading {
Measurement-first research layer
MAYAN ALFA
Independent ARM64 benchmark and validation program focused on reproducible prime-counting observations and controlled archive interpretation.
The current release separates wall-clock runtime of the intentionally unoptimized workflow from clean-binary timing with detailed instrumentation disabled. Optimization and deeper instrumentation will follow in a later phase.
How we measure
Validation first. Performance claims only after complete canonical comparison.
Measurement protocol
Why the same project can report different runtimes
Clean-binary timing
Clean-binary timing is reported as an indicative throughput signal with detailed instrumentation disabled. It is methodologically different from wall-clock runtime and should not be collapsed into the same speed claim.
Instrumentation horizon
More detailed instrumentation will be introduced after the current correctness-focused phase is stabilized and optimization work becomes the active priority.
Interpretive rule
Limit, step, execution mode, and archive tier are always reported together. The numeric result is therefore read as a bounded observation, not as an isolated slogan.
Interpretive rule
Limit, step, execution mode, and archive tier are always reported together. The numeric result is therefore read as a bounded observation, not as an isolated slogan.
Correctness-first stage
The current release keeps computational accuracy and reproducible output ahead of optimization speed.
Binary timing still indicative
Clean-binary timing remains indicative until later instrumentation turns it into a fully auditable performance layer.
Publication boundary
The public presentation layer stops at 10B, while 100B, 200B, and 500B remain controlled archive evidence.
Benchmark board
P0.7 Canonical Binary Benchmark
Measurement families
Interpretation map
Limit
Tier
MAYAN
PRIMESIEVE
10M
public
measured
measured
100M
public
measured
measured
1B
public
measured
measured
10B
public ceiling
measured
measured
100B
controlled
archive evidence
archive evidence
200B
controlled
archive evidence
archive evidence
500B
controlled reference
wall-clock reference
wall-clock reference
Interpretation
Current public wordingWall-clock runtime, clean-binary timing, and controlled archive evidence are separate methodological objects. They must be read in their own context before any speed claim is made.
The site is written to keep the scientific reading explicit: correctness-first workflow, long wall-clock runtime, and indicative binary timing are not merged into a single number.
Archive integrity
Reference package and source boundary
TESTY.zip SHA-256
This bundle contains the current performance evidence used for the measurement analysis.
Source directory
The current source directory is the primary working boundary for measured data, validation outputs, and program sources.
Publication tiers
Public pages stop at 10B. 100B, 200B, and 500B remain controlled archive evidence and are included in the GOLD package of detailed overviews and measurements.
Project memory
Master guides
Základní strategie
Vize, identita a publikační základ
- 01_VIZE_A_IDENTITA_PROJEKTU_EXPANDED.docx
- 02_PUBLIC_PRIVATE_ARCHITEKTURA_EXPANDED.docx
- 03_GITHUB_PUBLIKACE_EXPANDED.docx
- 04_ZENODO_DOI_PUBLIKACE_EXPANDED.docx
ABOUT THE PROJECT
Independent research framework for computational observation.
MAYAN_ALFA is built as an observation-first research environment for benchmark discipline, deterministic validation, reproducible datasets, and long-term archive integrity.
In the current phase, the project prioritizes zero-error computational results up to 10 billion numbers in the public release layer and up to 500 billion numbers in controlled archive evidence. Speed optimization is reserved for later phases.
01
Observation before interpretation
The project records measured computational behavior first. Validation, comparison, and publication follow only after correctness checks and QA, with wall-clock and clean-binary timing interpreted separately.
CORE PILLARS
A disciplined system for measured computational work.
01
Benchmark Validation
Cross-checking computational outputs across independent methods, summary files and QA reports.
02
ARM64 Observation
Focused measurement of runtime behavior, throughput, scaling and platform-specific execution patterns.
03
Dataset Archive
Public releases up to 10B, with extended 100B+ validated archives prepared as premium datasets.
VALIDATED PERFORMANCE
Benchmark datasets validated across independent systems.
PUBLIC
10B
Open validated release
Public benchmark datasets available for independent verification and reproducible computational testing.
PREMIUM
100B
Extended validation archive
Large-scale structured datasets prepared for research environments, benchmark comparison and archive storage.
SCALING
1000B+
Experimental scaling framework
Long-term computational observation model designed for future large-scale validation experiments.
VALIDATION RESULTS
Public benchmark comparison overview.
Public release covers validated benchmark outputs up to 10B. Extended 100B+ validation archives are reserved for premium datasets.
| LIMIT | MAYAN_ALFA | MR ONLY | PRIMESIEVE | π(N) | STATUS |
|---|---|---|---|---|---|
| 10M | 1.684354 s | 3.604905 s | 1.000000 s | 664579 | OK |
| 100M | 0.360000 s | 23.874431 s | 1.000000 s | 5761455 | OK |
| 1B | 1.793206 s | 244.145627 s | 9.000000 s | 50847534 | OK |
| 10B | 18.806417 s | NOT RUN | 94.000000 s | 455052511 | OK |
Measured values represent internal benchmark execution time under specific ARM64 testing conditions and should not be interpreted as universal performance metrics.
Results depend on hardware configuration, compiler optimization, execution methodology and dataset structure.
All benchmark outputs were cross-validated against independent computational methods and archived within the MAYAN_ALFA validation framework.
RELEASE STRUCTURE
Public research layer and extended archive system.
PUBLIC
Open validated releases
Public repository releases contain validated benchmark datasets, QA summaries, comparison reports and reproducible execution outputs up to 10B.
Designed for independent verification, long-term archival consistency and transparent computational observation.
PREMIUM
Extended validation archives
Large-scale 100B+ structured datasets, extended validation layers, archive-grade benchmark outputs and premium computational observation packages prepared for research and institutional environments.
OBSERVATION PRINCIPLES
A computational framework built on measured observation and reproducible validation.
01
Observation First
The framework records measured computational behavior before interpretation.
All conclusions are derived from validated execution outputs and structured comparison layers.
02
Validation Before Publication
Public releases are published only after cross-validation against independent computational systems, QA procedures and archive verification workflows.
03
Long-Term Archive Discipline
The project maintains reproducible datasets, benchmark summaries and structured archival layers designed for long-term computational research continuity.
DATASET FLOW
Structured validation pipeline for public and premium computational archives.
STEP 01
Computation
Execution outputs are generated under controlled ARM64 benchmark conditions with deterministic validation workflows and structured logging layers.
→
STEP 02
Cross Validation
Outputs are compared against independent computational systems including MR and primesieve validation frameworks.
→
STEP 03
Public Release
Validated datasets up to 10B are published as transparent public research layers with QA summaries and archive manifests.
→
STEP 04
Premium Archive
Extended 100B+ validation archives are maintained separately as premium computational research datasets and long-term archival packages.
VALIDATION SOURCES
Public repositories and archival validation layers.
MAYAN_ALFA maintains transparent public validation layers together with structured long-term archive systems prepared for reproducible computational observation and benchmark verification.
SOURCE 01
GitHub Repository
Public benchmark releases, validation summaries, source packages and computational observation layers published through the official GitHub research repository.
VIEW GITHUB
SOURCE 02
Zenodo Archive
Structured DOI-based archival releases synchronized with long-term preservation workflows for validated benchmark and research datasets.
VIEW ZENODO
SOURCE 03
Validation QA
Cross-validation reports, dataset integrity summaries, independent comparison outputs and benchmark QA documentation.
VIEW QA
RESEARCH TIMELINE
Long-term development and validation evolution of the MAYAN_ALFA framework.
PHASE 01
Core computational observation layer
Initial deterministic computational observation framework focused on structured execution behavior, validation logging and benchmark reproducibility under ARM64 environments.
PHASE 02
Independent cross-validation architecture
Integration of MR comparison layers, primesieve verification workflows, QA summaries and archive-oriented computational validation procedures.
PHASE 03
Public benchmark release framework
Structured public releases up to 10B including reproducible benchmark datasets, validation summaries and transparent publication methodology.
PHASE 04
Extended archival scaling system
Development of long-term premium validation archives, large-scale computational observation layers and institutional-grade archival preparation workflows.
VALIDATION MATRIX
Independent computational verification layers built for transparent benchmark discipline.
The MAYAN_ALFA framework combines structured execution, independent cross-validation systems and archival reproducibility layers to ensure measurable computational transparency.
LAYER 01
Execution Validation
Deterministic execution environments designed for stable runtime observation and reproducible computational measurements.
ARM64 execution monitoring
Controlled benchmark pipelines
Structured runtime summaries
LAYER 02
Cross-System Comparison
Outputs are independently compared across verification systems including MR frameworks and primesieve validation references.
MR validation workflows
primesieve comparison layers
QA mismatch control
LAYER 03
Public Dataset Publishing
Validated datasets are structured into reproducible public releases with transparent archival methodology and benchmark summaries.
10B public validation releases
CSV and QA archive structure
Long-term reproducibility
LAYER 04
Premium Research Archives
Extended computational observation archives prepared for large-scale validation environments and institutional-grade archival workflows.
100B+ structured archives
Extended benchmark storage
Research-grade dataset preparation
RESEARCH ACCESS
Structured computational observation for transparent benchmark research.
MAYAN_ALFA combines deterministic computational observation, independent validation systems and long-term archival discipline into a transparent benchmark research framework prepared for reproducible public and premium dataset environments.
ARCHIVE ACCESS
Structured computational validation infrastructure.
Explore validated benchmark ecosystems, protected archive layers and long-term computational preservation workflows within the MAYAN_ALFA research platform.
