brichan 0.5.0__tar.gz

brichan-0.5.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Minh Tran
+
+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.

brichan-0.5.0/PKG-INFO

@@ -0,0 +1,193 @@
+Metadata-Version: 2.4
+Name: brichan
+Version: 0.5.0
+Summary: Repository-native AI Chief of Staff orchestration
+Author: Minh Tran
+License: MIT License
+        
+        Copyright (c) 2026 Minh Tran
+        
+        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.
+        
+Keywords: ai,orchestration,codex,claude-code,chief-of-staff
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: POSIX
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development :: Build Tools
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Dynamic: license-file
+
+# Brichan
+
+![Brichan coordinating a team of AI workers](assets/brida-hero.png)
+
+Brichan is an AI Chief of Staff for Codex and Claude Code. Give it a project
+goal; it keeps the necessary context, coordinates independent workers through
+Herdr, checks their evidence, and records useful project state outside chat.
+Its existing runtime package and console commands remain `brida` and
+`brida-*` for compatibility.
+
+## Current dogfood scope
+
+The primary one-user dogfood path is now an installed Python package running
+inside an existing top-level Git repository. Installed-project mode currently
+supports Codex on POSIX-compatible systems with Python 3.10+. Herdr is needed
+only when Brida coordinates independent worker sessions.
+
+Brida is not published to a package registry yet; the planned PyPI
+distribution name is `brichan` (`pip install brichan`), while the importable
+package stays `brida` and every console command keeps its existing name.
+Until it is published, build the wheel locally from this repository with the
+installer. It can be invoked from any directory and does not activate or
+modify the target project's virtual environment:
+
+```bash
+/absolute/path/to/brida/scripts/install-brida
+```
+
+By default, the script creates a dedicated environment at
+`$HOME/.local/share/brida/venv` and command symlinks in `$HOME/.local/bin`.
+It automatically selects an available Python 3.10+ interpreter with `pip`,
+`setuptools`, `venv`, and `wheel`, builds from a temporary source snapshot,
+and installs all Brida console commands. No virtualenv activation is
+required. If the command directory is not on `PATH`, the installer prints
+the exact export to add to the shell profile.
+
+## Initialize a project
+
+Preview the complete footprint before writing:
+
+```bash
+brida init --project /absolute/path/to/repository
+brida init --apply --project /absolute/path/to/repository
+```
+
+`init` defaults to dry-run and performs zero writes. `--apply` creates only a
+versioned `.brida/` directory containing managed policy, model routing, Herdr
+skill resources, and mutable project memory. Repeating it against healthy
+state is idempotent.
+
+Diagnose and launch from any directory with an explicit target:
+
+```bash
+brida status --project /absolute/path/to/repository
+brida doctor --project /absolute/path/to/repository
+brida run --project /absolute/path/to/repository -- <codex arguments>
+```
+
+From inside a healthy initialized repository, bare `brida` also launches
+Codex. The installed entrypoint:
+
+- leaves `AGENTS.md`, `CLAUDE.md`, `.codex/`, and provider configuration
+  untouched;
+- launches external `codex` directly at the target root and never executes
+  target-owned `bin/brida-*` wrappers;
+- injects package-owned Brida policy and Herdr skill discovery;
+- rejects native delegation, permission bypasses, cwd/scope widening, profiles,
+  remote execution, and arbitrary Codex configuration before `--`;
+- treats option-looking text after `--` as literal prompt content.
+
+State diagnostics reject malformed, dangling, symlinked, inaccessible, or
+incompatible `.brida/` state without silently repairing it. Schema v1 has no
+automatic migration: package-version changes require deliberate backup and
+reinitialization. See the
+[installed Codex dogfood guide](docs/guides/installable-dogfood.md) for the
+exact footprint, exit codes, safeguards, and compatibility boundary.
+
+## Checkout compatibility and development
+
+The original checkout workflow remains available for development and for
+Claude Code:
+
+```bash
+bin/brida
+bin/brida --runtime claude
+```
+
+Checkout mode uses package-owned `bin/brida-*` wrappers. Installed-project mode
+does not. Coordinator defaults and worker routes are settings-driven, so the
+coordinator and implementation, review, planning, or scan workers may use
+different runtimes. See the [model-routing guide](docs/guides/model-routing.md)
+to change defaults, select a named route, or use a one-off override.
+
+The `brida-codex` and `brida-claude` console commands installed by `brichan`
+remain checkout-oriented: `brida-codex` resolves coordinator routing from a
+Brida source checkout (or `BRIDA_ROOT`) or from an already-initialized
+project's `.brida/` state, while `brida-claude` resolves only from a checkout
+or `BRIDA_ROOT`. Both are for development and checkout use, not standalone
+installed-project launches. `--help`/`--version` work from any directory; the
+[installed Codex dogfood guide](docs/guides/installable-dogfood.md) has the
+exact boundary.
+
+## How it works
+
+1. You describe the outcome and constraints.
+2. Brida reads only the project context needed for that work.
+3. Brida gives bounded tasks to independent workers through Herdr.
+4. Brida verifies results, records decisions and status, then reports back.
+
+Herdr is the worker control plane. Native runtime delegation stays disabled so
+worker ownership, evidence, and cleanup remain visible.
+
+Project context lives in `projects/<project-slug>/` as a small set of Markdown
+files for overview, current state, tasks, decisions, and references. Read the
+[project memory policy](docs/policy/memory-policy.md) for the contract.
+
+## Development
+
+Run the complete local validation suite before sharing a change:
+
+```bash
+make check
+```
+
+You can also run individual layers while iterating:
+
+```bash
+make test-unit
+make test-contract
+make test-integration
+make package-check
+```
+
+The importable implementation is in `src/brida/`; stable command wrappers are
+in `bin/` and `scripts/`. See [CONTRIBUTING.md](CONTRIBUTING.md) for the change
+workflow and [the repository layout](docs/architecture/repository-layout.md)
+for module boundaries.
+
+## Learn more
+
+- [Model routing and worker launch settings](docs/guides/model-routing.md)
+- [Installed Codex dogfood](docs/guides/installable-dogfood.md)
+- [Documentation index](docs/index.md)
+- [Operating principles](docs/policy/operating-principles.md)
+- [Security policy](SECURITY.md)
+
+## License
+
+Brida is available under the [MIT License](LICENSE).

