brigade-cli 0.5.0__tar.gz

brigade_cli-0.5.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Solomon Neas
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

brigade_cli-0.5.0/MANIFEST.in

@@ -0,0 +1,4 @@
+recursive-include src/solo_mise/templates *
+include README.md
+include QUICKSTART.md
+include LICENSE

brigade_cli-0.5.0/PKG-INFO

@@ -0,0 +1,211 @@
+Metadata-Version: 2.4
+Name: brigade-cli
+Version: 0.5.0
+Summary: Run your agent brigade: an operator-system CLI that bootstraps, checks, and operates agent workspaces across harnesses.
+Author-email: Solomon Neas <srneas@gmail.com>
+License: MIT
+Project-URL: Homepage, https://github.com/escoffier-labs/brigade
+Project-URL: Cookbook, https://github.com/solomonneas/solos-cookbook
+Project-URL: Issues, https://github.com/escoffier-labs/brigade/issues
+Keywords: agents,openclaw,claude-code,codex,memory,bootstrap,brigade,operator
+Classifier: Development Status :: 3 - Alpha
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Provides-Extra: dev
+Requires-Dist: pytest>=7; extra == "dev"
+Dynamic: license-file
+
+<p align="center">
+  <img src="docs/assets/solo-mise-banner.png" alt="Solomon's Mise en Place banner">
+</p>
+
+<h1 align="center">Solomon's Mise en Place</h1>
+
+<p align="center">
+  <strong>Mise en place for agent memory.</strong>
+</p>
+
+<p align="center">
+  <em>Public-safe workspace bootstrap, memory handoffs, and publish guards for real agent setups.</em>
+</p>
+
+<p align="center">
+  <img src="https://img.shields.io/github/actions/workflow/status/escoffier-labs/brigade/ci.yml?branch=main&style=for-the-badge&label=ci" alt="CI status">
+  <img src="https://img.shields.io/badge/python-3.10%2B-blue?style=for-the-badge&logo=python&logoColor=white" alt="Python 3.10+">
+  <img src="https://img.shields.io/badge/license-MIT-green?style=for-the-badge" alt="MIT license">
+  <img src="https://img.shields.io/badge/harnesses-4-orange?style=for-the-badge" alt="4 harnesses">
+</p>
+
+<p align="center">
+  <code>brigade</code> is the installable starter kit behind <a href="https://github.com/solomonneas/solos-cookbook">Solomon's Guide to Cookin' with Gas</a>.
+  It gives you the workspace skeleton, handoff inbox, conservative ingester, and publish guard that make a multi-agent setup usable without leaking private junk into public repos.
+</p>
+
+## What this is
+
+Mise en place means "everything in its place before the work starts." In a kitchen, that is chopped mirepoix, clean pans, labels, and a station that does not make you hunt for salt & butter mid-service. For agents, it is the same idea: rules, memory, tools, handoff inboxes, publish guards, and boring verification already laid out before the session gets expensive.
+
+This package lays down a clean starting point for an agent workspace or a repo that needs durable memory handoffs. It is meant for people running real tools, real docs, and real automation across OpenClaw, Claude Code, Codex, Hermes, or a similar harness.
+
+The cookbook explains the why. This package gives you the kitchen.
+
+## What you get
+
+- sanitized bootstrap files for agent behavior, safety, tools, identity, and memory
+- a canonical memory layout where one configured owner holds durable knowledge
+- a shared `.claude/memory-handoffs/` inbox for Claude Code, Codex, and other side harnesses
+- starter memory cards and routing rules
+- multi-workspace handoff patterns for people administering more than one agent setup
+- memory-care staleness checks so durable cards do not quietly rot
+- TokenJuice output-compaction guidance for Claude Code and Codex, including wrapper notes and savings expectations
+- content-guard publish gates so private infrastructure does not leak into public docs
+- adapter fragments for OpenClaw (tested), Hermes (stubbed), and generic harnesses
+- doctor checks that prove the system is wired before you trust it
+
+## What you do not get
+
+- private hostnames, IPs, account IDs, or personal details
+- live auth profiles or OAuth tokens
+- cron jobs that post publicly by default
+- destructive automation or write-enabled integrations without explicit opt-in
+
+## Install
+
+```bash
+pipx install brigade-cli
+```
+
+Or, to track `main`:
+
+```bash
+pipx install git+https://github.com/escoffier-labs/brigade
+```
+
+The workspace config directory is `.brigade` (older `.solo-mise` installs are still read), and the `solo-mise` command is a deprecated alias for `brigade`.
+
+## Quick path
+
+Run `brigade init` with no flags for the interactive picker:
+
+```bash
+brigade init --target ~/agent-kitchen
+```
+
+For CI or scripts, pass flags directly:
+
+```bash
+brigade init --target ~/agent-kitchen --depth workspace --harnesses claude,codex,openclaw
+brigade init --target ./repo --depth repo --harnesses codex
+brigade init --target ./repo --harnesses none           # generic install
+```
+
+Once installed, `brigade doctor` verifies the wiring and `brigade status` reports over the station registry.
+
+## Two axes: depth + harnesses
+
+brigade installs material on two independent axes:
+
+**Depth, how much shared baseline you want:**
+
+| Depth | Installs |
+|---|---|
+| `repo` *(default)* | `AGENTS.md`, `SAFETY_RULES.md`, `INSTALL_FOR_AGENTS.md`, `hooks/pre-push`, `.brigade/policies/public-repo.json` |
+| `workspace` | repo + `MEMORY.md`, `TOOLS.md`, `USER.md`, `SOUL.md`, `IDENTITY.md`, `HEARTBEAT.md`, `memory/cards/`, starter cards |
+
+**Harnesses, which tools you actually use:**
+
+| Harness | Role | Adds |
+|---|---|---|
+| `claude` | writer | `CLAUDE.md` + `.claude/memory-handoffs/` inbox |
+| `codex` | writer | `.codex/memory-handoffs/` inbox (AGENTS.md is in the baseline) |
+| `openclaw` | reader | `.brigade/openclaw/` config fragments + cron stubs |
+| `hermes` | reader | `.brigade/hermes/` adapter fragments (experimental) |
+
+**Includes, optional add-ons:**
+
+| Include | Adds |
+|---|---|
+| `publisher` | `.brigade/policies/public-content.json` + content-safety memory card + scrub-cache |
+
+## Picking your harnesses
+
+Four common combos:
+
+- **Claude Code only:** `--harnesses claude`, the lightest setup, just one writer.
+- **Claude Code + OpenClaw:** `--harnesses claude,openclaw`, durable memory owner (OpenClaw) plus side writer (Claude Code).
+- **Claude Code + Codex + OpenClaw:** `--harnesses claude,codex,openclaw`, both writers feed into OpenClaw as the canonical owner.
+- **Codex + OpenClaw:** `--harnesses codex,openclaw`, Codex-first user with OpenClaw as the canonical store.
+
+The canonical memory owner is picked automatically by priority (`openclaw > hermes > claude > codex > this-repo`). Override with `--owner`.
+
+Re-running `brigade init` against an existing target is safe. It refuses to overwrite tracked files without `--force`, and the `.gitignore` block it manages is replaced between its markers without touching the rest of your file.
+
+See [QUICKSTART.md](QUICKSTART.md) for setup, verification, and the ingest flow.
+
+### What a green doctor looks like
+
+```text
+brigade doctor: target /home/you/agent-kitchen (generic)
+  [ok]   bootstrap: AGENTS.md              /home/you/agent-kitchen/AGENTS.md
+  [ok]   bootstrap: CLAUDE.md              /home/you/agent-kitchen/CLAUDE.md
+  [ok]   bootstrap: MEMORY.md              /home/you/agent-kitchen/MEMORY.md
+  [ok]   bootstrap: TOOLS.md               /home/you/agent-kitchen/TOOLS.md
+  [ok]   bootstrap: USER.md                /home/you/agent-kitchen/USER.md
+  [ok]   bootstrap: SAFETY_RULES.md        /home/you/agent-kitchen/SAFETY_RULES.md
+  [ok]   bootstrap: INSTALL_FOR_AGENTS.md  /home/you/agent-kitchen/INSTALL_FOR_AGENTS.md
+  [ok]   handoff: inbox                    /home/you/agent-kitchen/.claude/memory-handoffs
+  [ok]   handoff: TEMPLATE.md              /home/you/agent-kitchen/.claude/memory-handoffs/TEMPLATE.md
+  [ok]   handoff: processed/               /home/you/agent-kitchen/.claude/memory-handoffs/processed
+  [ok]   memory: cards/                    /home/you/agent-kitchen/memory/cards
+  [ok]   publish: hooks/pre-push           /home/you/agent-kitchen/hooks/pre-push
+  [ok]   publish: content-guard            /home/you/repos/content-guard
+
+summary: 14 checks, 0 failed, 0 manual
+```
+
+Anything `[warn]` is fine; `[fail]` means the install is incomplete. The `openclaw` and `hermes` harnesses add their own checks on top.
+
+### Privacy
+
+brigade makes no network calls. It does not phone home, collect telemetry, or sync anything to a server. Everything happens on your local filesystem against the templates packaged with the install. The only file that touches the network is the `pre-push` hook, and it runs the local `content-guard` scanner against your own commits before they leave the machine.
+
+## The design
+
+One memory owner stays canonical (typically OpenClaw or Hermes when present, otherwise `this-repo`). Writer harnesses drop handoffs into their own inboxes; the ingester scans all of them.
+
+```text
+Claude Code              Codex
+     |                     |
+     v                     v
+.claude/memory-handoffs/ .codex/memory-handoffs/
+     \                   /
+      \                 /
+       v               v
+      brigade ingest
+              |
+              v
+  memory/cards/*.md, TOOLS.md, USER.md,
+  rules/*.md, .learnings/*.md
+```
+
+The ingester is intentionally conservative. Safe card handoffs become cards. Targeted updates append to the right file. Ambiguous material gets kicked out for review instead of being trusted automatically.
+
+For users running multiple agent homes, treat the owner workspace as the hub. Remote or secondary workspaces can write handoffs into their own per-harness inboxes, then a trusted sync pulls those files into a staging inbox on the owner. That keeps agents informed about what happened elsewhere without creating multiple canonical memories.
+
+Token-heavy terminal work gets the same treatment: make the wrapper explicit, make the escape hatch obvious, and tell every harness what is happening. The TokenJuice starter card documents Claude Code's PreToolUse wrapper path, Codex's hook setup, and the savings model.
+
+## Related
+
+- [Solomon's Cookbook](https://github.com/solomonneas/solos-cookbook): the long-form guide and reference docs
+- [content-guard](https://github.com/solomonneas/content-guard): the publish-gate scanner used by the pre-push hook
+- [OpenClaw](https://github.com/openclaw/openclaw): the reference memory owner
+
+## License
+
+MIT

brigade_cli-0.5.0/QUICKSTART.md

@@ -0,0 +1,101 @@
+# Quickstart
+
+Five minutes from clone to a working agent kitchen.
+
+## 1. Install
+
+```bash
+pipx install git+https://github.com/solomonneas/solo-mise
+```
+
+If you do not have `pipx`:
+
+```bash
+python3 -m pip install --user pipx
+python3 -m pipx ensurepath
+```
+
+## First install
+
+The fastest path is to run `solo-mise init` with no flags and answer the prompts:
+
+```bash
+$ solo-mise init --target ~/agent-kitchen
+
+Which harnesses do you use? (type numbers separated by space/comma to toggle, enter to confirm)
+  [x] 1. Claude Code
+  [ ] 2. Codex
+  [ ] 3. OpenClaw
+  [ ] 4. Hermes (experimental)
+
+Depth? (type a number, enter for default)
+  * 1. repo       (handoff flow + publish guard)
+    2. workspace  (full home: MEMORY.md, TOOLS.md, USER.md, ...)
+
+Add-ons? (type numbers separated by space/comma to toggle, enter to confirm)
+  [ ] 1. publisher  (content-guard policies for blog/social/docs)
+```
+
+Defaults are claude harness, repo depth, no includes. Enter ships the install.
+
+## CI / scripted install
+
+Pass flags directly to skip the prompt:
+
+```bash
+# Claude Code + Codex + OpenClaw, full workspace
+solo-mise init --target ~/agent-kitchen \
+  --depth workspace \
+  --harnesses claude,codex,openclaw
+
+# Codex-only project, minimal install
+solo-mise init --target ./my-project --depth repo --harnesses codex
+
+# Generic layout, no harness-specific files
+solo-mise init --target ./my-project --harnesses none
+```
+
+## Verifying
+
+After install, `solo-mise doctor --target <path>` reports the apparent harness shape and checks every configured inbox and adapter:
+
+```
+solo-mise doctor: target /home/you/agent-kitchen
+  harnesses: claude, codex, openclaw (owner=openclaw, depth=workspace)
+  [ok]   bootstrap: AGENTS.md   /home/you/agent-kitchen/AGENTS.md
+  [ok]   handoff: claude inbox  /home/you/agent-kitchen/.claude/memory-handoffs
+  [ok]   handoff: codex inbox   /home/you/agent-kitchen/.codex/memory-handoffs
+  [ok]   openclaw: config        /home/you/.openclaw/openclaw.json
+  ...
+```
+
+A `[fail]` line means the install is incomplete; `[warn]` is informational; `[todo]` means the check needs your attention (e.g. Hermes is experimental).
+
+## Reconfiguring
+
+To change which harnesses are installed on an existing target:
+
+```bash
+# Add a harness
+solo-mise reconfigure --target . --harnesses claude,codex
+
+# Drop one (without removing its files)
+solo-mise reconfigure --target . --harnesses claude
+
+# Drop one and remove its files
+solo-mise reconfigure --target . --harnesses claude --prune
+```
+
+## The handoff flow
+
+The starter handoff template lives at `<inbox>/TEMPLATE.md`. Copy it to a new dated file (e.g. `2026-05-16-1430-fixed-X.md`), fill it in, and the ingester promotes safe card handoffs into `memory/cards/`, appends targeted updates to the right file, and kicks ambiguous material to the review inbox.
+
+See the [Solo Cookbook](https://github.com/solomonneas/solos-cookbook) for the longer-form guidance on what makes a good handoff and when to use which routing.
+
+## Next steps
+
+- Read [the cookbook](https://github.com/solomonneas/solos-cookbook) for the deep version of every concept here.
+- Customize `USER.md` and `TOOLS.md` with your real preferences and runbooks (kept private; do not commit personal details).
+- Wire the ingester on a cron or a manual end-of-day workflow.
+- Add a memory-care staleness scan when your card set starts to matter. See `memory/cards/memory-care-staleness.md`.
+- If you use TokenJuice, wire Claude Code and Codex hooks deliberately and tell agents what the wrapper means. See `memory/cards/tokenjuice-output-compaction.md`.

brigade_cli-0.5.0/README.md

@@ -0,0 +1,188 @@
+<p align="center">
+  <img src="docs/assets/solo-mise-banner.png" alt="Solomon's Mise en Place banner">
+</p>
+
+<h1 align="center">Solomon's Mise en Place</h1>
+
+<p align="center">
+  <strong>Mise en place for agent memory.</strong>
+</p>
+
+<p align="center">
+  <em>Public-safe workspace bootstrap, memory handoffs, and publish guards for real agent setups.</em>
+</p>
+
+<p align="center">
+  <img src="https://img.shields.io/github/actions/workflow/status/escoffier-labs/brigade/ci.yml?branch=main&style=for-the-badge&label=ci" alt="CI status">
+  <img src="https://img.shields.io/badge/python-3.10%2B-blue?style=for-the-badge&logo=python&logoColor=white" alt="Python 3.10+">
+  <img src="https://img.shields.io/badge/license-MIT-green?style=for-the-badge" alt="MIT license">
+  <img src="https://img.shields.io/badge/harnesses-4-orange?style=for-the-badge" alt="4 harnesses">
+</p>
+
+<p align="center">
+  <code>brigade</code> is the installable starter kit behind <a href="https://github.com/solomonneas/solos-cookbook">Solomon's Guide to Cookin' with Gas</a>.
+  It gives you the workspace skeleton, handoff inbox, conservative ingester, and publish guard that make a multi-agent setup usable without leaking private junk into public repos.
+</p>
+
+## What this is
+
+Mise en place means "everything in its place before the work starts." In a kitchen, that is chopped mirepoix, clean pans, labels, and a station that does not make you hunt for salt & butter mid-service. For agents, it is the same idea: rules, memory, tools, handoff inboxes, publish guards, and boring verification already laid out before the session gets expensive.
+
+This package lays down a clean starting point for an agent workspace or a repo that needs durable memory handoffs. It is meant for people running real tools, real docs, and real automation across OpenClaw, Claude Code, Codex, Hermes, or a similar harness.
+
+The cookbook explains the why. This package gives you the kitchen.
+
+## What you get
+
+- sanitized bootstrap files for agent behavior, safety, tools, identity, and memory
+- a canonical memory layout where one configured owner holds durable knowledge
+- a shared `.claude/memory-handoffs/` inbox for Claude Code, Codex, and other side harnesses
+- starter memory cards and routing rules
+- multi-workspace handoff patterns for people administering more than one agent setup
+- memory-care staleness checks so durable cards do not quietly rot
+- TokenJuice output-compaction guidance for Claude Code and Codex, including wrapper notes and savings expectations
+- content-guard publish gates so private infrastructure does not leak into public docs
+- adapter fragments for OpenClaw (tested), Hermes (stubbed), and generic harnesses
+- doctor checks that prove the system is wired before you trust it
+
+## What you do not get
+
+- private hostnames, IPs, account IDs, or personal details
+- live auth profiles or OAuth tokens
+- cron jobs that post publicly by default
+- destructive automation or write-enabled integrations without explicit opt-in
+
+## Install
+
+```bash
+pipx install brigade-cli
+```
+
+Or, to track `main`:
+
+```bash
+pipx install git+https://github.com/escoffier-labs/brigade
+```
+
+The workspace config directory is `.brigade` (older `.solo-mise` installs are still read), and the `solo-mise` command is a deprecated alias for `brigade`.
+
+## Quick path
+
+Run `brigade init` with no flags for the interactive picker:
+
+```bash
+brigade init --target ~/agent-kitchen
+```
+
+For CI or scripts, pass flags directly:
+
+```bash
+brigade init --target ~/agent-kitchen --depth workspace --harnesses claude,codex,openclaw
+brigade init --target ./repo --depth repo --harnesses codex
+brigade init --target ./repo --harnesses none           # generic install
+```
+
+Once installed, `brigade doctor` verifies the wiring and `brigade status` reports over the station registry.
+
+## Two axes: depth + harnesses
+
+brigade installs material on two independent axes:
+
+**Depth, how much shared baseline you want:**
+
+| Depth | Installs |
+|---|---|
+| `repo` *(default)* | `AGENTS.md`, `SAFETY_RULES.md`, `INSTALL_FOR_AGENTS.md`, `hooks/pre-push`, `.brigade/policies/public-repo.json` |
+| `workspace` | repo + `MEMORY.md`, `TOOLS.md`, `USER.md`, `SOUL.md`, `IDENTITY.md`, `HEARTBEAT.md`, `memory/cards/`, starter cards |
+
+**Harnesses, which tools you actually use:**
+
+| Harness | Role | Adds |
+|---|---|---|
+| `claude` | writer | `CLAUDE.md` + `.claude/memory-handoffs/` inbox |
+| `codex` | writer | `.codex/memory-handoffs/` inbox (AGENTS.md is in the baseline) |
+| `openclaw` | reader | `.brigade/openclaw/` config fragments + cron stubs |
+| `hermes` | reader | `.brigade/hermes/` adapter fragments (experimental) |
+
+**Includes, optional add-ons:**
+
+| Include | Adds |
+|---|---|
+| `publisher` | `.brigade/policies/public-content.json` + content-safety memory card + scrub-cache |
+
+## Picking your harnesses
+
+Four common combos:
+
+- **Claude Code only:** `--harnesses claude`, the lightest setup, just one writer.
+- **Claude Code + OpenClaw:** `--harnesses claude,openclaw`, durable memory owner (OpenClaw) plus side writer (Claude Code).
+- **Claude Code + Codex + OpenClaw:** `--harnesses claude,codex,openclaw`, both writers feed into OpenClaw as the canonical owner.
+- **Codex + OpenClaw:** `--harnesses codex,openclaw`, Codex-first user with OpenClaw as the canonical store.
+
+The canonical memory owner is picked automatically by priority (`openclaw > hermes > claude > codex > this-repo`). Override with `--owner`.
+
+Re-running `brigade init` against an existing target is safe. It refuses to overwrite tracked files without `--force`, and the `.gitignore` block it manages is replaced between its markers without touching the rest of your file.
+
+See [QUICKSTART.md](QUICKSTART.md) for setup, verification, and the ingest flow.
+
+### What a green doctor looks like
+
+```text
+brigade doctor: target /home/you/agent-kitchen (generic)
+  [ok]   bootstrap: AGENTS.md              /home/you/agent-kitchen/AGENTS.md
+  [ok]   bootstrap: CLAUDE.md              /home/you/agent-kitchen/CLAUDE.md
+  [ok]   bootstrap: MEMORY.md              /home/you/agent-kitchen/MEMORY.md
+  [ok]   bootstrap: TOOLS.md               /home/you/agent-kitchen/TOOLS.md
+  [ok]   bootstrap: USER.md                /home/you/agent-kitchen/USER.md
+  [ok]   bootstrap: SAFETY_RULES.md        /home/you/agent-kitchen/SAFETY_RULES.md
+  [ok]   bootstrap: INSTALL_FOR_AGENTS.md  /home/you/agent-kitchen/INSTALL_FOR_AGENTS.md
+  [ok]   handoff: inbox                    /home/you/agent-kitchen/.claude/memory-handoffs
+  [ok]   handoff: TEMPLATE.md              /home/you/agent-kitchen/.claude/memory-handoffs/TEMPLATE.md
+  [ok]   handoff: processed/               /home/you/agent-kitchen/.claude/memory-handoffs/processed
+  [ok]   memory: cards/                    /home/you/agent-kitchen/memory/cards
+  [ok]   publish: hooks/pre-push           /home/you/agent-kitchen/hooks/pre-push
+  [ok]   publish: content-guard            /home/you/repos/content-guard
+
+summary: 14 checks, 0 failed, 0 manual
+```
+
+Anything `[warn]` is fine; `[fail]` means the install is incomplete. The `openclaw` and `hermes` harnesses add their own checks on top.
+
+### Privacy
+
+brigade makes no network calls. It does not phone home, collect telemetry, or sync anything to a server. Everything happens on your local filesystem against the templates packaged with the install. The only file that touches the network is the `pre-push` hook, and it runs the local `content-guard` scanner against your own commits before they leave the machine.
+
+## The design
+
+One memory owner stays canonical (typically OpenClaw or Hermes when present, otherwise `this-repo`). Writer harnesses drop handoffs into their own inboxes; the ingester scans all of them.
+
+```text
+Claude Code              Codex
+     |                     |
+     v                     v
+.claude/memory-handoffs/ .codex/memory-handoffs/
+     \                   /
+      \                 /
+       v               v
+      brigade ingest
+              |
+              v
+  memory/cards/*.md, TOOLS.md, USER.md,
+  rules/*.md, .learnings/*.md
+```
+
+The ingester is intentionally conservative. Safe card handoffs become cards. Targeted updates append to the right file. Ambiguous material gets kicked out for review instead of being trusted automatically.
+
+For users running multiple agent homes, treat the owner workspace as the hub. Remote or secondary workspaces can write handoffs into their own per-harness inboxes, then a trusted sync pulls those files into a staging inbox on the owner. That keeps agents informed about what happened elsewhere without creating multiple canonical memories.
+
+Token-heavy terminal work gets the same treatment: make the wrapper explicit, make the escape hatch obvious, and tell every harness what is happening. The TokenJuice starter card documents Claude Code's PreToolUse wrapper path, Codex's hook setup, and the savings model.
+
+## Related
+
+- [Solomon's Cookbook](https://github.com/solomonneas/solos-cookbook): the long-form guide and reference docs
+- [content-guard](https://github.com/solomonneas/content-guard): the publish-gate scanner used by the pre-push hook
+- [OpenClaw](https://github.com/openclaw/openclaw): the reference memory owner
+
+## License
+
+MIT

brigade_cli-0.5.0/pyproject.toml

@@ -0,0 +1,44 @@
+[build-system]
+requires = ["setuptools>=68", "wheel"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "brigade-cli"
+version = "0.5.0"
+description = "Run your agent brigade: an operator-system CLI that bootstraps, checks, and operates agent workspaces across harnesses."
+readme = "README.md"
+requires-python = ">=3.10"
+license = { text = "MIT" }
+authors = [{ name = "Solomon Neas", email = "srneas@gmail.com" }]
+keywords = ["agents", "openclaw", "claude-code", "codex", "memory", "bootstrap", "brigade", "operator"]
+classifiers = [
+    "Development Status :: 3 - Alpha",
+    "License :: OSI Approved :: MIT License",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3.10",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+]
+dependencies = []
+
+[project.optional-dependencies]
+dev = ["pytest>=7"]
+
+[project.urls]
+Homepage = "https://github.com/escoffier-labs/brigade"
+Cookbook = "https://github.com/solomonneas/solos-cookbook"
+Issues = "https://github.com/escoffier-labs/brigade/issues"
+
+[project.scripts]
+brigade = "brigade.cli:main"
+solo-mise = "brigade.cli:main_deprecated"
+
+[tool.setuptools.packages.find]
+where = ["src"]
+
+[tool.setuptools.package-data]
+brigade = ["py.typed", "templates/**/*"]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+addopts = "-ra"

brigade_cli-0.5.0/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

brigade_cli-0.5.0/src/brigade/__init__.py

@@ -0,0 +1,3 @@
+"""Solomon's Mise en Place: installable starter kit for an agent kitchen."""
+
+__version__ = "0.5.0"

brigade_cli-0.5.0/src/brigade/__main__.py

@@ -0,0 +1,5 @@
+"""Enable `python -m brigade`."""
+from .cli import main
+
+if __name__ == "__main__":
+    raise SystemExit(main())