Operational Continuity Framework

Institutional partners reasonably ask early-stage data and intelligence platforms what happens to the platform if the principal author is incapacitated, the technical infrastructure becomes inaccessible, or business circumstances change abruptly. This page publishes Afrimintel's operational continuity framework so the answer is structural, not improvised. The framework is published proactively rather than produced reactively.

Why this is published. Most early-stage institutional research platforms do not publish business continuity plans. Either they don't have them, or they have them but treat them as confidential, or they avoid drawing attention to key-person risk. The platform's position is the opposite: institutional procurement teams will reasonably ask, and the answer is better given as a published framework than as an improvised response under engagement pressure. The framework is also a discipline document for the platform itself — committing publicly to specific continuity arrangements increases the probability they remain in place.

The risk being addressed

Afrimintel currently operates with single-editor capacity. The editorial responsibility role, the methodology authorship role, the data quality verification role, the audit log custodianship role, and the technical pipeline maintenance role are all held by the same person (Nikesh Patel). The advisory review role is being formed (see about). This is the operational reality the platform discloses publicly and does not paper over.

The principal risk this concentration creates is key-person continuity risk: if the principal author is incapacitated for any reason, can the platform continue to serve customers, maintain data quality, deploy fixes, respond to corrections, and honour engagements? The remainder of this page answers that question across three time horizons (30 days, 90 days, permanent) and across the principal operational dimensions (codebase, data, customer relationships, deploy mechanism, editorial continuity).

Three continuity scenarios

Scenario A — Principal author unavailable for up to 30 days

Examples: medical leave, family emergency, travel without connectivity, scheduled sabbatical.

Operational response. The platform continues to serve all existing surfaces (dossiers, methodology, audit log, case studies, pricing, intake, engagement protocol). New deploys are paused. Correction Velocity SLA on material errors (7 business days) is suspended for the duration of the absence; non-material correction SLA (30 business days) absorbs the absence without breach. Customer-facing communications are handled by an out-of-office auto-response naming an alternative contact (currently being formalised; an interim arrangement is in place with a designated trusted associate as message-routing and continuity-contact).

What customers experience. Static-site infrastructure (Netlify-hosted) continues to serve all pages without intervention. Existing data layer continues to be accessible to all subscribers. New material corrections are queued and addressed on return. Engagement Protocol pilot requests received during the absence are acknowledged with a published timeline for response.

Communication. Out-of-office auto-response on nikesh@afrimintel.com naming the expected return window and the continuity-contact for urgent matters. Audit log entry posted on return summarising the absence period and any corrections deferred during it.

Scenario B — Principal author unavailable for 30 to 90 days

Examples: extended medical issue, prolonged family situation, regulatory matter requiring extended attention.

Operational response. The platform continues to serve all existing surfaces. Deploy mechanism is transferred to the designated continuity-contact through a documented handover (Netlify deploy-key access; GitHub repository write access; domain registrar account access — all currently held in encrypted offline backup, with retrieval mechanism documented to the continuity-contact). New deploys are made only for critical security or data integrity issues; substantive content publishing is paused. Editorial Responsibility role temporarily transfers to a named senior reviewer (to be formalised through the advisor recruitment in flight; current state of advisor formation published at about).

What customers experience. Substantive content updates pause for the duration. Material corrections are addressed by the continuity-contact escalating to the designated senior reviewer. Existing engagement protocol pilots in flight are paused or transferred by mutual agreement; no new pilot intake during this period. Subscribers receive a published notice on the platform indicating the operational pause and the expected resumption framework.

Communication. A published continuity notice on the platform's homepage and on this page, dated and signed by the continuity-contact. Audit log entries continue to be posted by the continuity-contact for any operational changes. Customers may request pro-rata refund per the published refund policy if the operational pause exceeds the threshold defined in their subscription terms.

Scenario C — Permanent change in operating circumstances

Examples: permanent incapacitation, decision to wind down operations, transfer of platform ownership through commercial transaction, regulatory or jurisdictional change requiring fundamental restructuring.

Operational response. The platform's wind-down or transfer is governed by a documented succession protocol covering: (a) customer notification (minimum 90 days advance notice for paying subscribers, refund of any unused subscription period at the customer's election); (b) data layer disposition (intelligence-grade dossiers and methodology documents preserved with continued public access for at least 12 months post-transition; raw working data destroyed per Privacy Policy retention schedule); (c) audit log preservation (the public audit log is the platform's institutional record and continues to be accessible for at least 24 months post-transition); (d) engagement protocol pilots in flight (each pilot is honoured to its 30-day delivery date or the institution's pro-rata withdrawal per mutual agreement); (e) editorial responsibility transfer (where the platform continues under new ownership) or formal closure announcement (where it does not).

What customers experience. Minimum 90-day notice. Pro-rata refund availability. Continued access to historical material for at least 12 months. Engagement protocol pilots honoured to their delivery dates. Public audit log entries documenting the transition.

Communication. Formal notice on the platform's homepage and via direct email to all paying subscribers. Audit log entry documenting the transition trigger, the timeline, and the disposition framework. Customer-facing FAQ on transition mechanics published within five business days of the transition trigger.

Operational dimensions covered

