AXP-122 / PUBLICATION 1
Seven constraints that change an ESG data system in West Africa
Requests come from buyers and financing institutions. For the company expected to respond, the task is not to describe the field but to build data that remains traceable through it.
We receive a request for emissions data, policies and supporting records. It does not come from a newly created local rule. It comes from a buyer monitoring its value chain, a bank framing its risk or a financing institution asking for environmental and social monitoring. The request sits outside the system we use every day, but the answer must be assembled from our real operations.
This is where many discussions begin from the wrong place. They describe West Africa from the outside, as a collection of missing data to be brought closer to a model already completed elsewhere. The company facing the request sees a different problem. We have invoices, records, payments, generators, suppliers and several working languages. The material exists. It was simply not produced to enter an ESG data system built on different assumptions without friction.
The seven constraints below are neither a list of delays nor a set of exceptions. They describe the operating conditions the system must obey. Each one forces a decision about source, quality, time, synchronisation or lineage. Ignoring them does not simplify the system. It merely moves uncertainty to the moment when someone asks how a figure was obtained.
The chosen point of view is that of the company expected to organise the response. No emission-factor values are supplied. No local legal duty is implied where none exists. This text does not assemble a financing application for a third party and does not promise access to a financing institution. Its purpose is to make the problem precise enough for a builder to decide what must be modelled.
01 TO 07 / FIELD AND SYSTEM
The field, seen from the company expected to respond
Each entry begins with a controlled English rendering of the constraint and consequence fixed in branch EJ. The company voice then moves from outside observation to the operational “we”. That shift reveals what the data must preserve and what must remain stated as uncertain.
01 / 07
The choice becomes data in its own right
Controlled rendering of branch EJ
No national emission-factor database
A method for selecting, justifying and versioning foreign factors, with a traceable record of that choice
From the company
We must respond without a single national database on which every calculation can rely. If we select a foreign factor, we must be able to explain its source, why it was chosen, which version was used and what a later update would change.
The selected factor cannot remain an isolated spreadsheet cell. Its source, geographic scope, reference technology, unit, year and version belong to the same object. The rationale must survive the departure of the person who made the choice. Otherwise a later recalculation cannot separate a change in activity from a change in reference.
The method therefore comes before the value. It sets the order in which sources are searched, the acceptable gaps, the person who decides and the trace left by the decision. The system must also preserve the previous version when a reference changes. Continuity of reasoning matters as much as the output of the calculation.
- What the system must preserve
- Source, version, scope, unit, decision date, rationale and recalculation rule.
- What it must not claim
- Do not present a foreign factor as a natural representation of the local context.
02 / 07
Absence has several causes and they are not interchangeable
Controlled rendering of branch EJ
Scarce, incomplete and sometimes paper-based data
A model that treats absence as a value and an evidence chain that can accept a photograph of a record
From the company
Our records are spread across files, notebooks, receipts, messages and paper logs. A blank field does not always mean zero. It may mean that the data was not produced, was not received or exists in a form that has not yet been entered.
A useful model separates a measured zero, an unknown value, an expected record, an unreadable record and an object outside the boundary. These states lead to different actions. Reducing them to an empty cell creates apparent cleanliness at the cost of traceability. A photograph of a record can be accepted when its origin, date, entry author and link to the record are preserved.
The company does not need a system that makes paper disappear. It needs one that links a digital entry to the material that triggered it, then states what that material can and cannot establish. Quality comes from qualifying absence rather than hiding it.
- What the system must preserve
- Distinct absence states, provenance for each entry, attached record and correction log.
- What it must not claim
- Never turn missing data into zero or treat an available image as verified data by default.
03 / 07
Operational continuity changes the categories to be tracked
Controlled rendering of branch EJ
Intermittent electricity and generators
Emission categories that European models handle poorly and that carry significant local weight
From the company
Our electricity supply alternates between the grid, outages and generation on site. If the system sees only the grid invoice, it describes operations different from those we actually ran.
A generator is not a footnote. It has a fuel, a quantity, a period of use, a piece of equipment, sometimes a meter and often separate purchase records. These elements must be linked to the relevant period and site. A switch from the grid to a generator must not create a gap in the time series.
The system must show the combination of sources without assuming continuous grid availability. That structure also makes corrections possible: an invoice received later can complete the period without erasing the trace of the earlier estimate.
- What the system must preserve
- Energy source, site, equipment, fuel, period of use, record and measurement state.
- What it must not claim
- Do not infer complete consumption from a grid invoice when generation on site took over.
04 / 07
Offline operation changes the model, not only the screen
Controlled rendering of branch EJ
Costly and intermittent connectivity
An architecture that works offline and synchronises later, changing the data model rather than only the interface
From the company
We cannot organise collection as if every site had a stable connection. Entry must continue during an outage and later reach the system without creating a duplicate or erasing a correction made elsewhere.
An interface that merely displays a page without a connection is not enough. Every record needs an identifier created locally, a synchronisation state, an observation time separate from the transmission time and a conflict rule. Attachments must be able to wait without being lost or sent repeatedly when the network returns.
This architecture also requires economical transfer. Structured fields move before large files, retries are partial and the user can see what remains pending. Performance is not a comfort added later. It determines whether collection is possible at all.
- What the system must preserve
- Local identifier, queue, separate timestamps, partial retry, duplicate detection and conflict rule.
- What it must not claim
- Do not display “sent” until the server has acknowledged the record and its attachments.
05 / 07
Collect without inventing a record that does not exist
Controlled rendering of branch EJ
The informal sector in the supply chain
A collection method for suppliers without formal accounting records, with a candid account of what cannot be evidenced
From the company
Some of our suppliers operate without formal accounting records. We may obtain quantities, dates, receipts or an oral confirmation, but not always the document expected by a model built for a fully documented chain.
The system must separate what was declared, observed, photographed, matched to a payment or supported by a second source. These categories do not give information the same weight. They still preserve a useful fact without assigning it a quality it does not have.
An explicit limitation is part of the result. If a quantity cannot be linked to a record, the system says so and preserves the collection method. The company can then respond with a readable boundary instead of filling the gap with a silent approximation.
- What the system must preserve
- Collection mode, source, person entering the data, date, available corroboration and traceability level.
- What it must not claim
- Do not manufacture documentary continuity or confuse a statement, an observation and an accounting record.
06 / 07
Conversion must never erase the original flow
Controlled rendering of branch EJ
Multiple currencies and mobile money
Flows whose conversion and reference period are recorded in the data lineage
From the company
Our purchases and payments may cross several currencies and mobile-money services. To review an amount, we need the original currency, date, conversion rule and period to which the transaction belongs.
A converted amount without its source currency cannot be reviewed. The system therefore preserves both values, the source of the rate, the reference date or period and the rounding rule. It also separates the payment date, invoice date and conversion date. Those dates answer different questions.
Mobile money adds a transaction identifier and sometimes an intermediary. These elements belong in the lineage. They link the financial flow to the activity being tracked without turning the payment service into sufficient evidence of the nature of the expense.
- What the system must preserve
- Original amount and currency, reporting amount, rate source, period, rounding and transaction identifier.
- What it must not claim
- Do not replace the original value with the converted value or infer the purpose of an expense from the payment channel alone.
07 / 07
Oral collection is a mode of work, not a defect to hide
Controlled rendering of branch EJ
Several working languages, including languages used orally
Collection designed to take place orally and to be entered into the system afterwards
From the company
Work does not always take place in the language of the form. A person may explain an operation in Wolof or Pular before someone else enters it in French. The system must preserve the separation between what was said, what was understood and what was recorded.
The entry must show the language of the exchange, the person who reformulated it, the date and the attainable fidelity. A note field can preserve a local term that is difficult to translate. Immediate validation by the person interviewed can confirm the general meaning without claiming to produce a transcript.
Written material remains in French or English. Wolof and Pular are used to open the exchange and unblock technical discussion orally. This boundary protects quality: publishing written material that cannot be maintained would create a commitment the system cannot sustain.
- What the system must preserve
- Language of the exchange, language of entry, person who reformulated it, validation of meaning and terms kept in the original language.
- What it must not claim
- Do not present a reformulation as a transcript or publish written material in Wolof or Pular.
08 / A METHOD BEFORE A VALUE
Select a factor without presenting the choice as self-evident
The absence of a national database permits neither improvisation nor the copying of a value found elsewhere. It requires the method to remain visible. The sequence below describes the choice, not factor values. It can be reviewed when a source changes or a contextual gap becomes too large.
- 01
Define the use
Name the activity, boundary, expected unit, period and precision actually required before searching for a source.
- 02
Compare gaps
Read the geography, technology, year, boundary and unit of each possible source. A gap remains written down rather than being absorbed into the value.
- 03
Record the rationale
Preserve rejected options, the reason for the choice, the person who decides and the date of the decision.
- 04
Version the choice
Freeze the source and its version with the calculation. A future update creates a new version rather than rewriting the old one.
- 05
Prepare recalculation
Separate activity data from the selected reference so that the effect of a source change can be measured.
09 / TRANSLATION CONTROL
Words that carry a different weight in English
The English text is not a literal copy. The choices below keep the operational meaning without adding legal weight, moral judgement or a claim that the French source does not make.
Donneur d’ordre
Buyer or lead firm
Contracting authority would suggest a public-procurement role that is not stated here.Financeur
Financing institution or lender
Funder can sound like a grant sponsor, while the source also covers banks and development-finance institutions.Preuve
Evidence
Proof can imply legal certainty. Evidence better describes a trace that still carries a boundary and a method.Secteur informel
Informal sector, then suppliers without formal accounting records
The phrase describes the absence of formal records. It does not state that an activity is illegal.Lignage
Data lineage
Lineage is used in its technical data meaning, not to describe ownership or ancestry.Langues orales
Languages used orally
The phrase describes the collection channel. It does not reduce a language to the absence of writing.10 / USEFUL RESONANCE
Measure recognition of a problem, not audience size
This first publication does not ask how many people saw it. It asks whether the seven constraints describe situations recognised by people who collect, finance, buy or build, before they are given an answer.
Signals are recorded privately. A short reaction, an impression count or a follower count does not become evidence of interest. A share counts only when it returns with a precise question or a field correction.
Situated recognition
- Counts
- A response names one constraint and the decision it blocks, without case-file data.
- Does not count
- General approval or a simple sign of agreement.
Useful correction
- Counts
- A practitioner adds a language nuance, collection condition or missing limitation.
- Does not count
- A style preference with no effect on the method.
Architecture question
- Counts
- The publication triggers a question about the model, synchronisation, lineage or quality.
- Does not count
- A request for a value, a score or access to a financing institution.
Move to the second publication
- Counts
- A reader asks how to turn the recognised constraint into a system rule.
- Does not count
- An isolated click with no question or return.
Private register
- Publication and language
- Reader category, without an organisation name
- Constraint number
- Signal type
- Normalised question, without case-file quotation
- Next step: answer, correct, deepen or produce nothing
Resonance exists when several reader categories return to the same constraints with distinct architecture consequences. It is not inferred from a public volume, and no arbitrary threshold is set before the first responses exist.
11 / BOUNDARY
This text concerns the construction of the system
If your need is to produce a report rather than build the tool, ESG Optimizer Africa exists. If your need is to run day-to-day operations, IROKO products exist. This document is for those who build the system.
This controlled rendering preserves the routing of the French clause. It separates system-building method from reporting and day-to-day management software.
12 / CONCLUSION
A constraint named precisely becomes a design rule
The seven constraints do not require a separate narrative. They require a system that can distinguish absence from zero, a choice from a given fact, a statement from a record, an observation from a transmission and a translation from a transcript. These distinctions are modest. They still determine whether the data can be reviewed after the person who entered it has left.
The next step is not to produce another tool immediately. It is to listen for where the constraints are recognised, which ones return together and which building questions they create. The second publication starts there and turns each constraint into a reviewable architecture decision.
COMPANION PUBLICATION