KF-L001-B01 · Knowledge as the Object of Knowledge Systems

Representation, Evidence and Justification

Evidence · Expanded Draft · v0.2 · 29 min read

Question  →  Corpus  →  Evidence  →  Patterns  →  Candidate Insight

Purpose

To examine the foundational concepts that underpin knowledge systems and to determine what exactly is engineered, governed, represented and evolved across the diverse traditions examined in the Literature Landscape.

Rather than attempting to resolve centuries of philosophical debate concerning the nature of knowledge itself, this chapter investigates the practical concepts that repeatedly appear across Knowledge Engineering, Knowledge Management, Information Science, Governance and Artificial Intelligence.

Its purpose is to establish a coherent conceptual vocabulary for the remainder of the Literature Landscape and to provide a common foundation for the subsequent Literature Synthesis.

Executive Summary

Every scholarly tradition examined in the preceding chapters refers to knowledge. Knowledge Engineering represents knowledge (B02). Knowledge Management cultivates it (B03). Governance disciplines regulate its change (B04). Foundation models increasingly manipulate it parametrically (B05).

Yet surprisingly few traditions explicitly agree on what constitutes the object that these systems manipulate.

This chapter does not seek a universal definition of knowledge. It examines instead the concepts that consistently recur across the literature: information, representation, claims, evidence, justification, accepted knowledge, and the knowledge systems that operate upon them.

The chapter advances one interpretive claim, developed cumulatively and marked throughout as provisional. Knowledge systems rarely manipulate knowledge directly. They operate upon representations, evidence relationships and processes of justification through which knowledge is established, maintained and revised — and upon the acceptance by which a community certifies a representation as knowledge at all.

This restates, at the level of foundational vocabulary, a line already load-bearing across the Landscape:

Every knowledge system governs representations, not knowledge itself.

Consistent with the Literature Landscape methodology, whether this interpretation adequately reconciles the preceding chapters is reserved for C01.

Orientation for the Standalone Reader

The preceding chapters examined knowledge through four complementary dimensions.

B02 investigated the engineering of knowledge systems and read that history as a progressive expansion of the object of engineering.

B03 examined knowledge as enduring collective capability across eight adjacent traditions.

B04 examined the governance of knowledge change and named six recurring Governance PrimitivesGovernance Primitive — one of the six operations by which warrant is conferred: evidence, authority, provenance, validation, versioning, reversibility (KF-1104). Vocabulary →.

B05 evaluated whether foundation models fundamentally alter those conclusions, and found that they relocate capabilities across the symbolic–parametric boundary rather than abolishing them.

This chapter steps back from those perspectives. Rather than examining a particular scholarly tradition, it investigates the foundational concepts that all of those traditions appear to share.

A note on placement. Within the agreed chapter order (B02 → B03 → B04 → B05 → B01 → C01) this chapter is written last among the evidence chapters and therefore assumes the reader has already met the traditions. It functions less as an introductory primer than as a conceptual consolidation: the point at which the vocabulary used loosely across four chapters is made precise, immediately before the Synthesis. A reader encountering B01 first will still find the concepts self-contained, but the cross-references reward prior reading.

1. Introduction

Knowledge is among the most frequently used — and least consistently defined — concepts in the scholarly literature.

Philosophers debate its justification. Information scientists distinguish it from information. Knowledge engineers represent it computationally. Organisations attempt to manage it. Artificial intelligence increasingly models it parametrically.

Each tradition adopts definitions appropriate to its own purposes. Each definition is locally coherent and globally incompatible with the others.

This chapter treats that incompatibility as data rather than as a defect to be corrected. Operational knowledge systems cannot wait for epistemology to converge; they are built and governed regardless. The interesting question is therefore not what knowledge ultimately is, but what these systems actually operate upon when they claim to handle knowledge.

The objective is accordingly modest and deliberately so. This chapter does not resolve philosophical disputes concerning the essence of knowledge. It investigates the concepts that recur across the knowledge sciences and examines how they relate to one another within knowledge systems.

2. Central Research Question

The chapter is organised around one guiding question.

