@azure-id/orc 1.6.0 → 1.7.1

package/templates/skills/_shared/rules/writing.md

@@ -0,0 +1,223 @@
+<!-- orc-rules:pack id=writing prefix=OSW layer=writing -->
+
+# ORC RULES · Writing (`OSW`)
+
+> **READ-ONLY.** This file ships with ORC and changes only with `orc update`.
+> Your own rules go in `.claude/orc/rules.md` (`orc rules add --priority P0
+> --text "…"`), and **yours win** wherever the two disagree.
+
+**Applies to** every word an agent writes: wiki docs, analysis reports, plans,
+requirement specs, commit bodies, PR descriptions, and what it says in chat.
+
+**Source.** Peter G. Yang — [`petergyang/no-ai-slop`](https://github.com/petergyang/no-ai-slop) (MIT) ·
+Miqdad Badjuber — [`miqdadbadjuber/anti-slop`](https://github.com/miqdadbadjuber/anti-slop), the `antislop-copywriting` skill (MIT) ·
+Matty Cartwright — [The Anti-Slop Writing Rules](https://mattycartwright.com/blog/the-anti-slop-writing-rules).
+Full attribution in `CREDITS.md`.
+
+**Tiers.** `HARD` absolute · `PURPOSE` allowed with a written one-line reason ·
+`LOCK` a consistency requirement, reported but never blocking.
+
+---
+
+### OSW-01 · HARD · Lead with the point
+
+No throat-clearing opener. Cut "Here's the thing", "Here's what I mean", "Let me
+be clear", "I'll be honest", "The uncomfortable truth is". State the point.
+
+Keep a personal aside, a story or an admission when it creates context or
+tension. The ban is on the empty run-up, not on character.
+
+### OSW-02 · HARD · No binary contrast
+
+Cut "It's not X, it's Y", "The question isn't X, it's Y", "It's not just X but
+Y", and negative listing ("Not a X. Not a Y. A Z."). State Y directly.
+
+"The question isn't the model. It's the eval." becomes "The eval matters more
+than the model."
+
+### OSW-03 · HARD · No faux-insight setup
+
+Cut "What nobody tells you", "the part everyone misses", "what most people get
+wrong", "this is the part most people skip". The setup flatters the writer and
+carries no information. Make the claim stand on its own.
+
+### OSW-04 · LOCK · No colon reveal
+
+A noun phrase, a colon, then a dramatic lowercase reveal is a generated shape:
+"The detail that makes it work: a separate agent grades it." Rewrite as a plain
+sentence. Colons are for lists, labels and quotes.
+
+### OSW-05 · HARD · No fake-profound kicker, no summary recap
+
+Cut the final "deep" line that turns the point into an aphorism or a mic drop.
+Do not rewrite it into a better metaphor. Delete it.
+
+Cut "In conclusion", "Ultimately", "Overall" and the closing paragraph that
+restates the piece. End on the last concrete point, the takeaway, or the next
+action.
+
+### OSW-06 · HARD · No importance puffery
+
+Cut "marks a pivotal moment", "underscores its significance", "plays a vital
+role", "stands as a testament", "solidifies its position". State the fact and
+let the reader judge whether it matters.
+
+"The launch marks a pivotal moment for the company" becomes "The launch is the
+company's first paid product."
+
+### OSW-07 · HARD · No `-ing` pseudo-analysis
+
+Cut trailing clauses that pretend to explain meaning: "highlighting",
+"underscoring", "reflecting", "showcasing", "demonstrating". Replace with the
+actual consequence.
+
+"The launch adds file search, highlighting the team's commitment to workflows"
+becomes "The launch adds file search, so users find old drafts without leaving
+the editor."
+
+### OSW-08 · HARD · No weasel attribution
+
+Cut "experts agree", "studies show", "industry reports suggest", "many argue",
+"widely regarded as". Name the source, or cut the claim. If there is no source,
+ask. Never invent one.
+
+### OSW-09 · LOCK · No synonym cycling
+
+If the clear word is right, repeat it. Do not rotate terms for style. "The agent
+reviews the draft. The assistant scores the piece. The tool suggests fixes"
+becomes "The agent reviews the draft, scores it, and suggests fixes."
+
+This matters more in technical writing than anywhere else: a second name for one
+thing reads as a second thing.
+
+### OSW-10 · HARD · Banned lexicon
+
+Never use, in any output: delve · leverage · utilize · facilitate · empower ·
+streamline · robust · cutting-edge · paradigm shift · game changer · tapestry ·
+realm · beacon · multifaceted · meticulous · intricate · paramount ·
+transformative · elevate · embark · supercharge · harness · ever-evolving ·
+seamless · unleash · pivotal.
+
+Use the plain word. "Utilize" is "use". "Leverage" is "use". "Facilitate" is
+"help" or the verb for what actually happens.
+
+Checked by `orc rules lint`.
+
+### OSW-11 · HARD · Banned phrases
+
+Never use: "it's worth noting" · "it's important to note" · "at the end of the
+day" · "when it comes to" · "at its core" · "in today's world" · "in the age
+of" · "in the world of" · "the reality is" · "the truth is" · "in terms of" ·
+"with regard to" · "going forward" · "let's dive in" · "in this article".
+
+Every one of them delays the point by a clause. Delete the clause and keep the
+point.
+
+Checked by `orc rules lint`.
+
+### OSW-12 · PURPOSE · Hedge adverbs earn their place
+
+Cut when they add nothing: just · literally · honestly · simply · actually ·
+truly · fundamentally · importantly · crucially · inherently · inevitably.
+
+Keep one when it carries real uncertainty, a real contrast, or the writer's own
+rhythm. That is the written reason.
+
+### OSW-13 · PURPOSE · Em dash dose cap
+
+This is a **dose rule, not a ban.** The em dash is a real punctuation mark and
+ORC's own documentation uses it.
+
+- Short output (a chat answer, a commit body, a CTA, a label): none.
+- A long document: at most two per thousand words, and only where the dash
+  clearly beats a comma, a period or parentheses.
+- Never as a rhythm crutch, and never in clusters.
+
+`orc rules lint` reports **density**, not presence.
+
+### OSW-14 · LOCK · No rule-of-three padding
+
+Three items only when there are three items. Do not invent a third to complete
+the cadence, and do not drop a fourth to preserve it.
+
+### OSW-15 · HARD · No staccato drama
+
+Cut "X. And Y. And Z.", "That's it. That's the whole thing.", and stacked punchy
+fragments. Use complete sentences. Vary sentence shape only when it helps the
+point.
+
+### OSW-16 · HARD · No rhetorical setup
+
+Cut "What if I told you…", "Think about it:", "Plot twist:", and self-answered
+"Question? Answer." pairs. Make the point.
+
+### OSW-17 · HARD · No interpretive metadiscourse
+
+Cut lines that step outside the subject to tell the reader what to notice: "That
+last part matters more than it sounds", "The key point is", "As you can see",
+"This distinction matters", and a redundant "In other words".
+
+If the point is clear, delete the aside. If it is not, add the fact that would
+make it clear.
+
+### OSW-18 · LOCK · No formatting slop
+
+- No emoji in a heading (checked by `orc rules lint`).
+- No bold sprinkled mid-sentence for emphasis.
+- No heading over a two-sentence section.
+- No bullet list where two sentences of prose read better.
+- No table with one column of real content.
+
+Format follows the content. It does not decorate it.
+
+### OSW-19 · LOCK · Active voice, real actors
+
+"The team shipped it Tuesday" beats "the decision emerged". Never let an
+inanimate thing do a human verb: an architecture does not believe, a module does
+not want, a decision does not emerge.
+
+Passive voice is allowed when the actor is genuinely unknown or genuinely
+irrelevant, and only then.
+
+### OSW-20 · LOCK · The portability test
+
+If a sentence could move unchanged to another project, another company or
+another product, it is filler. Replace it with a fact, a mechanism, a
+consequence, or a judgement specific to this subject. Otherwise cut it.
+
+### OSW-21 · LOCK · Concrete beats abstract
+
+Names, numbers, dates, file paths, commands, error codes and examples beat
+abstractions. "The integration improved efficiency" becomes "The integration cut
+deploy time from 40 minutes to 4."
+
+Protect the specific fact. Never smooth a useful detail into generic importance.
+
+### OSW-22 · HARD · A human's paragraph is not yours to restyle
+
+Never rewrite user-authored prose to match this pack. Preserve the writer's
+vocabulary, bluntness, humour, digressions and level of polish.
+
+This rule beats every other rule in this file. A pack that flattens the human
+voice it was written to protect has failed.
+
+### OSW-23 · HARD · Never invent a specific
+
+No invented number, date, name, version, benchmark or range. No "anywhere from X
+to Y" that nothing measured. No filled-in gap presented as a fact.
+
+If the number is needed and unknown, say it is unknown, or ask.
+
+---
+
+## Not a ban — keep these
+
+Never cut, in the name of this pack:
+
+- A load-bearing caveat about scope, risk or uncertainty (see `delivery.md`, OSD-04).
+- A named source, a file path, a command, an error code, a version.
+- The user's own words, anywhere (OSW-22).
+- A hedge that reports real uncertainty rather than decorating a claim.
+
+**Removing slop leaves a void.** The fix for flat prose is never more bans — it
+is a fact, a mechanism, or a consequence the reader did not have.

package/templates/skills/context-combiner/SKILL.md

@@ -211,4 +211,12 @@ exit code, and never re-derive a state word — the CLI's state words are the on
 state words, and **an exit code is an ANSWER wherever that contract says so, not
 a failure**. A call the answer does not name is a call this lane does not make.
 Exit ≠ 0 from the catalogue itself → say the CLI is unavailable and name the
-command you are about to run, out loud, before running it.
+command you are about to run, out loud, before running it.
+
+## Rules — the anti-slop card (`../_shared/phases/rules.md`)
+
+`orc rules slice --lane context-combiner --json` is the ONLY assembler; never build
+the card here. It rides under the house rules and above the task —
+**house rules > your project's rules > ORC's own packs** — and its `line` prints
+VERBATIM at preflight. Returns gain `rules_applied[]`, `rules_conflicts[]` (a gap,
+never a silent choice) and `rules_overridden[]`.

package/templates/skills/orc/SKILL.md

@@ -111,6 +111,13 @@ the CLI is unavailable and fall back to `../_shared/config-precedence.md`'s
 documented defaults, out loud. Priorities and families:
 `../_shared/config-precedence.md`.
 
+## Rules — the anti-slop card (`../_shared/phases/rules.md`)
+
+`orc rules slice --lane orc --json` is the ONLY assembler; never build
+the card here. It rides under the house rules and above the task —
+**house rules > your project's rules > ORC's own packs** — and its `line` prints
+VERBATIM at preflight. Returns gain `rules_applied[]`, `rules_conflicts[]` (a gap,
+never a silent choice) and `rules_overridden[]`.
 ## Calls
 
 **ONE catalogue, and it is not you:** `orc lane calls orc --json` names every
@@ -191,7 +198,7 @@ them; they are never dispatched as subagents).
 - Phase 1 wiki grounding → `../_shared/phases/wiki-consult.md` + `references/preflight-report.md`
 - Phase 2 → `references/effort-and-mode.md`; tagging → `references/pattern-gate.md`
 - Phase 3 → `../_shared/phases/wave-grouping.md` + `log-protocol.md` + `../_shared/phases/house-rules.md`
-  + `pattern-gate.md` (resolve gate); workers → `subskills/orc-execution/`;
+  + `../_shared/phases/rules.md` (the `rules_card` rides every slice) + `pattern-gate.md` (resolve gate); workers → `subskills/orc-execution/`;
   stops → `subskills/orc-checkpoint/SKILL.md` + `../_shared/phases/stop-resume.md`
 - Phase 5–6 → `subskills/orc-review-verify/`; FE tasks →
   `../orc-pattern/references/fe-a11y.md` + `fe-perf.md` (as `fe_rules[]`)

package/templates/skills/orc/references/preflight-report.md

@@ -21,6 +21,7 @@ pattern:   js cached · ts cached
 gotchas:   12 known · 3 match this change's files
 pact:      11 holding · 2 drifted · 3 uncheckable
 bound:     9 execute · 2 escalate · 1 refuse (2 stale)
+rules:     ORC 65 (W 23 · C 22 · D 10 · U 10) · yours 9 lines (P0 4 · P1 2 · P2 3) · 1 override
 after:     src/payments — 2 shipped files rewritten within 30 days of run store-credit
 crosslink: 2 boundaries (payments-api) — advisory
 extra:     ON — 4 of 9 tasks foreign · deepseek/deepseek-v4-flash via api [0,30)
@@ -60,6 +61,11 @@ waves:     3 planned — will pause after wave 2 (batch_pause_every=2)
   ACTIVE mode is named whenever a verdict is later printed (`boundary_gate: off`
   omits the line). Uncarded areas are `unknown`, never REFUSE. Canonical:
   `../../orc-boundary/references/gate.md`.
+- **rules:** ALWAYS printed — the `line` field from `orc rules slice --lane orc
+  --json`, VERBATIM, never recounted. `yours none` is an answer (the project has
+  no `.claude/orc/rules.md` rules yet), not a failure. Name each override under
+  it. This line is the REPORT; the card itself is the `text` field, injected as
+  `rules_card` into every slice (`../../_shared/phases/rules.md`).
 - **after:** printed **ONLY when the area this run is about to touch has a recent
   churn signal** (`orc aftermath status --json`, exit 1 or 2, intersected with the
   plan's `declared_files`). A clean run prints nothing at all — the whole value of

package/templates/skills/orc/subskills/orc-execution/SKILL.md

@@ -26,7 +26,8 @@ contract); the summary below orients — on any conflict, `core.md` wins.
 2. Implement EXACTLY the task in the slice, touching only `declared_files[]`,
    honoring every `constraints[]` hard rule AND the standing `house_rules` card
    (surgical changes, simplicity-first, no unrequested scope, never claim
-   unobserved results, honest partial over false done); create/update
+   unobserved results, honest partial over false done), then the `rules_card`
+   under it (project rules beat ORC rules; return the three `rules_*` fields); create/update
    tests for what you build.
 3. Run the proof: build/test for your changes, capturing `evidence`
    {command, exit_code, tail} VERBATIM (no runner → `no_runner_detected: true`);

package/templates/skills/orc/subskills/orc-execution/core.md

@@ -59,6 +59,13 @@ subagent; the orchestrator never runs this itself.
 - house_rules             — the standing behavioral card (injected literally,
                             never a pointer): surgical changes, simplicity-first,
                             no unrequested scope, boring-solution preference
+- rules_card              — the anti-slop card from `orc rules slice`, injected
+                            literally directly under `house_rules`: the project's
+                            rules, then ORC's. A project rule beats an ORC rule;
+                            `house_rules` beat both on code and behaviour only.
+                            Carried → return `rules_applied[]`,
+                            `rules_conflicts[]`, `rules_overridden[]`
+                            (`../../../_shared/return-validation.md` §5c)
 - log_digest              — compacted decisions from prior waves; absorb before working
 - worktree_path           — null unless worktrees mode
 - model, effort           — informational (already applied by the caller)
@@ -74,7 +81,8 @@ subagent; the orchestrator never runs this itself.
    a FULL read before you edit it (an `old_string` rebuilt from an outline is a
    corruption bug), and build/test output is always read whole.
 3. Perform the task within `worktree_path` (or the current tree if null).
-   Obey every `house_rules` line. Follow every constraint. If `pattern` is present, MATCH its conventions,
+   Obey every `house_rules` line, then every `rules_card` rule (two rules that
+   disagree go in `rules_conflicts[]`, never a silent choice). Follow every constraint. If `pattern` is present, MATCH its conventions,
    satisfy every BLOCKING invariant, and satisfy every enforceable
    `validation_gate[]` line (re-read your diff to confirm before returning;
    advisory gate lines are informational — never add tooling to meet one);

package/templates/skills/orc-aftermath/SKILL.md

@@ -152,6 +152,13 @@ a failure**. A call the answer does not name is a call this lane does not make.
 Exit ≠ 0 from the catalogue itself → say the CLI is unavailable and name the
 command you are about to run, out loud, before running it.
 
+## Rules — the anti-slop card (`../_shared/phases/rules.md`)
+
+`orc rules slice --lane orc-aftermath --json` is the ONLY assembler; never build
+the card here. It rides under the house rules and above the task —
+**house rules > your project's rules > ORC's own packs** — and its `line` prints
+VERBATIM at preflight. Returns gain `rules_applied[]`, `rules_conflicts[]` (a gap,
+never a silent choice) and `rules_overridden[]`.
 ## Waiting mid-run (`/orc-wait`)
 
 Canonical: `../_shared/wait.md`. **`a lane that waits without a hand-back` has broken this contract.**

package/templates/skills/orc-analyze/SKILL.md

@@ -246,6 +246,13 @@ a failure**. A call the answer does not name is a call this lane does not make.
 Exit ≠ 0 from the catalogue itself → say the CLI is unavailable and name the
 command you are about to run, out loud, before running it.
 
+## Rules — the anti-slop card (`../_shared/phases/rules.md`)
+
+`orc rules slice --lane orc-analyze --json` is the ONLY assembler; never build
+the card here. It rides under the house rules and above the task —
+**house rules > your project's rules > ORC's own packs** — and its `line` prints
+VERBATIM at preflight. Returns gain `rules_applied[]`, `rules_conflicts[]` (a gap,
+never a silent choice) and `rules_overridden[]`.
 ## Waiting mid-run (`/orc-wait`)
 
 Canonical: `../_shared/wait.md`. **`a lane that waits without a hand-back` has broken this contract.**

package/templates/skills/orc-analyze-mini/SKILL.md

@@ -125,4 +125,12 @@ exit code, and never re-derive a state word — the CLI's state words are the on
 state words, and **an exit code is an ANSWER wherever that contract says so, not
 a failure**. A call the answer does not name is a call this lane does not make.
 Exit ≠ 0 from the catalogue itself → say the CLI is unavailable and name the
-command you are about to run, out loud, before running it.
+command you are about to run, out loud, before running it.
+
+## Rules — the anti-slop card (`../_shared/phases/rules.md`)
+
+`orc rules slice --lane orc-analyze-mini --json` is the ONLY assembler; never build
+the card here. It rides under the house rules and above the task —
+**house rules > your project's rules > ORC's own packs** — and its `line` prints
+VERBATIM at preflight. Returns gain `rules_applied[]`, `rules_conflicts[]` (a gap,
+never a silent choice) and `rules_overridden[]`.

package/templates/skills/orc-boundary/SKILL.md

@@ -243,6 +243,13 @@ a failure**. A call the answer does not name is a call this lane does not make.
 Exit ≠ 0 from the catalogue itself → say the CLI is unavailable and name the
 command you are about to run, out loud, before running it.
 
+## Rules — the anti-slop card (`../_shared/phases/rules.md`)
+
+`orc rules slice --lane orc-boundary --json` is the ONLY assembler; never build
+the card here. It rides under the house rules and above the task —
+**house rules > your project's rules > ORC's own packs** — and its `line` prints
+VERBATIM at preflight. Returns gain `rules_applied[]`, `rules_conflicts[]` (a gap,
+never a silent choice) and `rules_overridden[]`.
 ## Waiting mid-run (`/orc-wait`)
 
 Canonical: `../_shared/wait.md`. **`a lane that waits without a hand-back` has broken this contract.**

package/templates/skills/orc-brainstorm/SKILL.md

@@ -371,6 +371,13 @@ a failure**. A call the answer does not name is a call this lane does not make.
 Exit ≠ 0 from the catalogue itself → say the CLI is unavailable and name the
 command you are about to run, out loud, before running it.
 
+## Rules — the anti-slop card (`../_shared/phases/rules.md`)
+
+`orc rules slice --lane orc-brainstorm --json` is the ONLY assembler; never build
+the card here. It rides under the house rules and above the task —
+**house rules > your project's rules > ORC's own packs** — and its `line` prints
+VERBATIM at preflight. Returns gain `rules_applied[]`, `rules_conflicts[]` (a gap,
+never a silent choice) and `rules_overridden[]`.
 ## Waiting mid-run (`/orc-wait`)
 
 Canonical: `../_shared/wait.md`. **`a lane that waits without a hand-back` has broken this contract.**

package/templates/skills/orc-budget/SKILL.md

@@ -242,6 +242,13 @@ a failure**. A call the answer does not name is a call this lane does not make.
 Exit ≠ 0 from the catalogue itself → say the CLI is unavailable and name the
 command you are about to run, out loud, before running it.
 
+## Rules — the anti-slop card (`../_shared/phases/rules.md`)
+
+`orc rules slice --lane orc-budget --json` is the ONLY assembler; never build
+the card here. It rides under the house rules and above the task —
+**house rules > your project's rules > ORC's own packs** — and its `line` prints
+VERBATIM at preflight. Returns gain `rules_applied[]`, `rules_conflicts[]` (a gap,
+never a silent choice) and `rules_overridden[]`.
 ## Waiting mid-run (`/orc-wait`)
 
 Canonical: `../_shared/wait.md`. **`a lane that waits without a hand-back` has broken this contract.**

package/templates/skills/orc-challenge/SKILL.md

@@ -292,6 +292,13 @@ a failure**. A call the answer does not name is a call this lane does not make.
 Exit ≠ 0 from the catalogue itself → say the CLI is unavailable and name the
 command you are about to run, out loud, before running it.
 
+## Rules — the anti-slop card (`../_shared/phases/rules.md`)
+
+`orc rules slice --lane orc-challenge --json` is the ONLY assembler; never build
+the card here. It rides under the house rules and above the task —
+**house rules > your project's rules > ORC's own packs** — and its `line` prints
+VERBATIM at preflight. Returns gain `rules_applied[]`, `rules_conflicts[]` (a gap,
+never a silent choice) and `rules_overridden[]`.
 ## Waiting mid-run (`/orc-wait`)
 
 Canonical: `../_shared/wait.md`. **`a lane that waits without a hand-back` has broken this contract.**

package/templates/skills/orc-claude/SKILL.md

@@ -215,6 +215,13 @@ a failure**. A call the answer does not name is a call this lane does not make.
 Exit ≠ 0 from the catalogue itself → say the CLI is unavailable and name the
 command you are about to run, out loud, before running it.
 
+## Rules — the anti-slop card (`../_shared/phases/rules.md`)
+
+`orc rules slice --lane orc-claude --json` is the ONLY assembler; never build
+the card here. It rides under the house rules and above the task —
+**house rules > your project's rules > ORC's own packs** — and its `line` prints
+VERBATIM at preflight. Returns gain `rules_applied[]`, `rules_conflicts[]` (a gap,
+never a silent choice) and `rules_overridden[]`.
 ## Waiting mid-run (`/orc-wait`)
 
 Canonical: `../_shared/wait.md`. **`a lane that waits without a hand-back` has broken this contract.**

package/templates/skills/orc-diy/SKILL.md

@@ -128,6 +128,13 @@ command you are about to run, out loud, before running it.
 3. The fallback ask is ONE question with two outcomes (`/orc` or stop) —
    never a menu, never a silent fallback.
 
+## Rules — the anti-slop card (`../_shared/phases/rules.md`)
+
+`orc rules slice --lane orc-diy --json` is the ONLY assembler; never build
+the card here. It rides under the house rules and above the task —
+**house rules > your project's rules > ORC's own packs** — and its `line` prints
+VERBATIM at preflight. Returns gain `rules_applied[]`, `rules_conflicts[]` (a gap,
+never a silent choice) and `rules_overridden[]`.
 ## Waiting mid-run (`/orc-wait`)
 
 Canonical: `../_shared/wait.md`. **`a lane that waits without a hand-back` has broken this contract.**

package/templates/skills/orc-explain/SKILL.md

@@ -64,6 +64,13 @@ say so and use `../_shared/config-precedence.md`'s documented defaults, out
 loud. Nothing this lane reads is contested, gated or a stop, so it owes no
 preflight line and has no gate to honour.
 
+## Rules — the anti-slop card (`../_shared/phases/rules.md`)
+
+`orc rules slice --lane orc-explain --json` is the ONLY assembler; never build
+the card here. It rides under the house rules and above the task —
+**house rules > your project's rules > ORC's own packs** — and its `line` prints
+VERBATIM at preflight. Returns gain `rules_applied[]`, `rules_conflicts[]` (a gap,
+never a silent choice) and `rules_overridden[]`.
 ## Calls
 
 **ONE catalogue, and it is not you:** `orc lane calls orc-explain --json` names every

package/templates/skills/orc-export/SKILL.md

@@ -163,6 +163,13 @@ say so and use `../_shared/config-precedence.md`'s documented defaults, out
 loud. Nothing this lane reads is contested, gated or a stop, so it owes no
 preflight line and has no gate to honour.
 
+## Rules — the anti-slop card (`../_shared/phases/rules.md`)
+
+`orc rules slice --lane orc-export --json` is the ONLY assembler; never build
+the card here. It rides under the house rules and above the task —
+**house rules > your project's rules > ORC's own packs** — and its `line` prints
+VERBATIM at preflight. Returns gain `rules_applied[]`, `rules_conflicts[]` (a gap,
+never a silent choice) and `rules_overridden[]`.
 ## Calls
 
 **ONE catalogue, and it is not you:** `orc lane calls orc-export --json` names every

package/templates/skills/orc-fast/SKILL.md

@@ -121,8 +121,8 @@ pinned in the agent file). **Under `opus5_only` it is `orc-executor-opus-5-low`*
 - **the read ladder** (`../_shared/read-ladder.md`): read only as far up as the
   question needs — a file the task will EDIT is read in full first. Precomputed
   knowledge REPLACING exploration is this lane; a directory sweep is not.
