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 CHECKRINHA 2026 // YOLO MODE // PURE ASM API
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.
Every number below is lane-labeled. GitHub Actions evidence, local replay targets, and official hardware are not collapsed into one decorative counter.
IMPLEMENTATION LANE
Repository-owned runtime implementation stays assembly-only. Tests block non-assembly implementation drift.
OPEN PURITY CHECKRUNTIME PURITY LANE
Runtime purity target is zero preview/test-payload lookup artifacts in shipped assembly sources.
INSPECT PURITYCALIBRATION LANE
The vector oracle exercises reference payloads as an external smoke gate without generating runtime lookup artifacts.
OPEN ORACLEGITHUB ACTIONS LANE
CI proves smoke, fd-pass keepalive, purity, and compose validation. Build and Release is a separate lane for amd64 images and semantic tags.
INSPECT CIChallenge facts and reference implementations stay separate from YOLO CI evidence.
main currently publishes a Pages artifact, CI smoke and purity checks, and an amd64 release build for the assembly candidate.
k6 / judge reaches :9999The public boundary is the shared YOLO assembly load balancer.
SCM_RIGHTS over Unix socketsAccepted client descriptors move to api1.sock and api2.sock without a second public TCP listener.
manual HTTP + fraud fieldsAssembly code reads only the bytes the workload needs for scoring and response selection.
heuristic branch-light pathPayload fields feed amount, velocity, MCC, merchant, geo, online, and card-present risk buckets.
prebuilt HTTP bytes outWorkers write prepared response bytes back on the inherited client descriptor.
Default lane. Lead with assembly runtime, runtime purity, CI status, and caveats above the fold.
REVIEW EVIDENCE LANEMake provenance the lead object: source, run, compose, purity, workflow, and Pages deployment.
REVIEW LEDGER LANELead with architecture: load balancer, fd pass, parser, scorer, and bytes written back.
REVIEW RUNTIME LANECandidate metrics are local evidence from GitHub Actions. Official hardware and reference-site proof remain separate lanes.