What is the object manipulated by knowledge systems?

Supporting questions include: What distinguishes information from knowledge? What is a representation? What constitutes a knowledge claim? What is evidence? What is justification? When does information become accepted knowledge? What exactly do knowledge systems engineer, govern and evolve?

The question is posed operationally, not metaphysically. It asks what a working system holds, transforms and hands on — not what knowledge is in the last analysis.

3. Analytical Lens

Unlike previous chapters, which analysed scholarly traditions, this chapter analyses foundational concepts.

The Landscape’s recurring tradition-lens — Scale → Capability → Time (introduced in B03) — is designed to compare disciplines. It is the wrong instrument for comparing concepts, which have no scale of operation and no institutional time horizon of their own. This chapter therefore adopts a concept-oriented lens of six recurring analytical questions.

The two lenses are complementary rather than competing. The six-question lens characterises each concept; §6 then shows how the concepts, once characterised, populate the Capability and Time axes of the tradition-lens and map onto B04’s six Governance Primitives. B01 supplies the vocabulary; the axis-lens spends it.

        The KF-L001 Method
    ───────────────────────────
         Research Question
                ↓
              Corpus
                ↓
          Analytical Lens
                ↓
        Comparative Analysis
                ↓
           Cross-patterns
                ↓
     Candidate Integrative Insight

Figure B01·1 — the recurring KF-L001 review method, applied uniformly across every evidence chapter of the Landscape.

4. Corpus of Investigation

Unlike previous chapters, whose corpora consisted of intellectual traditions, this chapter examines the principal conceptual building blocks that recur throughout the knowledge sciences.

Each concept below is examined through the six-question lens of §3. The treatment is compact by design: the aim is a shared vocabulary precise enough to be reused, not a monograph on each term.

4.1 Knowledge

Central Question: What does the literature mean by “knowledge”? Representative literature: Plato; Gettier (1963); Polanyi (1966); Goldman (1979).

Definition. The classical account defines knowledge as justified true belief — a belief that is true and held for adequate reasons (Plato, Theaetetus; Meno, where true belief is “tethered” by an account, aitias logismos). Gettier (1963) demonstrated with brief counterexamples that justified true belief can still fail to be knowledge, when the justification is true only by accident. Six decades of proposed repairs (causal, reliabilist, no-false-lemmas, defeasibility) have refined but not closed the definition.

Purpose. The concept exists to mark a status stronger than mere opinion: a claim one is entitled to act upon and to transmit to others as settled.

Relationship. Knowledge sits atop the other concepts in this chapter. It presupposes a representation to be believed, evidence in its favour, and justification linking the two. Polanyi (1966) adds an orthogonal distinction: much knowledge is tacit — “we know more than we can tell” — and therefore resists representation altogether.

Limitations. No operational definition commands consensus. Worse for engineering, the two most-cited features of knowledge — truth and tacitness — are precisely the two a machine cannot directly inspect. A system cannot verify that a belief is true (only that it is justified and accepted), and it cannot store what is tacit (only what has been made explicit).

Role in Knowledge Systems. Because truth and tacitness are inaccessible, systems substitute a tractable operational knowledge objectOperational Knowledge Object — the unit of design: a versioned representation together with its attached evidence, justification and acceptance-state (KF-1101). The system governs the object, never "knowledge itself". Vocabulary →: they hold representations, track the evidence and justification attached to them, and record the community’s acceptance. “Knowledge,” in an operational system, is the name given to a representation that has cleared those three tests.

Implications. If knowledge itself is inaccessible to the system, then the object of engineering, management and governance cannot be knowledge as such. This is the chapter’s central move, established here and defended across §§4.2–4.8. (The tacit/explicit distinction is used here only to motivate the representational limit; its social and managerial development belongs to B03 and is not duplicated.)

4.2 Information

Central Question: How is information distinguished from knowledge? Representative literature: Shannon (1948); Buckland (1991); Floridi (2011); with Ackoff (1989) and Dretske (1981) in support.