-- the standing `house_rules` card (`../_shared/phases/house-rules.md`,
-  injected literally, same as full/mini)
+- the standing `house_rules` card (`../_shared/phases/house-rules.md`, literal,
+  same as full/mini) + the `rules_card` under it (`orc rules slice` → `text`, verbatim)
 - constraints from the intent spec
 - **terse-return rule:** standard contract fields, NO narrative prose — files
   changed, one-line diff summary, smoke-relevant notes only.
@@ -192,6 +192,13 @@ documented defaults, out loud. Priorities and families:
 Fast has no config key of its own — command-entry only; wave/scoring/review
 keys never apply, and the tier edges the F0 gate reads arrive resolved.
 
+## Rules — the anti-slop card (`../_shared/phases/rules.md`)
+
+`orc rules slice --lane orc-fast --json` is the ONLY assembler; never build
+the card here. It rides under the house rules and above the task —
+**house rules > your project's rules > ORC's own packs** — and its `line` prints
+VERBATIM at preflight. Returns gain `rules_applied[]`, `rules_conflicts[]` (a gap,
+never a silent choice) and `rules_overridden[]`.
 ## Calls
 
 **ONE catalogue, and it is not you:** `orc lane calls orc-fast --json` names every

package/templates/skills/orc-grill/SKILL.md

