Orchestration decision
Why Price Gouge keeps the interactive pricing product in Next.js, scheduled source checks, and Supabase, with AgentHero reserved for future durable workflows.
Audience
Developers and operators
Metric
No DAGApp required yet
Sources
3 official links
Current decision
Price Gouge does not need a separate AgentHero or GrokRxiv DAGApp for the current interactive pricing path. The public product is request/response: users describe a workload, the API builds a provider-price comparison, and plan drafts, alerts, and source observations stay in the product database.
Keeping this path in the Next.js app reduces runtime surface area and keeps pricing logic, UI state, provider prices, and workspace records in one deployable product.
- Next.js App Router owns the public pages and API routes.
- Supabase is the primary database for pricing data, plan drafts, alerts, and team workspace records.
- A scheduled Vercel job checks official source pages for dated pricing evidence.
- Published prices require numeric evidence from official provider pages.
Why orchestration is not required yet
The daily source check is bounded work. It reads official pages, validates numeric evidence, and writes dated observations. That fits a Vercel Function and Supabase persistence model.
A DAG runtime would make sense only when the job becomes long-running, human-reviewed, or multi-agent enough that retries, checkpoints, approvals, and resumable state are worth the added operational surface.
When AgentHero becomes useful
AgentHero should be introduced when the pricing system needs durable background workflows that are larger than one scheduled source check.
- Source-diff review with human approval before publishing major pricing-page structure changes.
- Marketplace normalization for region, reliability, capacity, reservations, storage, egress, and provisioned-throughput matrices.
- Long-running benchmark and evaluation jobs for local inference, fine-tuning, provider quality, and fallback-routing policies.
- Multi-step research jobs where outputs need checkpointed review before they affect public recommendations.
Boundary if a DAGApp is added
AgentHero should own workflow mechanics: queueing, retries, checkpoints, approvals, and execution state. Price Gouge should own pricing meaning: provider taxonomy, price validation, workload assumptions, strategy scoring, and user-facing recommendations.
That boundary keeps the product understandable: the orchestrator moves work through durable steps, while Price Gouge remains the source of truth for what a price means and when it is safe to show.
Operational contract
The current production contract is intentionally simple and auditable.
User request -> provider-price comparison -> pricing plan draft
Scheduled source check -> official pages -> dated price records
Future durable workflow -> long-running review -> approved recommendations