Definition. There is no single definition, but three influential ones frame the field. Shannon (1948) defines information syntactically, as the reduction of uncertainty, and pointedly excludes meaning. Buckland (1991) distinguishes information-as-process, information-as-knowledge and information-as-thing — the last being the tangible object (a document, a record) that systems actually store. Floridi (2011) offers a semantic definition: information is well-formed, meaningful and (on the strong reading) truthful data.

Purpose. The concept isolates the transmissible, storable, measurable substrate beneath knowledge. Shannon’s version is what makes storage and communication engineerable at all.

Relationship. The folk model — the DIKW hierarchy (data → information → knowledge → wisdom; Ackoff, 1989) — treats information as knowledge’s raw material. That hierarchy is widely taught and widely criticised (Rowley, 2007; Frické, 2009) for implying a clean, one-directional refinement that the concepts do not support. Dretske (1981) supplies a cleaner bridge: knowledge is belief caused by the information that makes it true.

Limitations. Shannon’s measure ignores meaning; Floridi’s truth-condition is contested; the DIKW ladder mistakes a vocabulary for a mechanism. None of the three, alone, explains how information acquires the warrant that distinguishes it from knowledge.

Role in Knowledge Systems. Systems overwhelmingly operate on Buckland’s information-as-thing. What they physically hold are informational artefacts. The transition from such an artefact to “knowledge” is not a change of substance but the attachment of evidence, justification and acceptance — the work of §§4.5–4.7.

Implications. If the difference between information and knowledge is warrant rather than substance, then a knowledge system is an information system plus the machinery that governs warrant. This reframes the object of engineering as warranted information, not a separate substance called knowledge.

4.3 Representation

Central Question: How is knowledge represented? Representative literature: Davis, Shrobe & Szolovits (1993); Peirce; Newell & Simon (1976).

Definition. A representation is a surrogate — a stand-in that lets a system reason about something without operating on the thing itself. The canonical statement (Davis, Shrobe & Szolovits, 1993) analyses any knowledge representation through five roles simultaneously: a surrogate for the world; a set of ontological commitments about what exists; a fragmentary theory of intelligent reasoning; a medium of efficient computation; and a medium of human expression.

Purpose. Representation makes knowledge manipulable. Only once something is represented can it be stored, indexed, inferred over, transmitted or governed.

Relationship. Semiotics locates the general structure: Peirce’s triad of sign, object and interpretant insists that a sign is never its object and always requires interpretation. The Physical Symbol System Hypothesis (Newell & Simon, 1976) is the strong engineering wager that symbol manipulation suffices for intelligence. B05’s parametric representations sit at the far end of the same axis — distributed and sub-symbolic, but still surrogates.

Limitations. Every representation is partial and committed: its ontological commitments admit some distinctions and foreclose others (Davis et al., 1993). It cannot capture the tacit remainder (§4.1), and it can be faithful or unfaithful without announcing which.

Role in Knowledge Systems. The representation is the thing the system actually holds and changes. Engineering (B02) is the design of representations; governance (B04) is the disciplined change of representations over time.

Implications. Because a representation is a surrogate and never its object, no system operates on knowledge unmediated. This is the concept that most directly grounds the chapter’s guiding line: systems govern representations, not knowledge.

4.4 Claims

Central Question: What constitutes a knowledge claim? Representative literature: Toulmin (1958); Popper (1959); argumentation theory and knowledge representation.

Definition. A claim is a representation asserted as true — a proposition put forward for acceptance and therefore capable of being supported or defeated. In representational terms it is an assertion or axiom; in argumentation it is the conclusion a structure of reasons is built to bear.

Purpose. The claim is the unit that carries a truth-value and a burden of proof. Only something asserted can be evidenced, justified, accepted, contested or revised.

Relationship. Toulmin (1958) decomposes the surrounding structure — claim, data, warrant, backing, qualifier, rebuttal — showing that a claim never stands alone but is embedded in the reasons that license it. Popper (1959) adds the demarcation condition: a claim earns scientific standing only if it is falsifiable, i.e. exposes itself to defeating evidence.

Limitations. A claim’s truth is not settled by its being asserted, nor even by its being justified (Gettier again). The claim isolates the bearer of warrant without supplying the warrant.

