RINHA 2026 // YOLO MODE // PURE ASM API

YOLO SIGNAL
UNDER LOAD.

A public proof dossier for the assembly fraud scorer: lane-labeled evidence first, runtime path second, CI caveats always visible.

Proof stays separated by lane: assembly runtime, runtime purity, GitHub Actions, Pages deployment, and reference-site lineage.

TCP arrives at the shared ASM load balancer, client descriptors move over Unix sockets, and `_start` writes response bytes back.

[asm] pure x86-64[purity] no lookup[fdpass] stream sockets
PROOF LEDGER

ASM RUNTIME, CORPUS REPLAY, CI DEPLOYMENT.

Every number below is lane-labeled. GitHub Actions evidence, local replay targets, and official hardware are not collapsed into one decorative counter.

[ASM-RUNTIME]

IMPLEMENTATION LANE

Pure assembly API

ENTRY
_start
BUILD
as + ld
CHECK
purity pass

Repository-owned runtime implementation stays assembly-only. Tests block non-assembly implementation drift.

OPEN PURITY CHECK
[PURITY-CLEAN]

RUNTIME PURITY LANE

No lookup tables

PAYLOAD
field-derived
LOOKUP
blocked
ASM
only

Runtime purity target is zero preview/test-payload lookup artifacts in shipped assembly sources.

INSPECT PURITY
[ORACLE-SMOKE]

CALIBRATION LANE

Vector oracle is optional

TARGET
make oracle-smoke
SOURCE
official resources
RULE
black-box only

The vector oracle exercises reference payloads as an external smoke gate without generating runtime lookup artifacts.

OPEN ORACLE
[CI-CLEAN]

GITHUB ACTIONS LANE

Main CI and release lanes

SMOKE
pass
PURITY
pass
RELEASE
separate

CI proves smoke, fd-pass keepalive, purity, and compose validation. Build and Release is a separate lane for amd64 images and semantic tags.

INSPECT CI

OFFICIAL / REFERENCE SOURCE

Challenge facts and reference implementations stay separate from YOLO CI evidence.

LOCAL YOLO EVIDENCE

main currently publishes a Pages artifact, CI smoke and purity checks, and an amd64 release build for the assembly candidate.

RUNTIME TRACE

THE FAST PATH IS SHORT. THE CAVEAT IS VISIBLE.

01

Ingress

k6 / judge reaches :9999

The public boundary is the shared YOLO assembly load balancer.

02

FD pass

SCM_RIGHTS over Unix sockets

Accepted client descriptors move to api1.sock and api2.sock without a second public TCP listener.

03

Parse

manual HTTP + fraud fields

Assembly code reads only the bytes the workload needs for scoring and response selection.

04

Score

heuristic branch-light path

Payload fields feed amount, velocity, MCC, merchant, geo, online, and card-present risk buckets.

05

Respond

prebuilt HTTP bytes out

Workers write prepared response bytes back on the inherited client descriptor.

A/B TEST SURFACE

THREE LANES TO TEST YOLO WITHOUT LOSING THE REFERENCE.

A

Evidence Terminal

Default lane. Lead with assembly runtime, runtime purity, CI status, and caveats above the fold.

REVIEW EVIDENCE LANE
B

Benchmark Ledger

Make provenance the lead object: source, run, compose, purity, workflow, and Pages deployment.

REVIEW LEDGER LANE
C

Runtime Trace

Lead with architecture: load balancer, fd pass, parser, scorer, and bytes written back.

REVIEW RUNTIME LANE

CI BENCHMARK STREAM

Candidate metrics are local evidence from GitHub Actions. Official hardware and reference-site proof remain separate lanes.

MAINCI LANE
0SMOKE FAILURES
0LOOKUP TABLES
LIVEPAGES DEPLOY