@agentsfleet/orly 0.10.11 → 0.10.13

package/AGENTS.md

@@ -85,6 +85,7 @@ Auto-memory is **disabled** (`autoMemoryEnabled: false` + `CLAUDE_CODE_DISABLE_A
 - Other dotfiles (`.zshrc`/`.gitconfig`/etc.): timestamped backup; minimal edits.
 - **Check a sibling repository for an existing pattern in the same language before inventing one.** A shape shipping next door is prior art; a new one needs a reason.
 - **Read the reference implementation before designing.** Where the language's dispatch page names a canonical external source, that read is mandatory in review and its guideline identifiers are cited — applied or diverged from. "Broken for us" means the delta was missed: diff our call site against theirs before blaming the principle.
+- Never publish a Claude Artifact unless asked for one in that session. Answer in the terminal.
 - Before commit/push: `gitleaks` must pass.
 - No new `make` targets without a distinct caller (CI job, spec-mandated gate, or a workflow existing targets can't express) — check `make/*.mk` first; extend over near-duplicate wrappers.
 - `*.zig` → read `dispatch/write_zig.md`; ZIG GATE fires.
@@ -288,17 +289,16 @@ Optimise for one thing: he never has to ask twice.
 - **Halve estimates before voicing.** I pad ~2x reliably.
 - **Draw when shape beats prose.** Three or more compared items, a
   before/after, a branching decision, an ordered flow, or who-points-at-what.
-  One picture, then the words.
+  One picture, then the words. A design decision opens with an ELI15 ASCII flow
+  — plain nouns, what a person does, no `file:line` — then the mechanism.
 - **No slop — chat, docs, code comments alike**. Comments say
   why, depth links out. Kill binary contrasts ("not X, it's Y" — say Y),
   throat-clearing openers, faux-insight setups, colon reveals, trailing `-ing`
   justification clauses, importance puffery, em-dash rhythm crutches, and
   fake-profound kickers. End on the clearest concrete sentence. The banned-word
   list lives in `docs/DOCUMENTATION_RULES.md` §DOC-05, §DOC-07, §DOC-14b, and
-  `orly gate verify` REPORTS it — `docs.language` prints its findings and stays
-  green, because the corpus predates the rule and a red on day one gets switched
-  off by the end of the week. Nobody fails a build over this, so the prose is
-  mine to get right.
+  `orly gate verify` REPORTS it — `docs.language` prints findings and stays
+  green. Nobody fails a build over this, so the prose is mine to get right.
 
 ## Reading Indy
 

package/SOUL.md

@@ -37,17 +37,16 @@ Optimise for one thing: he never has to ask twice.
 - **Halve estimates before voicing.** I pad ~2x reliably.
 - **Draw when shape beats prose.** Three or more compared items, a
   before/after, a branching decision, an ordered flow, or who-points-at-what.
-  One picture, then the words.
+  One picture, then the words. A design decision opens with an ELI15 ASCII flow
+  — plain nouns, what a person does, no `file:line` — then the mechanism.
 - **No slop — chat, docs, code comments alike**. Comments say
   why, depth links out. Kill binary contrasts ("not X, it's Y" — say Y),
   throat-clearing openers, faux-insight setups, colon reveals, trailing `-ing`
   justification clauses, importance puffery, em-dash rhythm crutches, and
   fake-profound kickers. End on the clearest concrete sentence. The banned-word
   list lives in `docs/DOCUMENTATION_RULES.md` §DOC-05, §DOC-07, §DOC-14b, and
-  `orly gate verify` REPORTS it — `docs.language` prints its findings and stays
-  green, because the corpus predates the rule and a red on day one gets switched
-  off by the end of the week. Nobody fails a build over this, so the prose is
-  mine to get right.
+  `orly gate verify` REPORTS it — `docs.language` prints findings and stays
+  green. Nobody fails a build over this, so the prose is mine to get right.
 
 ## Reading Indy
 

package/core/operating-model.md

@@ -85,6 +85,7 @@ Auto-memory is **disabled** (`autoMemoryEnabled: false` + `CLAUDE_CODE_DISABLE_A
 - Other dotfiles (`.zshrc`/`.gitconfig`/etc.): timestamped backup; minimal edits.
 - **Check a sibling repository for an existing pattern in the same language before inventing one.** A shape shipping next door is prior art; a new one needs a reason.
 - **Read the reference implementation before designing.** Where the language's dispatch page names a canonical external source, that read is mandatory in review and its guideline identifiers are cited — applied or diverged from. "Broken for us" means the delta was missed: diff our call site against theirs before blaming the principle.
+- Never publish a Claude Artifact unless asked for one in that session. Answer in the terminal.
 - Before commit/push: `gitleaks` must pass.
 - No new `make` targets without a distinct caller (CI job, spec-mandated gate, or a workflow existing targets can't express) — check `make/*.mk` first; extend over near-duplicate wrappers.
 - `*.zig` → read `dispatch/write_zig.md`; ZIG GATE fires. <!-- oracle-packs:language.zig -->

package/dispatch/write_changelog.md

@@ -40,10 +40,9 @@ a gate skip.
   names, money amounts stay verbatim.
 - **Internal cleanup** gets aggressive trimming, not a paragraph.
 - **History is archived, not rewritten** — past entries are an immutable record.
-- **Rate constants** are pinned by `cross_runtime_rates.rs`, which reads the
-  app and Command-Line Interface (CLI) mirrors against the Rust constant. A
-  changelog money or rate claim must match those, and `rates.mdx` in the docs
-  repository, which no test can reach.
+- **Rate constants** are declared once, in `afd_billing`'s `nanos.rs`, with the
+  nanos denominator in `afd_core::money`. A changelog money or rate claim must
+  match those — and `rates.mdx` in the docs repository, which no test reaches.
 
 ## Required output (self-audit line before committing the changelog)
 

package/docs/CHANGELOG_VOICE.md

@@ -14,5 +14,5 @@ Editing `~/Projects/docs/changelog.mdx` or any other Mintlify `<Update>` block.
 - **Internal cleanup / refactor entries get the most aggressive trimming.** One lead paragraph + one bullet list. Skip "Test coverage" sections unless the test count is the headline. Indy's exact direction: *"Keep internal code cleanup, refactor to a minimal."*
 - **Never drop load-bearing facts.** Error codes (`UZ-AUTH-003`), endpoint paths + method + body shape + status code, env var names + defaults, schema column / table names, CLI subcommand + flag names, migration steps, money amounts. Tighten prose, not meaning.
 - **Historical entries are archives.** Brevity-pass them; never rewrite the past. A typo correction (e.g. `$0.001` → `$0.01` when it was never true) is allowed and must be called out in the commit message.
-- **Rate constants stay pinned across the runtime surfaces, and a test says so.** `rustd/crates/afd_billing/tests/cross_runtime_rates.rs` reads `ui/packages/app/lib/types.ts` and `cli/src/constants/billing.ts` and fails when either drifts from `rustd/crates/afd_billing/src/nanos.rs` — a test beside the constant it defends, not a gate nothing invokes. Public docs are the one surface it cannot reach: when a rate changes, update `~/Projects/docs/snippets/rates.mdx` in a paired Pull Request (PR). In `*.mdx`, import its named values rather than hand-typing money amounts.
+- **Rate constants are declared once, so a money claim has one thing to match.** `rustd/crates/afd_billing/src/nanos.rs` holds the rates and `afd_core::money` holds the nanos denominator; the daemon charges from them and every client renders the figure it was served. A changelog rate or money claim is checked against those constants, never against a client. Public docs are the surface nothing reaches: when a rate changes, update `~/Projects/docs/snippets/rates.mdx` in a paired Pull Request (PR). In `*.mdx`, import its named values rather than hand-typing money amounts.
 - **The Mintlify reference Indy pasted (May 1 / May 8 entries) is canonical voice.** Mirror its rhythm, not its product nouns.

package/docs/RULE_ENFORCEMENT.md

@@ -11,10 +11,10 @@ regenerates this file and fails on any difference. To update it, run
 | `docs/SCHEMA_CONVENTIONS.md` | — | 0 | 0 | 0/16 | mechanical |
 | `docs/DOCUMENTATION_RULES.md` | — | 0 | 0 | 0/22 | latent |
 | `docs/LIFECYCLE_PATTERNS.md` | — | 0 | 0 | 0/22 | mechanical |
-| `docs/CHANGELOG_VOICE.md` | — | 0 | 0 | 0/3 | latent |
+| `docs/CHANGELOG_VOICE.md` | — | 0 | 0 | 0/4 | latent |
 | `docs/VERIFY_TIERS.md` | — | 0 | 0 | 0/4 | uncited |
 | `docs/greptile-learnings/RULES.md` | — | 0 | 0 | 0/114 | mechanical |
-| **corpus** | | | | **30/276** | |
+| **corpus** | | | | **30/277** | |
 
 ## How to read this
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agentsfleet/orly",
-  "version": "0.10.11",
+  "version": "0.10.13",
   "description": "Repository-scoped engineering harness: renders agent rules, materialises the gates that enforce them, and proves the PR boundary \u2014 for any coding agent.",
   "license": "MIT",
   "type": "module",