Local processing needs a resource ledger from the first batch

GFT's position is that a resource statement should be no broader than its record. A site electricity result describes a site electricity boundary. A batch water result describes its measured and allocated water boundary. A supplier estimate remains an estimate. GFT recommends preserving those distinctions through management reporting and any later public wording, so a narrow operational improvement cannot be read as an established reduction across an entire product life cycle.

The opening chapter's practical deliverable is therefore a measurement contract. GFT recommends that it name the product boundary, accepted-output rule, resource categories, reporting period and responsible roles. It should also state how missing readings, shared services, outsourced work and changes to the process will be treated. These definitions give later chapters a common decision boundary without predetermining their detailed technical methods.

The contract should require an evidence status beside each significant result. GFT recommends distinguishing direct readings, calculations from readings, estimates and proposed scenarios. Preserve the underlying record and the calculation version. An estimate may be useful for planning, but it should not silently become measured evidence when copied into a dashboard. A change in evidence status needs an identifiable reason and supporting record.

The claim itself should be drafted with its evidence test. GFT recommends recording the intended reader, the physical boundary and the comparison being asserted before a trial begins. A statement about lower intake at unchanged accepted production requires different proof from a statement about lower intensity during expansion. A statement about supplier engagement requires different proof from a measured supplier reduction. If the available record supports only the narrower statement, publish only that statement after the appropriate internal approval. This approach makes communication part of the measurement design, while leaving the actual outcome open to what the trial demonstrates.

GFT also recommends a short challenge process before a resource claim is released. Can the result be traced to its readings? Does its output have the stated quality release? Is the comparison boundary unchanged or explicitly reconciled? Are unsuccessful runs included? Is any supplier contribution missing? The purpose is to expose the condition that could change the conclusion. A claim that survives these questions is more useful than an attractive ratio with an unknown denominator.

For the proposed Cameroon programme, the next useful action is to commission this contract against the intended product route and supplier boundary. GFT recommends collecting the first comparable production records before approving an environmental performance target. During commissioning, use the ledger to identify missing instruments and unresolved allocations. During trials, use it to compare methods. During operation, use it to determine which exceptions need corrective work.

The commissioning handover should include a demonstrated reading path. GFT recommends selecting a completed production record and following it from the original resource reading through its calculation to the management result. A second person should be able to reconstruct the stated boundary and identify any assumed allocation without relying on an oral explanation. If that cannot be done, the handover should identify the missing record and an action owner. This is a proposed acceptance exercise, not a report of an exercise already performed. Its value is to test whether the ledger can support a decision after the person who assembled it is no longer in the room.

The sponsor should retain the right to withhold a reduction claim while continuing useful engineering work. GFT recommends treating an unresolved comparison as an information problem with a defined next test. Production can continue to generate evidence, and procurement can continue to clarify guarantees, without giving an incomplete result a stronger label. The ledger should help the team move from uncertainty to a reproducible conclusion, rather than create pressure to declare success before the necessary account exists.

This framework is an engineering and management recommendation. It is not investment, legal or tax advice, a compliance determination, a certification statement or a substitute for site-specific environmental assessment. No GFT reduction, client performance or installed resource system is asserted here. The paper defines the evidence that would be needed before reporting those outcomes and leaves their achievement to a documented operating test.

The resource ledger makes the Warp and Signal proposition concrete: production provides the material route, and measurement provides the record needed to judge it. GFT recommends keeping the record close enough to the batch that a manager can identify the action behind a result. Local processing can then be discussed through visible choices about inputs, accepted output and responsibility, with the remaining uncertainty retained alongside the answer.