Role in Knowledge Systems. The claim is the atomic governable unit. Provenance attaches to claims; validation targets claims; versioning tracks claims as they are asserted, qualified, retracted and superseded. B04’s Governance Primitives all take claims as their operands.

Implications. If the claim is the unit that is asserted and defended, then evidence and justification (next) are best understood not as free-standing objects but as relations to a claim.

4.5 Evidence

Central Question: What justifies accepting a claim? Representative literature: Sackett et al. (1996); Achinstein (2001); Wang & Strong (1996).

Definition. Evidence is that which raises or lowers the credibility of a claim. It is inherently relational: nothing is evidence simpliciter, only evidence for or against some claim. Achinstein (2001) distinguishes potential, veridical and subjective evidence; a Bayesian gloss treats evidence as whatever changes the probability of a hypothesis.

Purpose. Evidence converts an asserted claim into a credible one. It is the currency in which credibility is bought.

Relationship. Evidence-based practice (Sackett et al., 1996) institutionalises the concept as graded — some evidence counts for more — and thereby introduces quality as a first-class property. Information-quality research (Wang & Strong, 1996) supplies the dimensions (accuracy, completeness, timeliness, and others) along which evidential inputs are themselves assessed.

Limitations. Evidence underdetermines claims: the same evidence can support rival claims, and its weight depends on background assumptions that are rarely explicit. Evidence establishes credibility, not truth.

Role in Knowledge Systems. Evidence is stored and governed as links — the traceable relations between a claim and its supporting or defeating grounds. This is exactly B04’s Evidence/Justification primitive, and its integrity is what Provenance/Traceability and Validation/Quality exist to protect.

Implications. If evidence is a relation and not a possession, the system’s real asset is the graph of claims and their evidential links — not a heap of facts.

4.6 Justification

Central Question: Why should a claim be believed? Representative literature: Goldman (1979; 1999); with foundationalism/coherentism and internalism/externalism as framing debates.

Definition. Justification is the structure of reasons connecting evidence to a claim such that accepting the claim is warranted. Where evidence is the material, justification is the argument that assembles it. Reliabilism (Goldman, 1979) locates justification in the reliability of the process that produced the belief; internalist accounts locate it in reasons accessible to the believer; foundationalist and coherentist accounts disagree over whether justification terminates in basic beliefs or in mutual support.

Purpose. Justification is what makes belief rational and defensible rather than merely caused. It is the concept that answers challenges.

Relationship. Justification is the hinge of the classical definition of knowledge and the site of the Gettier problem — showing that even true, justified belief can fall short. Social epistemology (Goldman, 1999) extends justification beyond the individual to testimony, expertise and institutional processes, which is where operational systems in fact live.

Limitations. Justification guarantees neither truth nor acceptance. It can be locally impeccable and globally mistaken; and a well-justified claim may still be rejected by the community that matters.

Role in Knowledge Systems. This is the pivotal operational point of the chapter. A system cannot engineer truth — truth is not inspectable. It can engineer justification: it can record why a claim is held, by what process, on what evidence, and expose that structure to audit. Justification is the richest thing a knowledge system can actually govern.

Implications. If justification is what systems can govern and truth is not, then the honest description of a “knowledge” system is a justification-management system. The candidate concern of governed knowledge evolution — the controlled transition of a system from one justified state to another — takes justification, so defined, as its object. (The chapter states this dependency; it does not adjudicate any methodology’s contribution, which is reserved for C01.)

4.7 Accepted Knowledge

Central Question: When does a community recognise knowledge as accepted? Representative literature: Kuhn (1962); Wenger (1998); Lave & Wenger (1991); Argyris & Schön (1978).

Definition. Accepted knowledge is a claim that a community with the authority to do so has certified and adopted as settled for its purposes. Acceptance is a social status, not a property of the claim in isolation.

Purpose. Acceptance closes the loop between the individual’s justified belief and the collective’s usable stock. It is what turns “a well-justified claim” into “what we know.”

