Chapter 6.4 follows chapter 6.3, The batch ledger, and precedes chapter 6.5, The detailed design of the harness, within part 6, the reference part.
The experiment record consists of plan documents, appendices, trackers, run-set folders, metrics tables and reports. The plan readme file (README), the experiment readme file, the reproducibility record, the North Star, the style contract and the site maintenance record are the owning records.
6.4.1 Record hierarchy of the campaign record
The plan folder contains four tiers. The first tier, a level in the record hierarchy, contains the six plan documents. The second tier contains appendices A to P. The third tier contains the trackers that capture decisions and task status. The fourth tier contains the working folder, including run-set folders and raw data.
source: 0. Plan/README.md lines 41 to 73 and the folder listing
6.4.2 Precedence rule of the campaign record
Order of precedence, the rule for choosing a record when records disagree, gives priority to a normative appendix, an appendix that fixes a rule or definition. A narrative describes the experiment in prose. A tier, a level in the record hierarchy, places each kind of material in relation to the others. The normative appendix takes precedence over the narrative, and the narrative takes precedence over the working folder.
The working folder contains the Decision Sheet, the record of operational choices, and the task tracker, the record of task status. Run-set folders contain the raw data. A normative number therefore follows the applicable appendix, while a narrative account follows the applicable plan document when no appendix governs the matter.
The site maintenance record states the same rule for the experiment record and raw data. The North Star and style contract provide the current references for site structure and content rules. The absent SITE_SPEC.md references are rewritten to those records.
6.4.3 Record map of the campaign record
The plan documents state the design and narrative account. The appendices establish rules, definitions and procedures. The Decision Sheet and task tracker preserve operational choices and task status. Run-set folders preserve raw data. Metrics tables and reports present calculated results and interpretations, subject to the records that govern their inputs.
The precedence arrow runs from the normative appendix through the narrative and toward the working folder. When a narrative and a working record disagree, the narrative governs the account and the working record remains the source for raw data. When a normative appendix and a narrative disagree, the normative appendix governs.
Figure D-X4-1. The primary records of the campaign and the order of precedence between them
%% figure D-X4-1 flowchart TB subgraph g1[" "] n1_1["0. Plan/README.md"] --> n1_2["0. The Website/SITE_MAINTENANCE.md"] end
source: operations/site-ia/A3-diagram-specification.md
source: 0. Plan/README.md lines 41 to 73 and the folder listing
Record tiers and the precedence arrow.
6.4.4 Source alignment of the campaign record
The one-paragraph facts assign plan documents to the experiment narrative, appendices to normative rules, trackers to operator decisions and run-set folders to raw data. The same assignments govern the record map. The Decision Sheet and task tracker are the working records named by that map.
The retired subsection and the conflict resolution text carry the same precedence rule into this entry. The redirect list points former headings and unresolved paths to their replacement records. SITE_SPEC.md has never existed in this repository or in the portal history, so its references use the North Star and style contract instead.
source: operations/site-ia/A6-page-briefs.md, section ”# X4.”