@@ -232,6 +232,13 @@ a failure**. A call the answer does not name is a call this lane does not make.
 Exit ≠ 0 from the catalogue itself → say the CLI is unavailable and name the
 command you are about to run, out loud, before running it.
 
+## Rules — the anti-slop card (`../_shared/phases/rules.md`)
+
+`orc rules slice --lane orc-grill --json` is the ONLY assembler; never build
+the card here. It rides under the house rules and above the task —
+**house rules > your project's rules > ORC's own packs** — and its `line` prints
+VERBATIM at preflight. Returns gain `rules_applied[]`, `rules_conflicts[]` (a gap,
+never a silent choice) and `rules_overridden[]`.
 ## Waiting mid-run (`/orc-wait`)
 
 Canonical: `../_shared/wait.md`. **`a lane that waits without a hand-back` has broken this contract.**

package/templates/skills/orc-handoff/SKILL.md

@@ -220,4 +220,12 @@ exit code, and never re-derive a state word — the CLI's state words are the on
 state words, and **an exit code is an ANSWER wherever that contract says so, not
 a failure**. A call the answer does not name is a call this lane does not make.
 Exit ≠ 0 from the catalogue itself → say the CLI is unavailable and name the
-command you are about to run, out loud, before running it.
+command you are about to run, out loud, before running it.
+
+## Rules — the anti-slop card (`../_shared/phases/rules.md`)
+
+`orc rules slice --lane orc-handoff --json` is the ONLY assembler; never build
+the card here. It rides under the house rules and above the task —
+**house rules > your project's rules > ORC's own packs** — and its `line` prints
+VERBATIM at preflight. Returns gain `rules_applied[]`, `rules_conflicts[]` (a gap,
+never a silent choice) and `rules_overridden[]`.

