@airmark/quiver 0.32.2 → 0.34.0

package/README.md

@@ -7,14 +7,17 @@ and aligned to the current Quillmark spec.
 
 ## Contents
 
-| Quill        | Version | Description                                                                       |
-|--------------|---------|-----------------------------------------------------------------------------------|
-| `usaf_memo`  | 0.3.0   | USAF / DAF Official Memorandum (AFH 33-337)                                       |
-| `usaf_memo`  | 0.2.0   | Previous release, retained so documents pinned to `@0.2` keep resolving           |
-| `af4141`     | 0.1.0   | AF Form 4141 — Individual's Record of Duties and Experience (Ground Environment)  |
-| `daf1206`    | 0.1.0   | DAF Form 1206 — Nomination for Award                                              |
-| `daf4392`    | 0.1.0   | DAF Form 4392 — Pre-Departure Safety Briefing (Page 2)                            |
-| `afmc_moa`   | 0.0.1   | DoD Memorandum of Agreement (DoDI 4000.19)                                        |
+| Quill                | Version | Description                                                                      |
+|----------------------|---------|----------------------------------------------------------------------------------|
+| `usaf_memo`          | 0.3.0   | USAF / DAF Official Memorandum (AFH 33-337)                                      |
+| `usaf_memo`          | 0.2.0   | Previous release, retained so documents pinned to `@0.2` keep resolving          |
+| `usaf_letter`        | 0.1.0   | USAF / DAF Personal Letter (AFH 33-337)                                          |
+| `af4141`             | 0.1.0   | AF Form 4141 — Individual's Record of Duties and Experience (Ground Environment) |
+| `daf1206`            | 0.1.0   | DAF Form 1206 — Nomination for Award                                             |
+| `daf4392`            | 0.1.0   | DAF Form 4392 — Pre-Departure Safety Briefing (Page 2)                           |
+| `afmc_moa`           | 0.0.1   | DoD Memorandum of Agreement (DoDI 4000.19)                                       |
+| `classic_resume`     | 0.0.1   | Classic single-page resume                                                       |
+| `cyber_ribbon_chart` | 0.0.1   | 17X Cyber Operations Officer ribbon chart and career vector planner              |
 
 ## Install
 
@@ -22,8 +25,8 @@ and aligned to the current Quillmark spec.
 npm install @airmark/quiver @quillmark/quiver @quillmark/wasm
 ```
 
-This package ships only the source-quiver assets (`Quiver.yaml` + `quills/`) and
-exposes no JavaScript API. Loading is `@quillmark/quiver`'s, rendering is
+This package ships the source-quiver assets (`Quiver.yaml` + `quills/`) and the
+official [templates](#templates), and exposes no JavaScript API. Loading is `@quillmark/quiver`'s, rendering is
 `@quillmark/wasm`'s.
 
 ## Usage
@@ -91,11 +94,32 @@ quills/
   <name>/
     <x.y.z>/
       Quill.yaml
+      example.md
       plate.typ
       assets/
       packages/
+templates/
+  templates.json
+  <file>.md
 ```
 
+## Templates
+
+`templates/` holds the official starter documents Tongue to Quill offers in its
+template library. They sit beside the quiver rather than inside it: the quiver
+loaders never read them, and a consumer reaches them as files, through
+`@airmark/quiver/templates/templates.json` and the Markdown it names. Each entry
+is `{ id, name, description, file, tags }`, and every listed template is live.
+
+An entry's `id` is permanent. Tongue to Quill derives the template's row id and
+its shareable short code from it, so renaming one retires the old template (its
+stars and its short code with it) and publishes a new one. Removing an entry
+retires it the same way.
+
+`npm test` renders every template against this quiver after `quillkit test`, and
+a warning fails it as an error does, so a quill change that breaks a template
+fails here rather than on the app's build.
+
 ## Working on a quill
 
 Two verbs, and they answer different questions.
@@ -106,23 +130,27 @@ this collection's own `node_modules`, so the versions pinned here are the format
 the quiver is packed in and the wasm the gate renders through.
 
 **Does it work?** `quillkit test` loads the collection with `fromDir`, compiles