brichan-0.5.0/README.md

@@ -0,0 +1,149 @@
+# Brichan
+
+![Brichan coordinating a team of AI workers](assets/brida-hero.png)
+
+Brichan is an AI Chief of Staff for Codex and Claude Code. Give it a project
+goal; it keeps the necessary context, coordinates independent workers through
+Herdr, checks their evidence, and records useful project state outside chat.
+Its existing runtime package and console commands remain `brida` and
+`brida-*` for compatibility.
+
+## Current dogfood scope
+
+The primary one-user dogfood path is now an installed Python package running
+inside an existing top-level Git repository. Installed-project mode currently
+supports Codex on POSIX-compatible systems with Python 3.10+. Herdr is needed
+only when Brida coordinates independent worker sessions.
+
+Brida is not published to a package registry yet; the planned PyPI
+distribution name is `brichan` (`pip install brichan`), while the importable
+package stays `brida` and every console command keeps its existing name.
+Until it is published, build the wheel locally from this repository with the
+installer. It can be invoked from any directory and does not activate or
+modify the target project's virtual environment:
+
+```bash
+/absolute/path/to/brida/scripts/install-brida
+```
+
+By default, the script creates a dedicated environment at
+`$HOME/.local/share/brida/venv` and command symlinks in `$HOME/.local/bin`.
+It automatically selects an available Python 3.10+ interpreter with `pip`,
+`setuptools`, `venv`, and `wheel`, builds from a temporary source snapshot,
+and installs all Brida console commands. No virtualenv activation is
+required. If the command directory is not on `PATH`, the installer prints
+the exact export to add to the shell profile.
+
+## Initialize a project
+
+Preview the complete footprint before writing:
+
+```bash
+brida init --project /absolute/path/to/repository
+brida init --apply --project /absolute/path/to/repository
+```
+
+`init` defaults to dry-run and performs zero writes. `--apply` creates only a
+versioned `.brida/` directory containing managed policy, model routing, Herdr
+skill resources, and mutable project memory. Repeating it against healthy
+state is idempotent.
+
+Diagnose and launch from any directory with an explicit target:
+
+```bash
+brida status --project /absolute/path/to/repository
+brida doctor --project /absolute/path/to/repository
+brida run --project /absolute/path/to/repository -- <codex arguments>
+```
+
+From inside a healthy initialized repository, bare `brida` also launches
+Codex. The installed entrypoint:
+
+- leaves `AGENTS.md`, `CLAUDE.md`, `.codex/`, and provider configuration
+  untouched;
+- launches external `codex` directly at the target root and never executes
+  target-owned `bin/brida-*` wrappers;
+- injects package-owned Brida policy and Herdr skill discovery;
+- rejects native delegation, permission bypasses, cwd/scope widening, profiles,
+  remote execution, and arbitrary Codex configuration before `--`;
+- treats option-looking text after `--` as literal prompt content.
+
+State diagnostics reject malformed, dangling, symlinked, inaccessible, or
+incompatible `.brida/` state without silently repairing it. Schema v1 has no
+automatic migration: package-version changes require deliberate backup and
+reinitialization. See the
+[installed Codex dogfood guide](docs/guides/installable-dogfood.md) for the
+exact footprint, exit codes, safeguards, and compatibility boundary.
+
+## Checkout compatibility and development
+
+The original checkout workflow remains available for development and for
+Claude Code:
+
+```bash
+bin/brida
+bin/brida --runtime claude
+```
+
+Checkout mode uses package-owned `bin/brida-*` wrappers. Installed-project mode
+does not. Coordinator defaults and worker routes are settings-driven, so the
+coordinator and implementation, review, planning, or scan workers may use
+different runtimes. See the [model-routing guide](docs/guides/model-routing.md)
+to change defaults, select a named route, or use a one-off override.
+
+The `brida-codex` and `brida-claude` console commands installed by `brichan`
+remain checkout-oriented: `brida-codex` resolves coordinator routing from a
+Brida source checkout (or `BRIDA_ROOT`) or from an already-initialized
+project's `.brida/` state, while `brida-claude` resolves only from a checkout
+or `BRIDA_ROOT`. Both are for development and checkout use, not standalone
+installed-project launches. `--help`/`--version` work from any directory; the
+[installed Codex dogfood guide](docs/guides/installable-dogfood.md) has the
+exact boundary.
+
+## How it works
+
+1. You describe the outcome and constraints.
+2. Brida reads only the project context needed for that work.
+3. Brida gives bounded tasks to independent workers through Herdr.
+4. Brida verifies results, records decisions and status, then reports back.
+
+Herdr is the worker control plane. Native runtime delegation stays disabled so
+worker ownership, evidence, and cleanup remain visible.
+
+Project context lives in `projects/<project-slug>/` as a small set of Markdown
+files for overview, current state, tasks, decisions, and references. Read the
+[project memory policy](docs/policy/memory-policy.md) for the contract.
+
+## Development
+
+Run the complete local validation suite before sharing a change:
+
+```bash
+make check
+```
+
+You can also run individual layers while iterating:
+
+```bash
+make test-unit
+make test-contract
+make test-integration
+make package-check
+```
+
+The importable implementation is in `src/brida/`; stable command wrappers are
+in `bin/` and `scripts/`. See [CONTRIBUTING.md](CONTRIBUTING.md) for the change
+workflow and [the repository layout](docs/architecture/repository-layout.md)
+for module boundaries.
+
+## Learn more
+
+- [Model routing and worker launch settings](docs/guides/model-routing.md)
+- [Installed Codex dogfood](docs/guides/installable-dogfood.md)
+- [Documentation index](docs/index.md)
+- [Operating principles](docs/policy/operating-principles.md)
+- [Security policy](SECURITY.md)
+
+## License
+
+Brida is available under the [MIT License](LICENSE).

