@airmark/quiver 0.32.1 → 0.33.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
@@ -94,8 +97,28 @@ quills/
       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,17 +129,17 @@ 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, rendering its
+`default:` or its blank. 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 no answer, so a page with a long list or a wrapping value in
+it is a design fixture's to exercise (`design/`), not the gate's.
 
 **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
@@ -134,7 +157,9 @@ 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
+every deploy previews them 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 +167,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,28 +1,30 @@
 {
   "name": "@airmark/quiver",
-  "version": "0.32.1",
+  "version": "0.33.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.26.0",
-    "@quillmark/wasm": "^0.109.1",
-    "quillkit": "0.5.3"
+    "@quillmark/quiver": "0.30.0",
+    "@quillmark/wasm": "^0.116.0",
+    "quillkit": "0.9.0"
   },
   "scripts": {
-    "test": "quillkit test",
-    "site": "quillkit site --out site",
+    "test": "quillkit test && node scripts/check-templates.mjs",
+    "site": "quillkit site --out site --drafts",
     "dev": "quillkit studio"
   },
   "keywords": [

package/quills/af4141/0.1.0/Quill.yaml

@@ -35,9 +35,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

package/quills/afmc_moa/0.0.1/Quill.yaml

@@ -173,33 +173,29 @@ main:
 
 card_kinds:
   background:
+    title: 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: |
         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:
+    title: 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: |
         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:
+    title: 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: |
         PURPOSE AND SCOPE: [State the purpose and the scope of the MOA here. Always use this paragraph.]
 
   responsibilities_of_the_parties:
+    title: 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: |
         RESPONSIBILITIES OF THE PARTIES:
@@ -212,17 +208,15 @@ card_kinds:
           - [insert as many responsibilities as necessary but ensure that they apply to both Parties]
 
   personnel:
+    title: 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: |
         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:
+    title: 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: |
         GENERAL PROVISIONS:
@@ -249,9 +243,8 @@ 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:
+    title: 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: |
         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"]:
@@ -263,9 +256,8 @@ 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:
+    title: 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: |
         LIST OF ATTACHMENTS:
@@ -273,9 +265,10 @@ card_kinds:
         - [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
+      groups: [attachment]
     body:
       example: |
         [Describe the attachment's content here.]

package/quills/classic_resume/0.0.1/Quill.yaml

@@ -0,0 +1,361 @@
+quill:
+  name: classic_resume
+  version: 0.0.1
+  backend: typst
+  description: Classic single-page resume
+
+typst:
+  plate_file: plate.typ
+
+# A resume is a stack of sections, and each kind of section is a card kind: a
+# heading, optional prose under it, and the rows that section holds. The rows
+# are the section's own, so an entry cannot land under the wrong heading.
+main:
+  ui:
+    groups: [identity, page]
+  # Everything prints under a section heading, so main carries no body: a
+  # summary is a Summary card.
+  body:
+    enabled: false
+  fields:
+    name:
+      type: string
+      example: John Doe
+      ui:
+        group: identity
+      description: "Your name, set large at the top. It is the document's level 1 heading, and becomes the exported PDF's title and author."
+
+    contacts:
+      type: array
+      items:
+        type: string
+      example:
+        - john.doe@example.com
+        - (555) 123-4567
+        - github.com/johndoe
+        - linkedin.com/in/johndoe
+        - Pittsburgh, PA
+      ui:
+        group: identity
+      description: "The line under your name, one contact per line here, printed across the page separated by a diamond. Order them by how much you want them used."
+
+    link_contacts:
+      type: boolean
+      default: true
+      ui:
+        group: identity
+        compact: true
+      description: "Turn contacts that look like an email address, a web address or a phone number into live links in the PDF. Anything else — a city, a clearance level — is printed as written."
+
+    paper:
+      type: enum
+      values:
+        - us-letter
+        - a4
+      default: us-letter
+      ui:
+        group: page
+        compact: true
+      description: "Page size."
+
+    font_size:
+      type: number
+      default: 12
+      ui:
+        group: page
+        compact: true
+      description: "Body text size in points; decimals allowed, such as 11.5. Along with the margin, this is the lever for fitting a resume onto one page — drop a half point before you drop a bullet."
+
+    margin:
+      type: number
+      default: 0.5
+      ui:
+        group: page
+        compact: true
+      description: "Page margin in inches, the same on all four sides. The layout is dense by design; below about 0.4 a printer starts clipping."
+
+
+# Each kind carries the same heading pair and optional prose under it. A blank
+# title prints the kind's usual heading, which the plate holds.
+card_kinds:
+  summary:
+    title: Summary
+    description: "A heading and prose under it. With a title of its own it is any section that is only prose — an objective, a statement of interest."
+    ui:
+      groups: [heading]
+    body:
+      example: |
+        Security engineer of eight years, most of it on detection pipelines other people have to keep running.
+    fields:
+      title:
+        type: plaintext
+        inline: true
+        default: ""
+        ui:
+          group: heading
+        description: &title_description "Printed in uppercase over a rule. Leave blank for the usual heading: Summary, Work Experience, Education, Projects, Skills or Certifications."
+      extra: &extra
+        type: richtext
+        inline: true
+        default: ""
+        ui:
+          group: heading
+          compact: true
+        description: "Qualifier set after the title in the same style, such as a date range or a clarifier. Italicize with *asterisks*. Leave blank for the usual case."
+
+  experience:
+    title: Experience
+    description: "Jobs, most recent first: employer and dates on the first line, role and location on the second, details under them."
+    ui:
+      groups: [heading]
+    body: &section_body
+      # Empty is a heading straight over its rows, which is the usual section.
+      example: ""
+    fields:
+      title:
+        type: plaintext
+        inline: true
+        default: ""
+        ui:
+          group: heading
+        description: *title_description
+      extra: *extra
+      jobs:
+        type: array
+        items:
+          type: object
+          properties:
+            company:
+              type: plaintext
+              inline: true
+              example: Templar Archives Research Division
+              description: "Set in bold at the left of the first line."
+            dates: &dates
+              type: plaintext
+              inline: true
+              default: ""
+              example: August 2024 – Present
+              description: "Set in bold at the right, opposite the name. Free text rather than a date, so a range reads as you write it: 'August 2024 – Present', 'December 2025'. Keep the form the same down the page."
+            role:
+              type: plaintext
+              inline: true
+              default: ""
+              example: Psionic Research Analyst
+              description: "Your title, set in italics under the employer. Leave blank to omit."
+            location: &location
+              type: plaintext
+              inline: true
+              default: ""
+              example: Pittsburgh, PA
+              description: "Set in italics at the right of the second line. 'Pittsburgh, PA', 'Remote'. Leave blank to omit; with the line's other half blank too, the second line is not printed."
+            details: &details
+              type: richtext
+              default: ""
+              example: |
+                - What you did, and what came of it.
+              description: "Set under the entry. Usually a bulleted list, one line each and strongest first; a sentence, *italics* and **bold** set as well, and a heading sets as a bold line. Leave blank for nothing under the entry."
+        example:
+          - company: Templar Archives Research Division
+            dates: August 2024 – Present
+            role: Psionic Research Analyst
+            location: Aiur
+            details: |
+              - Analyzed Khala disruption patterns, developing countermeasures to protect neural link infrastructure.
+        description: "One row per job. A row is never split across a page break."
+
+  education:
+    title: Education
+    description: "Schools, most recent first: school and date on the first line, degree and location on the second."
+    ui:
+      groups: [heading]
+    body: *section_body
+    fields:
+      title:
+        type: plaintext
+        inline: true
+        default: ""
+        ui:
+          group: heading
+        description: *title_description
+      extra: *extra
+      schools:
+        type: array
+        items:
+          type: object
+          properties:
+            school:
+              type: plaintext
+              inline: true
+              example: Carnegie Mellon University
+              description: "Set in bold at the left of the first line."
+            dates:
+              <<: *dates
+              example: May 2024
+            degree:
+              type: plaintext
+              inline: true
+              default: ""
+              example: BS, Data Science
+              description: "Degree and field, set in italics under the school. Leave blank to omit."
+            location: *location
+            details:
+              <<: *details
+              example: |
+                - Distinguished Graduate (top 10%).
+              description: "Honors, activities, coursework, set under the entry. Most degrees need none."
+        example:
+          - school: Carnegie Mellon University
+            dates: December 2025
+            degree: Master of Information Technology Strategy
+            location: Pittsburgh, PA
+        description: "One row per school or degree."
+
+  projects:
+    title: Projects
+    description: "Projects: name and link on the first line, details under them."
+    ui:
+      groups: [heading]
+    body: *section_body
+    fields:
+      title:
+        type: plaintext
+        inline: true
+        default: ""
+        ui:
+          group: heading
+        description: *title_description
+      extra: *extra
+      projects:
+        type: array
+        items:
+          type: object
+          properties:
+            name:
+              type: plaintext
+              inline: true
+              example: Quillmark
+              description: "Set in bold at the left."
+            url:
+              type: string
+              default: ""
+              example: https://github.com/nibsbin/quillmark
+              description: "Set small and italic at the right, and made a live link when it starts with http. Anything else is printed as written, so '<closed source>' stands in for a project with nothing to link. Leave blank to omit."
+            details: *details
+        example:
+          - name: Quillmark
+            url: https://github.com/nibsbin/quillmark
+            details: |
+              - Parameterization engine for typesetting documents from markdown.
+        description: "One row per project."
+
+  skills:
+    title: Skills
+    description: "Labelled lists of skills, filled across the columns and then down."
+    ui:
+      groups: [heading]
+    body: *section_body
+    fields:
+      title:
+        type: plaintext
+        inline: true
+        default: ""
+        ui:
+          group: heading
+        description: *title_description
+      extra: *extra
+      skills:
+        type: array
+        ui:
+          layout: table
+        items:
+          type: object
+          properties:
+            label:
+              type: plaintext
+              inline: true
+              example: Programming
+              description: "Set in bold on its own line above the text."
+            text:
+              type: plaintext
+              inline: true
+              example: Python, R, JS, Rust, PowerShell, CI/CD
+              title: Items
+              description: "The items under that label, usually comma separated. Printed as written — markup is the one thing a labeled row does not carry."
+        example:
+          - label: Programming
+            text: "Python, R, JS, C#, Rust, PowerShell, CI/CD"
+          - label: Cloud
+            text: "AWS EC2/S3, Helm, Docker, Serverless"
+        description: "One label and its items per row."
+      columns: &columns
+        type: integer
+        default: 2
+        ui:
+          compact: true
+        description: "Number of columns. Two suits items that run most of a line; three suits single words."
+
+  certifications:
+    title: Certifications
+    description: "A list of certifications, filled across the columns and then down."
+    ui:
+      groups: [heading]
+    body: *section_body
+    fields:
+      title:
+        type: plaintext
+        inline: true
+        default: ""
+        ui:
+          group: heading
+        description: *title_description
+      extra: *extra
+      items:
+        type: array
+        items:
+          type: richtext
+          inline: true
+        example:
+          - Offensive Security Certified Professional (OSCP)
+          - GIAC Cyber Threat Intelligence (GCTI)
+        description: "One item per line. Keep each to a line at the column width. Italicize with *asterisks*."
+      columns: *columns
+
+  other:
+    title: Other section
+    description: "A section the kinds above do not name — volunteer work, military service, publications, a competition. Rows take the Experience shape with neutral names."
+    ui:
+      groups: [heading]
+    body: *section_body
+    fields:
+      title:
+        type: plaintext
+        inline: true
+        example: Cyber Competition
+        ui:
+          group: heading
+        description: "Printed in uppercase over a rule. Other has no usual heading, so this one is yours to write."
+      extra: *extra
+      entries:
+        type: array
+        default: []
+        items:
+          type: object
+          properties:
+            heading:
+              type: plaintext
+              inline: true
+              example: 1st in NCX 2023
+              description: "Set in bold at the left of the first line."
+            dates: *dates
+            subtitle:
+              type: plaintext
+              inline: true
+              default: ""
+              description: "Set in italics under the heading. Leave blank to omit."
+            location: *location
+            details: *details
+        example:
+          - heading: 1st in NCX 2023
+            details: |
+              - Developed strategies, defensive scripts, and exploits for the Cyber Combat event.
+        description: "One row per item. A section that is only prose is a Summary with a title of its own."

package/quills/classic_resume/0.0.1/packages/ttq-classic-resume/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2024 Nibs
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.