package/templates/skills/orc-learn/SKILL.md

@@ -175,6 +175,13 @@ a failure**. A call the answer does not name is a call this lane does not make.
 Exit ≠ 0 from the catalogue itself → say the CLI is unavailable and name the
 command you are about to run, out loud, before running it.
 
+## Rules — the anti-slop card (`../_shared/phases/rules.md`)
+
+`orc rules slice --lane orc-learn --json` is the ONLY assembler; never build
+the card here. It rides under the house rules and above the task —
+**house rules > your project's rules > ORC's own packs** — and its `line` prints
+VERBATIM at preflight. Returns gain `rules_applied[]`, `rules_conflicts[]` (a gap,
+never a silent choice) and `rules_overridden[]`.
 ## Waiting mid-run (`/orc-wait`)
 
 Canonical: `../_shared/wait.md`. **`a lane that waits without a hand-back` has broken this contract.**

package/templates/skills/orc-mini/SKILL.md

@@ -52,9 +52,9 @@ Phase 0  intake (Q1–Q4, soft sign-off) + run folder + intent-spec
 Phase 1  planning (dispatch orc-planner-mini; analyst first only on real docs)
          → one-line complexity read (mini-ok? or recommend switch-to-full)
 Phase 3  dispatch ONE executor (orc-executor-sonnet-5-high) — slice carries
