Knowledge Currency — What Happens to a Decision Asset When the Policy Changes

The file was impeccable. Structured notes, organised by theme, keyed to the original questions. Every claim traced back to a transcript, an agenda, and a verified practitioner who had actually said it. It was the kind of thing an investment memo could rest on without embarrassment.

And then there was the date. Eleven months. In those eleven months, the government changed the rules the entire finding rested on.

Nobody enjoys this part of the story, and Kofa does not either. We have spent a lot of words describing what it takes to preserve practitioner knowledge. Capture it completely. Keep the qualifications. Keep it searchable, keep it citable, keep it reusable. All of that is necessary, but none of it is sufficient — preservation is only half of the problem.

The other half is time.

Knowledge has to survive two journeys, not one. The first runs from the person who knows to the person who decides. The second runs from the day it was true to the day it is used. Nobody waits politely for the second one to finish.

A snapshot in a moving world

Every decision asset is a snapshot. On the day it was made, it captured what a practitioner knew, with all the qualifications and conditions attached. That snapshot was true. It is still true as a record of that moment. What it is not is a promise about the present.

Think of what actually moves in the markets Kofa serves. Say a central bank revises its credit guidelines in the middle of the year. Overnight, the lending dynamics a loan officer described to you in Q1 are no longer the ones you are facing. A procurement reform gets gazetted, and the supplier-selection patterns a procurement evaluator walked you through become history. Import tariffs change. Health protocols get revised. Exchange-control rules shift. In each case, the practitioner's judgement was not wrong. The conditions it rested on were.

None of these changes appear in the asset. The notes sit there, organised and attributable, doing nothing wrong. Nothing about them moved when the world did, and nothing told you they had not.

Stale knowledge is worse than no knowledge

It is tempting to file this under "absent knowledge" and move on. It is not absent. When you do not know, you know you do not know. You build in uncertainty, you hedge, you ask. Absent knowledge is honest; stale knowledge only looks like it is.

Stale knowledge arrives with the full confidence of a verified, citable source. It has a transcript behind it, a practitioner behind it, an agenda behind it. Everything about it says this is reliable. Only the date says otherwise, and unless the date is built into how the record is used, it is the first thing nobody looks at.

Organisations do not usually lose to the intelligence they never had. They lose to the intelligence they had, and stopped checking.

This is the quiet failure mode of the idea we believe in most: knowledge that compounds. Compounding only works if the base is current. Build a new decision on a finding that has quietly stopped being true, and you are not compounding knowledge, you are compounding error. Each decision inherits the staleness, and the confidence grows in step with the age of what you are building on.

A library that never refreshes is a museum. Museums are for looking at. They are not for deciding with.

Every record is 'as of' — or it is not a record

The way out is not to try to make knowledge permanent. It is to make it dated. Every decision asset in Kofa carries the moment it was true, an as-of date inseparable from the record itself. Not a metadata field that gets ignored. Part of how the record reads.

Once that is true, a simple thing becomes possible: old knowledge can stop pretending to be new.

An asset from March is not wrong. It is as of March. Those are different statements, and the difference between them is the difference between a library that compounds and a library that decays. Old knowledge remains evidence: of what was true then, of the conditions that held, of the arc of how the truth changed. What it stops being, the moment it is honestly dated, is a current claim.

Every serious record-keeping system ends up here eventually, because there is no other option that survives contact with time. You cannot stop the world from changing. So you make the record tell the truth about when it was made.

Never let old look new

So the platform starts with labeling. Every asset carries its as-of date at the object level, the same object-level discipline Kofa applies to confidentiality. And every asset carries a validity state, because a date alone still leaves the work of judgement to whoever opens the file:

The states are not decorative. When Ask Kofa returns an asset, the freshness and the date appear before the content, so a stale answer is never presented as a current one. The record never stops being citable — it simply stops being mistaken for something it is not.

How the platform knows the world moved