-every quill, and renders each one's example document — the blueprint seeded from
-the `example:` values in `Quill.yaml`. It is the gate CI runs, so a validation
-failure surfaces here rather than on a consumer's build:
+every quill, and renders each one's seed, every field absent but what a card
+kind's `seed:` writes and rendering its `default:` or its blank, and its
+`example.md`, one filled-in page of made-up values. `npm test` then fails a
+quill that ships no example or whose example warns, and a template that warns.
+It is the gate CI runs, so a validation failure surfaces here rather than on a
+consumer's build:
 
 ```bash
 npm install
 npm test
 ```
 
-The gate renders nothing the schema did not write, so the coverage is the
-`example:` block: a field with no example is a field no render exercises.
+The gate renders one answer per quill, so a page with a long list or a
+wrapping value in it is a design fixture's to exercise (`design/`).
 
 **What is it like to use?** `npm run dev` is `quillkit studio`: it packs this
 quiver, serves the studio client over it, and repacks on every save — pick a
-quill, edit the seeded document, watch it paint, read the diagnostics. The
-client is quillkit's own, so there is nothing to install for it and nothing to
-keep in step.
+quill, edit its example (or, with **Examples** off, its seed), or open one
+of the official templates from **Templates…**, watch it paint, read the
+diagnostics. The client is quillkit's own, so there is nothing to install for it
+and nothing to keep in step.
 
 Reload to pick up a repack. Editing a quill into an invalid state is not a
 failure of the loop: it packs, and the client says what is wrong with that quill
@@ -134,7 +162,10 @@ wasm it was built against, and nothing at runtime reconciles the two. The gate
 is authoritative, studio is advisory.
 
 `npm run site` writes the arrangement a deploy serves into `site/` — the client
-at the root, a built quiver at `quiver/` beneath it — without serving it. CI
+at the root, a built quiver at `quiver/` beneath it — without serving it. It
+passes `--drafts`, so the `0.0.x` prototypes are packed beside the releases, and
+`--templates`, so every deploy previews them and the templates as `npm run dev`
+does. CI
 uploads that on every run, so a pull request — a fork's included — is reviewed
 by downloading the artifact and serving the directory.
 
@@ -142,7 +173,18 @@ by downloading the artifact and serving the directory.
 that same command and keeps the deploy here: nothing outside this repository
 holds `pages: write`.
 
+`vercel.json` deploys the same layout to Vercel, where a pull request gets a
+preview URL instead of an artifact to download. It carries the build, the output
+directory and the one cache rule a host owes this layout — `assets/*` immutable,
+which is the engine, and everything else already right by default. Importing the
+repository is the rest of the setup. Both deploys run off `main` and neither
+knows about the other.
+
 ## License
 
-Apache-2.0. Individual quills carry their own licensing terms; see the
-`packages/` directory inside each quill for upstream font and template licenses.
+Apache-2.0, the quill packages under `quills/` included, except
+`classic_resume`'s `ttq-classic-resume`, which is MIT. Two things a quill
+carries are not the project's to license: the fonts its package bundles, which
+keep their own upstream terms — see the `packages/` directory inside each quill
+— and the DoD and DoW seals under `quills/*/*/assets/`, which are US
+Government insignia and whose use is governed as such.

package/package.json