Relationship. Kuhn (1962) shows acceptance operating at the scale of paradigms and scientific communities; Communities of Practice (Lave & Wenger, 1991; Wenger, 1998) at the scale of situated groups; organisational learning (Argyris & Schön, 1978) as the single- and double-loop revision by which accepted knowledge is corrected. Acceptance is therefore the concept that most clearly requires B03’s social dimension and B04’s notion of authority.

Limitations. Communities can accept the false and reject the true; acceptance tracks warrant and power, not truth. It is also revisable — today’s accepted knowledge is tomorrow’s superseded claim.

Role in Knowledge Systems. Acceptance is operationalised as authorisation and release: the recorded act by which a claim moves to “approved,” “published” or “current,” under some authority. This is precisely B04’s Authority and Versioning/Release primitives.

Implications. If acceptance is authorised release, then the object of a knowledge system includes not just claims and their justification but their acceptance-state — who certified what, when, and under what authority.

4.8 Knowledge Systems

Central Question: What exactly do knowledge systems manipulate? Representative literature: Knowledge Engineering (B02); Knowledge Management (B03); AI (B05); Information Systems.

This concept is not a further building block but the convergence point the previous seven build toward; it is analysed here to state what the chapter has been assembling.

Definition. A knowledge system is any system that holds representations and governs their evidence, justification and acceptance so as to make warranted claims available, revisable and trustworthy over time.

Purpose. Such systems exist to let a community act on, transmit and revise what it takes itself to know, without each member re-deriving it.

Relationship. The traditions surveyed across the Landscape are, on this reading, specialisations by which part of the vocabulary they foreground: engineering foregrounds representation (B02); management foregrounds conversion and acceptance (B03); governance foregrounds the disciplined change of claims and their justification (B04); AI foregrounds a new representational substrate (B05).

Limitations. No tradition foregrounds all of the vocabulary at once. Each holds part of the object steady while working on another part — a division of labour that B04 named for change-governance specifically and that this chapter generalises to the whole vocabulary.

Role in Knowledge Systems. Trivially, this is the role. The substantive point is negative and is the chapter’s thesis: at no layer does the system reach past its representations to touch knowledge itself.

Implications. The seven preceding concepts jointly specify the object. A knowledge system manipulates representations of claims, the evidence and justification attached to them, and their acceptance-state under some authority. It does not manipulate knowledge. That is the finding carried to §8 and to C01.

5. Comparative Analysis

Each concept has been analysed through the six-question lens of §3. Read across, three patterns recur.

Conceptual dependency. The concepts form a dependency chain rather than a set of alternatives. Knowledge presupposes justification; justification assembles evidence; evidence attaches to claims; claims are asserted representations; representations stand in for information about reality. Remove any link and the ones above it lose their footing.

The recurring retreat from truth. At every concept where truth might have been the operative property — knowledge (4.1), information (4.2, Floridi’s truth-condition), claims (4.4), justification (4.6), acceptance (4.7) — the operationalisable property turns out to be something adjacent that a system can actually inspect: warrant, credibility, justification-structure, authorised acceptance. Truth is the property the literature reaches for and the property systems cannot hold.

Disciplinary foregrounding. Traditions differ less in their vocabulary than in which term they treat as primary and which they take for granted (§4.8).

The comparative concept map summarises the relationships and, for each concept, the Governance Primitive (B04) and the operational knowledge object through which systems actually handle it.

The right-hand columns are the chapter’s contribution to the Landscape vocabulary: they show every foundational concept resolving, under engineering pressure, into something a system can store and govern — and none of them resolving into knowledge.

6. Cross-Concept Patterns

The chapter investigates whether a common conceptual progression emerges across otherwise diverse traditions.

A provisional operational sequence is:

Reality
   ↓ (observation)
Information
   ↓ (representation)
Representation
   ↓ (assertion)
Claim
   ↓ (support / defeat)
Evidence
   ↓ (reasoning)
Justification
   ↓ (authorised acceptance)
Accepted Knowledge
   ↓ (operationalisation)
Knowledge System

Figure B01·2 — the operational sequence: a loop, not a ladder. The stages a claim passes through inside a working system, with feedback edges from acceptance back to representation.

