System overview¶
VeriLib is a library of formally verified code with a web app, a contributor CLI, a queue-based atomizer, and a certificate probe/worker stack.
Layers¶
| Layer | Job |
|---|---|
| Experience | Browse, upload, certify, graph/repo browser (frontend) |
| Contributor tooling | Local .verilib/ lifecycle and API sync (CLI) |
| Processing | Clone to S3, probe extract, persist atoms (atomizer) |
| Certification | Reproducible probe images + validate/promote workers (certificates) |
| Data plane | MySQL (owned by frontend for certs; atomizer writes atoms), RabbitMQ, S3 |
Trust boundaries¶
- PHP owns certificate and most product DB writes after queue responses.
- Atomizer / cert workers are headless; cert workers are intentionally DB-free.
- Probes are science-team binaries/images; platform repos orchestrate them.
Where to go next¶
- System map — repo diagram
- Data flows — sequences
- Message contracts — the queue payloads between components
- Database — who writes what
- Repo list