docs: add hummbl-dev org style guide

STYLE.md

@@ -0,0 +1,69 @@
+# hummbl-dev — Org Style Guide
+
+Scope: **org-level conventions only.** Code style, branch naming, and commit
+format already live in each repo's `CLAUDE.md` / `.agents/rules/` — this guide
+does not restate them, it points at them and adds the 3 rules the org level
+needs. Home: this file belongs in `hummbl-dev/.github` (the org profile repo,
+already exists).
+
+## Already decided — don't re-litigate
+| Convention | Owner (source of truth) |
+|---|---|
+| Branch naming `type/agent/short-desc`, squash-merge, main-only | repo `CLAUDE.md` → Branching Policy |
+| Conventional Commits | repo `CLAUDE.md` → Key Conventions |
+| Account/service naming | `.agents/rules/account-naming.md` |
+| No secrets, no vendor attribution | `.agents/rules/security.md`, `no-vendor-attribution.md` |
+
+## Rule 1 — Repo naming
+- **kebab-case.** `main` is the default branch. A one-line **description is required.**
+- **Prefixes denote a real namespace — keep them where one applies:**
+  - `hd-` = **Home Depot** (client work) — e.g. `hd-ai-adoption-prototype`.
+  - `delta-` = the **Delta** machine/fleet — e.g. `delta-agents`, `delta-fleet`.
+  - Add a client/machine prefix when the repo is scoped to one; a general
+    product repo gets a bare descriptive name (`founder-mode`).
+- **Avoid a redundant `hummbl-` self-prefix** — the org already says HUMMBL, so
+  `founder-mode` beats `hummbl-founder-mode`. Existing `hummbl-*` repos are
+  fine; just don't add the prefix to new ones.
+- **Forks keep their upstream name** (`rich`, `paramiko`) — never rename a fork.
+  See Rule 3 on whether the fork should exist at all.
+- **README: optional while private, required the moment a repo goes public.**
+  Private repos have no visitor, so don't sink time into READMEs for them. On
+  the flip to public, add one paragraph: what / why / status. It's the front
+  door — nobody lands on a private repo uninvited.
+
+## Rule 2 — Archive vs. delete (the org is 80% graveyard: 33/41 archived)
+The test: **"Did we write it AND might we cite it later?"**
+- **Yes → Archive** (read-only, kept): HUMMBL-original dead experiments with
+  reference/legal value — `evidence-gate`, `hummbl-asi`, `hummbl-assurance`,
+  `HUMMBL-Unified-Tier-Framework`.
+- **No → Delete**, don't archive:
+  - **Third-party forks you don't maintain** — they exist upstream:
+    `rich`, `cli`, `paramiko`, `vllm`, `markitdown`, `awesome-python`,
+    `awesome-ai-agents{,-1,-2026}`, `Real-Time-Voice-Cloning`, `deer-flow`,
+    `adversary-emulation-playbook`. A fork you're not shipping from is not IP,
+    it's noise in every search and diligence scan.
+  - **Junk:** the repo literally named `-` (no name, no branch, no desc). Delete now.
+- Archiving is not a landfill. If the reason to keep it is "might reference,"
+  archive. If there's no reason, delete.
+
+## Rule 3 — OPSEC: the org is a brand & trust surface
+A governance vendor's org gets read by the buyer during diligence (same reason
+`numberOfEmployees:1` in hummbl.io's JSON-LD matters). Treat it like the website.
+- **No forks of jailbreak / prompt-injection / offensive red-team repos in
+  `hummbl-dev`.** Currently present as `elder-plinius/*` forks:
+  `L1B3RT4S`, `G0DM0D3`, `CL4R1T4S`, `OBLITERATUS`, `V3SP3R`, `ST3GG`,
+  `NATURALIS-FUTURA`, `sint-protocol`. A CISO evaluating "AI governance" who
+  finds jailbreak repos in your org discounts the whole pitch. **Remove them**
+  (delete, or move to a separate private non-hummbl-branded org for red-team
+  research).
+- Leetspeak/edgy repo names don't belong in the company namespace either —
+  same reason.
+
+---
+**Net action list (do this before writing any new doc):**
+1. Delete the `-` repo.
+2. Remove the 8 `elder-plinius`/leetspeak forks from `hummbl-dev`.
+3. Delete the unmaintained third-party forks (~11 repos).
+4. Add descriptions to the 3 active repos missing one.
+That cuts the org from 41 → ~20 real repos. The guide is the easy part; the
+cleanup is the value.