Every piece of knowledge in an organisation has a lifecycle. It starts as something someone noticed, felt, or experienced — not yet verified, not yet shared, not yet named. It moves, if the conditions are right, through a series of stages as it is expressed, tested, challenged, and refined. At the far end of that lifecycle, it becomes the settled, documented understanding that organisations build their systems, policies, and processes on.
Most of an organisation's infrastructure — its knowledge management systems, its AI tools, its analytical platforms — operates on the far end of that lifecycle. On what is already settled. On what has already been expressed, documented, and structured into a form that a database or a model can process.
This is a significant capability. It is also the wrong end of the lifecycle for the challenges that matter most.
The knowledge lifecycle
Understanding matures through recognisable stages. Anecdotal knowledge is the first expression of something noticed or experienced — personal, fragmented, not yet connected to a wider pattern. Emergent knowledge is the beginning of pattern formation — multiple signals pointing in the same direction, though not yet sufficiently grounded to act on. Forming knowledge is developing, being tested, acquiring connections to other bodies of understanding — credible enough to inform inquiry but not yet stable enough to institutionalise. Grounded knowledge has been validated and connected — it holds under scrutiny and can be shared with confidence. Settled knowledge has reached organisational consensus — it forms the basis of policy, process, and documented institutional understanding. Legacy knowledge is historical record — it shaped the present but may no longer reflect current reality.
Most AI tools, knowledge management platforms, and analytical systems operate on Grounded, Settled, and Legacy knowledge. That is what a training corpus contains. That is what a document repository holds. That is what structured data represents.
The most consequential decisions an organisation faces are almost never made on settled knowledge. They are made on understanding that is still forming — and the quality of that understanding determines everything that follows.
Why the frontier matters more than the archive
When the challenge is clear and the knowledge required to address it is well established, operating on settled knowledge is the right approach. But most of the challenges that define an organisation's trajectory are not like that.
They are challenges where the question itself is not yet clear — where the frame that will eventually organise the response does not yet exist, where the people who understand different parts of the problem have not yet encountered each other's thinking, where the understanding that will eventually become settled is currently anecdotal, personal, and distributed across a population of people who have not been asked to build it together.
Operating on settled knowledge in these conditions produces the wrong answers confidently. The archive is consulted. The patterns are found. The synthesis is produced. And the result is optimised for past conditions rather than forming ones.
What 2026 knowledge management gets right — and misses
The knowledge management industry has understood, in 2026, that tacit knowledge is a competitive moat. The California Management Review describes it precisely: the organisations making the most progress with AI are those treating tacit knowledge as the differentiator, not the models. The tools industry is responding — building AI-assisted transcription, knowledge capture, and synthesis infrastructure designed to surface what is currently in people's heads.
This is progress. The gap it misses: capturing tacit knowledge from individuals is not the same as building emergent knowledge collectively. Transcribed interviews produce settled individual understanding. Collective sensemaking produces emergent collective understanding — understanding that no individual held and that could not have been produced by aggregating individual inputs.
The frontier of the knowledge lifecycle is not just tacit. It is collectively emergent. It is the understanding that forms in the space between contributors — the frame that nobody held before the deliberation, the connection that crossed a disciplinary boundary that no single person could see both sides of, the challenge that shifted an assumption that everyone had inherited without examining.
Where Hunome operates
Hunome is built for the beginning of the knowledge lifecycle, not the end of it. A SparkMap structures the formation of emergent collective understanding — with contributions carrying their epistemic ground, connections between perspectives preserved, and the development of understanding visible as it matures from anecdotal through emergent to forming.
This is not a replacement for knowledge management tools. It is the layer that produces the understanding that eventually becomes the knowledge those tools should manage. The organisations that build this layer are not just operating more effectively than those that do not. They are operating on a different part of the competitive terrain — where the understanding that will define next year's decisions is forming now.