dos-kernel 0.24.1__tar.gz → 0.26.0__tar.gz

{dos_kernel-0.24.1/src/dos_kernel.egg-info → dos_kernel-0.26.0}/PKG-INFO

@@ -1,15 +1,18 @@
 Metadata-Version: 2.4
 Name: dos-kernel
-Version: 0.24.1
+Version: 0.26.0
 Summary: Dispatch Operating System — the domain-free trust substrate for fleets of autonomous agents (verdict spine, ship oracle, structured refusal, lane arbiter, correlation spine).
 Author: Anthony Chaudhary
 License: MIT
 Project-URL: Homepage, https://github.com/anthony-chaudhary/dos-kernel
+Project-URL: Website, https://anthony-chaudhary.github.io/dos-kernel/
 Project-URL: Documentation, https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/QUICKSTART.md
+Project-URL: FAQ, https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/FAQ.md
+Project-URL: llms.txt, https://raw.githubusercontent.com/anthony-chaudhary/dos-kernel/master/llms.txt
 Project-URL: Repository, https://github.com/anthony-chaudhary/dos-kernel
 Project-URL: Issues, https://github.com/anthony-chaudhary/dos-kernel/issues
 Project-URL: Changelog, https://github.com/anthony-chaudhary/dos-kernel/tree/master/docs/releases
-Keywords: agents,ai-agents,llm,multi-agent,agent-orchestration,orchestration,dispatch,scheduler,oracle,leases,verification,trust,mcp
+Keywords: agents,ai-agents,llm,multi-agent,agent-orchestration,orchestration,dispatch,scheduler,oracle,leases,verification,trust,mcp,claude,claude-code,mcp-server,model-context-protocol,agent-verification,autonomous-agents,agent-monitoring
 Classifier: Development Status :: 4 - Beta
 Classifier: Intended Audience :: Developers
 Classifier: License :: OSI Approved :: MIT License
@@ -43,6 +46,8 @@ Requires-Dist: slack-helpers>=0.2; extra == "notify-slack"
 Provides-Extra: export-otlp
 Requires-Dist: opentelemetry-sdk>=1.20; extra == "export-otlp"
 Requires-Dist: opentelemetry-exporter-otlp-proto-http>=1.20; extra == "export-otlp"
+Provides-Extra: memory-mem0
+Requires-Dist: mem0ai>=0.1; extra == "memory-mem0"
 Provides-Extra: paper
 Requires-Dist: arxiv-latex-cleaner>=1.0; extra == "paper"
 Dynamic: license-file
