aibreze 0.1.7 → 0.1.9

package/dist/index.d.ts

@@ -1,6 +1,6 @@
 declare const packageRoot: string;
 declare const rulesDir: string;
-export declare const ruleIds: readonly ["core", "audit", "claims", "essays", "landing", "outreach", "launch"];
+export declare const ruleIds: readonly ["core", "audit", "claims", "essays", "landing", "outreach", "launch", "civic", "academic"];
 export type RuleId = (typeof ruleIds)[number];
 export declare const files: {
     readonly core: string;
@@ -10,6 +10,8 @@ export declare const files: {
     readonly landing: string;
     readonly outreach: string;
     readonly launch: string;
+    readonly civic: string;
+    readonly academic: string;
     readonly cursor: string;
 };
 export type FileId = keyof typeof files;

package/dist/index.js

@@ -11,6 +11,8 @@ export const ruleIds = [
     "landing",
     "outreach",
     "launch",
+    "civic",
+    "academic",
 ];
 export const files = {
     core: join(rulesDir, "core.md"),
@@ -20,6 +22,8 @@ export const files = {
     landing: join(rulesDir, "landing.md"),
     outreach: join(rulesDir, "outreach.md"),
     launch: join(rulesDir, "launch.md"),
+    civic: join(rulesDir, "civic.md"),
+    academic: join(rulesDir, "academic.md"),
     cursor: join(rulesDir, "cursor.mdc"),
 };
 export const catalog = [
@@ -58,6 +62,16 @@ export const catalog = [
         title: "Launch / announcement",
         use: "Shipping posts. Open on a specific moment or the artifact, not the announcement formula.",
     },
+    {
+        id: "civic",
+        title: "Civic / institutional",
+        use: "Filings, testimony, legal-adjacent memos. Ceremony is earned; colleague voice is wrong here.",
+    },
+    {
+        id: "academic",
+        title: "Academic / scholarly",
+        use: "Papers and methods. Precision and citations, not the academic costume.",
+    },
     {
         id: "cursor",
         title: "Cursor pocket card",

package/package.json

@@ -1,59 +1,62 @@
-{
-  "name": "aibreze",
-  "version": "0.1.7",
-  "private": false,
-  "type": "module",
-  "description": "Installable writing rule set for AI agents. Sprays the performative, faux-profound register off prose. Core bans, smell audit, claims review, genre overlays.",
-  "license": "MIT",
-  "author": "Catalyst Forge LLC",
-  "keywords": [
-    "ai",
-    "writing",
-    "style-guide",
-    "prose",
-    "llm",
-    "prompts",
-    "copyediting",
-    "voice"
-  ],
-  "homepage": "https://aibreze.com",
-  "repository": {
-    "type": "git",
-    "url": "git+https://github.com/Catalyst-Forge-LLC/aibreze.git"
-  },
-  "bugs": {
-    "url": "https://github.com/Catalyst-Forge-LLC/aibreze/issues"
-  },
-  "exports": {
-    ".": {
-      "types": "./dist/index.d.ts",
-      "default": "./dist/index.js"
-    },
-    "./rules/*": "./rules/*",
-    "./skills/*": "./skills/*",
-    "./package.json": "./package.json"
-  },
-  "files": [
-    "dist/index.js",
-    "dist/index.d.ts",
-    "rules",
-    "skills",
-    "README.md",
-    "LICENSE"
-  ],
-  "engines": {
-    "node": ">=20"
-  },
-  "devDependencies": {
-    "@types/node": "^24.3.0",
-    "typescript": "^5.9.2"
-  },
-  "scripts": {
-    "build": "tsc",
-    "test": "tsc && node --test dist/index.test.js dist/publish-gate.test.js",
-    "ship": "pnpm --dir site run ship",
-    "site:dev": "pnpm --dir site dev",
-    "site:build": "pnpm --dir site run build",
-    "site:deploy": "pnpm --dir site run ship"
-  }
-}
+{
+	"name": "aibreze",
+	"version": "0.1.9",
+	"private": false,
+	"type": "module",
+	"description": "Installable writing rule set for AI agents. Sprays the performative, faux-profound register off prose. Core bans, smell audit, claims review, genre overlays.",
+	"license": "MIT",
+	"author": "Catalyst Forge LLC",
+	"keywords": [
+		"ai",
+		"writing",
+		"style-guide",
+		"prose",
+		"llm",
+		"prompts",
+		"copyediting",
+		"voice"
+	],
+	"homepage": "https://aibreze.com",
+	"repository": {
+		"type": "git",
+		"url": "git+https://github.com/Catalyst-Forge-LLC/aibreze.git"
+	},
+	"bugs": {
+		"url": "https://github.com/Catalyst-Forge-LLC/aibreze/issues"
+	},
+	"exports": {
+		".": {
+			"types": "./dist/index.d.ts",
+			"default": "./dist/index.js"
+		},
+		"./rules/*": "./rules/*",
+		"./skills/*": "./skills/*",
+		"./package.json": "./package.json"
+	},
+	"files": [
+		"dist/index.js",
+		"dist/index.d.ts",
+		"rules",
+		"skills",
+		"README.md",
+		"LICENSE"
+	],
+	"scripts": {
+		"build": "tsc",
+		"test": "tsc && node --test dist/index.test.js dist/publish-gate.test.js",
+		"prepare": "tsc",
+		"prepublishOnly": "tsc && node dist/publish-gate.js && pnpm test",
+		"ship": "pnpm --dir site run ship",
+		"site:dev": "pnpm --dir site dev",
+		"site:build": "pnpm --dir site run build",
+		"site:deploy": "pnpm --dir site run ship"
+	},
+	"engines": {
+		"node": ">=20"
+	},
+	"packageManager": "pnpm@10.30.1",
+	"devDependencies": {
+		"@types/node": "^24.3.0",
+		"typescript": "^5.9.2"
+	}
+}

package/rules/academic.md

@@ -0,0 +1,114 @@
+# Academic / scholarly
+
+Apply [`core.md`](./core.md) first. This file is the genre overlay for
+journal articles, working papers, methods sections, literature reviews,
+and dissertation chapters that are papers.
+
+It is not the file for essays or talks ([`essays.md`](./essays.md)),
+filings ([`civic.md`](./civic.md)), or product pages. Reference docs
+and textbooks that are really manuals still get core only.
+
+The colleague voice is close. Precision and citations are the shift.
+Do not put on the academic costume.
+
+---
+
+## Register
+
+Write for a peer who already knows the field. Say what you did, what
+you found, and where the claim stops. Full forms more often than the
+default. Contractions are rare, not banned. One is not a finding.
+
+First person is allowed when the field or the overlay uses it ("we
+measured," "I argue"). Passive is not required. Do not convert every
+sentence to "it was found that."
+
+Hedging is earned when it names a limit, a method bound, or a claim
+the data cannot support. "In this sample," "we did not observe,"
+"suggests" stay when they are true. "It could perhaps be argued that"
+is hiding.
+
+The read-aloud test is a careful colleague in the field, not a tired
+product person and not a quarterly from 1987.
+
+Pronouns follow the overlay or the journal. Do not invent "the authors"
+to sound impersonal if the venue uses we.
+
+Hard bans still hold. Insight theater does not become allowed because
+the bibliography is long. Earn the word: "robust," "novel," and
+"seminal" need a measurement, a contrast, or a cite that actually
+carries that weight.
+
+---
+
+## What earns its place
+
+- Citations, operational definitions, method, limitations
+- Field terms of art (applicability heuristic)
+- The journal's sections (IMRaD or whatever they print)
+- An abstract that states the finding, not a teaser
+
+Repeating a defined term is not hand-holding. Numbered hypotheses and
+result rows are not triad packing.
+
+---
+
+## The costume (do not reach for it)
+
+These are the stereotypical academic tells. Ban them as furniture.
+Leave a word if it is doing a real job in the sentence.
+
+- "Moreover," "Thus," "Furthermore," "Indeed" opening clause after
+  clause
+- "This paper seeks to" / "this study aims to" / "the present work"
+- "It has been shown that" with no cite, or with a cite that does not
+  show it
+- "The extant literature," "a growing body of work," "little attention
+  has been paid"
+- "It is worth noting that" / "it is important to note"
+- Nominalization stacks ("the utilization of the implementation")
+- Forced passive when the actor is known and the field allows we
+- A literature review that only announces a gap
+- A last sentence that winks or mic-drops
+
+Do not inject an essay scene to "humanize" the paper. A worked example
+or a named dataset is an instance, not a memoir. Do not apply essay
+law here.
+
+Do not apply civic captions or landing pain lists.
+
+---
+
+## Claims
+
+This genre lives on citations. Run [`claims.md`](./claims.md) when the
+paper asserts effects, magnitudes, or what prior work showed.
+
+A clean-smelling wrong paper is still wrong. Do not cologne a missing
+cite or an overclaim in the abstract.
+
+---
+
+## Audit extras for this genre
+
+On top of `core.md` and `audit.md`:
+
+- Costume density (Moreover / Thus / seeks to / extant literature)
+- Hedging that hides a claim instead of naming a limit
+- Forced impersonal voice against the overlay or the venue
+- Abstract that teases and never states the finding
+- Essay anecdote or landing structure
+- A claim that needs a cite and has none
+
+---
+
+## Acceptance criteria
+
+1. Overlay or venue named the speaker (we, I, or the paper's convention).
+2. Abstract states the finding.
+3. Hedging names a limit or is cut.
+4. No costume furniture in the open or the close.
+5. Claims that need cites have them, or `claims.md` already flagged
+   the gaps.
+6. No essay scene. No civic caption. No landing pain list.
+7. Hard bans still hold.

package/rules/audit.md

@@ -1,7 +1,7 @@
 # AI smell audit prompt
 
 Reusable prompt for auditing any copy (landing pages, emails, blog posts,
-social posts, docs) for signs it was AI-generated or AI-flavored.
+social posts, docs, filings) for signs it was AI-generated or AI-flavored.
 
 **This prompt is additive.** Paste into a model, in order:
 
@@ -51,13 +51,16 @@ pass that skips the house bans.
 ### From core.md (do not re-list)
 
 Hunt every hard ban and cadence tell in `core.md`: escalation formula,
-honest framing, validation+profundity, mechanism inflation, narrative
-theater, genuinely-stacks, dramatic apology, suspense, setup sentences,
-em-dash furniture, triad packing including prefix-repetition, empty marketing
+honest framing (including Look / Let's be clear / Here's the thing),
+validation+profundity, mechanism inflation, narrative
+theater, genuinely-stacks, dramatic apology, suspense, cataphoric
+teasers, setup sentences, em-dash furniture, triad packing including
+prefix-repetition and Not X. Not Y. But Z., empty marketing
 vocab, helper theater, signpost openers, mic-drop closers, intensifier
 filler, parallel-zinger density, bold-lead lists, riddle labels, cozy
 machinery, operator notes in the brochure, hand-holding the obvious,
-unparseable sentences. Apply the
+unparseable sentences, participial afterthoughts, topic-sentence
+pinning. Apply the
 corpus-applicability heuristic before rewriting overlay terms. Teaching
 antithesis is allowed only when categories differ, never as
 synonym-escalation. One concrete landing chant is a named exception,
@@ -81,6 +84,9 @@ not a free pass for every triad.
   you?" / "The result?" / "The best part?"
 - **The hedge-flourish.** Winking qualifiers like "(yet)" or "at least
   for now" that perform humility instead of having it.
+- **False concessions.** "To be fair…", "It's not all bad…", "That said,
+  there is another side." A real limit stays. A performed even-hand
+  before the pitch does not.
 - **False momentum closers.** "The future is here." / "And this is just
   the beginning." / "The only question is whether you'll be ready."
 - **Setup-payoff formula on every heading.** Colon constructions: "The
@@ -100,9 +106,11 @@ product names, and words that would get less precise if swapped for
 
 - delve, dive deep, deep dive, unpack, explore (as a section-verb with
   no object worth exploring)
+- intricate, realm, tapestry (as atmosphere with no object)
 - unlock, unleash, harness, empower, supercharge, turbocharge
 - leverage (as empty marketing verb: "leverage your workflow"), utilize
-  (instead of use). Domain projects may carve out doctrinal "leverage"
+  (instead of use), underscore (as pomp: "this underscores the need").
+  Domain projects may carve out doctrinal "leverage"
   (force / fulcrum sense) in an overlay.
 - seamless, seamlessly, effortless, frictionless, streamline
 - game-changer, game-changing, revolutionary, cutting-edge, next-level
@@ -133,6 +141,12 @@ product names, and words that would get less precise if swapped for
 - **Uniform paragraph lengths.** Every paragraph 2-3 sentences, every
   sentence medium-length. Human writing has variance: a one-word
   sentence, then a long one.
+- **Bro-etry / short-line stanzas.** Prose broken into one clause per
+  line, with blank lines as drama, when the piece is not a poem. Flag
+  the formatting, then the sentences.
+- **Do not flag Oxford commas** or other house punctuation as AI tells.
+  A serial comma is a style choice. Em dashes are a density budget in
+  `core.md`, not a mark to erase.
 - **Perfectly balanced sections.** Every section the same length, every
   card grid filled to an even number, every argument given exactly equal
   weight.

package/rules/civic.md

@@ -0,0 +1,112 @@
+# Civic / institutional
+
+Apply [`core.md`](./core.md) first. This file is the genre overlay for
+regulatory comment letters, government filings, testimony, legal-adjacent
+memos, and compliance notes.
+
+It is not the file for product pages, essays, outreach, ship posts, or
+papers. Those have their own genre files. Reference docs still get
+core only.
+
+The default colleague voice is wrong here. Overlay this file. Do not
+obey the tired-colleague register in a captioned filing.
+
+---
+
+## Register
+
+Ceremony is earned. Contractions loosen their grip. Full forms are the
+default, not a leak.
+
+Write for a docket clerk, a reviewing attorney, an ALJ, or a comment-
+period staffer. The read-aloud test is whether they recognize a filing,
+not whether you would say it to a peer at the end of a long day.
+
+Pronouns are a project decision. Typical: the named organization,
+"the commenter," or institutional we. An individual comment may use I
+when the overlay says the filer is speaking as themselves. Do not let
+an agent default to colleague I, or to landing-page we, without that
+choice.
+
+Hard bans still hold. Escalation, honest-framing, and insight theater
+do not become allowed because the letterhead is formal. Earn the word
+still applies: "transformative" needs from-what-into-what even at OMB.
+
+---
+
+## Ceremony that earns its place
+
+Leave these when the form or the forum requires them:
+
+- Captions, docket numbers, agency names, comment deadlines
+- Recitals of authority and standing
+- Defined terms, used consistently
+- Pin cites, record cites, statutory and regulatory citations
+- "Respectfully submitted," signature blocks, certificates of service
+
+Do not spray those into a blog post. Do not strip them from a filing
+to make it sound like core's default.
+
+Numbered headings (`I.`, `II.`, `Comment 1`) are the genre. They are
+not riddle labels and not signpost smell.
+
+Repeating a defined term is not hand-holding. Parallel numbered
+comments are not triad packing.
+
+---
+
+## Ceremony that does not
+
+- Empty deference stacks ("we respectfully submit that we respectfully
+  request")
+- Throat-clearing that is not a required recital
+- "Hereby," "aforementioned," "herein" added as furniture. If the form
+  uses them, leave them. Do not import them for the smell of formality.
+- Launch energy: "excited to comment," "pleased to share our views"
+- Colleague contractions in the caption, the summary of request, or
+  the prayer for relief
+- Mic-drop closers and punchy hooks. Close on the request.
+- An essay scene injected so the letter "has a person in it." A
+  first-hand harm belongs when the commenter is that person and the
+  overlay says so. Do not invent one to satisfy essay law.
+- A landing pain list. This is not a product page.
+
+---
+
+## Claims
+
+This genre lives on citations. Run [`claims.md`](./claims.md) when the
+letter asserts facts, effects, costs, or what the record shows.
+
+A clean-smelling wrong filing is still wrong. Do not cologne a missing
+cite.
+
+---
+
+## Audit extras for this genre
+
+On top of `core.md` and `audit.md`:
+
+- Colleague-voice leak in a captioned draft
+- Missing request: the letter never says what the agency should do
+- A claim that needs a cite and has none
+- Ceremony stripped that the form requires, or ceremony added that
+  the form does not
+- Essay anecdote or landing structure where the forum did not ask
+  for either
+
+---
+
+## Acceptance criteria
+
+1. Overlay named the speaker (organization, commenter, or I).
+2. Full forms default; contractions rare, and never in the caption or
+   the request.
+3. Required caption / docket / authority / signature elements present
+   when the forum uses them.
+4. Closes on the request, not a zinger.
+5. Claims that need cites have them, or `claims.md` already flagged
+   the gaps.
+6. No essay scene and no landing pain list unless the overlay asked
+   for a first-hand comment.
+7. Hard bans still hold.

package/rules/claims.md

@@ -1,7 +1,7 @@
 # Claims + voice review prompt
 
 Reusable prompt for a hard review of any essay, landing page,
-announcement, or internal doc. It answers two questions at once:
+announcement, filing, paper, or internal doc. It answers two questions at once:
 
 1. **Does what we're claiming hold up?** (truth, scope, evidence,
    overclaim)

package/rules/core.md

@@ -7,9 +7,11 @@ Written **aiBreze**. npm **`aibreze`**. A spray, not a breeze.
 
 This file is the shared core. Genre files add surface-specific rules.
 They are additive: point here, then write only what that surface adds.
-Do not copy the hard bans, cadence budgets, or register into each genre
-file. Projects add a short overlay for dialect carve-outs and pronoun
-policy. Do not copy this file into each repo and then diverge.
+Do not copy the hard bans or cadence budgets into each genre file.
+Register stays in core as the default; a genre file may shift it by
+name (`civic.md`, `academic.md`). Projects add a short overlay for dialect carve-outs
+and pronoun policy. Do not copy this file into each repo and then
+diverge.
 
 Judge the sentence, not the byline. Human prose in this register gets
 sprayed too. Distinctive dialect and verbatim testimony still stand.
@@ -21,7 +23,8 @@ Protected maxims (do not rewrite into a cleverer synonym):
 
 **Also in this package:** `audit.md` (smell), `claims.md` (substance then
 voice), `essays.md`, `landing.md`, `outreach.md`, `launch.md`,
-`cursor.mdc` (agent pocket card).
+`civic.md`, `academic.md`. The pocket card `cursor.mdc` ships in `rules/`
+on npm and on this host. It is not in the skill ZIP.
 
 The name is a household joke. People who live with a smell stop noticing
 it. Generated prose does the same trick: the tics fade into the furniture
@@ -46,6 +49,18 @@ second. Concrete over abstract. Em dashes earn their place, like everything
 else, and most don't. A comma, period, or colon usually does the job with
 less drama.
 
+This is the **default** for essays, product pages, and internal docs. It
+is not the only register. Genre files shift it. Civic and institutional
+writing ([`civic.md`](./civic.md)) earns ceremony and loosens
+contractions. Scholarly papers ([`academic.md`](./academic.md)) keep
+the colleague close and add precision; they do not put on the academic
+costume. Overlay the file for the room. Do not force the default into
+a filing, and do not "elevate" a paper into Moreover / Thus.
+
+The target is the absence of theater, not a personality. Clean is a
+floor. If every surface sounded like the same colleague, that would be
+a new smell. Overlay the register for the room you are in.
+
 Pronouns are a project decision (I / we / you). Pick one per surface and
 hold it. Do not let an agent default to corporate "we" on a personal essay,
 or to "I" on a two-person product page, without an overlay that says so.
@@ -112,6 +127,7 @@ Ban openers like:
 - "Here is the honest take…"
 - "I want to be honest with you…"
 - "Let me be direct with you…"
+- "Look," / "Let's be clear," / "Let's be honest," / "Here's the thing"
 
 Just say the thing. (Saying "the right word is obligation" is fine;
 announcing honesty is not.)
@@ -149,16 +165,29 @@ A single plain use can stay. Flag stacks and repetition.
 Avoid: "and that's on me," "that mistake was genuinely mine,"
 laugh-crying theater. Brief correction is enough.
 
-### 8. Suspense / delayed reveal
+### 8. Suspense / cataphoric teasers
+
+Do not withhold the answer while building drama. Do not promise a
+later payoff instead of saying the thing.
 
-Do not withhold the answer while building drama. Answer first.
+Ban forward-pointing setups: "Here's the part that nobody tells you…",
+"Here's what most people get wrong…", "Here's where it gets interesting.",
+"Here's the best part:", "The part most people sleep on…". Claude-flavored
+cousins: "a caveat worth leading with", "one thing I'll name rather than
+route around:", "worth knowing too:", "now the skepticism part."
+Clickbait cousins: "You won't believe what happened next."
+
+Answer first. The name is descriptive (a teaser that points forward).
+The tell is the promise, not the grammar.
 
 ### Also still banned
 
 - Alliterative triads and stacked-negation chants, except protected
   maxims the overlay names, or **one concrete chant a genre file
   explicitly allows** (landing). **Prefix-repetition triads count**
-  ("unfindable, unindexed, unreadable"): same chant, different clothes.
+  ("unfindable, unindexed, unreadable"). So does **Not X. Not Y. But
+  Z.** ("Not for fame. Not for glory. You posted this just because…"):
+  same chant, different clothes.
 - Universality claims ("this applies to every domain") without evidence.
   That is a claims problem; do not only cologne it.
 - Setup sentences whose only job is to announce the next sentence
@@ -181,9 +210,9 @@ not single instances.
 - **Mic-drop closers.** Short zinger fragments ending a section ("That
   was the job."). Effective in small doses; not every section may end
   on one.
-- **Intensifier repetition.** "actually," "whole," "real," "very"
-  recurring as filler. Keep only where the word marks a true contrast;
-  cut the padding uses.
+- **Intensifier repetition.** "actually," "whole," "real," "very,"
+  "really," "truly" recurring as filler. Keep only where the word marks
+  a true contrast; cut the padding uses.
 - **Em-dash furniture.** Clause-then-punchline, a dash in every heading,
   or stacks. One earned dash is not a finding. Density plus other tells
   is. Do not treat the mark as an AI tell to erase.
@@ -220,6 +249,13 @@ not single instances.
   repeat: "This is meant to live on a desktop you already leave on."
   Related to riddle labels, but at sentence level. Rewrite until a smart
   friend can say it back.
+- **Participial afterthoughts.** A present participle bolted on after
+  a comma for atmosphere: "…, looking out the window", "…, underscoring
+  the need." One earned modifier is fine. A piece that keeps attaching
+  a -ing clause to land the emotion is a template.
+- **Topic-sentence pinning.** Every paragraph opens with a neat label
+  of what it will say, then says it. One clear lead is not a finding.
+  A whole page of outline-then-body paragraphs is.
 
 ---
 
@@ -228,13 +264,14 @@ not single instances.
 | Mode | Extra watch |
 | --- | --- |
 | **Agent chat** | Honest framing, validation theater, suspense, dramatic apology, genuinely-stack, helper theater |
-| **Drafts / posts / pages** | Escalation formula, insight-labeling without evidence, setup sentences, riddle labels, cozy machinery, operator notes in the brochure, hand-holding, unparseable sentences, em-dash furniture, triad packing |
+| **Drafts / posts / pages** | Escalation formula, insight-labeling without evidence, setup sentences, cataphoric teasers, riddle labels, cozy machinery, operator notes in the brochure, hand-holding, unparseable sentences, em-dash furniture, triad packing, participial afterthoughts |
 
 The table is extra watch, not a partition. Chat theater infects drafts.
 Publish tells show up in chat.
 
 Helper theater (any model): "Great question!", "I'd be happy to", empty
-"Absolutely!", "It's important to note." Just do the work.
+"Absolutely!", "It's important to note." Performed enthusiasm
+("This is huge!", "Love this.") is the same family. Just do the work.
 
 Socratic beats and real questions aimed at a reader are method, not
 "transition question" smell. "So what does this mean for you?" as a
@@ -267,6 +304,11 @@ the loop is theater.")
 Bad: "The idea worth keeping:"  
 Good: Just state the idea.
 
+**Cataphoric teaser**  
+Bad: "Here's the part that nobody tells you: the archive was too
+scattered to hand off."  
+Good: "The archive was too scattered to hand off."
+
 **Em dash furniture**  
 Bad: "Brain — the model plus the loop."  
 Good: "Brain: the model plus the loop."
@@ -311,7 +353,8 @@ Good: "Run it on a computer you leave turned on."
 
 Keep a short file in the consuming project. It should contain:
 
-- Pronoun policy per surface (essay I, landing we, outreach I, …)
+- Pronoun policy per surface (essay I, landing we, outreach I, civic
+  as the overlay names the filer, academic as the venue uses we or I, …)
 - Terms that pass the applicability heuristic here, with one-line why
 - Protected maxims / testimony the agent must not "de-smell"
   (this package: Earn the word. Spray the prose, not the author.)
@@ -319,5 +362,5 @@ Keep a short file in the consuming project. It should contain:
 
 Do not restate the hard bans. Point at this package. Genre files in
 this package follow the same rule. They may grant a named exception
-(one concrete landing chant; talks may signpost). They may not silently
-rewrite a ban.
+(one concrete landing chant; talks may signpost; civic and academic
+may shift register). They may not silently rewrite a ban.