aibreze 0.1.6 → 0.1.8

package/README.md

@@ -6,60 +6,13 @@
 
 An installable writing rule set for AI agents.
 
-Editorial rules for prose that actually says something instead of just
-sounding like it. AI-assisted or not.
-Written **aiBreze**. npm **`aibreze`**. A spray, not a breeze.
-
-Direct > clever. Clear > profound. Useful > insightful-sounding. Em dashes
-earn their place; most don't.
+Editorial rules for prose that says something instead of sounding like it.
+AI-assisted or not. Written **aiBreze**. npm **`aibreze`**. A spray, not a
+breeze.
 
 Spray the prose, not the author. Earn the word.
 
-## Before / after
-
-**Before.** At its core, building software isn't just about writing
-code. It's about bridging the gap between imagination and execution,
-creating solutions that don't merely function but fundamentally
-transform the way we interact with technology.
-
-**After.** Software turns an idea into something people can use. Good
-software does that reliably.
-
-## What it is
-
-A composable editorial system for agent-generated prose, and for human
-prose in the same register. Markdown you install and point an agent at.
-v1 has no CLI.
-
-```text
-core.md          shared law (register, bans, cadence, heuristic)
-genre files      surface extras only (essay, landing, outreach, launch)
-project overlay  pronouns, carve-outs, protected lines
-                 ↓
-drafting
-                 ↓
-audit.md         smell
-claims.md        substance first, then voice
-```
-
-Genre files assume `core.md` and are additive: surface law only, no
-copied bans. Do not fork `core.md`.
-
-The **applicability heuristic** is the rule. The problem is unearned
-language, not the dictionary. Earn the word: "transformative" is fine
-if something transformed and you can say from what into what.
-"Inflection point" is fine if there was one. Overlay the terms that
-usually pass *here*, with one-line why. The list is not exhaustive.
-
-`claims.md` is substance first, voice after. A clean-smelling wrong
-essay is still wrong. Do not polish a lie.
-
-Cadence tells are a budget, not a ban. Flag density: signpost openers,
-em-dash furniture, riddle labels (a heading you can only decode after
-the body), cozy machinery (register standing in for a fact you have),
-operator notes in the brochure, hand-holding the obvious, unparseable
-sentences. One earned em dash is not a finding. Do not treat the mark
-as an AI tell to erase.
+**Docs:** [aibreze.com/docs](https://aibreze.com/docs) · **Site:** [aibreze.com](https://aibreze.com)
 
 ## Install
 
@@ -67,107 +20,34 @@ as an AI tell to erase.
 pnpm add -D aibreze
 ```
 
-## What's in the box
-
-| File | Use |
-| --- | --- |
-| `rules/core.md` | Always. Register, applicability heuristic, teaching antithesis, hard bans, cadence budgets (density, not single uses), chat vs publish. |
-| `rules/audit.md` | Paste-in smell audit (score, flags, protect list, top 5). |
-| `rules/claims.md` | Skeptical peer review. Substance first, voice after. |
-| `rules/essays.md` | Longform: one register, author in the essay, concrete instance. Not for reference docs. |
-| `rules/landing.md` | Page copy: pronouns, rhetorical budgets, substance, read-aloud. |
-| `rules/outreach.md` | Email / DM / text. Relationship first, one ask. |
-| `rules/launch.md` | Shipping posts. Open on a specific moment or the artifact, not the announcement formula. |
-| `rules/cursor.mdc` | Always-on agent digest. Copy into `.cursor/rules/`. |
-| `skills/aibreze/` | Host-agnostic skill. Copy into `.claude/skills/` or `.cursor/skills/`. |
-
-## Why "aiBreze"?
-
-People who live with a smell stop noticing it. Generated prose does the
-same trick. Charles Duhigg tells the household version in *The Power of
-Habit* (2012): an odor-eliminating spray that flopped until the company
-realized habituation was the problem, then sold the bottle as the reward
-at the end of a cleaning habit. This package is that move for writing.
-Make the smell visible, then take it off. Read Duhigg for the original.
+Copy `node_modules/aibreze/rules/cursor.mdc` to `.cursor/rules/aibreze.mdc`.
+Keep a short overlay. Full wiring: [docs](https://aibreze.com/docs/install).
 
-The register is also leaking the other way: humans now write like the
-models. aiBreze is a writing standard, not an AI-cleanup gimmick.
+Or skip npm and [install the skill](https://aibreze.com/skill) as a folder.
 
 ## Not a humanizer
 
-aiBreze does not determine whether a human or a model wrote something,
-and it does not try to fool AI detectors. It applies the same standard
-either way. If the prose smells, spray it.
+aiBreze does not determine whether a human or a model wrote something, and it
+does not try to fool AI detectors. Same standard either way. If the prose
+smells, spray it.
 
-Adjacent tools tend to be humanizers ("make this sound human"), banned-word
-anti-slop lists, or general style linters (Vale, write-good). This package
-layers genre files, an earn-the-word test, claims before voice, and overlays
-instead of forks. Use it while drafting or on a finished pass. Authorship
-is irrelevant. Prose quality is the subject.
+<!-- xfacts-nutrition-label -->
 
-## Use from Node
+## Nutrition label
 
-```ts
-import { readRule, files, catalog } from "aibreze";
+- **AppFacts:** [viewer](https://appfacts.dev/v#af1.eNp1kU1rAyEQhv_KMmeTpVePDRRa0l42t1LKrE6Mjaui4xYb8t-Lu6GQQ29-PO_H6AVmkA8CPE4EEtA-JvohEMA1tgNnx4SpgoDMyCU3RrGdG-KsIp8b9fp8WAl1BnkBh94UNO3mUCMNKtnIonvBGdc1CEjFs10y34Km7VdeDKqz3oCE3TCAgFPIfNu7UPTRYWq5EdUZDX1O6NFQAgnRxwmuAjTFDPL9Ah4kfCf0xlFqijuLTlN0oU7kGa5ihQ3x0TqKiXK-CXRQpTHINvhuDVs1HwLyrP6C7sq1OrfeHXrdkTbUqTDFsozStGOxTrd3-n-QRDFkyyHVZsccs-x7Y_lUxq0KU79DRlczb55CMrTZ73c92nH5uusvQqie3Q) · [raw](https://github.com/Catalyst-Forge-LLC/aibreze/blob/main/APP_FACTS.md)
+- **SkillFacts:** [viewer](https://skillfacts.dev/v#sf1.eNq9VE1v2zgQ_SsD9dIYlu3mECzU0_Yji2DTIkCCvViBQUu0RUQiBZKy4Gbzu3rvL-vMUJLt2AHSHoogcTxfnHnz3jxGmyh5N460qGSUREItrfwmo3GUy40sTS0tWj8KL8qt83Bp7JqcG2mdMhpds8m7yQVanBe-cVQh82pDMaXKpHZU9MvVHX5_UDrHL1ljnbGxe1Blida6sbXhqM-58sYqUYJtSulgZSzUzbJUrhDLUkJtMe49uNqK7RhEg-H4ofM-KK6Fc9Aa-7AqTRvy_76K0aiclzm0Vnml1_SmNRuphc7w2cfImcbSf1Hhfe2S6XStfNEsJ5mppv3gMQ8eX19_nO4Q6t49hdDTOFLaedsgGEa7hZUiK_ixQuLYSaSNphJaemoYDaqqSyVztK0UTo-lZIVmTMypmjempDIraSX2jUDO78fRstF5KfOFsF6tEHjEf_4Y1cIXlEooTjNj5aTKd_gbTx0_jZ_FMZ6vCcxKoSp3KhIbkmsrnaNBvSxlJb3d7obNpcMFCEaE-sexClPJWqz30e_wJfgxx0pkB_Fi-xsLsqLFrDiOU810WzBGi468CaTM3lkapZron0CXmuqB_AkcbjbVz7IvKDuQH_OZ-6nuqJ8AMj_VhFIC-7xPdUd7qvKHeE999nAncALtVO_A3gW8CmucZ5BUkmqAoKlfrgIwaOoY-GNBhadIUQkQx-hrp6gEOkGRbaeoBEhQqX4uJ640v0_1kaLYEwNJIIEDSZEDICyXFXAc2YvqFaGDrE7EBlVxJ4OsdhPvyyrhIdZSSyt8N1aO_yVwPju_iGd_xeczsnURBmEukEqxaHyBU-HjGf5V3dhDnUWrqNN-m8xhRmeCQqHIZaNKv1huic-He8Mx-7S2bSdZ51yRj_lAvGSJpvoN3FJluKTSmDjwItX_A_7gB0byL1lGo0-9TEcj9D97uIv5L-iVI1iwveOWRcv2oNvecR3Uyx4UcG_-F1fCtn0lkzPVoy9iCyvps2IgcM57DdSDlTUV7EkNhAMBpcBecbPG-vdh1a1ykhnqoDRZfxGmkxGj8wZuwtWgb3_qanQPD_J-aRm3rHh0_JLkA7Y3vehPLpEbuNoTP7D4X2yE7gHaSR6h_NdwEtDW3YRgvhyuAnoI9OGxO7oOsLsOZH5L9c66gA_hSsBwJUIzN6hnrEVEOWrr4HRgEO8b9lz9rTjlG47DvpM7-cyn4SUs7vprcYDHp72DgY4wWajIQhz90-seSPcwZ1WyKO_fnr4BZ_DjO6KCRwCWW5gfLnGXdPoCnCG9o6efXsK6pA) · [raw](https://github.com/Catalyst-Forge-LLC/aibreze/blob/main/skills/aibreze/SKILL_FACTS.md)
 
-const core = readRule("core");
-// files.audit is an absolute path to rules/audit.md
-```
-
-Markdown is also exported as `aibreze/rules/core.md` (and the rest), so
-an agent or a prompt assembler can read the files from `node_modules`.
-v1 is `readRule`. Assembling core + genre + overlay is concatenation on
-purpose.
-
-## Agent setup
-
-1. `pnpm add -D aibreze`
-2. Copy `node_modules/aibreze/rules/cursor.mdc` to
-   `.cursor/rules/aibreze.mdc`
-3. Point "Full rules" at `node_modules/aibreze/rules/core.md`
-4. Keep a project overlay (carve-outs, I vs we, protected lines)
-5. When drafting a page, essay, note, or ship post, open that genre file
-6. For a publish pass: paste `rules/core.md` plus the overlay, then
-   `rules/audit.md` or `rules/claims.md` (both are additive; do not paste
-   the prompt alone)
-
-## Skill
-
-Host-agnostic `SKILL.md` for Claude Code and anything else that loads a
-named folder. Raw file on the site:
-
-https://aibreze.com/skills/aibreze/SKILL.md
-
-Copy `skills/aibreze/` (or `node_modules/aibreze/skills/aibreze/`) to
-`~/.claude/skills/aibreze/`, `.claude/skills/aibreze/`, or
-`.cursor/skills/aibreze/`. Full law is next to it on
-https://aibreze.com/rules/core.md.
-
-## Overlay shape
-
-Keep it short. Point at this package, then only:
-
-- Pronouns per surface
-- Terms that pass the applicability heuristic *here*, with one-line why
-- Protected maxims / testimony
-- Genre extras that are house law (every essay ends in a deed, brand
-  metaphor budget, …)
-
-## Site
-
-The public site lives in [`site/`](site/) (FilePress, [`getfilepress`](https://www.npmjs.com/package/getfilepress)). [aibreze.com](https://aibreze.com). Source: [Catalyst-Forge-LLC/aibreze](https://github.com/Catalyst-Forge-LLC/aibreze).
+## Development
 
 ```bash
+pnpm install
+pnpm test
 pnpm site:dev
-pnpm site:build
 ```
 
-## Publishing to npm
-
-The maintainer publishes. `pnpm publish` runs a gate first: `pnpm whoami`,
-then `pnpm login` if that fails, then a patch bump if this version is
-already on npm (or behind it). Agents must not run `npm publish`,
-`pnpm publish`, or `yarn npm publish`.
+Site (FilePress + docs mount): `pnpm ship`. The maintainer publishes to npm.
+Agents must not run `npm publish`.
 
 ## License
 

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,6 +1,6 @@
 {
   "name": "aibreze",
-  "version": "0.1.6",
+  "version": "0.1.8",
   "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.",

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:
 

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,7 @@ 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`, `cursor.mdc` (agent pocket card).
 
 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 +48,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.
@@ -311,7 +325,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 +334,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.

package/rules/cursor.mdc

@@ -16,10 +16,11 @@ not copy genre law into this file.
 
 ## Target
 
-Sharp, slightly tired colleague. Direct > clever. Clear > profound.
-Useful > insightful-sounding. Em dashes earn their place; most don't.
-Judge the sentence, not the byline. Spray the prose, not the author.
-Earn the word.
+Sharp, slightly tired colleague. Default register, not the only one.
+Direct > clever. Clear > profound. Useful > insightful-sounding. Em
+dashes earn their place; most don't. Judge the sentence, not the
+byline. Spray the prose, not the author. Earn the word. Filings:
+[`civic.md`](./civic.md). Papers: [`academic.md`](./academic.md).
 
 ## Hard bans
 
@@ -93,6 +94,8 @@ digest.
 - Essay / talk / long argument: [`essays.md`](./essays.md)
 - Email / DM / text to someone you know: [`outreach.md`](./outreach.md)
 - Ship post / announcement: [`launch.md`](./launch.md)
+- Filing / testimony / legal-adjacent: [`civic.md`](./civic.md)
+- Paper / methods / lit review: [`academic.md`](./academic.md)
 
 Reference docs, changelogs, API pages, UI chrome: core only. Do not
 inject a scene to satisfy essay law.

package/rules/essays.md

@@ -5,7 +5,8 @@ essays, talks, and other long argumentative prose.
 
 It is not the file for reference docs, changelogs, API pages, or UI
 chrome. Those get core only. Same house register is fine. Required
-anecdote is not.
+anecdote is not. Journal articles and working papers use
+[`academic.md`](./academic.md), not this file's scene rule.
 
 ---