2.9 Burden
2.9.1 Burden is a governed Construct that identifies the responsibility generated when a scholarly object claims, performs, distinguishes, includes, excludes, transforms, or enables something consequential.
2.9.2 Burden is not a synonym for importance, difficulty, complexity, workload, relevance, or good practice.
2.9.3 It names what an object must answer for because of what that object asks others to accept or makes possible in scholarly use.
2.9.4 The direct argumentative genealogy of burden begins with burden of proof.
2.9.5 Walton (2014) examines how burdens and presumptions allocate responsibility within argumentative dialogue: who must provide support, what degree of support is required, and how that responsibility may shift as arguments and critical Questions develop.
2.9.6 The importance of this genealogy lies in allocation. Not every proposition enters an Argument with the same presumptive status, and not every participant bears the same responsibility at every moment.
2.9.7 A claim may generate a responsibility to provide reasons. A challenge may generate a responsibility to identify the point at issue, while an established presumption may remain operative until adequate counterargument is supplied.
2.9.8 Toulmin (1958/2003) provides a complementary foundation by examining the practical structure through which claims are supported.
2.9.9 Grounds, warrants, backing, qualification, and rebuttal make visible that a claim depends not only on the presence of information, but also on the relation through which that information is made relevant.
2.9.10 Walton and Toulmin do not provide the complete burden architecture used by Scholarly Research.
2.9.11 Walton supports the allocation and standards of argumentative responsibility. Toulmin supports analysis of the structure, warrant, qualification, rebuttal, and field-sensitive adequacy of support.
2.9.12 Scholarly Research extends this principle of answerability to several kinds of scholarly object while remaining responsible for that authorial extension.
2.9.13 The generative formulation of burden is:
Because this object claims, performs, includes, excludes, changes, or enables X, it must answer for Y.
2.9.14 A Construct creates a definitional burden because users must be able to identify what it means and distinguish it from neighboring objects.
2.9.15 It creates a boundary burden because its application includes some cases and excludes others.
2.9.16 It creates a genealogical burden when inherited elements, integrations, translations, and authorial developments must remain distinguishable.
2.9.17 A source creates a bibliographic burden when it is asked to support a claim, definition, genealogy, Method, standard, or normative requirement.
2.9.18 That burden includes accurate source identity, an appropriate Manifestation Base, APA7 citation and reference control through GBB7, external identifiers where available, relevant localizers, authoritative information routes, and an explicit statement of what the source supports.
2.9.19 A Method creates a methodological burden because its operations must be adequate to the Object, Question, Constructs, Field/Corpus, intended Evidence, and proposed inference.
2.9.20 Naming a recognized Method does not carry this burden unless the actual operations and their fit are explained.
2.9.21 Data create provenance burdens because another person must be able to understand how material became available, selected, recorded, transformed, classified, and preserved.
2.9.22 Evidence creates an evidentiary burden because the relation between material and claim must remain visible, including the warrant through which Data acquire evidentiary force.
2.9.23 An Argument creates burdens of support, relevance, qualification, counterargument, and limitation because it asks others to accept a claim through an identifiable structure of reasons.
2.9.24 A Technical-Technological Product / Artifact creates design, evaluation, and consequence burdens because it makes a designed intervention, representation, process, or infrastructure available for use.
2.9.25 Functionality alone does not establish the adequacy of an Artifact. It must answer for what it is intended to do, for whom, under which conditions, with which limitations, and with which possible effects.
2.9.26 A standard creates a normative burden because it prescribes or constrains action. Its scope, authority, applicability, implementation conditions, and limits must therefore remain explicit.
2.9.27 A version creates a continuity burden because change may affect previous citations, PSB locators, definitions, GBB7 Records, Manifestations, Source packages, focused pages, and downstream derivatives.
2.9.28 A new version must make material change interpretable rather than merely replacing the earlier state.
2.9.29 Burdens may be principal or secondary, stable or shifting, local or distributed. Their configuration depends on what the object performs and on the relations through which it enters scholarly use.
2.9.30 Burden must therefore be specified rather than invoked generically. Saying that an object “has a burden” is insufficient unless the responsibility, bearer, supporting conditions, and possible failure are identifiable.
2.9.31 Burdens also interact. A bibliographic failure may weaken an Argument; an unstable Construct may distort a Method; an inaccessible Manifestation may compromise verification; and an ungoverned version may make correction impossible to propagate.
2.9.32 The recognition of burden does not require maximal apparatus for every object. Governance must remain proportional to consequence, complexity, recurrence, uncertainty, and dependence.
2.9.33 Proportionality does not mean convenience. A central or repeatedly reused object may require extensive governance even when its surface form appears simple.
2.9.34 Burden is therefore the recurring operator that transforms scholarly importance into answerable responsibility.
2.9.35 It asks not only whether an object is valuable, persuasive, elegant, innovative, or useful, but what must remain visible, supported, preserved, and criticizable because that object has entered the architecture of knowledge.