brichan-0.5.0/pyproject.toml

@@ -0,0 +1,43 @@
+[build-system]
+requires = ["setuptools>=68", "wheel"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "brichan"
+version = "0.5.0"
+description = "Repository-native AI Chief of Staff orchestration"
+readme = "README.md"
+requires-python = ">=3.10"
+license = {file = "LICENSE"}
+authors = [{name = "Minh Tran"}]
+keywords = ["ai", "orchestration", "codex", "claude-code", "chief-of-staff"]
+classifiers = [
+    "Development Status :: 3 - Alpha",
+    "Environment :: Console",
+    "Intended Audience :: Developers",
+    "License :: OSI Approved :: MIT License",
+    "Operating System :: POSIX",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3.10",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+    "Topic :: Software Development :: Build Tools",
+]
+dependencies = []
+
+[project.scripts]
+brida = "brida.cli.runtime:main"
+brida-codex = "brida.cli.codex:main"
+brida-claude = "brida.cli.claude:main"
+brida-herdr-agent-start = "brida.orchestration.worker_launch:main"
+brida-validate-receipts = "brida.contracts.receipts.validation:main"
+
+[tool.setuptools]
+package-dir = {"" = "src"}
+
+[tool.setuptools.packages.find]
+where = ["src"]
+
+[tool.setuptools.package-data]
+"brida.resources.dogfood_v1" = ["**/*"]

brichan-0.5.0/setup.cfg

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

brichan-0.5.0/src/brichan.egg-info/PKG-INFO

@@ -0,0 +1,193 @@
+Metadata-Version: 2.4
+Name: brichan
+Version: 0.5.0
+Summary: Repository-native AI Chief of Staff orchestration
+Author: Minh Tran
+License: MIT License
+        
+        Copyright (c) 2026 Minh Tran
+        
+        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.
+        
+Keywords: ai,orchestration,codex,claude-code,chief-of-staff
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: POSIX
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development :: Build Tools
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Dynamic: license-file
+
+# Brichan
+
+![Brichan coordinating a team of AI workers](assets/brida-hero.png)
+
+Brichan is an AI Chief of Staff for Codex and Claude Code. Give it a project
+goal; it keeps the necessary context, coordinates independent workers through
+Herdr, checks their evidence, and records useful project state outside chat.
+Its existing runtime package and console commands remain `brida` and
+`brida-*` for compatibility.
+
+## Current dogfood scope
+
+The primary one-user dogfood path is now an installed Python package running
+inside an existing top-level Git repository. Installed-project mode currently
+supports Codex on POSIX-compatible systems with Python 3.10+. Herdr is needed
+only when Brida coordinates independent worker sessions.
+
+Brida is not published to a package registry yet; the planned PyPI
+distribution name is `brichan` (`pip install brichan`), while the importable
+package stays `brida` and every console command keeps its existing name.
+Until it is published, build the wheel locally from this repository with the
+installer. It can be invoked from any directory and does not activate or
+modify the target project's virtual environment:
+
+```bash
+/absolute/path/to/brida/scripts/install-brida
+```
+
+By default, the script creates a dedicated environment at
+`$HOME/.local/share/brida/venv` and command symlinks in `$HOME/.local/bin`.
+It automatically selects an available Python 3.10+ interpreter with `pip`,
+`setuptools`, `venv`, and `wheel`, builds from a temporary source snapshot,
+and installs all Brida console commands. No virtualenv activation is
+required. If the command directory is not on `PATH`, the installer prints
+the exact export to add to the shell profile.
+
+## Initialize a project
+
+Preview the complete footprint before writing:
+
+```bash
+brida init --project /absolute/path/to/repository
+brida init --apply --project /absolute/path/to/repository
+```
+
+`init` defaults to dry-run and performs zero writes. `--apply` creates only a
+versioned `.brida/` directory containing managed policy, model routing, Herdr
+skill resources, and mutable project memory. Repeating it against healthy
+state is idempotent.
+
+Diagnose and launch from any directory with an explicit target:
+
+```bash
+brida status --project /absolute/path/to/repository
+brida doctor --project /absolute/path/to/repository
+brida run --project /absolute/path/to/repository -- <codex arguments>
+```
+
+From inside a healthy initialized repository, bare `brida` also launches
+Codex. The installed entrypoint:
+
+- leaves `AGENTS.md`, `CLAUDE.md`, `.codex/`, and provider configuration
+  untouched;
+- launches external `codex` directly at the target root and never executes
+  target-owned `bin/brida-*` wrappers;
+- injects package-owned Brida policy and Herdr skill discovery;
+- rejects native delegation, permission bypasses, cwd/scope widening, profiles,
+  remote execution, and arbitrary Codex configuration before `--`;
+- treats option-looking text after `--` as literal prompt content.
+
+State diagnostics reject malformed, dangling, symlinked, inaccessible, or
+incompatible `.brida/` state without silently repairing it. Schema v1 has no
+automatic migration: package-version changes require deliberate backup and
+reinitialization. See the
+[installed Codex dogfood guide](docs/guides/installable-dogfood.md) for the
+exact footprint, exit codes, safeguards, and compatibility boundary.
+
+## Checkout compatibility and development
+
+The original checkout workflow remains available for development and for
+Claude Code:
+
+```bash
+bin/brida
+bin/brida --runtime claude
+```
+
+Checkout mode uses package-owned `bin/brida-*` wrappers. Installed-project mode
+does not. Coordinator defaults and worker routes are settings-driven, so the
+coordinator and implementation, review, planning, or scan workers may use
+different runtimes. See the [model-routing guide](docs/guides/model-routing.md)
+to change defaults, select a named route, or use a one-off override.
+
+The `brida-codex` and `brida-claude` console commands installed by `brichan`
+remain checkout-oriented: `brida-codex` resolves coordinator routing from a
+Brida source checkout (or `BRIDA_ROOT`) or from an already-initialized
+project's `.brida/` state, while `brida-claude` resolves only from a checkout
+or `BRIDA_ROOT`. Both are for development and checkout use, not standalone
+installed-project launches. `--help`/`--version` work from any directory; the
+[installed Codex dogfood guide](docs/guides/installable-dogfood.md) has the
+exact boundary.
+
+## How it works
+
+1. You describe the outcome and constraints.
+2. Brida reads only the project context needed for that work.
+3. Brida gives bounded tasks to independent workers through Herdr.
+4. Brida verifies results, records decisions and status, then reports back.
+
+Herdr is the worker control plane. Native runtime delegation stays disabled so
+worker ownership, evidence, and cleanup remain visible.
+
+Project context lives in `projects/<project-slug>/` as a small set of Markdown
+files for overview, current state, tasks, decisions, and references. Read the
+[project memory policy](docs/policy/memory-policy.md) for the contract.
+
+## Development
+
+Run the complete local validation suite before sharing a change:
+
+```bash
+make check
+```
+
+You can also run individual layers while iterating:
+
+```bash
+make test-unit
+make test-contract
+make test-integration
+make package-check
+```
+
+The importable implementation is in `src/brida/`; stable command wrappers are
+in `bin/` and `scripts/`. See [CONTRIBUTING.md](CONTRIBUTING.md) for the change
+workflow and [the repository layout](docs/architecture/repository-layout.md)
+for module boundaries.
+
+## Learn more
+
+- [Model routing and worker launch settings](docs/guides/model-routing.md)
+- [Installed Codex dogfood](docs/guides/installable-dogfood.md)
+- [Documentation index](docs/index.md)
+- [Operating principles](docs/policy/operating-principles.md)
+- [Security policy](SECURITY.md)
+
+## License
+
+Brida is available under the [MIT License](LICENSE).

brichan-0.5.0/src/brichan.egg-info/SOURCES.txt

@@ -0,0 +1,44 @@
+LICENSE
+README.md
+pyproject.toml
+src/brichan.egg-info/PKG-INFO
+src/brichan.egg-info/SOURCES.txt
+src/brichan.egg-info/dependency_links.txt
+src/brichan.egg-info/entry_points.txt
+src/brichan.egg-info/top_level.txt
+src/brida/__init__.py
+src/brida/lifecycle.py
+src/brida/project.py
+src/brida/cli/__init__.py
+src/brida/cli/_root.py
+src/brida/cli/claude.py
+src/brida/cli/codex.py
+src/brida/cli/provider_commands.py
+src/brida/cli/runtime.py
+src/brida/contracts/__init__.py
+src/brida/contracts/receipts/__init__.py
+src/brida/contracts/receipts/discovery.py
+src/brida/contracts/receipts/parser.py
+src/brida/contracts/receipts/schema.py
+src/brida/contracts/receipts/validation.py
+src/brida/orchestration/__init__.py
+src/brida/orchestration/herdr_client.py
+src/brida/orchestration/layout.py
+src/brida/orchestration/model_routing.py
+src/brida/orchestration/worker_launch.py
+src/brida/resources/__init__.py
+src/brida/resources/dogfood_v1/__init__.py
+src/brida/resources/dogfood_v1/config/model-routing.json
+src/brida/resources/dogfood_v1/policy/bootstrap.md
+src/brida/resources/dogfood_v1/policy/identity.md
+src/brida/resources/dogfood_v1/policy/memory-policy.md
+src/brida/resources/dogfood_v1/policy/operating-principles.md
+src/brida/resources/dogfood_v1/project-memory/index.md
+src/brida/resources/dogfood_v1/project-memory/main/current-state.md
+src/brida/resources/dogfood_v1/project-memory/main/decisions.md
+src/brida/resources/dogfood_v1/project-memory/main/overview.md
+src/brida/resources/dogfood_v1/project-memory/main/references.md
+src/brida/resources/dogfood_v1/project-memory/main/tasks.md
+src/brida/resources/dogfood_v1/skills/herdr-orchestration/SKILL.md
+src/brida/resources/dogfood_v1/skills/herdr-orchestration/references/commands.md
+src/brida/resources/dogfood_v1/skills/herdr-orchestration/references/task-packet.md

brichan-0.5.0/src/brichan.egg-info/dependency_links.txt

@@ -0,0 +1 @@
+

brichan-0.5.0/src/brichan.egg-info/entry_points.txt

@@ -0,0 +1,6 @@
+[console_scripts]
+brida = brida.cli.runtime:main
+brida-claude = brida.cli.claude:main
+brida-codex = brida.cli.codex:main
+brida-herdr-agent-start = brida.orchestration.worker_launch:main
+brida-validate-receipts = brida.contracts.receipts.validation:main

brichan-0.5.0/src/brichan.egg-info/top_level.txt

@@ -0,0 +1 @@
+brida

brichan-0.5.0/src/brida/__init__.py

@@ -0,0 +1,3 @@
+"""Brida's importable orchestration core."""
+
+__version__ = "0.5.0"

brichan-0.5.0/src/brida/cli/__init__.py

@@ -0,0 +1 @@
+"""Stable Brida command-line entrypoints."""