Deep Battle Cards A–D
A — Content vs Document vs Record
Definition: Content = information; Document = object/container communicating it; Record = information/document retained as evidence under stronger lifecycle controls.
Purpose: determine the management obligation that applies.
Inputs: purpose, approval/evidence role, record criteria and lifecycle obligations.
Outputs: ordinary content, controlled document, or governed record/copy of record.
Use when: - “what does it say?” → Content; - file/page/object → Document; - proof of action/decision/approval → Record.
Common confusion: file format does not determine record status.
Scenario: draft procedure PDF = Document; formally approved version proving instructions in force = Record.
Exam trap: not every document deserves records-level controls.
Memory hook: Meaning → Bucket → Evidence.
Source: pp. 290–301.
B — Content Model vs Information Architecture
Content Model: types/components/attributes/relationships for structured reuse.
IA: organizes the body of information for navigation, labeling, browsing, search and retrieval.
Purpose: separate “how content units are structured” from “how users find and understand the information space.”
Use when: - same content reused across web/mobile/print → Content Model; - good content exists but users cannot find it → IA.
Trap: better navigation does not make unstructured blobs reusable across channels.
Memory hook: Model the pieces; architect the place.
Source: pp. 291–293 and IA sections.
C — Synonym Ring vs Authority List vs Taxonomy vs Thesaurus vs Ontology
Synonym Ring: equivalents treated equally.
Authority List: preferred term + variants.
Taxonomy: classification/hierarchy/facets.
Thesaurus: equivalent + hierarchical + associative relations.
Ontology: classes/concepts, instances, attributes, relations/events.
Deciding question: what relationship must the structure express?
Use: equals → Synonym; approved label → Authority; browse/classify → Taxonomy; broader/narrower/related → Thesaurus; formal semantic model → Ontology.
Trap: “more complex” is not a deciding clue.
Memory hook: Equal / Preferred / Classify / Relate / Model meaning.
Source: pp. 293–295.
D — Formal vs Revision vs Custody Control
Formal: formal change initiation, impact evaluation, authorized decision, status/validation.
Revision: version/change tracking and stakeholder notification.
Custody: safe storage/retrieval.
Purpose: match control strength to risk/evidentiary need.
Use: consequential regulated procedure → Formal; ordinary controlled policy history → Revision; low-risk reference archive → Custody.
Trap: versioning alone is not Formal Control.
Memory hook: Store → Track → Govern change.
Source: pp. 295–301.