Chapter 3.4 follows chapter 3.3, The project manifest, and precedes chapter 3.5, Construction and freezing of the builds, within part 3, the project library.
The variant set contains documented trees, a stripped twin, a frozen unguided control, and retained predecessors of that control. A rung, a documented tree at a specified documentation dose, adds a defined collection of documentation to the common runnable code. A strip, a removal of documentation artifacts, produces the stripped twin. An artifact, a documentation file or embedded documentation item, is recorded by an artifact manifest.
source: operations/site-ia/A6-page-briefs.md line 510
3.4.1 Documented build of the experimental codebases
H-LAP-L5P, the top documented level-five position for Literate and Anchored Programming (LAP), is the highest documented ladder profile and the build with the fullest documentation treatment, meaning the top documented position in the documentation ladder and the heaviest documented tree. Its readme file records the build, and its deployment manifest declares the deployed tree. Its artifact manifest records the documentation files, inline markers, content stubs, strip order, trace anchor sites, probe comment sites, and payload metrics. The tree contains the full documentation layer, including files, inline markers, content stubs, trace anchors, probe comments, and measured payload data.
source: operations/site-ia/A6-page-briefs.md line 514
The heaviest rung contains fifteen documentation files.
source: operations/site-ia/A6-page-briefs.md line 514
It contains two inline markers.
source: operations/site-ia/A6-page-briefs.md line 514
It contains two content-stub files.
source: operations/site-ia/A6-page-briefs.md line 514
The deployment manifest and artifact manifest together declare the frozen tree and its documentation payload. The tree’s descriptive file supplies the tree-specific description.
3.4.2 Stripped twin of the experimental codebases
The stripped twin is the documentation-free counterpart of the documented build. Its deployment manifest declares the strip operation and the resulting tree. The strip removes documentation-only files, inline documentation, and content stubs while preserving the runnable code. The manifest records the strip order, trace anchor sites, probe comment sites, and payload metrics used to describe that removal.
3.4.3 Intermediate rungs of the experimental codebases
Every documented folder in the ladder range adds its own documentation dose to the common code. Each tree has a readme file, a deployment manifest, and an artifact manifest. Its deployment manifest declares the tree and its build placement. Its artifact manifest declares the documentation files, inline markers, content stubs, strip order, trace anchor sites, probe comment sites, and payload metrics.
source: operations/site-ia/A6-page-briefs.md line 514
The corresponding figures for every rung come from that rung’s own artifact manifest and its documentation inventory. The strip order in each manifest identifies the documentation removed before that rung was formed. The deployment manifest and readme file identify the tree independently of the artifact inventory.
3.4.4 Unguided control of the experimental codebases
The frozen unguided control is a tree produced outside the documented build sequence. Its readme file describes the tree. Its artifact manifest records the documentation inventory, and its variant manifest records the variant identity. Its deployment manifest declares the frozen control deployment. The control is retained as a separate build with its own code history and manifest record.
3.4.5 Superseded control trees of the experimental codebases
The repository retains three superseded control folders. These folders preserve earlier control states for audit, provenance, and comparison. They remain separate from the frozen unguided control so that later repairs do not overwrite the evidence of the earlier states. They are retained for traceability of control construction and for review of the changes that led to the frozen control.
source: operations/site-ia/A6-page-briefs.md line 508
3.4.6 Migrated material of the experimental codebases
Material moved from the earlier build page concerns the tree derivation and the application of each profile on the highest documented profile. The derivation of the profile trees belongs with the rung descriptions here. Material moved from the corpus page supplies the derivation figure for the corpus and its arms.
source: operations/site-ia/A6-page-briefs.md line 516
3.4.7 Artifact derivation of the experimental codebases
The artifact manifest comparison presents the documentation inventories and declared payload fields for the documented trees, the stripped twin, and the control trees. A corpus derivation figure presents the relationships among the variant trees and the derivation of the arms. The artifact comparison is generated from the artifact manifests. The corpus derivation figure anchors the corpus derivation and the arm derivation used by R1.
source: operations/site-ia/A6-page-briefs.md line 512