Skip to content
panamorphixINTELLIGENCE
Panamorphix

Contact about /Hop

Talk to us about the ideas in /Hop or your work.

Verification complete

Please see our Privacy Policy regarding how we will handle this information. You can also use our /Hop data posture page to request access to or deletion of the data you have shared with us.

Issue 09September 2026

A lead erodes. A position compounds.

Most technology advantages are leads. A better model. Faster AI. A cleaner design. A bigger dataset. These are real and they matter. And they are, almost without exception, temporary. The company behind you is working on the same problem with much the same information. The gap closes. The advantage becomes a line in a comparison table.

A position is different. A position is when the advantage is not in what you built, but in what your foundations have been collecting since you started. When the gap between you and the next company is not about what they could build tomorrow, but about what you have been recording properly since day one. Catching up would mean rebuilding all of it.

That is not a lead. It is a moat. And it works differently from other advantages, because it does not need you to stay ahead. It needs your competitors to start again.

Panamorphix is building a position, not a lead. That difference matters for everything that follows.

What builds up and what does not

Data fades as an advantage faster than people expect. It can be bought, licensed, generated or collected more cheaply every year. And even where a data lead holds, what it delivers, such as better AI answers, tends to even out as the technology improves for everyone.

Compute is not an advantage for most companies at all. It can be rented. For everyone except a handful of giants, it is a cost, not a position.

Network effects do build up, but only once enough people use the product. Below that point, they are just users, and users can leave.

Context, kept properly on closed foundations, builds up differently from all of these. It needs no threshold. It does not depend on buying data, owning compute or reaching a crowd. It grows from the first fact recorded properly. Every source checked adds to the map of knowledge. Every organisation matched correctly makes the next match more precise. Every pattern spotted makes the next change easier to see. Every chain of evidence kept makes the next review simpler.

This is not a future plan. It is already happening in our directories, one recorded fact at a time.

The gap that cannot be closed later

Every health tech company using AI today is creating context. Thousands of AI actions. Thousands of clinical and operational decisions. Records of patients, staff and devices spread across systems that were never designed to talk to each other. Clinicians accepting, changing or rejecting AI suggestions. AI confidence in real patients that looks nothing like the group it was tested on. And robots, including humanoid robots, are starting to play a bigger part in health and care.

Very little of this is being kept properly.

The context is created and lost at the same time. Chains of evidence break wherever data moves between systems. The same patient, clinician or device appears in two systems with two different IDs, and nobody links them. Patterns in how tools behave come and go unrecorded. The quality of each input is never measured.

This cannot be fixed after the event. Context that was not captured when a decision was made cannot be rebuilt later. An AI action that ran without its sources attached does not gain them when the audit arrives. Drift in a tool's behaviour cannot be measured against a starting point that was never recorded.

Health tech companies that are not keeping their context properly now are not standing still. They are building up a gap that is invisible today and cannot be closed with money later.

That moment arrives in different ways. For some, a patient safety investigation asks what the AI knew, what it did and why. For some, an NHS trust's procurement asks for proof of well-governed AI before signing. For some, a regulator asks for evidence of how the product behaves in real use, not just in testing. For some, a competitor simply shows that its AI can be checked and theirs cannot. And AI will always work on probabilities, so the need to check it never goes away.

Each time the question is the same. Can you show what your system did, why, what it knew at the time and how it has behaved since it went live?

The companies whose foundations can answer that walk in with a position. Those whose foundations cannot walk in with a problem they cannot fix fast enough.

Why the window is now

Health tech is at a turning point that will not come again.

AI in health and care is moving from pilots to everyday use. The question is no longer whether AI will be used. It is already being used. The question is whether the foundations underneath it are fit for what it is actually doing.

Regulators are asking that question more seriously. The MHRA's work on software and AI as a medical device. NICE's evidence standards for digital health technologies. NHS requirements such as DTAC and the DCB0129 and DCB0160 clinical safety standards. The FDA's approach to AI in medical devices. The EU AI Act. The direction is clear and speeding up. Companies will need to show not only that their AI performs, but that its behaviour is tracked and its reasoning is kept.

The window to build the foundations properly is open now: before the rules harden, before the first major investigation into an AI agent in a clinical setting, and before NHS procurement builds in AI governance checks that cannot be added to existing products afterwards.

It will not stay open.

Companies that build properly in this window are not just preparing for regulation. They are building a position that makes them more trustworthy than competitors over time. Not because their models will be better, since models will even out. Because they will have something nobody else can copy at any price: a properly kept record of how their AI has behaved in the real world since day one.

That record is the product. Not the AI. Not the interface. Not the integration. A record of every action the system has taken, with its sources attached, its knowledge quality measured, its people and devices correctly matched and its behaviour visible. That is what wins procurement. That is what survives scrutiny. That is what an NHS trust means when it says it needs AI it can trust.

The position Panamorphix is building

CongDB is the graph. Every organisation, relationship, record and decision kept with its source from the moment it arrives. Not logged afterwards. Kept as part of the foundations.

ECP is the knowledge layer. It checks evidence on the way in, measures how good the knowledge behind each decision is, and shows the difference between a system that claims to perform and one that can prove it.

Makemake is the matching layer. It works out when records in different systems describe the same patient, clinician, device, supplier or site, and keeps the evidence for each match before anything is recorded as fact.

Behaviour OS is the pattern layer. It shows how things change over time: where an AI tool is working as designed, where it is drifting, and where the way people respond to it reveals a problem that testing never found.

Kynes prepares what changes for human review, and DBx3T keeps the record and its history safe for the long term.

Our own directories already run on these foundations. Care Tech Directory, Care Robotics Directory and Clinical Research Directory each add to the same kind of record, one checked fact at a time.

This is not a product roadmap. It is a position. It becomes more defensible with every fact recorded properly, more precise with every match, clearer with every pattern found and more complete with every chain of evidence kept.

A lead erodes. A position compounds. The ground is being claimed now, and the compounding has already started.


What comes next

Hop 9 is the moat argument. Not a vision, but a position built from nine hops of reasoning and from foundations that become more valuable from the moment they start recording.

Hop 10 goes to the ground. A step-by-step walk through a real clinical scenario across the full set of foundations. What CongDB records, what ECP measures, what Makemake matches and what Behaviour OS shows, in a setting where AI agents act, records are messy and the reasoning has to hold up.

Written byMark Nicoll

EDITORIAL UPDATES

Receive /Hop in your inbox

One issue per month on evidence, AI and human judgement in health and care.