-         the standing `house_rules` card (../_shared/phases/house-rules.md,
-         injected literally) + the cached `postgres` pattern on a data-access
-         task (cache HIT only) — collect + validate return
+         the standing `house_rules` card (../_shared/phases/house-rules.md, literal)
+         + the `rules_card` under it (`orc rules slice` → `text`, verbatim) + the
+         cached `postgres` pattern on a data-access task (cache HIT only) — collect + validate return
 Phase M  SMOKE GATE — run build+test → GREEN proceed · RED block ship + surface
 Phase X  MOCK EXAMPLE (config mock_example) — offer/build after a GREEN gate
 Phase T  TEST-AUTHORING ASK (opt-in) — offer to write test cases (never run them)
@@ -176,6 +176,13 @@ documented defaults, out loud. Priorities and families:
 Wave/scoring/scout keys never apply to mini — and they are not in the answer,
 so there is nothing to render or ask.
 
+## Rules — the anti-slop card (`../_shared/phases/rules.md`)
+
+`orc rules slice --lane orc-mini --json` is the ONLY assembler; never build
+the card here. It rides under the house rules and above the task —
+**house rules > your project's rules > ORC's own packs** — and its `line` prints
+VERBATIM at preflight. Returns gain `rules_applied[]`, `rules_conflicts[]` (a gap,
+never a silent choice) and `rules_overridden[]`.
 ## Calls
 
 **ONE catalogue, and it is not you:** `orc lane calls orc-mini --json` names every

