Doctrine Conventions
Rules for doctrine/. This tree holds chapter-by-chapter digests of
open, publicly released military publications, produced through the
pipeline in NOTEBOOKLM-PROMPT.md at the repo root.
Layout
- One folder per publication, named by short form:
ATP 2-01.3/. - Pub MOC inside it, same name:
ATP 2-01.3/ATP 2-01.3.md. It states full title, edition and date, scope, and a chapter table with digest status. - One note per chapter:
Ch 3 - Planning.md. Title Case, hyphens only.
Frontmatter (required on every note)
---
title: "<Pub short form> Ch <N> - <Chapter Title>"
aliases: []
tags: [doctrine, <pub-slug>, <topic tags>]
date: YYYY-MM-DD
section: "doctrine"
status: draft | stable
source: "<Full designator and title> (<edition/date>), Chapter <N>"
---
status: draft means pasted from the pipeline, not yet reviewed against
the pub. status: stable means a human checked it against the chapter.
Hard rules
- Digest, never transcribe. Paraphrase throughout; direct quotes 25 words or fewer with a paragraph reference. Raw manual text and PDF page dumps never enter this repo.
- Only publicly released publications. The source line names the exact edition so a reader can pull the original.
- Cite paragraphs as plain text: (para 3-12). No footnote markers or citation chips; they do not survive paste and rot into noise.
- Every figure in the chapter appears reinterpreted as a markdown table, a mermaid fence, or an ASCII fence. “See figure” is a defect.
- No em dashes anywhere (check-enforced repo-wide). No emojis.
- No lesson scaffolding: no learning objectives, activities, rubrics, or instructor notes. This is a reference shelf, not a course.
Relationship to tactics/
A tactics concept note is the teaching layer; a doctrine chapter digest is the depth layer. When both exist, the concept note links to the chapter digest in its Related Concepts, and the digest wikilinks the concept at first mention. Field cards in tactics/10 Field Procedures are cut from stable notes in either tree.