# panda-rpki-validator M5 architecture

The first public package is intentionally a single Cargo package. Its internal
boundaries are:

1. `model-crypto`: TAL/TA, ASN.1/RPKI objects, signatures and resources.
2. `transport`: HTTP, RRDP, rsync and offline replay inputs.
3. `sync-validation-engine`: snapshot/delta orchestration, CA-tree validation,
   policy/TA constraints and parallel scheduling.
4. `state-cache`: repository bytes, RocksDB state and cache lifecycle.
5. `runtime-lifecycle`: run numbering, retention, TA refresh, failure reset and
   artifact materialization for native and Docker execution.

M4 contains the extracted normal synchronization and validation implementation
across all five boundaries, plus the daemon and shell lifecycle wrapper used
by the Docker image. Metrics, query, UI, RTR, Prometheus/Grafana, old installer
control plane, remote scripts and `verification-only` are not dependencies of
this package. M5 has established the first canonical normal-run and
multi-architecture baseline; the remaining profile/performance gates against
the old runtime must pass before this repository can be considered
release-ready.