Operational transparency

Service status should be factual, not decorative.

This page states the current operational boundary for the packaged TradeGospel build. Stage 17R connects public status, incident history, notification evidence, account preference controls, escalation records and production dependency evidence while admin-only response telemetry remains protected.

Live public status Checking service status

TradeGospel is reading the public-safe status endpoint. Private account data, storage keys and broker credentials are never returned here.

Public incident history

Operational updates without private evidence.

No private account evidence appears in this feed. It returns public incident titles, component labels, summaries and visible updates only.

JSON feed

Loading incident historyChecking /api/v1/system/incidents
The browser is reading the public incident workflow endpoint.

Running in validated ComposeFrontend, backend, worker, Postgres and Redis

The local development stack is validated by the Stage Gate audit before code is pushed to the development branch.

Operations readiness APIPublic status is sanitized; admin telemetry is protected

The public endpoints expose component state and public incident history only. Detailed job, DSR and security response operations live behind administrator authentication.

Notification routing evidenceDelivery decisions are logged behind admin authentication

No private delivery contacts appear on this public page. Stage 17R preserves notification criteria, delivery attempts, receipts and escalation evidence for operations review.

Notification preference controlsAccount-level choices gate delivery

Authenticated traders can set notification preferences while this public page never exposes preference records, user emails or delivery contacts.

Production dependency evidenceLaunch blockers are tracked without private notes

Admin readiness can record uptime, paging, legal, billing and security dependency evidence while this public page never exposes internal notes or raw evidence references.

Production dependencyExternal paging provider still required

TradeGospel now records escalation policy evidence and preference-aware delivery decisions, but broad production still requires a monitored paging vendor and staffed on-call process.

Production dependencyMalware scanning and quarantine pending

Unrestricted public uploads should wait for document sandboxing, malware scanning, quarantine controls and processor evidence review.

Components that must be monitored

Public website and static assets.
Secure API and authentication.
Evidence upload and object storage.
Analysis worker and report generation.
Read-only broker connector ingestion.
Email delivery, password recovery and notifications.

Incident communication

Material incidents identify start time, affected component, user impact, current containment status and final resolution when public disclosure is appropriate. Security incidents still require a separate controlled notification process.

Maintenance windows

Maintenance can affect uploads, report generation, source registry updates or connector snapshots. Paid production users should receive planned maintenance windows through the account email or in-product notice once those channels are operational.

Launch readiness boundary

The public feed is workflow-backed, not an uptime vendor replacement.

The current page is backed by public-safe status, incident, notification, preference, escalation and production-dependency workflows. Production should still add monitored uptime, privacy request ownership SLAs, backup erasure evidence review, legal notification review, billing-provider evidence and an external paging provider.