@@ -61,8 +66,18 @@ Dynamic: license-file
 [![Python versions](https://img.shields.io/pypi/pyversions/dos-kernel)](https://pypi.org/project/dos-kernel/)
 [![CI](https://github.com/anthony-chaudhary/dos-kernel/actions/workflows/ci.yml/badge.svg)](https://github.com/anthony-chaudhary/dos-kernel/actions/workflows/ci.yml)
 [![verified by DOS](https://github.com/anthony-chaudhary/dos-kernel/actions/workflows/dos-gate.yml/badge.svg)](https://github.com/anthony-chaudhary/dos-kernel/actions/workflows/dos-gate.yml)
+[![commit-claims](https://img.shields.io/endpoint?url=https%3A%2F%2Fraw.githubusercontent.com%2Fanthony-chaudhary%2Fdos-kernel%2Fmaster%2Fdocs%2Fscoreboard%2Fanthony-chaudhary%2Fdos-kernel%2Fbadge.json)](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/scoreboard/methodology.md)
 [![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](https://github.com/anthony-chaudhary/dos-kernel/blob/master/LICENSE)
 
+<p align="center">
+  <img src="https://raw.githubusercontent.com/anthony-chaudhary/dos-kernel/master/docs/assets/caught-lie-cast.svg" alt="A terminal recording of the caught lie. The agent reports: Done! Shipped the login endpoint (AUTH1) and the password reset (AUTH2). git log shows one commit — AUTH1: ship the login endpoint. dos verify AUTH AUTH1 answers SHIPPED (exit 0); dos verify AUTH AUTH2 answers NOT_SHIPPED via none (exit 1) — caught. The exit code is the verdict: gate the agent's done on it and a false claim cannot land." width="100%">
+  <br>
+  <em>The whole pitch in one recording: the agent claims two features shipped; git backs one.
+  <code>dos verify</code> answers from the commits, the lie exits <code>1</code>, and a gate on that
+  exit code refuses the false "done". Every line is the real CLI's verbatim output —
+  <a href="https://github.com/anthony-chaudhary/dos-kernel/blob/master/scripts/build_caught_lie_cast.py"><code>scripts/build_caught_lie_cast.py</code></a> re-records it whenever the output changes.</em>
+</p>
+
 <p align="center">
   <img src="https://raw.githubusercontent.com/anthony-chaudhary/dos-kernel/master/docs/assets/loop-hero.svg" alt="Two agent fleets side by side. Left, no referee: agents all report 'done!', every report is believed, and silent corruption (lies, collisions, spin) piles up into a codebase that 'sorta works' and can't be changed. Right, DOS adjudicates: dos verify reads git and the run branches to SHIPPED (exit 0, land it) or NOT_SHIPPED (exit 1, re-dispatch — caught), and that verdict steers the next step." width="100%">
   <br>
@@ -96,7 +111,23 @@ zero config, and the only thing you ever install is one small Python package.
 > ⏱️ **Want to try it right now?** Jump to **[Try it in 60 seconds](#try-it-in-60-seconds)**
 > — one command, real output, then come back for the why.
 
-<sub>**v0.24.1** · 3900+ tests · CI: Python 3.11–3.13 on Linux + a Windows 3.13
+> ⚡ **Or just add it — two commands, zero decisions.** From the repo where your
+> agent works:
+>
+> ```bash
+> pip install dos-kernel
+> dos init --hooks auto   # finds the agent runtime(s) you already use, wires in the checks
+> ```
+>
+> From then on: your agent can't tell you **"done"** unless the work actually
+> landed, two agents can't silently overwrite each other's files, and a run
+> that stalls gets flagged instead of quietly spinning. Nothing about your
+> workflow changes, and you don't need to learn any of the vocabulary below to
+> be covered. It prints the one config file it wrote; deleting the `dos hook`
+> entries there undoes it. (No runtime detected? It says so and lists the
+> names to pick from — it never guesses.)
+
+<sub>**v0.26.0** · 3900+ tests · CI: Python 3.11–3.13 on Linux + a Windows 3.13
 smoke run · the only runtime dependency is **PyYAML** · **MIT**.</sub>
 
 > 🧭 **Want it in plain words first?** What DOS is, what it catches, and what
@@ -549,9 +580,11 @@ first (`dos_verify` "did it ship?", `dos_commit_audit` "does this commit's claim
 match its diff?", `dos_status` one folded fact about a run), then
 `dos_arbitrate` (may two workers run without colliding?), the structured-refusal
 pair (`dos_refuse_reasons` / `dos_check_reason`), `dos_recall` (is this recalled
-memory still true?), and `dos_doctor` (the workspace report) — so any
-MCP-speaking host — Claude Desktop, Cursor, Cline, Trae, an Agent-SDK app — can
-call the referee over JSON-on-stdio with zero Python coupling. Each verdict comes
+memory still true?), `dos_citation_resolve` (does this cited legal case exist in
+a third-party reporter? — the *Mata v. Avianca* witness), and `dos_doctor` (the
+workspace report) — so any
+MCP-speaking host — Claude Desktop, Claude Cowork, Cursor, Cline, Trae, an
+Agent-SDK app — can call the referee over JSON-on-stdio with zero Python coupling. Each verdict comes
 back with a one-line interpretation of what it means for the agent's next move.
 (See **[the MCP server surface](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/80_mcp-server-surface.md)**.)
 
@@ -566,6 +599,20 @@ thinks to. The per-host wiring for Cursor / Codex / Gemini is in
 **[the MCP README](https://github.com/anthony-chaudhary/dos-kernel/blob/master/src/dos_mcp/README.md)** — all four are MCP clients, so this
 works on every one of them with zero code.
 
+**Gemini CLI users get a one-liner.** DOS ships a `gemini-extension.json`
+manifest at the repo root, so the whole referee — the MCP server plus a context
+file that tells the model to gate its own done-claims — installs as one Gemini
+extension, no clone and no config edit:
+
+```bash
+pip install 'dos-kernel[mcp]'   # the server the extension launches
+gemini extensions install https://github.com/anthony-chaudhary/dos-kernel
+```
+
+The same manifest is what Google's auto-indexed
+[extensions gallery](https://geminicli.com/extensions/) crawls, so the listing
+is automatic.
+
 ### …then make the verdict *act* (hooks)
 
 To go from "the agent can ask" to "the host won't let a bad call through", wire
@@ -573,22 +620,46 @@ DOS's hooks into the runtime you actually run. One command per host — it write
 that host's own hook-config file, merged into anything already there:
 
 ```bash
+dos init --hooks auto .          # don't know the names below? this detects the
+                                 # runtime(s) this repo already uses and wires them all
 dos init --hooks claude-code .   # .claude/settings.json
 dos init --hooks cursor .        # .cursor/hooks.json
 dos init --hooks codex .         # .codex/config.toml
 dos init --hooks gemini .        # .gemini/settings.json
 dos init --hooks antigravity .   # .agents/hooks.json
+dos init --hooks claude-cowork . # the SAME .claude/settings.json Claude Code reads
 ```
 
+The list above is illustrative, not authoritative — the live matrix is a verb:
+`dos hosts` prints every host DOS can wire, sourced from the registries themselves
+(`dos hosts --json` for tooling), so the table never rots out of sync with what
+`dos init --hooks` actually installs. Each row carries the host's tier, the events
+it binds, its dialect, its config path, the exact wiring command, and the host's
+own caveat (Codex's partial tool coverage, Cowork's not-yet-firing hooks). A host
+with **no** row is itself the signal: it has no hook seam, so its DOS surface is
+the advisory one (MCP + skills).
+
 That binds three shipped hooks: `pretool` denies a structurally-refused call
 before it runs, `stop` refuses a stop on an unverified "done," `posttool`
 re-surfaces a stalled stream. This is the **enforcement** path (the *host*
 denies on a DOS verdict) — the complement to MCP's advisory path. Until
-recently this spoke only Claude Code; it now installs across five hosts —
-Claude Code, Cursor, Codex, Gemini, and Antigravity
+recently this spoke only Claude Code; it now installs across six hosts —
+Claude Code, Cursor, Codex, Gemini, Antigravity, and Claude Cowork
 ([docs/221](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/221_the-cross-vendor-hook-installer.md),
-[docs/269](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/269_antigravity-the-fifth-host.md)).
-`--with-hooks` is the back-compat alias for `--hooks claude-code`.
+[docs/269](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/269_antigravity-the-fifth-host.md),
+[docs/298](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/298_claude-cowork-the-sixth-host-shared-surface.md)).
+`--with-hooks` is the back-compat alias for `--hooks claude-code`. `auto`
+([docs/303](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/303_hooks-auto-detection-plan.md))
+names the host *for* you: it probes which of those config dirs already exist in
+the repo — plus the shell's own environment, so a fresh repo opened inside
+Claude Code still detects — wires every runtime it finds (a shared config file
+is wired once), and fails loud with the list above when nothing is detectable,
+never guessing. Claude
+Cowork is the *shared-surface* host: it runs the same agent harness as Claude
+Code, so wiring either name binds both — one file, one set of hooks. (One
+honest caveat, carried on the install note itself: the Cowork app doesn't
+*fire* hooks yet — anthropics/claude-code#63360 — so until that closes,
+Cowork's working DOS surface is the advisory one above.)
 
 Under the installer sits a pluggable dialect seam: the verdict is decided
 once, then rendered into whatever JSON shape the host parses
@@ -770,9 +841,9 @@ pip install "dos-kernel[mcp]"
 
 After installing, run **`/dos-kernel:dos-setup`** once — it confirms the package
 is importable, reports what the plugin wired, and points at the next skill. The
-same three hooks are available à la carte via `dos init --hooks claude-code`
-(and for Cursor / Codex / Gemini); the plugin is just the pre-packaged Claude
-Code form. The bundle's design + the build that keeps its skills in lockstep
+same three hooks are available à la carte via `dos init --hooks auto` (detects
+your runtime; or name one — claude-code, cursor, codex, gemini, antigravity,
+claude-cowork); the plugin is just the pre-packaged Claude Code form. The bundle's design + the build that keeps its skills in lockstep
 with the source are in **[claude-plugin/README.md](https://github.com/anthony-chaudhary/dos-kernel/blob/master/claude-plugin/README.md)**.
 
 ## CLI
@@ -990,12 +1061,33 @@ for a copy-me skeleton.
 ## Documentation
 
 - **[docs/QUICKSTART.md](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/QUICKSTART.md)** — runnable 5-minute hello-world. Start here.
+- **[docs/FAQ.md](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/FAQ.md)** — the arriving questions ("how do I
+  verify an agent's claim?", "does it need an LLM?"), each answered in one
+  self-contained block.
+- **[docs/ALTERNATIVES.md](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/ALTERNATIVES.md)** — DOS and the
+  alternatives: evals, framework guardrails, Temporal, in-toto, plain CI —
+  what each does well, what DOS adds, and when NOT to use DOS.
 - **[docs/README.md](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/README.md)** — the docs index (guides vs. design notes
   vs. the dated build-journal; the numbers are chronology, not a reading order).
 - **[docs/HACKING.md](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/HACKING.md)** — extend DOS without forking it.
+- **[docs/DOT_DOS.md](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/DOT_DOS.md)** — the `.dos`
+  surface: what that directory is, why it's safe to delete, and the
+  repo-resident state contract (policy in `dos.toml`, fossils under `.dos/`,
+  verdicts in git) that keeps every host adapter thin.
+- **[docs/STABILITY.md](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/STABILITY.md)** — the compatibility
+  promise: what you may depend on, what SemVer means here, how deprecations
+  are announced (`DosDeprecationWarning`, a two-minor-release window), and
+  what will never break.
 - **[CLAUDE.md](https://github.com/anthony-chaudhary/dos-kernel/blob/master/CLAUDE.md)** / **[CONTRIBUTING.md](https://github.com/anthony-chaudhary/dos-kernel/blob/master/CONTRIBUTING.md)** — the
   architecture contract and how to send a change.
+- **[verify-action/](https://github.com/anthony-chaudhary/dos-kernel/blob/master/verify-action/README.md)** — the CI gate: a
+  composite Action and a reusable workflow that run `dos commit-audit` on every
+  PR and merge-queue group and post the verdict as the named **dos-verify**
+  status check; make it required and GitHub enforces what the kernel decides
+  (the *verified by DOS* badge above is this gate on the kernel's own repo).
 - **[docs/releases/](https://github.com/anthony-chaudhary/dos-kernel/tree/master/docs/releases)** — per-version release notes (the changelog).
+- **[The website](https://anthony-chaudhary.github.io/dos-kernel/)** — this page,
+  condensed to one screen (good for sending to someone).
 
 ## Playbooks & examples
 
@@ -1017,6 +1109,10 @@ back verbatim:
   CrewAI, AutoGen, the OpenAI/Claude Agents SDK — with every framework recipe also
   shipped as a runnable, suite-pinned file under
   [`examples/fleet_frameworks/`](https://github.com/anthony-chaudhary/dos-kernel/tree/master/examples/fleet_frameworks).
+  Two seats ship as drivers in the package itself ([docs/305](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/305_guardrail-seat-pair-openai-agents-and-crewai-plan.md)):
+  an OpenAI Agents SDK output guardrail that trips on a deliverable git can't
+  see, and a CrewAI task guardrail that turns the retry loop into a
+  do-the-work loop — one import line each.
 - [**Wire DOS into a Hermes / OpenClaw swarm**](https://github.com/anthony-chaudhary/dos-kernel/tree/master/examples/hermes_integration) —
   the offline, A/B-measured swarm-runtime example: the `exec-capability` gate
   refuses a prompt-injected command before it runs (real at a single agent), and

{dos_kernel-0.24.1 → dos_kernel-0.26.0}/README.md

@@ -12,8 +12,18 @@
 [![Python versions](https://img.shields.io/pypi/pyversions/dos-kernel)](https://pypi.org/project/dos-kernel/)
 [![CI](https://github.com/anthony-chaudhary/dos-kernel/actions/workflows/ci.yml/badge.svg)](https://github.com/anthony-chaudhary/dos-kernel/actions/workflows/ci.yml)
 [![verified by DOS](https://github.com/anthony-chaudhary/dos-kernel/actions/workflows/dos-gate.yml/badge.svg)](https://github.com/anthony-chaudhary/dos-kernel/actions/workflows/dos-gate.yml)
+[![commit-claims](https://img.shields.io/endpoint?url=https%3A%2F%2Fraw.githubusercontent.com%2Fanthony-chaudhary%2Fdos-kernel%2Fmaster%2Fdocs%2Fscoreboard%2Fanthony-chaudhary%2Fdos-kernel%2Fbadge.json)](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/scoreboard/methodology.md)
 [![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](https://github.com/anthony-chaudhary/dos-kernel/blob/master/LICENSE)
 
+<p align="center">
+  <img src="https://raw.githubusercontent.com/anthony-chaudhary/dos-kernel/master/docs/assets/caught-lie-cast.svg" alt="A terminal recording of the caught lie. The agent reports: Done! Shipped the login endpoint (AUTH1) and the password reset (AUTH2). git log shows one commit — AUTH1: ship the login endpoint. dos verify AUTH AUTH1 answers SHIPPED (exit 0); dos verify AUTH AUTH2 answers NOT_SHIPPED via none (exit 1) — caught. The exit code is the verdict: gate the agent's done on it and a false claim cannot land." width="100%">
+  <br>
+  <em>The whole pitch in one recording: the agent claims two features shipped; git backs one.
+  <code>dos verify</code> answers from the commits, the lie exits <code>1</code>, and a gate on that
+  exit code refuses the false "done". Every line is the real CLI's verbatim output —
+  <a href="https://github.com/anthony-chaudhary/dos-kernel/blob/master/scripts/build_caught_lie_cast.py"><code>scripts/build_caught_lie_cast.py</code></a> re-records it whenever the output changes.</em>
+</p>
+
 <p align="center">
   <img src="https://raw.githubusercontent.com/anthony-chaudhary/dos-kernel/master/docs/assets/loop-hero.svg" alt="Two agent fleets side by side. Left, no referee: agents all report 'done!', every report is believed, and silent corruption (lies, collisions, spin) piles up into a codebase that 'sorta works' and can't be changed. Right, DOS adjudicates: dos verify reads git and the run branches to SHIPPED (exit 0, land it) or NOT_SHIPPED (exit 1, re-dispatch — caught), and that verdict steers the next step." width="100%">
   <br>
@@ -47,7 +57,23 @@ zero config, and the only thing you ever install is one small Python package.
 > ⏱️ **Want to try it right now?** Jump to **[Try it in 60 seconds](#try-it-in-60-seconds)**
 > — one command, real output, then come back for the why.
 
-<sub>**v0.24.1** · 3900+ tests · CI: Python 3.11–3.13 on Linux + a Windows 3.13
+> ⚡ **Or just add it — two commands, zero decisions.** From the repo where your
+> agent works:
+>
+> ```bash
+> pip install dos-kernel
+> dos init --hooks auto   # finds the agent runtime(s) you already use, wires in the checks
+> ```
+>
+> From then on: your agent can't tell you **"done"** unless the work actually
+> landed, two agents can't silently overwrite each other's files, and a run
+> that stalls gets flagged instead of quietly spinning. Nothing about your
+> workflow changes, and you don't need to learn any of the vocabulary below to
+> be covered. It prints the one config file it wrote; deleting the `dos hook`
+> entries there undoes it. (No runtime detected? It says so and lists the
+> names to pick from — it never guesses.)
+
+<sub>**v0.26.0** · 3900+ tests · CI: Python 3.11–3.13 on Linux + a Windows 3.13
 smoke run · the only runtime dependency is **PyYAML** · **MIT**.</sub>
 
 > 🧭 **Want it in plain words first?** What DOS is, what it catches, and what
@@ -500,9 +526,11 @@ first (`dos_verify` "did it ship?", `dos_commit_audit` "does this commit's claim
 match its diff?", `dos_status` one folded fact about a run), then
 `dos_arbitrate` (may two workers run without colliding?), the structured-refusal
 pair (`dos_refuse_reasons` / `dos_check_reason`), `dos_recall` (is this recalled
-memory still true?), and `dos_doctor` (the workspace report) — so any
-MCP-speaking host — Claude Desktop, Cursor, Cline, Trae, an Agent-SDK app — can
-call the referee over JSON-on-stdio with zero Python coupling. Each verdict comes
+memory still true?), `dos_citation_resolve` (does this cited legal case exist in
+a third-party reporter? — the *Mata v. Avianca* witness), and `dos_doctor` (the
+workspace report) — so any
+MCP-speaking host — Claude Desktop, Claude Cowork, Cursor, Cline, Trae, an
+Agent-SDK app — can call the referee over JSON-on-stdio with zero Python coupling. Each verdict comes
 back with a one-line interpretation of what it means for the agent's next move.
 (See **[the MCP server surface](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/80_mcp-server-surface.md)**.)
 
@@ -517,6 +545,20 @@ thinks to. The per-host wiring for Cursor / Codex / Gemini is in
 **[the MCP README](https://github.com/anthony-chaudhary/dos-kernel/blob/master/src/dos_mcp/README.md)** — all four are MCP clients, so this
 works on every one of them with zero code.
 
+**Gemini CLI users get a one-liner.** DOS ships a `gemini-extension.json`
+manifest at the repo root, so the whole referee — the MCP server plus a context
+file that tells the model to gate its own done-claims — installs as one Gemini
+extension, no clone and no config edit:
+
+```bash
+pip install 'dos-kernel[mcp]'   # the server the extension launches
+gemini extensions install https://github.com/anthony-chaudhary/dos-kernel
+```
+
+The same manifest is what Google's auto-indexed
+[extensions gallery](https://geminicli.com/extensions/) crawls, so the listing
+is automatic.
+
 ### …then make the verdict *act* (hooks)
 
 To go from "the agent can ask" to "the host won't let a bad call through", wire
@@ -524,22 +566,46 @@ DOS's hooks into the runtime you actually run. One command per host — it write
 that host's own hook-config file, merged into anything already there:
 
 ```bash
+dos init --hooks auto .          # don't know the names below? this detects the
+                                 # runtime(s) this repo already uses and wires them all
 dos init --hooks claude-code .   # .claude/settings.json
 dos init --hooks cursor .        # .cursor/hooks.json
 dos init --hooks codex .         # .codex/config.toml
 dos init --hooks gemini .        # .gemini/settings.json
 dos init --hooks antigravity .   # .agents/hooks.json
+dos init --hooks claude-cowork . # the SAME .claude/settings.json Claude Code reads
 ```
 
+The list above is illustrative, not authoritative — the live matrix is a verb:
+`dos hosts` prints every host DOS can wire, sourced from the registries themselves
+(`dos hosts --json` for tooling), so the table never rots out of sync with what
+`dos init --hooks` actually installs. Each row carries the host's tier, the events
+it binds, its dialect, its config path, the exact wiring command, and the host's
+own caveat (Codex's partial tool coverage, Cowork's not-yet-firing hooks). A host
+with **no** row is itself the signal: it has no hook seam, so its DOS surface is
+the advisory one (MCP + skills).
+
 That binds three shipped hooks: `pretool` denies a structurally-refused call
 before it runs, `stop` refuses a stop on an unverified "done," `posttool`
 re-surfaces a stalled stream. This is the **enforcement** path (the *host*
 denies on a DOS verdict) — the complement to MCP's advisory path. Until
-recently this spoke only Claude Code; it now installs across five hosts —
-Claude Code, Cursor, Codex, Gemini, and Antigravity
+recently this spoke only Claude Code; it now installs across six hosts —
+Claude Code, Cursor, Codex, Gemini, Antigravity, and Claude Cowork
 ([docs/221](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/221_the-cross-vendor-hook-installer.md),
-[docs/269](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/269_antigravity-the-fifth-host.md)).
-`--with-hooks` is the back-compat alias for `--hooks claude-code`.
+[docs/269](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/269_antigravity-the-fifth-host.md),
+[docs/298](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/298_claude-cowork-the-sixth-host-shared-surface.md)).
+`--with-hooks` is the back-compat alias for `--hooks claude-code`. `auto`
+([docs/303](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/303_hooks-auto-detection-plan.md))
+names the host *for* you: it probes which of those config dirs already exist in
+the repo — plus the shell's own environment, so a fresh repo opened inside
+Claude Code still detects — wires every runtime it finds (a shared config file
+is wired once), and fails loud with the list above when nothing is detectable,
+never guessing. Claude
+Cowork is the *shared-surface* host: it runs the same agent harness as Claude
+Code, so wiring either name binds both — one file, one set of hooks. (One
+honest caveat, carried on the install note itself: the Cowork app doesn't
+*fire* hooks yet — anthropics/claude-code#63360 — so until that closes,
+Cowork's working DOS surface is the advisory one above.)
 
 Under the installer sits a pluggable dialect seam: the verdict is decided
 once, then rendered into whatever JSON shape the host parses
@@ -721,9 +787,9 @@ pip install "dos-kernel[mcp]"
 
 After installing, run **`/dos-kernel:dos-setup`** once — it confirms the package
 is importable, reports what the plugin wired, and points at the next skill. The
-same three hooks are available à la carte via `dos init --hooks claude-code`
-(and for Cursor / Codex / Gemini); the plugin is just the pre-packaged Claude
-Code form. The bundle's design + the build that keeps its skills in lockstep
+same three hooks are available à la carte via `dos init --hooks auto` (detects
+your runtime; or name one — claude-code, cursor, codex, gemini, antigravity,
+claude-cowork); the plugin is just the pre-packaged Claude Code form. The bundle's design + the build that keeps its skills in lockstep
 with the source are in **[claude-plugin/README.md](https://github.com/anthony-chaudhary/dos-kernel/blob/master/claude-plugin/README.md)**.
 
 ## CLI
@@ -941,12 +1007,33 @@ for a copy-me skeleton.
 ## Documentation
 
 - **[docs/QUICKSTART.md](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/QUICKSTART.md)** — runnable 5-minute hello-world. Start here.
+- **[docs/FAQ.md](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/FAQ.md)** — the arriving questions ("how do I
+  verify an agent's claim?", "does it need an LLM?"), each answered in one
+  self-contained block.
+- **[docs/ALTERNATIVES.md](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/ALTERNATIVES.md)** — DOS and the
+  alternatives: evals, framework guardrails, Temporal, in-toto, plain CI —
+  what each does well, what DOS adds, and when NOT to use DOS.
 - **[docs/README.md](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/README.md)** — the docs index (guides vs. design notes
   vs. the dated build-journal; the numbers are chronology, not a reading order).
 - **[docs/HACKING.md](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/HACKING.md)** — extend DOS without forking it.
+- **[docs/DOT_DOS.md](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/DOT_DOS.md)** — the `.dos`
+  surface: what that directory is, why it's safe to delete, and the
+  repo-resident state contract (policy in `dos.toml`, fossils under `.dos/`,
+  verdicts in git) that keeps every host adapter thin.
+- **[docs/STABILITY.md](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/STABILITY.md)** — the compatibility
+  promise: what you may depend on, what SemVer means here, how deprecations
+  are announced (`DosDeprecationWarning`, a two-minor-release window), and
+  what will never break.
 - **[CLAUDE.md](https://github.com/anthony-chaudhary/dos-kernel/blob/master/CLAUDE.md)** / **[CONTRIBUTING.md](https://github.com/anthony-chaudhary/dos-kernel/blob/master/CONTRIBUTING.md)** — the
   architecture contract and how to send a change.
+- **[verify-action/](https://github.com/anthony-chaudhary/dos-kernel/blob/master/verify-action/README.md)** — the CI gate: a
+  composite Action and a reusable workflow that run `dos commit-audit` on every
+  PR and merge-queue group and post the verdict as the named **dos-verify**
+  status check; make it required and GitHub enforces what the kernel decides
+  (the *verified by DOS* badge above is this gate on the kernel's own repo).
 - **[docs/releases/](https://github.com/anthony-chaudhary/dos-kernel/tree/master/docs/releases)** — per-version release notes (the changelog).
+- **[The website](https://anthony-chaudhary.github.io/dos-kernel/)** — this page,
+  condensed to one screen (good for sending to someone).
 
 ## Playbooks & examples
 
@@ -968,6 +1055,10 @@ back verbatim:
   CrewAI, AutoGen, the OpenAI/Claude Agents SDK — with every framework recipe also
   shipped as a runnable, suite-pinned file under
   [`examples/fleet_frameworks/`](https://github.com/anthony-chaudhary/dos-kernel/tree/master/examples/fleet_frameworks).
+  Two seats ship as drivers in the package itself ([docs/305](https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/305_guardrail-seat-pair-openai-agents-and-crewai-plan.md)):
+  an OpenAI Agents SDK output guardrail that trips on a deliverable git can't
+  see, and a CrewAI task guardrail that turns the retry loop into a
+  do-the-work loop — one import line each.
 - [**Wire DOS into a Hermes / OpenClaw swarm**](https://github.com/anthony-chaudhary/dos-kernel/tree/master/examples/hermes_integration) —
   the offline, A/B-measured swarm-runtime example: the `exec-capability` gate
   refuses a prompt-injected command before it runs (real at a single agent), and

{dos_kernel-0.24.1 → dos_kernel-0.26.0}/pyproject.toml

@@ -9,7 +9,7 @@ build-backend = "setuptools.build_meta"
 # src/), and the console scripts stay `dos` / `dos-mcp` — only the pip-install /
 # dependency-pin name is `dos-kernel`. See SECURITY.md "Supply chain".
 name = "dos-kernel"
-version = "0.24.1"
+version = "0.26.0"
 description = "Dispatch Operating System — the domain-free trust substrate for fleets of autonomous agents (verdict spine, ship oracle, structured refusal, lane arbiter, correlation spine)."
 # The PyPI project page renders this. Point it at the README so the page isn't
 # blank below the metadata (twine warns when it's missing). PyPI resolves
@@ -24,6 +24,11 @@ keywords = [
     "agents", "ai-agents", "llm", "multi-agent", "agent-orchestration",
     "orchestration", "dispatch", "scheduler", "oracle", "leases",
     "verification", "trust", "mcp",
+    # The arrival terms an agent or answer engine actually types (docs/299 P3).
+    # Honesty rule: every keyword must be true of the package — no aspirational
+    # or adjacent-product terms.
+    "claude", "claude-code", "mcp-server", "model-context-protocol",
+    "agent-verification", "autonomous-agents", "agent-monitoring",
 ]
 classifiers = [
     "Development Status :: 4 - Beta",
@@ -118,6 +123,18 @@ export-otlp = [
     "opentelemetry-sdk>=1.20",
     "opentelemetry-exporter-otlp-proto-http>=1.20",
 ]
+# The Mem0 memory-store driver (src/dos/drivers/memory_mem0, docs/314 P3). Kept OUT
+# of the core for the same reason as [mcp]/[tui]/[notify-slack]: the kernel stays
+# near-stdlib. `dos memory recall/verify/admit` work with NO extra (the built-in
+# `file` store; the admit gate reads only candidate bytes); this extra adds only the
+# Mem0 SDK so the same gates sweep a HOSTED memory store. The driver imports the SDK
+# LAZILY (inside the client builder, never at module load) and fails with an install
+# hint only when a read is attempted — so entry-point discovery of the driver never
+# fails for lack of it (the notify_slack discipline). The store seam
+# (dos.memory_stores) names no provider and stays dependency-free.
+memory-mem0 = [
+    "mem0ai>=0.1",
+]
 # The arXiv paper bundle tooling (paper/arxiv/make_bundle.py). NOT part of the
 # kernel — it operates on the paper, which itself only `import dos`-es nothing
 # (the paper is downstream of the code, the one-way arrow). Kept OUT of the core
@@ -188,6 +205,10 @@ codex = "dos.drivers.hook_dialects:CodexDialect"
 gemini = "dos.drivers.hook_dialects:GeminiDialect"
 cursor = "dos.drivers.hook_dialects:CursorDialect"
 antigravity = "dos.drivers.hook_dialects:AntigravityDialect"
+# Claude Cowork runs the Claude Code agent harness in a desktop VM, so its envelope
+# IS CC's — the renderer delegates (the Codex precedent), kept as a named entry so
+# `--dialect claude-cowork` resolves and a future divergence has a home (docs/298).
+claude-cowork = "dos.drivers.hook_dialects:ClaudeCoworkDialect"
 # Hermes Agent (Nous Research) — its `pre_tool_call` SHELL hook is a real
 # stdout-JSON deny surface (`{"decision":"block","reason":…}`), docs/278. (OpenClaw's
 # real hook is an in-process TS return, not stdout — no renderer consumer; SwarmClaw
@@ -282,10 +303,34 @@ codex = "dos.drivers.hook_dialects:codex_install_spec"
 gemini = "dos.drivers.hook_dialects:gemini_install_spec"
 cursor = "dos.drivers.hook_dialects:cursor_install_spec"
 antigravity = "dos.drivers.hook_dialects:antigravity_install_spec"
+# Claude Cowork — the SHARED surface: the same .claude/settings.json Claude Code
+# reads (same harness, same file; the wired command carries NO --dialect because the
+# shared file must serve both runtimes and the default IS the envelope). The spec's
+# note carries the one Cowork-specific fact: the product does not fire hooks yet
+# (anthropics/claude-code#63360, docs/298).
+claude-cowork = "dos.drivers.hook_dialects:claude_cowork_install_spec"
+
+# The memory-STORE providers (docs/314 P2/P3) — where a fleet's memories live, so
+# the recall gate (docs/103) and the write gate (`dos memory admit`) can run against
+# hosted memory, not just a directory of markdown. The kernel seam
+# (`dos.memory_stores`) holds the read-only MemoryStore Protocol + resolver + the
+# ONE unshadowable `file` built-in; every provider store names its vendor as code
+# (a Mem0 store is inherently Mem0-specific), which the vendor-blindness litmus
+# forbids in a kernel module — so it lives in a DRIVER and registers here, the same
+# kernel/driver split as `dos.judges` / `dos.notifiers`. `--store-kind mem0`
+# discovers it by name; the kernel imports none of them. The `mem0` store needs the
+# `[memory-mem0]` extra; its lazy import means discovering it here never fails when
+# the extra is absent (it resolves, and reports the install hint only on a read).
+[project.entry-points."dos.memory_stores"]
+mem0 = "dos.drivers.memory_mem0:Mem0Store"
 
 [project.urls]
 Homepage = "https://github.com/anthony-chaudhary/dos-kernel"
+Website = "https://anthony-chaudhary.github.io/dos-kernel/"
 Documentation = "https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/QUICKSTART.md"
+FAQ = "https://github.com/anthony-chaudhary/dos-kernel/blob/master/docs/FAQ.md"
+# The agent-facing index (docs/299): the raw URL is the fetchable spelling.
+"llms.txt" = "https://raw.githubusercontent.com/anthony-chaudhary/dos-kernel/master/llms.txt"
 Repository = "https://github.com/anthony-chaudhary/dos-kernel"
 Issues = "https://github.com/anthony-chaudhary/dos-kernel/issues"
 Changelog = "https://github.com/anthony-chaudhary/dos-kernel/tree/master/docs/releases"

{dos_kernel-0.24.1 → dos_kernel-0.26.0}/src/dos/__init__.py

@@ -46,7 +46,7 @@ try:
 
     __version__ = _pkg_version("dos-kernel")
 except Exception:  # pragma: no cover - source-tree / not-installed fallback
-    __version__ = "0.24.1"
+    __version__ = "0.26.0"
 
 from dos import config  # noqa: F401  (re-export the seam as the package entry)
 from dos.config import (  # noqa: F401
@@ -166,6 +166,17 @@ from dos.reward import (  # noqa: F401  (the reward-set admission verdict, docs/
     AcceptanceAB,
     acceptance_ab as reward_acceptance_ab,
 )
+from dos.deprecation import (  # noqa: F401  (the typed deprecation category, docs/308)
+    DosDeprecationWarning,
+    warn_deprecated,
+)
+from dos.verified import (  # noqa: F401  (the in-process verify gate, issue #75)
+    # NB: this deliberately rebinds the `dos.verified` attribute from the
+    # submodule to the callable, so `from dos import verified` yields the
+    # decorator/context-manager (the issue-#75 surface), datetime.datetime-style.
+    verified,
+    NotShippedError,
+)
 
 __all__ = [
     "__version__",
@@ -258,4 +269,8 @@ __all__ = [
     "reward_admit",
     "AcceptanceAB",
     "reward_acceptance_ab",
+    "DosDeprecationWarning",
+    "warn_deprecated",
+    "verified",
+    "NotShippedError",
 ]