The South Africa Operating Window

Johannesburg is our South Africa operating office. It is not headquarters. It exists because a Dubai night pager cannot honestly cover a Johannesburg banking morning, and because za-jnb pinning needs staff who can speak to the record in the same working day as the customer.

What the office holds

• Follow-the-sun on-call overlap with Dubai (and later with Hong Kong on Asia incidents that have a group parent in Africa)
• Customer operations for Southern African deployments
• The human side of dual control during SAST hours
• No separate fork of the product

IAM is global. An engineer in Johannesburg sees what their role sees, including region-scoped payloads. They do not get a "local admin" that bypasses redaction.

POPIA on the wire

Production legal and ops projects tagged for South Africa default to personal-data controls: redaction on, sampling off, retention class explicit, export of raw prompts dual-controlled. We do not treat POPIA as a checkbox on a website footer. We treat it as invocation policy.

When a group has a Dubai parent and a Johannesburg desk, residency is still per project. Sharing a cache across ae-dubai and za-jnb requires an exception with dual control and a written transfer story. The default is no.

Time zones are a control problem

Most of our remaining incidents are not exotic model failures. They are humans out of window. A dual-control request that expires at 02:00 SAST because the second key is in Dubai is an outage of governance, not of GPUs.

We staff the Johannesburg window so that legal gates on za-jnb projects can complete in local hours. If we cannot staff a second key, we do not sell that project a same-day SLA. We have walked away from a timeline rather than fake a roster.

The sentence I want on the record

Eridian is run from Dubai, with operating offices in Hong Kong and South Africa. Johannesburg is how we keep the African morning honest. It is not a second company, and it is not a place we move a prompt to because someone is awake.