Chapter 3.7 follows chapter 3.6, The control build and its history, and precedes chapter 3.8, The archived projects, within part 3, the project library.
3.7.1 Product identity of the experimental codebases
The imported product is Project F, the external-validity project for the campaign. It is a brownfield, a pre-existing software project maintained by humans. Paperless-ngx supplies an additional instrument alongside the control build. Its source tree and its experimental variants are held in the Project F library.
3.7.2 Candidate selection of the experimental codebases
The candidate review records paperless-ngx as the selected open-source product. The selection record places it in the Project F repository. The candidate library and the import notes preserve the comparison and the decision record.
The operator selected paperless-ngx on 2026-07-19. source: source_manifest.json key selected_at
The product was imported on 2026-07-19. source: source_manifest.json key imported_at
3.7.3 Migrated selection record of the experimental codebases
The selection material moved from the earlier project page is retained here. A remaining paragraph stays with the earlier project page.
3.7.4 Pinned source of the experimental codebases
The imported source is fixed at commit d34ef75786fe806be9d521e9071ef92200fb3494. source: source_manifest.json key commit_or_tag
The licence is the GNU General Public License version 3.0 (GPL-3.0). source: source_manifest.json key license
The upstream snapshot and its associated records preserve this source choice.
3.7.5 Source tree of the experimental codebases
The source screen records 1,440 paths, including 313 Python files and 414 TypeScript files. source: source_manifest.json key source_tree_screen
The tree contains application code and supporting material. The source screen is the basis for the file-count check.
3.7.6 Experimental variants of the experimental codebases
F-NON, the untouched product variant from the frozen build tree and without the Literate/Anchored Programming (LAP) documentation treatment, is the untouched product. F-LAP, the product variant with that treatment, is the treated product. The import produces both variants, which are stored under the Project F variant records.
Figure D-P6-1. The selection and pinning of the imported codebase
%% figure D-P6-1 flowchart LR subgraph g1[" "] n1_1["Open Source Candidates/candidate_library_2026-07-11.md"] --> n1_2["Project F - Open Source/selection/"] n1_2 --> n1_3["source_manifest.json"] n1_3 --> n1_4["dependency_manifest.json"] end subgraph g2[" "] n2["upstream_snapshot/"] end n1_4 --> n2
source: operations/site-ia/A3-diagram-specification.md
source: A6-page-briefs.md P6 Diagrams
The imported product and its experimental variants.
3.7.7 Import record of the experimental codebases
The import status is imported_instrumentation_in_progress. source: source_manifest.json key status
The task library contains eighteen draft task folders. source: 4. Task Library/Project F/ folder listing
The folder range is F-M001 to F-M018. source: 4. Task Library/Project F/ folder listing
The task index records ten tasks as draft and eight tasks as superseded. source: task_index.csv
The import remains an instrumentation record while the task folders and both variants are prepared.