package/templates/skills/orc-pact/SKILL.md

@@ -249,6 +249,13 @@ a failure**. A call the answer does not name is a call this lane does not make.
 Exit ≠ 0 from the catalogue itself → say the CLI is unavailable and name the
 command you are about to run, out loud, before running it.
 
+## Rules — the anti-slop card (`../_shared/phases/rules.md`)
+
+`orc rules slice --lane orc-pact --json` is the ONLY assembler; never build
+the card here. It rides under the house rules and above the task —
+**house rules > your project's rules > ORC's own packs** — and its `line` prints
+VERBATIM at preflight. Returns gain `rules_applied[]`, `rules_conflicts[]` (a gap,
+never a silent choice) and `rules_overridden[]`.
 ## Waiting mid-run (`/orc-wait`)
 
 Canonical: `../_shared/wait.md`. **`a lane that waits without a hand-back` has broken this contract.**

package/templates/skills/orc-poly/SKILL.md

@@ -236,6 +236,13 @@ a failure**. A call the answer does not name is a call this lane does not make.
 Exit ≠ 0 from the catalogue itself → say the CLI is unavailable and name the
 command you are about to run, out loud, before running it.
 
+## Rules — the anti-slop card (`../_shared/phases/rules.md`)
+
+`orc rules slice --lane orc-poly --json` is the ONLY assembler; never build
+the card here. It rides under the house rules and above the task —
+**house rules > your project's rules > ORC's own packs** — and its `line` prints
+VERBATIM at preflight. Returns gain `rules_applied[]`, `rules_conflicts[]` (a gap,
+never a silent choice) and `rules_overridden[]`.
 ## Waiting mid-run (`/orc-wait`)
 
 Canonical: `../_shared/wait.md`. **`a lane that waits without a hand-back` has broken this contract.**