@@ -1,29 +1,31 @@
 {
   "name": "@airmark/quiver",
-  "version": "0.32.2",
+  "version": "0.34.0",
   "description": "Airmark Quiver — Air Force and DAF document Quills for Quillmark.",
   "type": "module",
   "exports": {
     "./Quiver.yaml": "./Quiver.yaml",
     "./quills/*": "./quills/*",
+    "./templates/*": "./templates/*",
     "./package.json": "./package.json"
   },
   "files": [
     "quills",
+    "templates",
     "Quiver.yaml"
   ],
   "engines": {
     "node": ">=24"
   },
   "devDependencies": {
-    "@quillmark/quiver": "0.27.0",
-    "@quillmark/wasm": "^0.110.0",
-    "quillkit": "0.5.4"
+    "@quillmark/quiver": "0.33.0",
+    "@quillmark/wasm": "^0.121.0",
+    "quillkit": "0.13.0"
   },
   "scripts": {
-    "test": "quillkit test",
-    "site": "quillkit site --out site",
-    "dev": "quillkit studio"
+    "test": "quillkit test && node scripts/check-examples.mjs && node scripts/check-templates.mjs",
+    "site": "quillkit site --out site --drafts --templates templates",
+    "dev": "quillkit studio --templates templates"
   },
   "keywords": [
     "quillmark",

package/quills/af4141/0.1.0/Quill.yaml

@@ -14,13 +14,11 @@ main:
     name:
       type: string
       default: ""
-      example: "Doe, John A."
       description: Full name in Last, First, Middle Initial format.
 
     unit:
       type: string
       default: ""
-      example: 1st Air Control Squadron
       description: Unit or organization of assignment.
 
     grade:
@@ -35,9 +33,9 @@ main:
 
 card_kinds:
   experience:
+    title: Record of Experience
     description: Each card represents one row in the Record of Experience table. Rows fill page 1 (up to 16 rows) then page 2 (up to 21 rows), for a maximum of 37 rows.
     ui:
-      title: Record of Experience
       groups: [record]
     body:
       enabled: false
@@ -45,7 +43,6 @@ card_kinds:
       date:
         type: date
         default: ""
-        example: "2026-03-14"
         ui:
           group: record
         description: Date of the action (column A).
@@ -53,7 +50,6 @@ card_kinds:
       action:
         type: string
         default: ""
-        example: Upgraded to 5-level; assumed ADO duties
         ui:
           group: record
         description: One type of action per line (column B).
@@ -61,16 +57,14 @@ card_kinds:
       written_grade:
         type: string
         default: ""
-        example: "3"
         ui:
           group: record
           compact: true
-        description: Written grade, if applicable (column C).
+        description: Written grade, as in 3, if applicable (column C).
 
       written_grade_date:
         type: date
         default: ""
-        example: "2026-02-28"
         ui:
           group: record
           compact: true
@@ -79,16 +73,14 @@ card_kinds:
       positional_grade:
         type: string
         default: ""
-        example: "2"
         ui:
           group: record
           compact: true
-        description: Positional grade, if applicable (column E).
+        description: Positional grade, as in 2, if applicable (column E).
 
       positional_grade_date:
         type: date
         default: ""
-        example: "2026-03-14"
         ui:
           group: record
           compact: true
@@ -97,7 +89,6 @@ card_kinds:
       auth_or_remarks:
         type: string
         default: ""
-        example: "J.A.D."
         ui:
           group: record
-        description: Authentication or remarks entry (column G).
+        description: Authentication initials, as in J.A.D., or remarks entry (column G).

package/quills/af4141/0.1.0/example.md

@@ -0,0 +1,53 @@
+~~~
+$quill: af4141
+name: Doe, John A.
+unit: 1st Air Control Squadron
+grade: SSgt
+commanders_auth: R.T.K., Lt Col
+~~~
+
+~~~
+$kind: experience
+date: 2025-06-02
+action: Assigned to 1st Air Control Squadron
+auth_or_remarks: M.S.P.
+~~~
+
+~~~
+$kind: experience
+date: 2025-09-19
+action: Completed initial qualification training
+auth_or_remarks: M.S.P.
+~~~
+
+~~~
+$kind: experience
+date: 2026-02-28
+action: Initial evaluation, written phase
+written_grade: "3"
+written_grade_date: 2026-02-28
+auth_or_remarks: L.E.W.
+~~~
+
+~~~
+$kind: experience
+date: 2026-03-14
+action: Initial evaluation, positional phase
+positional_grade: "2"
+positional_grade_date: 2026-03-14
+auth_or_remarks: L.E.W.
+~~~
+
+~~~
+$kind: experience
+date: 2026-03-14
+action: Upgraded to 5-level
+auth_or_remarks: R.T.K.
+~~~
+
+~~~
+$kind: experience
+date: 2026-03-16
+action: Assumed ADO duties
+auth_or_remarks: R.T.K.
+~~~

package/quills/afmc_moa/0.0.1/Quill.yaml

@@ -16,7 +16,6 @@ main:
     first_party_name:
       type: plaintext
       inline: true
-      example: "[First Party Name and Acronym]"
       ui:
         group: parties
       description: "Full organization name and acronym of the first party (the MOA's proponent). Printed as 'THE [FIRST PARTY]' in the title block and referenced throughout as '[the First Party]'."
@@ -24,7 +23,6 @@ main:
     second_party_name:
       type: plaintext
       inline: true
-      example: "[Second Party Name and Acronym]"
       ui:
         group: parties
       description: "Full organization name and acronym of the second party. Printed as 'THE [SECOND PARTY]' in the title block."
@@ -40,7 +38,6 @@ main:
     subject:
       type: plaintext
       inline: true
-      example: "[Insert Subject]"
       ui:
         group: parties
       description: "Subject of the agreement, printed in the title block ('FOR [SUBJECT]') and on the Attachment A cover if reimbursable."
@@ -48,7 +45,6 @@ main:
     agreement_number:
       type: plaintext
       inline: true
-      example: "[Insert Agreement Number]"
       ui:
         group: parties
       description: Unique agreement identification number, printed in the title block.
@@ -58,8 +54,6 @@ main:
       items:
         type: plaintext
       default: []
-      example:
-        - "[Insert Second Party Mailing Address]"
       ui:
         group: correspondence
       description: "Second Party's mailing address for MOA correspondence and notices. Also shown in the intro paragraph if second_party_is_non_government is true."
@@ -76,7 +70,6 @@ main:
       type: richtext
       inline: true
       default: ""
-      example: "[Insert Reimbursable Support]"
       ui:
         group: financial_details
       description: "Attachment A, item 1: description of the reimbursable support. Only used when reimbursable is true."
@@ -85,27 +78,24 @@ main:
       type: plaintext
       inline: true
       default: ""
-      example: "$[Insert Estimated Amount]"
       ui:
         group: financial_details
         compact: true
-      description: "Attachment A, item 2: estimated amount of funds to be reimbursed. Only used when reimbursable is true."
+      description: "Attachment A, item 2: estimated amount of funds to be reimbursed, as in $50,000. Only used when reimbursable is true."
 
     appropriation_fy:
       type: plaintext
       inline: true
       default: ""
-      example: "[Insert Appropriation FY]"
       ui:
         group: financial_details
         compact: true
-      description: "Attachment A, item 2: appropriation fiscal year. Only used when reimbursable is true."
+      description: "Attachment A, item 2: appropriation fiscal year, printed after 'FY', as in 2027. Only used when reimbursable is true."
 
     cost_center_provider:
       type: plaintext
       inline: true
       default: ""
-      example: "[Insert Provider Cost Center Number]"
       ui:
         group: financial_details
         compact: true
@@ -115,7 +105,6 @@ main:
       type: plaintext
       inline: true
       default: ""
-      example: "[Insert Receiver Cost Center Number]"
       ui:
         group: financial_details
         compact: true
@@ -125,7 +114,6 @@ main:
       type: plaintext
       inline: true
       default: ""
-      example: "[Insert Provider Financial POC]"
       ui:
         group: financial_details
       description: "Attachment A, item 4: provider's financial point of contact. Only used when reimbursable is true."
@@ -134,7 +122,6 @@ main:
       type: plaintext
       inline: true
       default: ""
-      example: "[Insert Receiver Financial POC]"
       ui:
         group: financial_details
       description: "Attachment A, item 4: receiver's financial point of contact. Only used when reimbursable is true."
@@ -143,7 +130,6 @@ main:
       type: richtext
       inline: true
       default: ""
-      example: "[Insert Any Additional Financial Information]"
       ui:
         group: financial_details
       description: "Attachment A, item 5: any other financial information required by DoD 7000.14-R or desired in the agreement. Only used when reimbursable is true."
@@ -151,7 +137,6 @@ main:
     first_party_signatory:
       type: plaintext
       inline: true
-      example: "[First Party Signatory Name and Title]"
       ui:
         group: signatures
       description: "Name and title of the First Party's approval authority, printed under the signature line."
@@ -159,7 +144,6 @@ main:
     second_party_signatory:
       type: plaintext
       inline: true
-      example: "[Second Party Signatory Name and Title]"
       ui:
         group: signatures
       description: "Name and title of the Second Party's approval authority, printed under the signature line."
@@ -173,35 +157,31 @@ main:
 
 card_kinds:
   background:
-    description: "Background section (DoDI 4000.19 paragraph 1) explaining the circumstances leading to this MOA. Authored as its own card, but rendered inline as the body's numbered paragraphs — same chained decimal numbering as the rest of the body, no page break. Exactly one is expected; if more than one is supplied, only the first is used. Renders before authorities."
-    ui:
-      title: Background
-    body:
-      example: |
+    title: Background
+    description: "Background section (DoDI 4000.19 paragraph 1) explaining the circumstances leading to this MOA. The body opens with 'BACKGROUND:'. Optional: include it only to explain a need the purpose does not make self-evident, typically with another federal agency; between OSD or DoD Components it is normally omitted. Authored as its own card, but rendered inline as the body's numbered paragraphs — same chained decimal numbering as the rest of the body, no page break. Exactly one is expected; if more than one is supplied, only the first is used. Renders before authorities."
+    seed:
+      $body: |
         BACKGROUND: [If there is a need to discuss background, do so here. Normally, there is no need to discuss the background or provide justification for the MOA, particularly if between OSD or DoD Components. Occasionally, however, there is a desire to explain the need for the MOA; particularly where it is not self-evident from the purpose or it is with another federal agency.]
 
   authorities:
-    description: "Authorities section citing the legal basis for this MOA. Authored as its own card, but rendered inline as the body's numbered paragraphs — same chained decimal numbering as the rest of the body, no page break. Exactly one is expected; if more than one is supplied, only the first is used. Renders after background, before purpose_and_scope."
-    ui:
-      title: Authorities
-    body:
-      example: |
+    title: Authorities
+    description: "Authorities section citing the legal basis for this MOA. The body opens with 'AUTHORITIES:' and states the legal authority for the MOA, such as the Economy Act, and each Party's authorities. Another federal agency's own asserted authority is prefaced 'The [Party] asserts the following authority:'; DoD need not agree with it. Authored as its own card, but rendered inline as the body's numbered paragraphs — same chained decimal numbering as the rest of the body, no page break. Exactly one is expected; if more than one is supplied, only the first is used. Renders after background, before purpose_and_scope."
+    seed:
+      $body: |
         AUTHORITIES: [State the legal authority upon which the reimbursable MOA is based, such as the Economy Act, or any other legal or significant authority that authorizes any such actions associated with this MOA. Discuss the authorities of the Parties here. If the other Party is another federal agency and insists on stating what it believes to be its own authority, preface that assertion with "The [Party] asserts the following authority:" The DoD has no obligation to agree with such assertions of authority by other federal agencies.]
 
   purpose_and_scope:
-    description: "Purpose and Scope section describing what this MOA establishes. Authored as its own card, but rendered inline as the body's numbered paragraphs — same chained decimal numbering as the rest of the body, no page break. Exactly one is expected; if more than one is supplied, only the first is used. Renders after authorities, before responsibilities_of_the_parties."
-    ui:
-      title: Purpose and Scope
-    body:
-      example: |
+    title: Purpose and Scope
+    description: "Purpose and Scope section describing what this MOA establishes. The body opens with 'PURPOSE AND SCOPE:' and states the MOA's purpose and scope. Every MOA includes it. Authored as its own card, but rendered inline as the body's numbered paragraphs — same chained decimal numbering as the rest of the body, no page break. Exactly one is expected; if more than one is supplied, only the first is used. Renders after authorities, before responsibilities_of_the_parties."
+    seed:
+      $body: |
         PURPOSE AND SCOPE: [State the purpose and the scope of the MOA here. Always use this paragraph.]
 
   responsibilities_of_the_parties:
-    description: "Responsibilities of the Parties section listing each party's obligations under this MOA. Authored as its own card, but rendered inline as the body's numbered paragraphs — same chained decimal numbering as the rest of the body, no page break. Exactly one is expected; if more than one is supplied, only the first is used. Renders after purpose_and_scope, before personnel."
-    ui:
-      title: Responsibilities of the Parties
-    body:
-      example: |
+    title: Responsibilities of the Parties
+    description: "Responsibilities of the Parties section listing each party's obligations under this MOA. The body opens with 'RESPONSIBILITIES OF THE PARTIES:', then a list item per Party ('The [First Party] will—', 'The [Second Party] will—', 'Both Parties will—'), each nesting every specific obligation of that Party. Authored as its own card, but rendered inline as the body's numbered paragraphs — same chained decimal numbering as the rest of the body, no page break. Exactly one is expected; if more than one is supplied, only the first is used. Renders after purpose_and_scope, before personnel."
+    seed:
+      $body: |
         RESPONSIBILITIES OF THE PARTIES:
 
         - The [First Party] will—
@@ -212,19 +192,17 @@ card_kinds:
           - [insert as many responsibilities as necessary but ensure that they apply to both Parties]
 
   personnel:
-    description: "Personnel section describing each party's responsibility for its own personnel costs. Authored as its own card, but rendered inline as the body's numbered paragraphs — same chained decimal numbering as the rest of the body, no page break. Exactly one is expected; if more than one is supplied, only the first is used. Renders after responsibilities_of_the_parties, before general_provisions."
-    ui:
-      title: Personnel
-    body:
-      example: |
+    title: Personnel
+    description: "Personnel section describing each party's responsibility for its own personnel costs. The body opens with 'PERSONNEL:' and states each Party's responsibility for all costs of its personnel (pay and benefits, support, travel) and for their supervision and management, with the process for any shared supervision. Authored as its own card, but rendered inline as the body's numbered paragraphs — same chained decimal numbering as the rest of the body, no page break. Exactly one is expected; if more than one is supplied, only the first is used. Renders after responsibilities_of_the_parties, before general_provisions."
+    seed:
+      $body: |
         PERSONNEL: [Explain each Party's responsibility for all costs of its personnel, including pay and benefits, support, and travel, if applicable to the agreement. Each Party is responsible for supervision and management of its personnel. For shared supervision or management, explain the process to accomplish that.]
 
   general_provisions:
-    description: "General Provisions section covering points of contact, termination, expiration, and other standard MOA terms. Authored as its own card, but rendered inline as the body's numbered paragraphs — same chained decimal numbering as the rest of the body, no page break. Exactly one is expected; if more than one is supplied, only the first is used. Renders after personnel, before financial_details."
-    ui:
-      title: General Provisions
-    body:
-      example: |
+    title: General Provisions
+    description: "General Provisions section covering points of contact, termination, expiration, and other standard MOA terms. The body opens with 'GENERAL PROVISIONS:', then a list of DoDI 4000.19's standard provisions, each led by its capitalized title: POINTS OF CONTACT (a primary and an alternate POC per Party, each with name, position, office, phone and email), CORRESPONDENCE, REVIEW OF AGREEMENT (a non-reimbursable MOA at least at mid-point, a reimbursable one annually for financial impacts), MODIFICATION OF AGREEMENT, DISPUTES, TERMINATION OF AGREEMENT (its days of written notice), TRANSFERABILITY, ENTIRE AGREEMENT, EFFECTIVE DATE, EXPIRATION DATE, NO THIRD PARTY BENEFICIARIES, SEVERABILITY and OTHER FEDERAL AGENCIES. CANCELLATION OR MODIFICATION OF PREVIOUS AGREEMENT, naming that agreement's subject, number and effective date, appears only when this MOA supersedes one. Authored as its own card, but rendered inline as the body's numbered paragraphs — same chained decimal numbering as the rest of the body, no page break. Exactly one is expected; if more than one is supplied, only the first is used. Renders after personnel, before financial_details."
+    seed:
+      $body: |
         GENERAL PROVISIONS:
 
         - POINTS OF CONTACT (POCS). The following POCs will be used by the Parties to communicate matters concerning this MOA. Each Party may change its POC upon reasonable notice to the other Party.
@@ -249,11 +227,10 @@ card_kinds:
         - OTHER FEDERAL AGENCIES. This MOA does not bind any federal agency, other than the Parties, nor waive required compliance with any law or regulation.
 
   financial_details:
-    description: "Financial Details section (DoDI 4000.19 paragraph 7) covering availability of funds, billing, payment, and Economy Act determination. Authored as its own card, but rendered inline as the body's numbered paragraphs — same chained decimal numbering as the rest of the body, no page break. Exactly one is expected; if more than one is supplied, only the first is used. Renders after general_provisions, before list_of_attachments."
-    ui:
-      title: Financial Details
-    body:
-      example: |
+    title: Financial Details
+    description: "Financial Details section (DoDI 4000.19 paragraph 7) covering availability of funds, billing, payment, and Economy Act determination. The body opens with 'FINANCIAL DETAILS:'. A non-reimbursable MOA follows it with 'This MOA does not provide for reimbursement between the Parties.' A reimbursable one lists AVAILABILITY OF FUNDS, BILLING, PAYMENT OF BILLS, FINANCIAL SPECIFICS (referring to Attachment A and stating any allowance or advance payments) and ECONOMY ACT DETERMINATION AND FINDINGS (D&F). The D&F adds that the provider can render the support without jeopardizing its missions when the provider is an OSD or DoD Component, and that any required D&F is completed when a separate written one is required. Authored as its own card, but rendered inline as the body's numbered paragraphs — same chained decimal numbering as the rest of the body, no page break. Exactly one is expected; if more than one is supplied, only the first is used. Renders after general_provisions, before list_of_attachments."
+    seed:
+      $body: |
         FINANCIAL DETAILS [include Attachment A in all reimbursable MOAs; if the MOA is not reimbursable add, "This MOA does not provide for reimbursement between the Parties"]:
 
         - AVAILABILITY OF FUNDS. This MOA does not document the obligation of funds between the Parties. The obligation of funds by the Parties, resulting from this MOA, is subject to the availability of funds pursuant to the DoD Financial Management Regulation. No provision in this MOA will be interpreted to require obligation or payment of funds in violation of the Anti-Deficiency Act, Section 1341 of Title 31, United States Code.
@@ -263,27 +240,27 @@ card_kinds:
         - ECONOMY ACT DETERMINATION AND FINDINGS (D&F). If the MOA is being entered into in accordance with Section 1535 of Title 31, United States Code (the Economy Act), both Parties agree that the requirements listed in Paragraph (a) of the Economy Act have been met. [Add the following sentence if the provider is an OSD or DoD Component] The provider has determined that the capabilities exist to render the requested support without jeopardizing its assigned missions. [Add the following sentence only if a separate, written Economy Act D&F is required.] Any required Economy Act D&F has been completed.
 
   list_of_attachments:
-    description: "List of Attachments section enumerating this MOA's attachments. Authored as its own card, but rendered inline as the body's numbered paragraphs — same chained decimal numbering as the rest of the body, no page break. Exactly one is expected; if more than one is supplied, only the first is used. Renders last, after financial_details, immediately before the signature blocks."
-    ui:
-      title: List of Attachments
-    body:
-      example: |
+    title: List of Attachments
+    description: "List of Attachments section enumerating this MOA's attachments. The body opens with 'LIST OF ATTACHMENTS:', then a list item per attachment, as in 'Attachment A, Financial Details'. Authored as its own card, but rendered inline as the body's numbered paragraphs — same chained decimal numbering as the rest of the body, no page break. Exactly one is expected; if more than one is supplied, only the first is used. Renders last, after financial_details, immediately before the signature blocks."
+    seed:
+      $body: |
         LIST OF ATTACHMENTS:
 
         - [List each attachment here, e.g. "Attachment A, Financial Details".]
 
   attachment:
+    title: Attachment
     description: "A lettered attachment to the MOA, starting at Attachment B (Attachment A is reserved for the reimbursable financial-details page and is generated automatically when 'reimbursable' is true). Each card starts on its own page."
     ui:
-      title: Attachment
-    body:
-      example: |
+      groups: [attachment]
+    seed:
+      title: "[Insert Attachment Title]"
+      $body: |
         [Describe the attachment's content here.]
     fields:
       title:
         type: plaintext
         inline: true
-        example: "[Insert Attachment Title]"
         ui:
           group: attachment
         description: "Subject of the attachment, printed on the cover line ('to [subject], [agreement_number] [title]')."