Dimension	Continuity arrangement
Codebase access	Primary repository (private GitHub) accessible to the principal author and the designated continuity-contact through documented backup credential retrieval. All deploy-time secrets (API keys, Netlify deploy tokens, domain registrar credentials, Stripe Payment Link configuration access, Plausible analytics access) held in encrypted offline backup with retrieval procedure documented to the continuity-contact.
Data layer integrity	Static data layer (the 18 intelligence-grade dossiers plus the operator-attestation, research-grade, and spatial-reference entries; the country risk composites; the case study dossiers; the methodology pages; the audit log) is part of the codebase and inherits the codebase continuity arrangement. No separate database that could become orphaned.
Hosting infrastructure	Netlify-hosted static site at afrimintel.com (custom domain) on a separate-from-principal payment instrument with sufficient pre-funding to cover at least 12 months of hosting costs in the event of access disruption. Domain registrar (separate from hosting) is on multi-year auto-renew with prepaid credit.
Customer relationships	All customer communications routed through nikesh@afrimintel.com which has documented credential-recovery mechanisms accessible to the continuity-contact. Customer subscription status held in Stripe (separate platform with documented account-recovery procedures). Customer commitments (engagement protocol pilots, paid subscriptions) are documented in a separate operational record accessible to the continuity-contact through the credential-recovery procedure.
Editorial continuity	Methodology and Quality Standard are published documents — the editorial framework is institutionalised in writing rather than carried as tacit knowledge. The continuity-contact and any future Editorial Responsibility holder can produce work consistent with the published framework by reading the published documents. The discipline architecture (37-check pre-deploy pipeline; three-state Quality Standard; field-level provenance schema; Counterparty Extension; Audit Log discipline) is automated to the maximum extent feasible, reducing dependency on tacit editorial judgment.
Deploy mechanism	Pre-deploy pipeline (37 automated checks) and Netlify deploy hook are the mechanism. Both are accessible through the documented credential retrieval. The pre-deploy pipeline blocks deploys that fail any of the 37 checks regardless of who is operating it, providing automated quality enforcement that does not depend on the editor's presence.
Counterparty Extension discipline	The discipline is published; it does not depend on the editor's tacit application. Any future operator can apply it by reading the published policy. Pre-deploy pipeline includes automated checks for permanent exclusions and forward-looking partnership claim patterns.

What this framework does NOT promise

This framework is operational continuity, not operational immortality. The platform's discipline architecture cannot fully substitute for the founding editor's judgment in unforeseen institutional circumstances. The framework explicitly does not promise:

Continued substantive content publishing during the principal author's absence. Substantive new content (case studies, methodology updates, deeper dossier work) requires editorial judgment that is not transferable in the short term. New content is paused during 30-day and 90-day continuity scenarios, and resumes only when editorial responsibility resumes.
Identical service quality during continuity scenarios. The continuity-contact and any interim editorial reviewer cannot replicate the principal author's full institutional context. Service continues; service quality may differ during the continuity period.
Indefinite operation under crisis circumstances. If the principal author becomes permanently unavailable, the platform's options are succession (with new editorial responsibility holder), commercial transfer, or wind-down. The framework documents the disposition mechanics for each but does not pre-commit to which path will be taken.
Institutional-redundancy at the level a multi-editor research desk provides. A Wood Mackenzie or S&P Capital IQ Mines team has dozens of editors and analysts; an Afrimintel-style platform does not. This framework reduces the operational impact of single-editor concentration; it does not eliminate it.

Where this framework is in the platform's roadmap

This framework is published as v1.0 on 9 May 2026. Three structural items remain in formation and are committed to the platform's Build Roadmap:

Named continuity-contact published with explicit consent. Currently the continuity-contact is a designated trusted associate without public attribution; full publication of the name with consent is sequenced with the broader advisor formation (Q2/Q3 2026 per the about page).
Named senior editorial reviewer for 30-90 day scenarios. Sequenced with advisor recruitment; a senior figure with named consent at this role would convert Scenario B from "framework in formation" to "framework operational with named senior reviewer."
Independent operational audit of the continuity arrangement. Annual review by an external party (security-auditor or institutional compliance reviewer) is committed to the roadmap once the platform reaches the institutional-pilot scale where the cost is justified by demonstrated demand.

The framework is published in its current state because the alternative — withholding publication until all three items are completed — would mean institutional partners encountering the platform have no published answer to their reasonable questions about continuity. Published-with-named-gaps is the correct discipline; published-only-when-perfect would defer the discipline indefinitely.

Why an early-stage platform publishes this

Three reasons:

Institutional procurement reads it on Day 1. Any DFI procurement officer evaluating a third-party data or research provider asks about business continuity within the first hour of due diligence. Most early-stage providers answer reactively, often imperfectly. Pre-publishing the framework is a respect-for-the-question signal.
Public commitment increases the probability the framework remains in place. Operational continuity arrangements that are unpublished are easier to deprioritise. Publication makes them part of the platform's institutional record.
The discipline of producing the framework forces clarity. Walking through 30-day, 90-day, and permanent scenarios across seven operational dimensions surfaces gaps that an unwritten framework would not. The platform is more operationally resilient post-publication than pre-publication, by virtue of having had to write down what would happen.

Framework v1.0 published 9 May 2026 · Editorial responsibility: Nikesh Patel, Honorary Consul of Rwanda in Mauritius · Published at platform version: Afrimintel v1.0.45 · Pipeline status at publication: 23/23 PASS · Annual review committed: framework is reviewed and updated at minimum once per calendar year, with material changes recorded in the public Audit Log. Material errors or omissions surfaced by readers are corrected per the Quality Standard's 7-business-day correction-velocity SLA.

← About · Quality Standard · Audit Log →