package/templates/skills/orc-pr-driver/SKILL.md

@@ -193,4 +193,12 @@ exit code, and never re-derive a state word — the CLI's state words are the on
 state words, and **an exit code is an ANSWER wherever that contract says so, not
 a failure**. A call the answer does not name is a call this lane does not make.
 Exit ≠ 0 from the catalogue itself → say the CLI is unavailable and name the
-command you are about to run, out loud, before running it.
+command you are about to run, out loud, before running it.
+
+## Rules — the anti-slop card (`../_shared/phases/rules.md`)
+
+`orc rules slice --lane orc-pr-driver --json` is the ONLY assembler; never build
+the card here. It rides under the house rules and above the task —
+**house rules > your project's rules > ORC's own packs** — and its `line` prints
+VERBATIM at preflight. Returns gain `rules_applied[]`, `rules_conflicts[]` (a gap,
+never a silent choice) and `rules_overridden[]`.

package/templates/skills/orc-pr-setup/SKILL.md

@@ -209,4 +209,12 @@ exit code, and never re-derive a state word — the CLI's state words are the on
 state words, and **an exit code is an ANSWER wherever that contract says so, not
 a failure**. A call the answer does not name is a call this lane does not make.
 Exit ≠ 0 from the catalogue itself → say the CLI is unavailable and name the
-command you are about to run, out loud, before running it.
+command you are about to run, out loud, before running it.
+
+## Rules — the anti-slop card (`../_shared/phases/rules.md`)
+
+`orc rules slice --lane orc-pr-setup --json` is the ONLY assembler; never build
+the card here. It rides under the house rules and above the task —
+**house rules > your project's rules > ORC's own packs** — and its `line` prints
+VERBATIM at preflight. Returns gain `rules_applied[]`, `rules_conflicts[]` (a gap,
+never a silent choice) and `rules_overridden[]`.