0006: Verify Rackspace in the application
Sequential server actions save each read-only result without workflow orchestration
- Status: Accepted
- Date: 2026-09-15
- Decision maker: Trevor Gerhardt
Context
Production verification checks a fixed registry in one administrative flow. Vercel Workflow added storage, retries, leases, and status APIs that this read-only check does not need.
Decision
Concourse advances verification through sequential server actions. Each request checks one registry entry and saves its safe result before the next request. The report keeps an immutable registry snapshot and an ordered result prefix. A failure stops the sequence. A reload shows saved progress. A new start creates a new report.
Overlapping read-only requests need no distributed lock. If duplicate requests append to one position, the first committed result remains. RSDB owns MySQL verification meaning. Persistence owns report and audit storage. The Rackspace guide owns the operator flow and runtime limits.
Consequences
- Completed results survive a reload or a later request failure.
- A request can end before its result is saved. The report then remains incomplete.
- Administrators start a new report after a failed or incomplete check.
History
This application flow replaced Vercel Workflow orchestration. Local snapshot generation remains a separate decision in ADR 0003.