Skip to main content

​
Why this exists

Ponzu now runs with two explicit operating brains so execution stays fast while customer-facing docs stay clear.

​
Brain 1: Agentic Ops Brain (ponzu-pi)

Host: ponzu-pi
Role: orchestration + reliability + automation Primary responsibilities:
  • keep gateway/session routing healthy
  • monitor node health and recover dropped lanes
  • schedule light cron/watchdog jobs
  • dispatch heavier work to clark-workhorse and sidecar loads to ponzu-worker
  • keep infra lean (avoid heavy compute on ponzu-pi)

​
Brain 2: Product Docs Brain (Conceptify Docs Hub)

Host/Repo: ClarkPhan/docs (Mintlify)
Role: consumer-facing clarity and onboarding quality Primary responsibilities:
  • explain workflows in product language
  • keep architecture + operations pages understandable for customers
  • document setup paths, guardrails, and troubleshooting
  • convert internal ops decisions into external-facing docs quickly

​
Operating contract between the two

  1. Ops decision happens (infra, routing, safeguards, workflows).
  2. Agentic brain ships + verifies in real runtime.
  3. Docs brain translates into customer-readable Mintlify docs.
  4. Both stay synced through routine updates and explicit ownership boundaries.

​
Consumer value

This split makes Ponzu more useful to external users because:
  • reliability work happens continuously without bloating product docs
  • product docs improve without waiting on deep infra context
  • setup guidance stays practical and current as the system evolves

​
Practical workflow template

  • Use ponzu-pi for orchestration and verification.
  • Use clark-workhorse for heavy builds/containers.
  • Use ponzu-worker for sidecar/light compute.
  • After meaningful workflow changes, update this docs hub in the same session.