aibreze 0.1.2 → 0.1.4

package/README.md

@@ -1,3 +1,7 @@
+<p align="center">
+  <img src="site/static/logo.svg" alt="aiBreze" width="128" />
+</p>
+
 # aiBreze
 
 An installable writing rule set for AI agents.
@@ -23,9 +27,9 @@ 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.
-Not a CLI (yet), not an editor, not a list of "words ChatGPT uses."
+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)
@@ -41,12 +45,11 @@ 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 load-bearing idea. 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.
+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 heuristic is the rule; the
-list is not exhaustive.
+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.
@@ -90,10 +93,9 @@ 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
-is the layered law: genre surfaces, an applicability heuristic (earn the
-word), claims before cologne, overlays instead of forks, and both
-prevention at draft time and audit after. Authorship is irrelevant. Prose
-quality is the subject.
+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.
 
 ## Use from Node
 
@@ -142,7 +144,9 @@ pnpm site:build
 
 ## Publishing to npm
 
-The maintainer publishes. Agents must not run `npm publish`,
+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`.
 
 ## License

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "aibreze",
-  "version": "0.1.2",
+  "version": "0.1.4",
   "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.",
@@ -48,7 +48,7 @@
   },
   "scripts": {
     "build": "tsc",
-    "test": "tsc && node --test dist/index.test.js",
+    "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",

package/rules/audit.md

@@ -55,7 +55,9 @@ 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
 vocab, helper theater, signpost openers, mic-drop closers, intensifier
-filler, parallel-zinger density, bold-lead lists. Apply the
+filler, parallel-zinger density, bold-lead lists, riddle labels, cozy
+machinery, operator notes in the brochure, hand-holding the obvious,
+unparseable sentences. 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,

package/rules/claims.md

@@ -122,7 +122,9 @@ Only after Passes A-D:
    validation+profundity, narrative theater, setup-only
    sentences, synonym antithesis, helper theater.
 3. Flag cadence budgets: signpost openers, mic-drop closers, intensifier
-   filler, em-dash furniture, parallel-zinger density, bold-lead lists.
+   filler, em-dash furniture, parallel-zinger density, bold-lead lists,
+   riddle labels, cozy machinery, operator notes in the brochure,
+   hand-holding the obvious, unparseable sentences.
 4. Apply **corpus-applicability**: do not "correct" overlay terms when
    they are structural.
 5. Quote lines to **protect** (distinctive human voice).

package/rules/core.md

@@ -192,6 +192,34 @@ not single instances.
   protect native pairs, trim assistant-added ones first.
 - **Bold-lead lists.** Every bullet "**Label.** Explanation" is a
   template when the whole piece does it.
+- **Riddle labels.** A bold lead-in or heading that is an aphorism the
+  reader can only decode after reading the body: "**Names you actually
+  say.**" over a paragraph about custom vocabulary. Core already bans the
+  setup sentence that announces the next sentence; this is the same waste
+  in reverse, withholding instead of announcing. Test: cover the body and
+  read the label alone. If it does not say which thing this is, name the
+  thing. The aphorism can go in the prose if it earns a place there.
+- **Cozy machinery.** Infrastructure written the way a fond craftsman
+  would talk: the model is "asleep," a worker stays "warm," heavy jobs go
+  to a "quieter" box, "the mesh is the door." Terms of art pass the
+  applicability heuristic (warm cache, cold start, daemon), and one idiom
+  is not a finding. The tell is the register standing in for a fact the
+  writer already has: "asleep" covers suspended, unreachable, and
+  misconfigured at once, so it tells the reader less than "unreachable"
+  would. Keep it where the machine literally sleeps.
+- **Operator notes in the brochure.** Recovery commands, internal folder
+  names, settle timers, gitignore facts, and "doctor and /health run the
+  same probes" listed as what the product is good at. The tell is
+  *placement*, not the fact. A recovery CLI belongs under Run. A Syncthing
+  wait belongs next to Syncthing. Test: would you say this first to a
+  friend who asked what it does? If not, it is later, or not at all.
+- **Hand-holding the obvious.** "config.json is gitignored." One trap
+  warning is fine. Stating what a competent reader already knows, in the
+  voice of a tour guide, is the tell.
+- **Unparseable sentence.** A finished-sounding line the reader cannot
+  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.
 
 ---
 
@@ -200,7 +228,7 @@ 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, em-dash furniture, triad packing |
+| **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 |
 
 The table is extra watch, not a partition. Chat theater infects drafts.
 Publish tells show up in chat.
@@ -243,6 +271,29 @@ Good: Just state the idea.
 Bad: "Brain — the model plus the loop."  
 Good: "Brain: the model plus the loop."
 
+**Riddle label**  
+Bad: "**Names you actually say.** `promptTerms` seeds the decoder."  
+Good: "**Custom vocabulary.** `promptTerms` seeds the decoder."
+
+**Cozy machinery**  
+Bad: "If the cleanup model is asleep, you still get raw text."  
+Good: "If the cleanup model is unreachable, you still get raw text."  
+(Still fine: "the laptop was asleep," when it was.)
+
+**Operator notes in the brochure**  
+Bad: "**Two settle timers.** Watched folders wait 30 minutes." as the
+first item under "What it is good at."  
+Good: Mention the wait next to Syncthing. Lead the feature list with
+what a friend would hear first.
+
+**Hand-holding**  
+Bad: "`config.json` is gitignored." after `cp config.example.json`.  
+Good: Omit it. They already copied the example.
+
+**Unparseable sentence**  
+Bad: "This is meant to live on a desktop you already leave on."  
+Good: "Run it on a computer you leave turned on."
+
 ---
 
 ## How to audit

package/rules/cursor.mdc

@@ -55,6 +55,19 @@ Earn the word.
   finding.
 - Parallel-zinger (chiasmus) density; trim assistant-added ones first.
 - Bold-lead lists on every bullet.
+- Riddle labels: a bold lead-in or heading the reader can only decode
+  after the body ("**Names you actually say.**" over custom vocabulary).
+  Name the thing instead.
+- Cozy machinery: the model is "asleep," the worker stays "warm," a
+  "quieter" box. Terms of art pass; the tell is register replacing a fact
+  you have ("unreachable" says more than "asleep").
+- Operator notes in the brochure: recovery CLIs, internal folder names,
+  settle timers, gitignore facts listed as what the product is good at.
+  Placement is the tell. Would you say this first to a friend?
+- Hand-holding the obvious: "config.json is gitignored" after they
+  already copied the example.
+- Unparseable sentence: a finished-sounding line the reader cannot
+  repeat ("a desktop you already leave on").
 
 ## Corpus-applicability carve-out (standing rule)