Labeling only works if someone does the watching. Kofa watches through three signals, and none of the three is a spreadsheet.

Time. Assets age on a schedule. Past a freshness window they read as aging, whether or not anything has happened. Time is the cheapest detector and the most honest, because it admits that nobody knows everything that changed, and behaves accordingly.

Events. Policy and regulatory change is not random noise, it is trackable: circulars, gazettes, guideline revisions, procurement reforms. Kofa monitors the signals that matter for the sectors and geographies its clients work in, and when a change lands it looks across the affected assets and flags them. This asset rests on conditions that may have moved. The coordinator network is part of this too. The people on the ground hear about change before it is gazetted, because they live inside it.

The practitioner. The cheapest signal of all is the person who said it. The asset already links back to the practitioner, the verified human being who made the record. When an asset matters, the platform can ask that same person the cheapest possible question: is this still true? Not a new engagement, a check. The person who told you what was true in March is the best person to tell you whether it is still true in August.

These three signals are not an audit. An audit says maybe something changed. The design goal is to say this changed, and here is what it touches.

The loop that keeps knowledge alive

Detection without renewal is just anxiety with metadata. The third mechanism is what turns the library from a watched thing into a living one: the refresh engagement.

A refresh is not a new engagement. It is the same question and the same practitioner, a shorter session, a smaller fee, a tighter window. Its entire job is to answer one question: what changed? The output is a delta record linked to the original asset: what still holds, what no longer holds, what is simply gone. The organisation sees not just the current answer but the arc, how the truth moved from March to August, and why.

This is the difference between collecting knowledge and keeping it. Collecting stops when the conversation ends. Keeping requires the loop: label, detect, refresh, repeat. That loop is what makes "knowledge that compounds" true in the only sense that matters for a decision: current knowledge, compounding.

Why this is the part nobody else can copy

There is a reason the refresh loop does not exist anywhere else, and it is the same reason the whole platform exists. The person you need to reach is the person cold outreach never reaches.

A refresh requires going back to the same practitioner, the loan officer in Gaborone or the cooperative leader in Western Kenya, and asking them again for their time. That is exactly the interaction that fails everywhere else. Cold outreach cannot do it twice; it cannot even do it once. A research firm's relationship with an expert ends when the project does. An expert network's relationship with an expert is a database row.

Kofa's relationship with a practitioner is a relationship. It is held by the coordinator who sourced them, maintained by the verification process that confirmed them, and honoured by the payment discipline the platform runs on. When something shifts, Kofa can go back. Because it never left.

A refresh is the interaction cold outreach cannot do twice. Kofa can, because it never left.

Cite it. And know when it was true.

This changes what it means to base a decision on an asset. "The record says X" becomes "the record said X as of March, and we checked, it still holds." That isn't cosmetic — it's the difference between citing a document and citing a live source, between a fact your organisation once owned and knowledge it currently holds.

For the analyst writing the memo, the asset arrives dated with its state visible. If it is flagged, the refresh is one action and two days away, which is before the committee meets, not after.

For the portfolio manager, a finding from two years ago can finally be tested against the present. The conditions under which it was true are on the record, and the same practitioner can be asked whether they still hold.

And for the organisation, the library is no longer a museum of what was once known. It is a living record: a timeline of how the truth changed, maintained by the people who made it true, current on the day it is used.

Knowledge that compounds stays current

The founder's letter said it first: information survives the journey remarkably well. Judgement rarely does. Kofa was built to change that, to make sure the judgement of a loan officer in Accra survives the journey from the field to the room where the decision is made.

Knowledge Currency is the second half of that promise. The first half made sure the knowledge arrived. The second half makes sure it is still true when you use it. Information survives the journey, and now, with a date on it, a check behind it, and a loop under it, it survives time as well.

Knowledge that compounds, and stays current. The loop is what keeps it that way. The museum was never the plan.

Aminu Rabiu

Founder, Kofa Insights Limited