Prime counting
Gold1
Exact interval prime counting with a dedicated Count Primes workflow and evidence-first benchmark tooling.
Explore Gold1 →FOUR ENGINES · ONE DISCIPLINED RESEARCH SURFACE
Numerical engines.
Different colours.
Shared rigor.
Chromatic Engines is the public home of Gold1, Red2, Blue3 and Violet4 — four distinct numerical research projects presented with explicit scope, evidence and commercial boundaries.
The public site is independent of the compute workstation. Phase 10 adds small, queued public demonstrations that degrade cleanly to offline status when MIK-LAB-01 is unavailable.
CEmeasure · challenge · retain
Gold1Gold · prime counting
Red2Red · prime sieving
Blue3Blue · prime search
Violet4Violet · gravity research
THE ENGINES
Four projects.
One chromatic rack.
Engine order and colour identity are fixed across the commercial platform.
Prime sieving
Red2
A high-performance prime-sieving research engine developed around explicit validation and reproducible measurement.
Explore Red2 →Prime search
Blue3
A structured large-prime candidate/search project whose public surface separates observed results from conjecture.
Explore Blue3 →Gravity research
Violet4
A research-preview numerical framework for gravity experiments, with model assumptions and validation kept explicit.
Explore Violet4 →OFFLINE-FIRST SITE
Public by design.
Private by boundary.
The public website does not read local engine files or depend on workstation availability.
Live demo status · Phase 10
The website stays up when the workstation is down.
MIK-LAB-01 is not required to render this site. When the public demo API is reachable, this card shows bounded node/queue status; if it is offline, the rest of Chromatic Engines remains available.
COMPUTE NODE
MIK-LAB-01
Offline / unavailable
UnavailablePublic demos
—Queue
0 inboundHome ports
RESEARCH DISCIPLINE
Evidence before theatre.
Interesting results are labelled by what was actually measured, not by how exciting they sound.
Scope stays explicit
Each engine page states its role without presenting research hypotheses as established fact.
Benchmarks need context
Machine, software version, interval/workload, warm-up and validation conditions belong with any performance claim.
Private source remains private
The public frontend contains presentation material only; numerical source stays under the private engine boundary.