Three qualifications are essential, and each keeps the sequence within the Landscape’s restrained posture.

It is operational, not metaphysical. The sequence is not a theory of how knowledge really arises. It is a description of the stages a claim passes through inside working systems — evaluated for descriptive fit, not asserted as truth.

It is a loop, not a ladder. Justification and acceptance feed back: a defeated claim revises the representation; a superseded acceptance-state triggers re-justification. Reading the sequence as one-directional would repeat the DIKW error criticised in §4.2. The concern with governed change lives precisely in the return edges, where an accepted state is transitioned to a new justified state. What persists through every iteration of the loop is not knowledge itself, but the governed transition from one accepted representation to another.

It maps onto the Landscape lenses. The lower stages (evidence → justification → acceptance) populate the Capability and Time axes of B03’s Scale→Capability→Time lens and correspond one-to-one with B04’s six Governance Primitives. The sequence is thus not a new framework but the spine on which the existing lenses hang.

One further pattern, connecting to B05. Foundation models enter this sequence at representation: they supply a new, parametric surrogate. They do not add or remove a stage. The claims, evidence, justification and acceptance downstream of the representation remain obligatory. This is the vocabulary-level statement of B05’s finding —

The substrate changes; the epistemic obligations do not.

6.1 Limitations of This Review

This chapter does not attempt to resolve longstanding philosophical debates concerning the nature of knowledge.

Its conclusions are bounded by:

• a selective corpus, chosen for recurrence across the knowledge sciences rather than for completeness within philosophy;
• an emphasis on operational rather than metaphysical questions, which deliberately brackets truth;
• an interdisciplinary scope that trades depth in any single tradition for comparability across several;
• an interpretive synthesis whose central claim is offered as a reading, not a proof.

Its purpose is to establish a shared conceptual vocabulary rather than a universal epistemology.

7. Existing Contributions

Across the literature, several concepts may be regarded as mature foundations of knowledge systems — settled enough to be relied upon before any synthesis is attempted. These include:

• the distinction between information and knowledge, framed as a difference of warrant rather than substance (Shannon, 1948; Buckland, 1991; Floridi, 2011);
• symbolic representation and its five roles (Davis, Shrobe & Szolovits, 1993);
• the tacit/explicit distinction marking the limit of representation (Polanyi, 1966);
• evidence as a graded, relational property (Sackett et al., 1996; Achinstein, 2001);
• justification as the governable structure of reasons (Goldman, 1979);
• acceptance as a social, authorised status (Kuhn, 1962; Wenger, 1998);
• the structure of a claim and its defences (Toulmin, 1958; Popper, 1959).

This inventory establishes the conceptual foundations already available. It is genuinely mature: none of it is any methodology’s to claim, and the Synthesis inherits it as given.

8. Candidate Integrative Insight

Only after examining the literature does the chapter advance its candidate observation. It is offered as an interpretation of the assembled concepts, not as a demonstrated result, and its adjudication is reserved for C01.

Proposition B01 · The Object of Knowledge Systems

Knowledge systems do not manipulate knowledge directly.

They manipulate representations of claims, the evidence and justification attached to them, and their acceptance-state under some authority — the machinery through which knowledge is established, maintained and revised.

The insight is negative in an important sense. It does not tell us what knowledge is; it tells us what the object of engineering, management and governance is not. Every layer surveyed in the Landscape — symbolic and parametric, individual and social, static and evolving — operates on the operational knowledge object, never on knowledge unmediated.

To fix the vocabulary in a single figure, the object resolves through the following anchor sequence, which C01 adopts as the spine of the Synthesis:

Reality
   ↓
Conceptual Object            (what the object is, in the abstract)
   ↓
Operational Knowledge Object (the concrete artefact a system holds)
   ↓
Representations
   ↓
Claims
   ↓
Evidence
   ↓
Accepted Knowledge

Figure B01·3 — the anchor sequence, adopted by C01 as the spine of the Synthesis.

