Informative publication — not a normative specification
Available for research; independent replication pending. ArtiProof is designed to support evidence-based assessment of organisational knowledge. It is not yet broadly independently validated. Reproducibility between independent assessors and proportionality in practice remain open questions; the first independent replication remains pending.
The equivalence of the English and Dutch texts has not yet been independently assessed.
Executive summary
Artificial intelligence is changing how organisations create, interpret and use knowledge. It can make work faster, more consistent and more scalable. It can also allow an organisation to continue producing answers while gradually losing the ability to explain where those answers come from, who understands them, which judgement still matters and how the work could be recovered if a person, system or supplier disappeared.
ArtiProof is designed to address that gap.
ArtiProof provides a structured way to examine which knowledge important work depends on and what evidence supports relying on it. It is designed to make dependencies, uncertainty and possible weaknesses explicit. Research must establish how consistently it does this and what value it adds in practice.
The method distinguishes three forms of organisational knowledge: Source Knowledge, Craft Knowledge and Generated Knowledge. It examines them through five assurance properties: Integrity, Provenance, Authority, Understandability and Resilience.
ArtiProof is deliberately not a general management system, a maturity ladder, an AI-safety standard or a documentation programme. It is a focused knowledge lens that can work alongside existing quality, process, risk, governance, HR, continuity, records and technology practices.
Its central design principle is simple: use enough assurance to support reliable action, but no more than the consequence requires.
WHY — Purpose and context
1. Knowledge is operational infrastructure
Every organisation relies on infrastructure that can be seen: buildings, systems, applications, contracts, procedures, organisational structures and data.
It also relies on infrastructure that is much harder to see: knowledge.
A process works because someone understands what a rule means. A public service remains lawful because legislation has been translated into interpretation and practice. A technician recognises when the documented procedure is not enough. A team knows which exception matters. A manager understands which figure can be trusted and which is only an approximation.
This knowledge is rarely stored in one place. Some of it sits in documents and records. Some lives in the judgement of experienced people. Some is embedded in software, analytics and automated rules. Increasingly, some is generated or transformed by artificial intelligence.
That makes organisational knowledge both distributed and fragile.
ArtiProof starts from a basic management question: what does this organisation need to continue to know in order to understand, justify, perform and recover its important work?
2. The efficiency paradox
Digitalisation makes information easier to store, retrieve and transform. AI makes it easier to produce summaries, recommendations, classifications, draft decisions and explanations.
That is valuable. But access to more information does not automatically create stronger organisational knowledge.
An organisation can become faster while becoming less capable of explaining what its systems do. It can automate a task successfully while allowing the human ability to challenge an unusual case to decay. It can retain every document while losing the people who understand why two contradictory documents exist. It can generate plausible answers while becoming less able to distinguish authoritative knowledge from copied or transformed material.
This is the efficiency paradox at the heart of ArtiProof: operational performance may improve while knowledge resilience weakens.
Nothing has to fail immediately. The weakness may remain invisible until a key expert leaves, a supplier changes, a model is challenged, regulation changes, a rare case appears, a system becomes unavailable or an organisation must reconstruct a decision years later.
3. Information is not the same as knowledge
A repository with thousands of documents contains information. Knowing which three documents govern a consequential decision is knowledge.
A database contains data. Understanding what a field means, why an exception exists and when the data should not be trusted is knowledge.
An AI system can produce an answer. Knowing why that answer deserves reliance, who can challenge it and what happens when the system is wrong is an organisational capability.
ArtiProof therefore does not begin by asking whether information exists. It asks whether the organisation can connect consequential work to the knowledge, people, sources, systems, evidence and authority on which it actually depends.
4. Why AI makes the issue urgent
The knowledge problem predates generative AI. Retirement, outsourcing, mergers, restructuring, long-lived legacy systems, staff turnover and supplier dependency have always created knowledge risk.
AI increases the speed and scale of the problem because it can move directly from information to action. Work that once required a person to read, interpret and decide can increasingly be performed through a system that summarises, recommends or generates.
The transition can be gradual: human understands; system assists; system recommends; system becomes the default; human capability is used less often; the organisation becomes dependent before it notices.
ArtiProof does not argue that human work should be preserved for its own sake. It asks a more practical question: which human and organisational capabilities must remain available so that automated work can still be understood, challenged and recovered when consequence requires it?
HOW — The ArtiProof method
5. Three types of organisational knowledge
ArtiProof uses three knowledge types because different knowledge fails in different ways and requires different evidence.
Source Knowledge is knowledge grounded in an identifiable source: legislation, policy, contracts, standards, specifications, approved records, manuals, process documentation or validated datasets. Its main strength is traceability to an explicit reference point. Its weakness is that a source can be current yet misunderstood, authoritative yet ambiguous, approved yet obsolete in practice.
Craft Knowledge is knowledge developed through practice, experience, professional judgement and repeated exposure to real situations. It includes recognising unusual cases, understanding why a procedure exists, knowing when a rule requires interpretation, seeing weak signals and understanding dependencies that are not obvious from formal documentation. Craft Knowledge can be reliable precisely because a professional has learned to judge context. It can also become a dangerous single-person dependency.
Generated Knowledge is knowledge produced, inferred, transformed or synthesised by technological systems. It includes outputs from AI, analytics, rules engines, automated calculations, classifications, predictions and generated summaries. Generated Knowledge is not treated as inherently weaker or stronger than human knowledge. It must be supported by evidence appropriate to its use and consequences.
The three forms often interact. A caseworker combines legislation with experience. A model transforms internal data. A system recommendation is reviewed through professional judgement. ArtiProof therefore treats knowledge as a network rather than as isolated categories.
6. Five assurance properties
ArtiProof examines important knowledge through five assurance properties.
Integrity asks whether the knowledge is sufficiently complete and protected against inappropriate alteration, degradation or unnoticed change.
Provenance asks whether the knowledge can be traced to its origin and development. An organisation should know, to a degree proportionate to consequence, where important knowledge came from and how it reached its current form.
Authority asks whether the knowledge is sufficiently authoritative for its intended use. Authority may come from law, an approved source, delegated responsibility, professional competence, an accountable role or another recognised basis.
Understandability asks whether the people who depend on the knowledge can understand it and appropriately challenge it. A correct answer that nobody can interpret or question may still create organisational weakness.
Resilience asks whether the organisation can preserve or recover the knowledge and the capability that depends on it when people, systems, suppliers or circumstances change.
The five properties are deliberately kept separate. A knowledge item may have excellent provenance and poor resilience. It may be authoritative but difficult to understand. It may be complete but concentrated in one person. ArtiProof does not hide those differences inside a single maturity score.
7. Scope is not maturity
One of the most important design choices in ArtiProof is to separate scope from strength.
A knowledge dependency may sit with one person, within an activity, across a process, across an organisation or across a chain of organisations and suppliers. A wider boundary is not automatically better or more mature. The correct scope is the smallest boundary that still captures the material dependency.
If a critical knowledge risk is local, the assessment should remain local. If the process depends on a supplier, external expert, shared platform or public partner, the scope should widen until the dependency is visible.
This avoids a common failure of maturity models: treating structural expansion as progress in itself.
ArtiProof therefore does not seek to place organisations on a universal Level 1-to-5 ladder. It asks whether the specific knowledge on which consequential work depends is sufficiently assured for its context.
8. Evidence before paperwork
Governance methods can easily become documentation programmes. ArtiProof is designed to resist that tendency.
The central evidence principle is Minimum Sufficient Evidence: gather enough evidence to support a reasonable assurance conclusion, but do not create material merely because a methodology exists.
Existing organisational evidence should be reused before new artefacts are created. Useful evidence may already exist in skills matrices, process descriptions, HR records, architecture repositories, quality files, audit material, responsibility matrices, training records, continuity plans, decision records, system documentation and operational data.
Reuse is not automatic acceptance.
Every reused artefact must be mapped to the exact ArtiProof claim it is meant to support and checked for relevance, currency and reliability. A skills matrix may be out of date. A process diagram may represent the intended process rather than the real process. A past audit may have tested a different question.
Where the consequence is high or documentary evidence is weak, ArtiProof allows reality testing: explanation, demonstration, walkthrough, interview, peer challenge, exception handling, handover or recovery exercises.
The point is not to prove that paperwork exists. It is to obtain enough evidence to justify a conclusion about knowledge.
9. Professional judgement is not a control failure
Knowledge-intensive work creates a difficult design problem. Reliability cannot always be achieved by writing a more detailed procedure.
Professional judgement may be essential because the real world contains ambiguity, exceptions and context that cannot be fully encoded.
ArtiProof does not assume that autonomy is the opposite of assurance. This is a Candidate/experimental implementation pattern: research is testing whether making the conditions for professional judgement explicit supports assurance without prescribing every judgement.
Those conditions may include appropriate competence and experience; access to authoritative sources; clear decision rights; explainable reasoning where consequence requires it; peer challenge; transfer to another capable person; and a credible recovery route.
Professional autonomy is never a waiver from assurance. Equally, documentation density is never proof of control.
A useful principle is: manage the dependency and the evidence around craft knowledge; do not automatically proceduralise the craft itself.
10. Consequence determines assurance
Not every knowledge item deserves the same controls.
The consequences of weak knowledge may range from inconvenience to legal error, financial exposure, operational disruption, public-service failure, safety impact or inability to recover an essential capability.
ArtiProof uses consequence-based proportionality. The greater the consequence of knowledge failure, the stronger the evidence and assurance that should be expected. The method asks assessors to match evidence and challenge to the consequences, uncertainty and dependencies of the case. This is a design rule. It does not establish that the resulting assessment will be proportionate in practice; additional effort and decision value must be evaluated.
The target is not maximum maturity. It is sufficient capability.
That distinction matters. Without it, organisations are encouraged to accumulate controls, documents and review layers simply because “higher” appears better. ArtiProof instead asks what level of assurance is justified by the actual consequence, context, rate of change and difficulty of recovery.
11. Assurance must remain alive
A static assessment decays.
Knowledge changes when people leave, systems are replaced, suppliers change, regulation evolves, AI is introduced, an incident exposes a hidden assumption or a once-routine skill stops being practised.
ArtiProof therefore treats assurance conclusions as time-bounded rather than permanently valid.
A conclusion must state its time boundary and material invalidation conditions. Each conclusion should state a review point and identify material changes that could invalidate it, such as departure of a key knowledge holder, a major system or AI change, supplier transition, a material source or regulatory change, a serious incident, a failed handover or an inability to explain or recover a critical capability. A formal event-triggered reassessment mechanism remains Candidate/experimental and is subject to further method research and should not yet be treated as a settled feature of the method. Any reduction in burden or missed changes must be tested.
A proportionate periodic review may be used where appropriate. The research question is whether more formal change-triggered approaches can later reduce burden without increasing missed-change risk or assessor inconsistency.
12. Calibration before complexity
Assessment methods often respond to disagreement by adding more criteria, more scores and more rules.
ArtiProof takes the opposite starting point.
When assessors reach materially different conclusions, the first question is whether the disagreement can be reduced through clearer examples, better evidence guidance, sharper scope and transparent reasoning.
Material disagreement should be recorded before consensus. It may reveal ambiguous criteria, unequal access to evidence, hidden local practices or genuine inconsistency in the organisation.
A reviewer should be able to follow the evidence and reasoning behind an assessment. Reproducibility is a separate question: do independent assessors reach materially compatible conclusions from the same evidence, scope, consequence framing and guidance? Record their initial judgements before calibration or discussion. Agreement reached afterwards is not evidence of independent agreement.
This principle — calibration before complexity — is especially important for ArtiProof because the method deliberately avoids false precision and composite maturity scores.
WHAT — Application and outcomes
13. A bounded assessment flow
The design aims to limit additional work; actual effort depends on the case and must be recorded.
First, define the bounded activity, process, decision, service or capability that matters.
Second, identify the knowledge required to understand, justify, perform and recover it.
Third, determine the relevant mix of Source Knowledge, Craft Knowledge and Generated Knowledge.
Fourth, map the material dependencies: people, sources, systems, teams, suppliers and external parties.
Fifth, reuse existing evidence and identify what remains unproven.
Sixth, assess the relevant knowledge against Integrity, Provenance, Authority, Understandability and Resilience, with the evidence level matched to consequence.
Seventh, identify the smallest sufficient action: reduce a dangerous concentration, clarify authority, preserve a source, capture a critical interpretation, test a handover, improve provenance, add an AI checkpoint, create a recovery route or consciously accept the risk.
The assessment should end in a decision, not in an inventory.
14. The Knowledge Matrix
Many organisations already use skills matrices to understand who can perform which tasks.
The Knowledge Matrix is a Candidate/experimental interface intended to display knowledge dependencies. Its added usefulness and proportionality remain to be tested.
The matrix can connect people to knowledge, processes to knowledge and organisational entities to knowledge. Where dependency crosses organisational boundaries, a chain or ecosystem view can be added.
Its purpose is not to reduce knowledge to a spreadsheet. It is to make concentration, coverage, authority, evidence and dependency visible.
A process may appear well staffed because five people can execute it. The Knowledge Matrix may reveal that only one person understands an exception, one supplier holds the recovery knowledge or no one can explain a legacy rule embedded in software.
That is often the vulnerability that conventional staffing or process data does not show.
15. A one-page management view
Comprehensive thinking does not require comprehensive paperwork.
The evidence base may be detailed, while a management synthesis can remain small. A Candidate/experimental One-Page Knowledge Assurance View is being tested to summarise the bounded context, consequential knowledge, principal dependencies, material assurance gaps, recovery position, highest-priority action and direct references to supporting evidence.
The one-page view is not the evidence base and should never become a red-amber-green score for the organisation. It is intended as a traceable synthesis for management discussion and action.
The one-page view is a Candidate/experimental management summary linked to supporting evidence. Keeping it operationally small is a design aim, not a demonstrated burden result.
16. AI implementation checkpoints
ArtiProof can be used before and after an AI implementation.
Before implementation, the organisation can ask what knowledge currently makes the process possible, who understands exceptions, where the authoritative sources sit, which human capabilities are consequential and which dependencies already exist.
After implementation, it can ask what knowledge is now generated by the system, which human skills are used less frequently, whether users can still challenge the reasoning, whether provenance is adequate, whether new dependencies have appeared and whether the organisation could continue or recover if the system or supplier became unavailable.
The objective is not to slow automation. It is to prevent knowledge loss from becoming an invisible transformation cost.
17. Knowledge Pollution
AI dramatically lowers the cost of producing plausible information.
That creates a new organisational risk: generated summaries become sources for new summaries; provisional interpretations are copied into procedures; old and new versions coexist; system-generated material becomes indistinguishable from approved knowledge; and provenance is lost as content is repeatedly transformed.
ArtiProof uses the term Knowledge Pollution for an information environment in which it becomes progressively harder to distinguish what should be trusted, why and on whose authority.
The danger is larger than an individual wrong statement. The organisation can lose the ability to determine which knowledge deserves reliance.
Integrity, Provenance and Authority are therefore increasingly important as the cost of content generation falls.
18. Accountable Knowledge Authority
Important knowledge should not become everyone’s responsibility and therefore nobody’s responsibility.
ArtiProof uses the concept of an Accountable Knowledge Authority: the person, role or body that can determine whether consequential knowledge is sufficiently authoritative for the organisation to rely on it.
This does not imply a new job title. The authority may already be a process owner, professional lead, legal expert, policy owner, product owner, governance body or other competent role.
The question is simple: who can stand behind this knowledge for this use?
19. What ArtiProof does not try to become
ArtiProof is intentionally bounded.
It is not an AI model, an AI-safety standard, a cybersecurity framework, a records-management system, a business-continuity standard, an HR competency model, a quality-management replacement or a universal management framework.
When an ArtiProof assessment reveals that a knowledge dependency is caused by weak cybersecurity, continuity, records management or another discipline, it should signal the dependency and refer it to the discipline that owns it.
ArtiProof should not absorb every problem it can see.
It also does not claim that a process, decision or body of knowledge is correct merely because the method has been applied. Knowledge assurance supports justified reliance; it does not create truth by declaration.
20. Learning from established management traditions
ArtiProof has been developed with an explicit preference for learning from established organisational practice without inheriting unnecessary architecture.
Research into EFQM, INK and the Common Assessment Framework reinforces several design choices: assessments should connect to action; evidence should be reused; professional autonomy and control must coexist; context matters; a framework should be understandable to practitioners; and large models can create bureaucracy, score chasing and false maturity when their structure becomes the objective.
The lesson is not to turn ArtiProof into another excellence model.
It is to retain the mechanisms that help organisations learn while keeping the object of assurance narrow: consequential organisational knowledge.
21. Validation and development status
ArtiProof is an emerging methodology under active development. The validation programme is intended to examine independent usability, assessor reproducibility, proportionality, added value beyond existing governance, transferability and organisational outcomes. The first independent replication remains pending. Publication readiness and internal review do not answer these empirical questions.
Its credibility should depend on evidence, reproducible assessment and transparent limitations rather than on the appearance of completeness.
Current research distinguishes several questions that must not be collapsed.
Method validity asks whether the concepts and assessment rules are coherent enough to support the intended conclusion.
Implementation usability asks whether organisations and assessors can apply the method without disproportionate burden. Test proportionality in bounded pilots: record gross additional effort, time spent clarifying or creating evidence, evidence reused and any decision-relevant findings beyond a competent comparator. Report observed and estimated benefits separately, with their assumptions. Assess whether the additional effort is justified by the decision value in that context. Preserve null, negative and contradictory results.
Sustained integration asks whether the practices remain part of real work rather than becoming a short-lived assessment exercise.
Observable knowledge-assurance effect asks whether using the method actually improves the organisation’s ability to identify, understand, trust, preserve or recover consequential knowledge.
A positive result at one stage does not prove the next.
ArtiProof is also testing whether assessors can reach materially similar conclusions from the same evidence, and whether natural-language English and Dutch interfaces preserve the same evidentiary threshold. This whitepaper is informative. It does not constitute certification, accreditation, regulatory approval, academic validation or third-party assurance.
22. Design principles
The method is guided by a small set of disciplines.
Knowledge first: begin with the knowledge required for reliable work.
Reuse before creation: use existing organisational evidence when it genuinely supports the claim.
Minimum Sufficient Evidence: require enough evidence to justify the conclusion, not paperwork for its own sake.
Consequence-based proportionality: stronger consequences require stronger assurance.
Small before complex: begin with a bounded problem and widen only when dependency requires it.
Scope is not maturity: a wider system boundary is not automatically better.
Human capability matters: automation does not remove the need to understand which human judgement remains consequential.
Signal, do not absorb: expose dependencies on other disciplines without turning ArtiProof into a universal framework.
Calibration before complexity: improve examples and evidential guidance before adding scores, criteria or properties.
Independent method: ArtiProof should remain understandable and usable without dependence on a particular vendor, technology or implementation provider.
23. The question ArtiProof ultimately asks
Many organisations know how many employees they have, which systems they run and how much data they store.
Far fewer can answer, with evidence:
What knowledge must we continue to possess in order to act reliably, and how do we know that this knowledge will remain trustworthy, understandable and recoverable when people, technology and circumstances change?
That is the question ArtiProof is designed to make explicit.
Artificial intelligence gives organisations extraordinary new capabilities. It should not require them to surrender their capacity to understand themselves.
ArtiProof in one sentence
ArtiProof is a knowledge-assurance methodology designed to examine consequential organisational knowledge dependencies, the evidence for relying on them and possible weaknesses, with consistency and practical value still to be established through research.
Publication note
This whitepaper is an informative introduction. Formal definitions, assessment rules, validation statements, research records and version information are maintained separately. Claims should never exceed the evidence available for the current version of the methodology.