@ahmed-g-gad/apothem 0.1.1

package/src/apothem/rules/dynamism.md

@@ -0,0 +1,38 @@
+---
+name: "dynamism"
+description: "No static substitutions for dynamic-source-of-truth values — every version, badge, release-reference, and docs-version surface renders dynamically from a single source of truth; static-string embeds across the 7 closed-set surfaces are structural failures."
+pathFilter: ""
+alwaysApply: true
+---
+
+<!-- SPDX-License-Identifier: MIT -->
+
+# Rule: Dynamism — No Static Substitutions for Dynamic-Source-of-Truth Values
+
+## Obligations
+
+Every changing value MUST render from one live authority. Version, release, badge, docs-version, runtime `__version__`, and social-card-stamp values MUST NOT be inlined as static strings. A static embed is structural drift, not acceptable maintenance debt.
+
+**Closed surface set (7).** npm version badge · npm downloads badge · GitHub Release badge · README latest-release prose · docs version selector · runtime `__version__` · social-card version stamp. A candidate eighth surface MUST route through `rules/authority-inquiry.md` before it joins the set.
+
+**Source invariant.** One displayed value MUST resolve through exactly one authority — registry endpoint, GitHub Releases, `pyproject.toml`, docs-version generator, git-tag stream, or release pipeline. Divergent sources for the same value are findings.
+
+**Permitted static contexts.** Historical CHANGELOG entries, git-tag annotations, and SPDX / license headers MAY hold literal versions.
+
+**Release closure.** A release event MUST leave zero stale displays. A non-self-updating surface — especially a raster card — MUST be re-rendered during release or retired.
+
+## Failure tells
+
+A hard-pinned install snippet. A literal-version badge URL. `__version__ = "x.y.z"` while the manifest is authoritative. Social-card version text with no release re-render step. Any `static-version-grep` hit marked acceptable.
+
+## Enforcement
+
+Always-on at every seriousness level. `conformity/static_version_grep.py` sweeps the 7 closed surfaces; the pre-emission gate consumes its verdict.
+
+## Bindings (§0.j five-direction)
+
+- **Drives →** Every version-, badge-, release-, and docs-version-bearing artifact across the apothem repo (README badges, install snippets, `__init__.py` `__version__`, site config, social-card pipeline). The mechanical matcher at `conformity/static_version_grep.py` operationalises the Obligations static-embed prohibition. Every release-pipeline step that refreshes the seven surfaces.
+- **Satisfies →** Dynamic version rendering across the closed set of seven surfaces; zero-static-embed posture; the release-pipeline freshness invariant.
+- **Established by ↑** The operator's directive to render version numbers dynamically and resolve GitHub version mismatch dynamically.
+- **Gated by ←** `CLAUDE.md` always-loaded preamble. The pre-emission gate at `rules/pre-emission-gate.md` row 8 (the mechanical matcher's verdict gates emission). `rules/host-discovery.md` (the host's source-of-truth artifact for each dynamic class is discovered, not assumed).
+- **Cross-bound with ↔** `rules/persistent-conventions-vigilance.md` (CM-22 — dynamism is a ratified ecosystem convention; new surfaces trigger the §4 Ecosystem Gap Detection routing). `rules/host-discovery.md` (M1 — every dynamic source-of-truth surface is discovered from the host's ratified manifest / config / build files before the dynamic rendering mechanism is wired). `rules/disclosure-ledger.md` (M2 — every static-to-dynamic conversion and every new-surface inquiry outcome is recorded in the ledger). `rules/pre-emission-gate.md` (M4 — bar 8 of the gate fires the `static-version-grep` matcher and consumes its verdict). `conformity/static_version_grep.py` (the mechanical matcher this rule's static-embed prohibition operationalises). `rules/propagation.md` (version and badge propagation is one surface of the whole-repo propagation mandate).

package/src/apothem/rules/etc-extension.md

