Skip to content

System map

Verified end-to-end map of VeriLib platform repositories. Science-team probe tools are linked from Processor / Certificates docs but are not first-class hub sections.

Platform repositories

Component Repository Role
CLI verilib-cli (public) Auth, init, deploy/pull, local create/atomize/specify/verify
Frontend / API verilib-frontend PHP + React UX; MySQL; RabbitMQ publishers; sole cert DB writer
Atomizer verilib-atomizer Upload + atomize workers; S3 + probe Docker; persist atoms
Certificates local_validate Probe images + validate/promote workers (RabbitMQ + S3, no DB)

Architecture diagram

flowchart LR
  cli[verilib-cli]
  frontend[verilib-frontend]
  api[VeriLib API / MySQL]
  mq[RabbitMQ]
  s3[(S3)]
  atomizer[verilib-atomizer]
  cert[local_validate]
  probes[probe-verus / lean / aeneas]

  cli --> api
  frontend --> api
  frontend --> mq
  mq --> atomizer
  mq --> cert
  atomizer --> s3
  atomizer --> probes
  atomizer --> api
  cert --> s3
  cert --> probes
  cert --> mq
  mq --> frontend

Interaction model

Path What happens
CLI → API Deploy / pull structure and metadata; CI often uses --check-only / --no-probe patterns
UI upload / reclone PHP enqueues upload.request (private GitHub tokens on message); atomizer clones → S3 → atomize → MySQL atoms
UI Certify PHP clones cert snapshot, certificates.status=pending, validate.request; worker runs probe, S3 manifest; PHP marks ready; optional Sepolia then separate mainnet promote
Probes Shared extract tools; atomizer and cert workers both invoke language probe images

Science team (out of scope)

probe, probe-verus, probe-lean, probe-aeneas, vericoding, benchmarks, and project repos document themselves under Beneficial-AI-Foundation.