The Conceptual Object is the abstract object this chapter defines; the Operational Knowledge Object is the concrete artefact a knowledge system actually manipulates — the versioned representation together with its attached evidence, justification and acceptance-state. The distinction is dormant here and becomes load-bearing in C01; it also fixes the term that replaces the looser “proxy” used earlier in the drafting.

If this reading holds, it dissolves a recurring confusion in the field. Debates about whether a system “really contains knowledge” are, on this account, mis-posed: no system does, and none needs to. What a system can contain, warrant, govern and revise is the vocabulary of §4. Whether that reframing does real work — or merely relabels a familiar intuition — is exactly the kind of question the Synthesis exists to test.

9. Burden of Proof

Consistent with the Literature Landscape methodology, this chapter defines evidence, not theory. It establishes what any methodology claiming to engineer knowledge systems would need to explain, structured around the three standard questions.

Established (what is mature). The conceptual foundations of §7 are settled and inherited as given: the warrant-based distinction between information and knowledge; representation and its five roles; the tacit/explicit limit; evidence as graded and relational; justification as a governable reason-structure; acceptance as an authorised social status; and the structure of a claim and its defences.

Unresolved (what remains open). No tradition foregrounds the whole vocabulary at once, nor operationalises the concepts together rather than one at a time. A methodology claiming to engineer knowledge systems would need to demonstrate:

1. what it treats as the operational knowledge object, given that knowledge itself is inaccessible to the system;
2. how claims are related to evidence, and how that relation is stored and traced;
3. how justification is represented, recorded and audited;
4. how acceptance is authorised, released and revised;
5. how representations evolve without loss of warrant;
6. how symbolic and parametric representations interoperate within one governed object (per B05);
7. how these concepts are operationalised together rather than one at a time (per §4.8’s division of labour);
8. how tacit knowledge is accommodated despite being only partially representable (per Polanyi, §4.1).

Implication (what the synthesis must explain). Whether existing traditions already discharge these requirements — individually or collectively — is not judged here. The requirements are stated as the standard against which the Synthesis will assess any candidate methodology.

10. Relationship to Previous and Subsequent Chapters

B02 examined knowledge from an engineering perspective; B01 specifies the conceptual object upon which engineering, governance and computation operate.

B03 examined knowledge as collective capability; B01 supplies the acceptance and justification vocabulary its social account presupposes.

B04 examined the governance of knowledge change; B01 shows that its six primitives are the operational counterparts of this chapter’s concepts.

B05 examined whether foundation models alter previous assumptions; B01 locates their contribution at a single stage (representation) and confirms the obligations downstream are unchanged.

B01 therefore establishes the conceptual vocabulary that underpins all four perspectives. Together, the five evidence chapters provide the material for the Literature Synthesis (C01), where the overall gap — deferred throughout the Landscape — is finally stated and tested.

11. Guiding Principle

The organising principle of this chapter is intentionally simple.

Knowledge systems rarely manipulate knowledge itself. They manipulate representations, claims, evidence, justification and acceptance — through which knowledge is constructed, communicated, governed and revised.

Every knowledge system governs representations, not knowledge itself.

Understanding these conceptual building blocks provides the foundation for integrating the engineering, social, governance and computational perspectives developed throughout the Literature Landscape — and for the Synthesis that follows. The enduring challenge of knowledge systems is therefore not the storage of knowledge, but the disciplined governance of representations through which knowledge is recognised.

With the object now clarified, the Landscape can synthesise the engineering, capability, governance and computational traditions into a single conceptual framework. That synthesis is C01.

References

Author–year only; DOI pass deferred to v1.0, consistent with B05.

Achinstein, P. (2001). The Book of Evidence. Oxford University Press.

Ackoff, R. L. (1989). From data to wisdom. Journal of Applied Systems Analysis, 16.

Argyris, C., & Schön, D. A. (1978). Organizational Learning: A Theory of Action Perspective. Addison-Wesley.

Buckland, M. K. (1991). Information as thing. Journal of the American Society for Information Science, 42(5).

Davis, R., Shrobe, H., & Szolovits, P. (1993). What is a knowledge representation? AI Magazine, 14(1).

