Agent Orchestrator
A dispatcher that runs three specialist validators in parallel against the same PDF.
A calibration certificate is validated by three independent rule systems — requirements, CMC scope, tolerances — that used to live in three different people’s heads. I built the orchestrator as a Cloud Run microservice: it ingests the job, fans out to three validator services, consolidates their verdicts, and hands the result to an operator for review.
TRIGGERS ORCHESTRATOR VALIDATORS────────── ────────────── ──────────────┌────────────┐ ┌──────────────┐ ┌────────────────┐│ operator │ │ │ │ requirements ││ console │─┐ │ launcher │ ┌──▶│ validator │└────────────┘ │ │ │ │ └────────┬───────┘│ └──────┬───────┘ │ │┌────────────┐ │ │ │ ┌────────▼───────┐│ scheduler │─┼────▶ api ─┤ ├──▶│ cmc │└────────────┘ │ │ │ │ validator ││ ┌──────▼───────┐ │ └────────┬───────┘┌────────────┐ │ │ │ │ ││ client │ │ │ aggregator │ │ ┌────────▼───────┐│ portal api│─┘ │ (fan-out) │──┘ │ tolerance │└────────────┘ │ │ │ validator │└──────┬───────┘ └────────┬───────┘│ ││ ◀─── verdicts ───────┘▼┌──────────────┐│ synthesis │ overall status +│ (consolidate)│ optional llm summary└──────┬───────┘│▼┌──────────────┐ ┌──────────────┐│ operator │──────▶│ postgres ││ review │ │ + storage │└──────────────┘ └──────────────┘
- shape
- Triggers (portal · upload · scheduler) → single-flight launcher → fan-out aggregator → three parallel validators → synthesis → review.
- design
- Validators are stateless Cloud Run services behind a shared contract: PDF + JSON + correlation id in, verdict out. Any one can be replaced in isolation.
- evidence
- Every task, verdict, and review decision is written to Postgres. Realtime channel streams progress back to the console.
- impact
- Manual certificate review dropped from days to minutes. Three reviewers can now supervise instead of execute.