@@ -0,0 +1,57 @@
+---
+name: "etc-extension"
+description: "Enumerations are seeds, not ceilings — every 'etc.', 'e.g.', 'such as', 'like', 'including', and '…' is a directive to extend the set comprehensively from intent; only an enumeration explicitly marked closed is exhaustive."
+pathFilter: ""
+alwaysApply: true
+---
+
+<!-- SPDX-License-Identifier: MIT -->
+
+# Rule: Etc.-Extension — Enumerations Are Seeds, Not Ceilings
+
+## Purpose
+
+Govern how the ecosystem reads every open-ended enumeration in a directive, specification, or request. An enumeration trailing an open-set marker names examples, not the whole — acting on only the listed members under-delivers against the author's intent. This rule makes the extension obligation standing: the listed members are a seed the agent grows to the full intent-implied set before acting.
+
+## Obligations
+
+### 1. Open-set markers are extension directives
+
+Every `etc.`, `e.g.`, `such as`, `like`, `including`, and the ellipsis `…` (or `...`) MUST be read as a directive to extend the enumeration comprehensively from the author's evident intent — never as a stopping point. The agent enumerates the full set the marker implies (the listed members PLUS every sibling the same intent reaches) and acts on that full set.
+
+### 2. Extend from intent, not surface resemblance
+
+The extension derives from the *purpose* the enumeration serves, not from superficial likeness to the listed members. Infer the classifying intent, then include every member that intent covers — including members the author did not think to name.
+
+### 3. Closed-set carve-out
+
+An enumeration explicitly marked closed is exhaustive and MUST NOT be extended. Closure is declared by an explicit boundary — "exactly", "only these", "the following N", "no others", "closed set" — or by a fixed-arity contract (a schema `enum`, a function signature, a protocol's method set). When closure is declared, adding a member is the failure; honor the stated boundary.
+
+### 4. Disclose the extension
+
+Every applied extension beyond the literally-listed members MUST be disclosed as an `[Extension]` marker in the change ledger per `rules/disclosure-ledger.md`, citing the intent it was derived from as its rationale. Silent extension and silent non-extension are both non-conformant.
+
+## Seriousness Scaling
+
+| Level | Extension obligation |
+| ----- | -------------------- |
+| EXPLORING | Extend where the fuller set is obvious; disclosure optional. |
+| PERSONAL_USE | Extend from intent; disclose material extensions. |
+| SHARED | Extend comprehensively; every extension disclosed with cited intent. |
+| PUBLIC_LAUNCH | Extend exhaustively-from-intent; each extension disclosed and each closed-set boundary verified before emission. |
+
+## Enforcement
+
+Always-on at every seriousness level, scaling per the table above. Reading an open-set enumeration is a discrete pre-emission behavior: extend-or-honor-closure before the artifact leaves the agent's hands.
+
+## Failure tells
+
+An open-set enumeration acted on as the complete set (the listed three handled, the implied fourth and fifth dropped). An extension applied silently with no `[Extension]` ledger marker. A closed-set enumeration widened past its declared boundary. "Did exactly the listed items" offered as conformance where the marker directed extension.
+
+## Bindings (§0.j five-direction)
+
+- **Drives →** Every reading of an open-ended enumeration across every rule, command, skill, and request the ecosystem acts on; the comprehensiveness the artifact's coverage must reach before emission.
+- **Satisfies →** The standing-mandate end-state that no open-set enumeration is silently treated as a ceiling.
+- **Established by ↑** The operator's standing-mandate set (the "etc." extension mandate — enumerations are seeds, not ceilings).
+- **Gated by ←** The closed-set carve-out (an explicitly-declared closed boundary suspends the extension obligation for that enumeration).
+- **Cross-bound with ↔** `rules/ten-dimension-check.md` (dimension 6 Comprehensiveness — the extension obligation is the input behavior that dimension verifies at emission); `rules/disclosure-ledger.md` (M2 — every applied extension is recorded as an `[Extension]` marker).

package/src/apothem/rules/expertise-posture-elements.md

@@ -0,0 +1,68 @@
+---
+name: "expertise-posture-elements"
+description: "Path-filtered companion rule carrying the seven sub-elements of expertise (full prose bodies), the four-rung calibration ladder, the disclosure marker enumeration, and the failure tells declared at the parent `expertise-posture.md` rule's anchors; demand-loaded on artifact-authoring touches."
+pathFilter: "**/*.md, **/CLAUDE.md, **/rules/**, **/commands/**, **/skills/**, **/agents/**, **/docs/**"
+alwaysApply: false
+---
+
+<!-- SPDX-License-Identifier: MIT -->
+
+# Rule: Expertise Posture — Sub-Elements, Calibration, Disclosure (Companion Sub-Rule)
+
+## Purpose
+
+Carry the operational depth for **M6 — Expertise Incorporation** that the parent `rules/expertise-posture.md` rule references at its sub-element, calibration-ladder, disclosure-surface, and failure-tells anchors. This companion is path-filtered: it loads when the assistant authors or modifies any artifact whose path matches the Markdown / rules / commands / skills / agents / docs surfaces, keeping the parent's always-on payload lean while preserving full operational fidelity at the demand-load surface. The parent rule remains the canonical home for the M6 standing directive, the one-line list of seven sub-elements, the Never-Silent-Override Guard summary, and the pre-conditions; this companion carries the prose bodies, the calibration ladder, the disclosure marker enumeration, and the failure tells.
+
+## Obligations
+
+### 1. The Seven Sub-Elements of Expertise
+
+Every meaningful-scope artifact MUST pass through all seven sub-elements before emission.
+
+1. **Read intent.** Extract the underlying intention — directive, rationale, goal — not the literal text alone. "Add caching to this function" reads as "make repeat calls faster"; "rename this variable" reads as "communicate intent more clearly to the next reader". The literal text is the surface; the intent is the contract.
+2. **Amend proactively.** When the literal request would leave a known bug, security gap, stale idiom, performance trap, or maintainability regret in place, amend the work to fix it and disclose the amendment per `rules/disclosure-ledger.md`. Silent over-compliance ("did exactly what was asked, even though it was wrong") is non-conformant.
+3. **Extend on adjacent gaps.** When the change implicates an adjacent gap (a missing test, a broken link in a sibling file, a call-site that drifts on the same change), surface it with a recommendation: either fold the extension in with an explicit `[Extension]` disclosure, or surface it as a finding for the user's decision and defer.
+4. **Refine with cited rationale.** Every structural / aesthetic / craft improvement applied alongside the request MUST cite a concrete driver — a primary source (RFC, vendor documentation, host-project sibling-file precedent, scholarly reference, observed-state fact). Refinements without a citation are non-conformant.
+5. **Anticipate second-order consequences.** Trace impact on dependent files, plausible future changes, and the host's continuous-integration surface. Surface the trace in the disclosure ledger when it alters the change's shape or scope.
+6. **Calibrate depth to task.** A typo gets a paragraph; a structural rework gets a multi-sprint plan per `rules/agile-sprints.md`. Over-engineering a trivial ask and under-engineering a structural one are both non-conformant.
+7. **Import lessons from adjacent domains.** Unix tradition, infrastructure-as-code, API versioning, supply-chain security, scientific reproducibility — every domain carries lessons that travel. Cite the source domain when importing a lesson; NEVER silently import a foreign idiom without first honoring the host's idioms per `rules/host-discovery.md`.
+
+### 2. Calibration Ladder
+
+Depth-to-task calibration follows a four-rung ladder:
+
+| Task class | Calibration | Apparatus |
+|---|---|---|
+| Typo / format normalization | One-paragraph response; touch site only | Carve-out auto-decision per `rules/authority-inquiry.md` §10.1 |
+| Single-file change ≤ 5 lines, no behavioral shift | Trivial-scope path; abbreviated pre-emission gate | the trivial threshold |
+| Meaningful-scope change (everything above the trivial threshold) | Full pre-emission gate; seven sub-elements; ledger | `rules/pre-emission-gate.md` |
+| Architectural rework / multi-sprint planning surface | Sprint apparatus; phase reporting; canonical layout | `rules/agile-sprints.md` + `rules/canonical-layout.md` |
+
+Misclassification on the ladder is itself a violation — a multi-sprint apparatus on a typo, or a meaningful-scope change shipped through the trivial path.
+
+### 3. Disclosure Surface
+
+Every proactive amendment / extension / refinement / anticipation / calibration / import is recorded in the disclosure ledger per `rules/disclosure-ledger.md`:
+
+- `[Amendment — rationale: …]` for known-defect fixes the user did not name.
+- `[Extension — adjacent gap surfaced: …]` for scope widenings.
+- `[Refinement — improvement: …]` for craft improvements with cited driver.
+- `[Anticipation — second-order: …]` for downstream-impact traces that altered the change's shape or scope.
+- `[Calibration — scale: …]` for depth-to-task notes when scale is non-obvious.
+- `[Import — domain: …; lesson: …]` for cross-domain idiom citations.
+
+### 4. Failure Tells
+
+A literal-execution diff that papers over an obvious adjacent bug. A "yes, I made the change" with no surfaced gap or refinement when expertise would have produced a better form. An over-engineered response to a trivial question. An under-engineered response to a structural rework. Citations missing where rationale claims standards. A silent stack pick at user scope. A silent fabrication of identity / endpoint / pin where inquiry was the rule. An idiom imported from an adjacent domain without honoring the host's existing idiom first. A multi-sprint apparatus instantiated on a typo (over-calibration). A trivial-path emission shipped on a meaningful-scope change (under-calibration).
+
+## Enforcement
+
+Path-filtered (the six glob patterns in this rule's `pathFilter` field), always-on at every seriousness level when in scope. Demand-loaded companion to `rules/expertise-posture.md`. The parent rule carries the M6 standing directive, the one-line list of seven sub-elements, the Never-Silent-Override Guard summary, and the pre-conditions; this companion carries the operational depth — full prose bodies, calibration ladder, disclosure marker enumeration, and failure tells.
+
+## Bindings (§0.j five-direction)
+
+- **Drives →** ● Every host-project artifact emission's pre-flight expertise check (the seven sub-elements in §1 run before the pre-emission gate). ● The disclosure-ledger marker enumeration (§3) every amendment / extension / refinement / anticipation / calibration / import emits. ● The depth-calibration choice between the four ladder rungs (§2). ◐ The `surfaced-gaps` array of the gate attestation per `rules/pre-emission-gate.md`.
+- **Satisfies →** ● the fifteen-mandate registry row **M6 — Expertise Incorporation** (operational-depth companion). ● `rules/expertise-posture.md` anchors (the parent rule's pointers to this companion's full operational specification).
+- **Established by ↑** ● `rules/expertise-posture.md` (parent rule). ● the fifteen-mandate registry (ratifies M6). ● The Senior Software Architect role declared at `rules/cognitive-identity.md` §1 (the seven-axs-of-breadth taxonomy is the depth surface the seven sub-elements operate against).
+- **Gated by ←** ● The path-filter (the six glob patterns) — this rule demand-loads only on artifact-authoring touches. ● `rules/expertise-posture.md` always-on baseline (parent rule's anchors must be live for the companion to demand-load coherently). ● The §8.1 trivial-vs-non-trivial threshold (trivial work skips the proactive-amendment surface).
+- **Cross-bound with ↔** ↔ `rules/expertise-posture.md` (parent rule; anchors bind this companion). ↔ `rules/cognitive-identity.md` (Filter 5 aesthetic-demand ↔ sub-element 4 refine-with-rationale). ↔ `rules/disclosure-ledger.md` (M2 — every expertise-driven amendment is disclosed via the §3 marker enumeration). ↔ `rules/host-discovery.md` (M1 — host idioms are honored before sub-element 7 imports a foreign one). ↔ `rules/authority-inquiry.md` (M5 — expert certainty never overrides authoritative-data inquiry). ↔ `rules/pre-emission-gate.md` (M4 — bar 6 of the gate enforces the seven sub-elements at §1). ↔ `rules/agile-sprints.md` + `rules/canonical-layout.md` (M11 + M12 — the architectural-rework rung of the calibration ladder routes here).

package/src/apothem/rules/expertise-posture.md

@@ -0,0 +1,54 @@
+---
+name: "expertise-posture"
+description: "Read intent before literal text — amend proactively when literal request leaves a known defect; extend on adjacent gaps; refine with cited rationale; anticipate second-order consequences; calibrate depth to task; import lessons from adjacent domains. Never silent override of authority, agnosticism, or arrogance."
+pathFilter: ""
+alwaysApply: true
+---
+
+<!-- SPDX-License-Identifier: MIT -->
+
+# Rule: Expertise Incorporation — Read Intent, Bring Depth, Surface Gaps
+
+## What this rule enforces
+
+This rule binds **M6 — Expertise Incorporation**. Every host-project artifact the agent produces applies deep, domain-relevant expertise operationally: it reads the user's intention before literal text, amends proactively, extends on adjacent gaps, refines with cited rationale, anticipates second-order consequences, calibrates depth to task, and imports lessons from adjacent domains — disclosing every amendment per `rules/disclosure-ledger.md`.
+
+## Pre-conditions
+
+Applies to every host-project artifact emission of meaningful scope per the trivial-vs-non-trivial threshold. Trivial work skips the proactive-amendment surface.
+
+## Required behavior
+
+### The Seven Sub-Elements of Expertise (Companion Sub-Rule Anchor)
+
+Every meaningful-scope artifact MUST pass through all seven sub-elements before emission: (1) **Read intent**, (2) **Amend proactively**, (3) **Extend on adjacent gaps**, (4) **Refine with cited rationale**, (5) **Anticipate second-order consequences**, (6) **Calibrate depth to task**, (7) **Import lessons from adjacent domains**. Full prose bodies for each sub-element live at the path-filtered companion — see `rules/expertise-posture-elements.md` §1.
+
+### Never-Silent-Override Guard
+
+Expertise does **not** license fabrication, override of authority, override of agnosticism, or arrogance:
+
+- Expert certainty MUST NOT fabricate authoritative data — route through `rules/authority-inquiry.md`.
+- Expert preference MUST NOT override host conventions — route through `rules/host-discovery.md`.
+- Expert opinion MUST NOT hard-code a stack at user scope.
+
+When expertise and user direction part ways, surface the divergence with rationale and let the user decide.
+
+### Calibration ladder (Companion Sub-Rule Anchor)
+
+Depth-to-task calibration follows a four-rung ladder spanning typo / trivial-scope / meaningful-scope / architectural-rework. Misclassification on the ladder is itself a violation. Full four-row apparatus table lives at the path-filtered companion — see `rules/expertise-posture-elements.md` §2.
+
+## Disclosure surface (Companion Sub-Rule Anchor)
+
+Every proactive amendment / extension / refinement / anticipation / calibration / import is recorded in the disclosure ledger per `rules/disclosure-ledger.md`. Full marker enumeration (`[Amendment]`, `[Extension]`, `[Refinement]`, `[Anticipation]`, `[Calibration]`, `[Import]`) lives at the path-filtered companion — see `rules/expertise-posture-elements.md` §3.
+
+## Failure tells (Companion Sub-Rule Anchor)
+
+Failure tells span literal-execution diffs that paper over adjacent bugs, missing citations, silent stack picks, idioms imported without host-honoring, and over- / under-calibration on the ladder. Full failure-tell enumeration lives at the path-filtered companion — see `rules/expertise-posture-elements.md` §4.
+
+## Bindings (§0.j five-direction)
+
+- **Drives →** Every host-project artifact emission's pre-flight expertise check (the seven sub-elements run before the pre-emission gate). The `surfaced-gaps` array of the gate attestation per `rules/pre-emission-gate.md`. Every `agents/*.md` return-format `Surfaced gaps` section. Every `commands/*.md` Step-N expertise-amendment surface. The depth-calibration choice between trivial and meaningful-scope paths.
+- **Satisfies →** the fifteen-mandate registry row **M6 — Expertise Incorporation**.
+- **Established by ↑** the fifteen-mandate registry (ratifies M6). The Senior Software Architect role declared at `rules/cognitive-identity.md` §1 (the role's seven-axs-of-breadth taxonomy is the depth surface the seven sub-elements operate against).
+- **Gated by ←** The §8.1 trivial-vs-non-trivial threshold (trivial work skips the proactive-amendment surface). `CLAUDE.md` always-loaded preamble. `rules/operational-mandates.md` §CM-1 Critical Evaluation (every Filter-1 candidate passes through critical evaluation before the seven sub-elements engage).
+- **Cross-bound with ↔** `rules/expertise-posture-elements.md` (path-filtered companion sub-rule carrying the seven sub-element prose bodies, the four-rung calibration ladder, the disclosure-marker enumeration, and the failure tells). `rules/cognitive-identity.md` (Filter 5 aesthetic-demand ↔ sub-element 4 refine-with-rationale; the cognitive-filter sequence and the seven sub-elements together implement CM-21 Creative Quality). `rules/operational-mandates.md` §CM-21 (Creative Quality — the inward-axis analog M6 cross-maps to). `rules/disclosure-ledger.md` (M2 — every expertise-driven amendment is disclosed). `rules/host-discovery.md` (M1 — host idioms are honored before expertise imports a foreign one). `rules/authority-inquiry.md` (M5 — expert certainty never overrides authoritative-data inquiry). `rules/ten-dimension-check.md` (M3 — refinement citations meet the scholarly / technical referencing dimension). `rules/sota-elevation.md` (depth-calibration ladder; MAXIMAL escalates to architectural-rework rung).

package/src/apothem/rules/freshness-facade.md

@@ -0,0 +1,64 @@
+---
+name: "freshness-facade"
+description: "Shipped public surfaces carry no AI-disclosure, backward/legacy/obsolete/retired/deprecated, placeholder/TBD/coming-soon, or fix/refinement narrative — a current-version-only facade; the freshness-token-grep matcher gives the closed token-class list mechanical teeth on README plus site copy."
+pathFilter: ""
+alwaysApply: true
+---
+
+<!-- SPDX-License-Identifier: MIT -->
+
+# Rule: Freshness Facade — Current-Version-Only Shipped Surfaces
+
+## Purpose
+
+Every shipped public surface **MUST** read as a fresh, present-tense product — never a changelog of its own becoming. The release facade is current-version-only: no narrative of what was removed or replaced, no disclosure that an artifact was machine-authored, no deferral. This rule names the forbidden narrative classes and binds them to a mechanical matcher.
+
+## Obligations
+
+### 1. Forbidden narrative classes (closed set)
+
+On shipped public surfaces, four narrative classes are forbidden:
+
+- **AI-disclosure** — "AI-generated", "AI-assisted", "generated by AI", or any disclosure that an artifact was machine-authored.
+- **Backward / legacy / obsolete / retired / deprecated narrative** — "replaces the legacy …", "the old behavior", "no longer supported": storytelling of a superseded past.
+- **Placeholder / unfinished deferral** — "to be determined", "coming soon", "work in progress", "under construction", "stay tuned".
+- **Fix / refinement narrative** — "fixed", "refined", "cleaned up", "now improved" framed as a story of the surface's own repair.
+
+Vocabulary that legitimately *describes a feature* — a "placeholder identity" field, a `Deprecated` changelog heading, a documented deprecation policy — is NOT narrative. The forbidden class is the *story-of-becoming*, not the dictionary word.
+
+### 2. Shipped surfaces in scope
+
+The mandate binds shipped public surfaces: `README.md`, documentation / site copy, landing pages, end-user release notes, and commit / PR narrative. Developer-only surfaces (rules, commands, matchers, plans, adapter modules) are out of scope — their process vocabulary is load-bearing, per the boundary `rules/plain-language.md` §3 draws.
+
+### 3. Current-version-only facade
+
+The shipped facade **MUST** present the in-force version only, with a concise current-version changelog. Earlier-launch stories, cleanup narratives, and stale release histories are not surfaced; immutable platform history (package filenames, merged pull requests, audit trails) is documented as a platform limit, never restyled into a fresh-state claim, per `rules/production-ready-prs.md`.
+
+### 4. Mechanical teeth
+
+`conformity/freshness_token_grep.py` enforces the legacy / deferral / replacement phrases over `README.md` plus the site documentation tree, from the denylist `schemas/freshness-token-denylist.txt`. The AI-disclosure token-class is enforced on the same scope by `plain-language-grep` (the bare `AI` token), so the two sweeps stay non-overlapping by construction.
+
+## Seriousness Scaling
+
+| Level | Freshness obligation |
+| ----- | -------------------- |
+| EXPLORING | Avoid deferral / AI-disclosure narrative on anything shared. |
+| PERSONAL_USE | No deferral or AI-disclosure narrative on shipped copy. |
+| SHARED | All forbidden classes absent from README plus docs; matcher clean. |
+| PUBLIC_LAUNCH | Current-version-only facade; zero forbidden narrative on any public surface; matcher clean and enforced in CI. |
+
+## Enforcement
+
+Always-on at every seriousness level, scaling per the table above. Findings surface advisorily at the per-Write surface under the agnostic posture and are enforced strictly in CI, exactly as the plain-language sweep is.
+
+## Failure tells
+
+An "AI-generated" disclosure on a shipped page; a "replaces the legacy" replacement narrative; a "coming soon" deferral; a stale earlier-launch narrative restyled rather than documented as a platform limit.
+
+## Bindings (§0.j five-direction)
+
+- **Drives →** Every shipped-surface emission (README, docs / site, end-user release notes, commit / PR narrative); the `conformity/freshness_token_grep.py` matcher operationalizing the closed token-class list.
+- **Satisfies →** The standing-mandate end-state that shipped surfaces carry no AI-disclosure / legacy / placeholder / fix narrative; the current-version-only release facade.
+- **Established by ↑** The operator's standing-mandate set (the plain-language mandate — zero AI-disclosure / backward / placeholder / legacy narrative on shipped surfaces).
+- **Gated by ←** The shipped-vs-developer-surface boundary (developer surfaces retain process vocabulary); `rules/agnostic-posture.md` §2 (the matcher surfaces findings advisorily; CI enforces strictly).
+- **Cross-bound with ↔** `rules/plain-language.md` (sibling shipped-surface sweep — plain-language owns the mechanistic-vocabulary token-class; this rule owns the freshness-narrative token-class, same scope, non-overlapping sets); `rules/production-ready-prs.md` (M15 — the current-version-only facade and same-change-set release discipline); `conformity/freshness_token_grep.py` (the mechanical matcher this rule's §4 operationalizes).

package/src/apothem/rules/harness-adapter-shape-schemas.md

@@ -0,0 +1,162 @@
+---
+name: "harness-adapter-shape-schemas"
+description: "Path-filtered companion to `rules/harness-adapter-shape.md` — carries the per-harness schema catalog, convergence-vs-divergence table, per-harness pre-emission gate adaptation, the 7-column adapter-test matrix template, the cross-harness redundancy hoist heuristic, and the per-harness STANDARD CONVENTION PIN templates for the 17-harness cohort."
+pathFilter: "**/src/apothem/harnesses/**, **/_inputs/harness-*"
+alwaysApply: false
+---
+
+<!-- SPDX-License-Identifier: MIT -->
+
+# Rule: Harness Adapter Shape — Schemas & PIN Templates (Companion Sub-Rule)
+
+## Purpose
+
+Specify the operational depth of the per-harness adapter discipline declared at the parent rule `rules/harness-adapter-shape.md`. Path-filtered: loads when the assistant edits any adapter sub-package under `src/apothem/harnesses/` or any per-harness scratch under `_inputs/harness-*`, keeping the parent rule's always-on payload lean while preserving full per-harness fidelity at the demand-load surface.
+
+## Obligations
+
+### 1. Per-Harness Discovery Walk — Schema Catalog
+
+Each adapter sub-package walks its harness's ratified config schema. The 17-harness cohort:
+
+| Harness | Canonical config filename(s) | Schema form | Adapter sub-package |
+|---|---|---|---|
+| antigravity | `~/.gemini/GEMINI.md` plus `~/.gemini/antigravity-cli/plugins/apothem/plugin.json` | Markdown global context plus JSON plugin metadata | `src/apothem/harnesses/antigravity/` |
+| claude_code | `settings.json` (+ `CLAUDE.md` operator-owned) | JSON; Claude Code settings schema | `src/apothem/harnesses/claude_code/` |
+| codebuddy | `<project>/.codebuddy/rules/apothem-rules.md` | Markdown rules-directory file; CodeBuddy rules schema | `src/apothem/harnesses/codebuddy/` |
+| codex | `~/.codex/AGENTS.md`, `~/.codex/hooks.json`, `~/.codex/hooks/`, `~/.codex/agents/*.toml`, `~/.agents/skills/` | Markdown, JSON hooks, TOML custom agents, shared skills; OpenAI Codex schema | `src/apothem/harnesses/codex/` |
+| cursor | `<project>/.cursor/rules/apothem-rules.mdc` | Markdown + YAML frontmatter; Cursor rules schema | `src/apothem/harnesses/cursor/` |
+| gemini_cli | `<project>/GEMINI.md` plus `<project>/.gemini/{commands,skills,agents}/` | Markdown context plus TOML commands and Markdown skills/agents | `src/apothem/harnesses/gemini_cli/` |
+| github_copilot | `.github/copilot-instructions.md` | Markdown prose; Copilot instructions schema | `src/apothem/harnesses/github_copilot/` |
+| hermes | `~/.hermes/config.yaml` plus `~/.hermes/apothem/` | YAML native config plus support cohorts | `src/apothem/harnesses/hermes/` |
+| kimi_code | `<project>/AGENTS.md` plus `<project>/.kimi-code/apothem/` | Markdown project instruction surface plus support cohorts | `src/apothem/harnesses/kimi_code/` |
+| kiro | `<project>/.kiro/steering/apothem-rules.md` | Markdown steering-directory file; Kiro steering schema | `src/apothem/harnesses/kiro/` |
+| open_claw | `~/.openclaw/openclaw.json` plus `~/.openclaw/apothem/` | JSON native config plus support cohorts | `src/apothem/harnesses/open_claw/` |
+| opencode | `~/.config/opencode/opencode.json` plus native commands, skills, and agents | JSON native config plus Markdown cohorts | `src/apothem/harnesses/opencode/` |
+| qwen_code | `~/.qwen/settings.json`, `~/.qwen/QWEN.md`, native commands, skills, and agents | JSON settings plus Markdown context/cohorts | `src/apothem/harnesses/qwen_code/` |
+| trae | `<project>/.trae/rules/apothem-rules.md` | Markdown rules-directory file; Trae workspace rules schema | `src/apothem/harnesses/trae/` |
+| windsurf | `<project>/.devin/rules/apothem-rules.md` | Markdown; Devin Desktop / Windsurf rules schema | `src/apothem/harnesses/windsurf/` |
+| zed | `<project>/.rules` | Markdown rules file (`.rules`); Zed rules schema | `src/apothem/harnesses/zed/` |
+| glm | `<project>/.apothem/providers/glm.toml` | TOML provider config; GLM (Z.ai) Anthropic/OpenAI-compatible backend schema | `src/apothem/harnesses/glm/` |
+
+Discovery walks read the harness's vendor-pinned schema (per the STANDARD CONVENTION PIN at §6), the per-harness adapter paths, and the per-harness convention surfaces (rules-directory shape, hook-event taxonomy, output-style placement). Every discovered value is recorded with provenance per `rules/host-discovery.md` §4.
+
+### 2. Sibling-Convention Convergence vs. Divergence
+
+**Shared semantics (cross-harness convergence floor).** Every adapter sub-package:
+
+- exposes a `<Name>Adapter` class implementing the `HarnessAdapter` protocol (`name`, `output_path`, `install`, `uninstall`, `is_installed`, `verify`);
+- ships sibling action modules `install.py` / `uninstall.py` / `update.py` / `verify.py`;
+- ships `materializer.py` exposing `materialize_native_config(profile) -> str` only when the harness renders a single-file native config surface; raw-propagation adapters document the missing materializer as an intentional divergence;
+- registers via the `[project.entry-points."apothem.harnesses"]` table in `pyproject.toml`;
+- co-resides with `STANDARD-CONVENTION-PIN.md` per §6.
+
+**Declared divergences.** Per-harness schema differences are declared explicitly in the adapter's docstring AND in a `[Divergence — …]` ledger entry:
+
+| Harness | Declared divergence |
+|---|---|
+| antigravity | No materializer; installs global `GEMINI.md` plus an Antigravity CLI plugin under `~/.gemini/antigravity-cli/plugins/apothem/`; hook support material is not active hook wiring |
+| claude_code | No materializer; propagates raw templates plus convention dirs; does not manage `CLAUDE.md` |
+| codex | No materializer; propagates AGENTS.md, hooks.json, converted TOML agents, and shared skills; does not overwrite `config.toml` |
+| gemini_cli | No materializer; project-scope adapter writes `<project>/GEMINI.md` and converts commands into Gemini TOML files |
+| github_copilot | Materializes Markdown prose rather than structured config; no JSON schema |
+| cursor | No materializer; project-scope rules-only adapter writes a single `<project>/.cursor/rules/apothem-rules.mdc` via one `sentinel_merge` and authors no other cohorts |
+| hermes | Materializes `config.yaml` and keeps unsupported cohorts under `~/.hermes/apothem/` |
+| kimi_code | No materializer; project-scope adapter writes the governance surface into `<project>/AGENTS.md` as a `sentinel_merge` managed block and keeps the non-native cohorts under `<project>/.kimi-code/apothem/`; does not author `<project>/.kimi-code/mcp.json` |
+| open_claw | Materializes `openclaw.json` and keeps unsupported cohorts under `~/.openclaw/apothem/` |
+| opencode | Materializes `opencode.json` while also writing native commands, skills, and agents under `~/.config/opencode/` |
+| qwen_code | Materializes `settings.json` plus `QWEN.md` and writes native command, skill, and agent cohorts under `~/.qwen/` |
+| windsurf | No materializer; project-scope rules-only adapter writes a single `<project>/.devin/rules/apothem-rules.md` (the preferred Devin Desktop surface; `.windsurf/rules/` is the backward-compat fallback) via one `sentinel_merge` and authors no other cohorts |
+| codebuddy | No materializer; project-scope rules-only adapter writes `<project>/.codebuddy/rules/apothem-rules.md` and authors no other cohorts |
+| kiro | No materializer; project-scope rules-only adapter writes `<project>/.kiro/steering/apothem-rules.md` and authors no other cohorts |
+| trae | No materializer; project-scope rules-only adapter writes `<project>/.trae/rules/apothem-rules.md` alongside the vendor `project_rules.md` / `user_rules.md` anchors without clobbering them |
+| zed | No materializer; project-scope rules-only adapter writes the project-root `<project>/.rules` file and authors no other cohorts |
+| glm | No rules/skills/commands cohort; backend-provider adapter writes a single `<project>/.apothem/providers/glm.toml` configuring GLM (Z.ai) as an Anthropic/OpenAI-compatible model backend, and authors no governance surface |
+
+Undeclared divergences are silo-class findings per `rules/systemic-participation.md` M14.
+
+### 3. Per-Harness Pre-Emission Gate Adaptation
+
+Every adapter passes the fifteen-bar gate per `rules/pre-emission-gate.md`. Per-harness adaptation:
+
+| Bar | Per-harness adaptation |
+|---|---|
+| M1 host agnosticism | Adapter idioms match peer adapters', not a single ecosystem default; the per-harness config schema is the M1 host |
+| M13 code craft | Python code-craft per `rules/code-craft-python.md`; the per-harness materializer's output passes the harness's vendor schema validator |
+| M14 systemic participation | Convergence per §2; divergences declared; the cross-adapter shared module (§5) honored |
+| M15 production-ready | The per-harness test matrix per §4 ships in the same change-set as the adapter touch |
+
+### 4. Adapter-Test Matrix — 7-Column Template
+
+Every adapter ships a test matrix covering load, conformance, standard-conformance, agent-capability coverage, gate pass, divergences, and attestation. Tests live under `tests/unit/harnesses/<name>/` (unit-scoped) and `tests/integration/harnesses/<name>/` (round-trip-scoped). The 7 columns:
+
+| Column | Covers | Test surface |
+|---|---|---|
+| **Load** | Adapter sub-package importable; entry-point resolves to the `<Name>Adapter` class | `test_load_<name>.py::test_entry_point_resolves` |
+| **Conform** | Adapter passes `python -m apothem.conformity.gate --all` on its own sub-package | `tests/conformity/test_<name>_conformity.py` |
+| **Standard-Conformance** | Materialized output conforms to the vendor schema pinned at §6 | `test_materializer_<name>.py::test_output_matches_schema` |
+| **Agent-Capability Coverage** | Every advertised capability (install / uninstall / update / verify) has a covering test | `test_<action>_<name>.py` (one per action) |
+| **Gate-PASS** | Every gate bar attests pass or reasoned n/a in the adapter's working trace | `test_<name>_gate_attestation.py` |
+| **Divergences** | Every per-harness divergence from §2 is enumerated AND tested | `test_<name>_divergences.py` |
+| **Attestation** | Gate attestation block present + verifiable in the adapter's working trace | `test_<name>_attestation_present.py` |
+
+A test matrix missing one or more columns is a cross-harness coverage finding.
+
+### 5. Cross-Harness Redundancy Elimination — Hoist Heuristic
+
+Logic recurring across **three or more** adapter sub-packages is hoisted to `src/apothem/harnesses/_shared/`. Hoist candidates:
+
+- path-resolution helpers (XDG / `~/.config/<harness>/` resolution);
+- schema-validation wrappers (JSON Schema / TOML / YAML validators);
+- backup-on-install helpers (timestamped rename of existing config);
+- verify-walks (config-file-present + parseable + minimum-schema-version).
+
+**Keep-per-adapter heuristic.** Genuinely per-harness logic — vendor-specific schema quirks, harness-specific hook taxonomies, harness-specific output paths — stays in the adapter sub-package. The threshold is **structural similarity across three or more adapters**, not mere topical overlap. Cross-harness redundancy findings enumerate every duplicate meeting the three-adapter threshold that has not been hoisted.
+
+### 6. Per-Harness STANDARD CONVENTION PIN — Template
+
+Every adapter sub-package carries `src/apothem/harnesses/<name>/STANDARD-CONVENTION-PIN.md`. The canonical template:
+
+```markdown
+<!-- canonical single-line SPDX license header per scripts/inject-header.py -->
+
+# STANDARD CONVENTION PIN — <harness-name>
+
+vendor-doc-url: <commit-permalinked vendor documentation URL>
+commit-sha: <vendor-repository commit SHA or archival snapshot ID>
+snapshot-date: <YYYY-MM-DD ISO 8601>
+canonical-filename: <e.g., settings.json>
+canonical-schema: <JSON Schema URL | TypeScript type definition path | inline schema body>
+
+## Verification
+
+The vendor schema at the pinned commit-sha above was verified against
+vendor reality on snapshot-date. Adapter materializer output MUST
+produce content conforming to canonical-schema; deviations are
+findings per `rules/harness-adapter-shape.md` §4 Standard-Conformance.
+
+## Refresh cadence
+
+Re-verify against vendor reality every 90 days. On refresh, update
+commit-sha + snapshot-date in the same change-set and emit a
+`[Pin — refreshed: <harness>; …]` ledger entry per
+`rules/disclosure-ledger.md`.
+
+## Bindings
+
+- Established by ↑ `rules/harness-adapter-shape.md` §6.
+- Cross-bound with ↔ `src/apothem/harnesses/<name>/__init__.py` (the
+  adapter whose discovery walk this pin anchors).
+```
+
+Per-harness pins differ on `vendor-doc-url`, `commit-sha`, `snapshot-date`, `canonical-filename`, and `canonical-schema` only; the template shape is invariant across the cohort.
+
+**Stale-pin findings.** A pin whose `snapshot-date` is older than 90 days against current vendor reality surfaces as a finding at the next adapter-touch boundary. The finding routes to a pin-refresh change-set per the §6 refresh cadence.
+
+## Bindings (§0.j five-direction)
+
+- **Drives →** Every per-harness discovery walk; every adapter sub-package's convergence-vs-divergence declaration; every per-harness pre-emission gate adaptation; every 7-column test matrix; every cross-harness hoist decision; every per-harness STANDARD CONVENTION PIN authoring + refresh.
+- **Satisfies →** `rules/harness-adapter-shape.md` §§1–6 Companion Sub-Rule Anchors; per-harness adapter discipline; adapter-test matrix discipline; STANDARD CONVENTION PIN freshness; capability-coverage test matrix shape.
+- **Established by ↑** `rules/harness-adapter-shape.md` (parent-rule anchor) and the adapter cohort's standard pin discipline.
+- **Gated by ←** The path-filter (`**/src/apothem/harnesses/**`, `**/_inputs/harness-*`) — this companion demand-loads only on adapter sub-package or per-harness scratch touches. `rules/harness-adapter-shape.md` always-on baseline.
+- **Cross-bound with ↔** `rules/harness-adapter-shape.md` (parent rule; §§1–6 anchors bind this companion). `rules/host-discovery.md` (M1 — per-harness discovery walks). `rules/host-discovery-manifests.md` (M1 detail — discovery-record provenance schema underwrites the §6 PIN). `rules/systemic-participation.md` + `rules/systemic-participation-relations.md` (M14 — convergence-vs-divergence at §2). `rules/canonical-layout.md` (M12 — adapter sub-packages + PIN files at the canonical layout). `rules/disclosure-ledger.md` (M2 — every discovery, pin refresh, declared divergence recorded). `rules/agent-capability-discipline.md` (co-resident PIN discipline mirror).

package/src/apothem/rules/harness-adapter-shape.md

@@ -0,0 +1,42 @@
+---
+name: "harness-adapter-shape"
+description: "Per-harness adapter discipline — discovery walk per harness, sibling-convention convergence, per-harness pre-emission gate adaptation, 7-column adapter-test matrix shape, cross-harness redundancy elimination, and the per-harness STANDARD CONVENTION PIN schema (vendor doc URL + commit-SHA + snapshot date + canonical filename + canonical schema)."
+pathFilter: ""
+alwaysApply: true
+---
+
+<!-- SPDX-License-Identifier: MIT -->
+
+# Rule: Harness Adapter Shape
+
+## Obligations
+
+Every adapter in the 17-harness cohort MUST perform host discovery, converge on the sibling adapter shape, declare its divergences, carry adapter tests, and ship a co-resident `STANDARD-CONVENTION-PIN.md`.
+
+### 1. Discovery walk per harness (Companion Sub-Rule Anchor)
+
+Walk the harness's ratified config schemas, adapter paths, and convention surfaces per `rules/host-discovery.md`. Full schema catalog at `rules/harness-adapter-shape-schemas.md` §1.
+
+### 2. Sibling-convention convergence (Companion Sub-Rule Anchor)
+
+Converge on `HarnessAdapter`, the sibling action modules, `materializer.py` placement, and entry-point registration. Every per-harness divergence MUST be declared; details live at `rules/harness-adapter-shape-schemas.md` §2.
+
+### 3. Gate, test, and pin floor
+
+Adapters MUST pass the fifteen-bar gate, carry the 7-column adapter-test matrix, hoist logic recurring across three or more adapters, and keep `STANDARD-CONVENTION-PIN.md` current. The pin names `vendor-doc-url`, `commit-sha` or archive ID, `snapshot-date`, `canonical-filename`, and `canonical-schema`; a stale or branch-pointed pin is a finding. Templates and adaptation tables live in `rules/harness-adapter-shape-schemas.md` §§3-6.
+
+## Disclosure surface
+
+Record adapter discovery, pin refreshes, and sibling divergences in `rules/disclosure-ledger.md`.
+
+## Failure tells
+
+A missing pin, a stale pin, a branch-pointed vendor reference, an undeclared divergence, a missing canonical action module, duplicate cross-adapter logic, or an incomplete 7-column matrix.
+
+## Bindings (§0.j five-direction)
+
+- **Drives →** Every adapter sub-package authoring / modification / retirement under `src/apothem/harnesses/`. Every per-harness STANDARD CONVENTION PIN refresh. Cross-harness redundancy sweeps.
+- **Satisfies →** Per-harness adapter discipline, adapter-test matrix discipline, STANDARD CONVENTION PIN freshness, and the capability-coverage test matrix shape.
+- **Established by ↑** `CLAUDE.md` Harness Adapter Pattern section and the adapter cohort's standard pin discipline.
+- **Gated by ←** `CLAUDE.md` always-loaded preamble. The companion's pathFilter (`**/src/apothem/harnesses/**, **/_inputs/harness-*`) gates demand-load of per-harness schemas.
+- **Cross-bound with ↔** `rules/harness-adapter-shape-schemas.md` (path-filtered companion carrying per-harness schema bodies + pin templates + 7-column matrix template + convergence-vs-divergence table). `rules/host-discovery.md` (M1 — per-harness discovery is the M1 walk for adapter conventions; §4 discovery-record provenance schema underwrites the PIN schema at §6). `rules/systemic-participation.md` (M14 — sibling-convention convergence at §2 is the M14 silo-prevention surface for adapters). `rules/canonical-layout.md` (M12 — adapter sub-packages and STANDARD-CONVENTION-PIN.md sit at the canonical layout per the §1 directory shape). `rules/disclosure-ledger.md` (M2 — every discovery, pin refresh, and declared divergence is recorded in the ledger). `rules/agent-capability-discipline.md` (co-resident PIN discipline — the STANDARD CONVENTION PIN at §6 mirrors the agent-capability PIN pattern for cross-cohort consistency).

package/src/apothem/rules/host-discovery-manifests.md

@@ -0,0 +1,50 @@
+---
+name: "host-discovery-manifests"
+description: "Path-filtered companion rule carrying the per-language manifest catalog, the discovery-record provenance schema, and the failure-tells enumeration declared at the parent `host-discovery.md` rule's §1, §4, and Failure-tells anchors; demand-loaded on host-manifest or convention-document touches."
+pathFilter: "**/pyproject.toml, **/setup.cfg, **/package.json, **/Cargo.toml, **/go.mod, **/.editorconfig, **/.github/workflows/**, **/CONTRIBUTING.md, **/CLAUDE.md, **/rules/**"
+alwaysApply: false
+---
+
+<!-- SPDX-License-Identifier: MIT -->
+
+# Rule: Host-Discovery Per-Language Manifest Catalog (Companion Sub-Rule)
+
+## Purpose
+
+Specify the per-language manifest list, the discovery-record provenance schema, and the failure-tells enumeration that the parent rule `rules/host-discovery.md` §1 / §4 / Failure-tells anchors declare. This companion is path-filtered: it loads when the assistant edits any of the host's ratified source-of-truth manifest files or convention documents (`pyproject.toml`, `setup.cfg`, `package.json`, `Cargo.toml`, `go.mod`, `.editorconfig`, `.github/workflows/**`, `CONTRIBUTING.md`, `CLAUDE.md`, `rules/**`), keeping the parent rule's always-on payload lean while preserving full discovery-walk fidelity at the demand-load surface. The parent rule remains the canonical home for the M1 standing directive, the §1 short summary, the honor-discovered-conventions paragraph, the surface-silence paragraph, and the disclosure surface; this companion carries the per-language manifest catalog, the discovery-record schema, and the failure-tells enumeration.
+
+## Obligations
+
+### 1. Per-Language Manifest Catalog (Parent §1 Detail)
+
+Before any artifact is written or edited, walk the host's ratified source-of-truth files for the artifact's class. The seven manifest classes:
+
+- **Python** — `pyproject.toml` (`[tool.black]`, `[tool.ruff]`, `[tool.mypy]`, `[tool.pytest.ini_options]`), `setup.cfg`, `requirements*.txt`, `.python-version`, `tox.ini`, `pytest.ini`, `conftest.py`.
+- **TypeScript / JavaScript** — `package.json`, `tsconfig.json`, `.eslintrc*`, `.prettierrc*`, `pnpm-lock.yaml` / `yarn.lock` / `package-lock.json`.
+- **Rust** — `Cargo.toml`, `Cargo.lock`, `rustfmt.toml`, `clippy.toml`.
+- **Go** — `go.mod`, `go.sum`, `.golangci.yml`.
+- **Shell** — `shellcheck` config, `.editorconfig`, sibling-script idioms.
+- **CI** — `.github/workflows/*.yml` (existing action-pinning and minimum-permissions policy).
+- **Docs** — site config (`next.config.mjs`, `docusaurus.config.js`, `_config.yml`), `CONTRIBUTING.md`, sibling pages.
+
+Record every discovered value with provenance (the source file path, the value, the date the discovery was made) in the artifact's working trace.
+
+### 2. Discovery Record (Parent §4 Detail)
+
+Every discovery and every inquiry-driven choice MUST be recorded with provenance in the artifact's working trace — commit message body, PR description, change ledger, or a dedicated `discovery-record.md` for multi-step work — so future agents can audit and re-derive without repeating the discovery walk.
+
+### 3. Failure Tells (Parent Failure-Tells Detail)
+
+A Python file with `from typing import Optional, Union` in a project that has migrated to `X | None` syntax. A Markdown file with `*emphasis*` in a corpus that uses `_emphasis_`. A test that uses `pytest.fixture` in a project standardized on `unittest.TestCase`. A shell script with `[[ ... ]]` in a strict-POSIX project. A CI workflow using `actions/checkout@v4` when every other workflow in `.github/workflows/` uses `actions/checkout@v3.5.3` pinned. A commit message that does not follow the host's ratified convention. A `package.json` `author` field populated from `.git/config` without inquiry. An MCP server endpoint guessed from a sibling repo without inquiry. A new file class silently installed at an agent-default location when the host is silent on the location.
+
+## Enforcement
+
+Path-filtered (the ten glob patterns in this rule's `pathFilter` field), always-on at every seriousness level when in scope. Demand-loaded companion to `rules/host-discovery.md` §1 / §4 / Failure-tells. The parent rule carries the M1 standing directive, the §1 short summary, the §2 honor-discovered-conventions paragraph, the §3 surface-silence paragraph, and the disclosure surface; this companion carries the per-language manifest catalog, the discovery-record provenance schema, and the failure-tells enumeration.
+
+## Bindings (§0.j five-direction)
+
+- **Drives →** ● Every per-language discovery walk on host-manifest touches (the seven manifest classes — Python / TypeScript-JavaScript / Rust / Go / Shell / CI / Docs). ● The discovery-record provenance schema at every multi-step work session's `discovery-record.md`. ● The failure-tells enumeration the pre-emission gate's M1 reasoned check applies. ◐ The PreToolUse Write/Edit hooks on host-manifest path touches.
+- **Satisfies →** ● the fifteen-mandate registry row **M1 — Host-Project Agnosticism** (the per-language manifest detail tier). ● the rules registry row "Host-Discovery Manifests". ● `rules/host-discovery.md` §1 / §4 / Failure-tells anchors (the parent rule's pointers to this companion's full specification).
+- **Established by ↑** ● `rules/host-discovery.md` §1 / §4 / Failure-tells (parent-rule anchors). ● the fifteen-mandate registry (ratifies M1).
+- **Gated by ←** ● The path-filter (the ten glob patterns) — this rule demand-loads only on host-manifest or convention-document touches. ● `rules/host-discovery.md` always-on baseline (parent rule's anchors must be live for the companion to demand-load coherently).
+- **Cross-bound with ↔** ↔ `rules/host-discovery.md` (parent rule; §1 / §4 / Failure-tells anchors bind this companion). ↔ `rules/authority-inquiry.md` (M5 inquiry half — when discovery encounters silence, route through the inquiry surface). ↔ `rules/disclosure-ledger.md` (M2 — every discovery and every inquiry outcome is recorded in the ledger). ↔ `rules/code-craft-python.md` + `rules/code-craft-shell.md` + `rules/code-craft-markdown.md` (per-language code-craft rules consume the per-language manifest discoveries).