Dretske, F. (1981). Knowledge and the Flow of Information. MIT Press.

Floridi, L. (2011). The Philosophy of Information. Oxford University Press.

Frické, M. (2009). The knowledge pyramid: a critique of the DIKW hierarchy. Journal of Information Science, 35(2).

Gettier, E. L. (1963). Is justified true belief knowledge? Analysis, 23(6).

Goldman, A. I. (1979). What is justified belief? In Justification and Knowledge (ed. Pappas). Reidel.

Goldman, A. I. (1999). Knowledge in a Social World. Oxford University Press.

Kuhn, T. S. (1962). The Structure of Scientific Revolutions. University of Chicago Press.

Lave, J., & Wenger, E. (1991). Situated Learning: Legitimate Peripheral Participation. Cambridge University Press.

Newell, A., & Simon, H. A. (1976). Computer science as empirical inquiry: symbols and search. Communications of the ACM, 19(3).

Plato. Theaetetus; Meno. (Standard editions.)

Polanyi, M. (1966). The Tacit Dimension. University of Chicago Press.

Popper, K. R. (1959). The Logic of Scientific Discovery. Hutchinson.

Rowley, J. (2007). The wisdom hierarchy: representations of the DIKW hierarchy. Journal of Information Science, 33(2).

Sackett, D. L., Rosenberg, W. M. C., Gray, J. A. M., Haynes, R. B., & Richardson, W. S. (1996). Evidence based medicine: what it is and what it isn’t. BMJ, 312.

Shannon, C. E. (1948). A mathematical theory of communication. Bell System Technical Journal, 27.

Toulmin, S. E. (1958). The Uses of Argument. Cambridge University Press.

Wang, R. Y., & Strong, D. M. (1996). Beyond accuracy: what data quality means to data consumers. Journal of Management Information Systems, 12(4).

Wenger, E. (1998). Communities of Practice: Learning, Meaning, and Identity. Cambridge University Press.

Appendix — Editorial Notes (flagged decisions, remove at v1.0)

The following are decisions taken in expanding v0.1 → v0.2 that are reversible and worth explicit sign-off.

1. Two lenses, kept both. B01’s concept-oriented six-question lens is retained as primary, with the Scale→Capability→Time axis-lens used only as the bridge in §3/§6, rather than recasting B01 in the axis-lens. Reasoning: concepts have no scale/time of their own, so the axis-lens fits awkwardly. Reversible fork: if strict Landscape-wide uniformity is wanted, B01 could be rebuilt on the axis-lens, at some cost to fit.
2. Placement assumed last-among-evidence. Per the agreed order (…→B05→B01→C01), B01 is written as a consolidation that assumes prior reading, and says so in the Orientation. Tension flagged: this trades away some “readable-first primer” quality. If B01 ever opens the Landscape, the cross-references and the “written last” framing need softening.
3. Truth is deliberately bracketed. The chapter’s spine is the claim that systems operationalise justification + acceptance and never truth. This is a substantive stance, not a neutral summary. The bracketing is judged the correct, falsifiable move and consistent with the posture of governed knowledge evolution, but it is the single most contestable choice in the chapter.
4. Sequence rendered as a loop, not a ladder (§6). Explicit feedback edges are added and tied to the governed-change concern, partly to pre-empt the DIKW critique the chapter itself levels.
5. “Knowledge Systems” (4.8) treated as convergence point, not a 9th building block. Analysed with the lens but framed as where the other seven concepts resolve.
6. Polanyi confined to the representational limit. Tacit/explicit is used here only to establish “knowledge exceeds representation,” with the social/KM development left to B03 to avoid double-coverage.
7. New portable line proposed. Alongside B03’s representations-not-knowledge line and B05’s substrate/obligations line, §5’s right-hand columns and §8 introduce a candidate third: systems hold operational knowledge objects, never truth — promoted in C01 to the Inspectable Objects Principle.
8. Citations. Author–year only; DOI pass deferred to v1.0 per the B05 convention. Ackoff (1989) and Dretske (1981) were added beyond the draft’s representative lists (DIKW critique and the information→knowledge bridge respectively).