ossa 0.1.0a1__tar.gz

ossa-0.1.0a1/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

ossa-0.1.0a1/PKG-INFO

@@ -0,0 +1,212 @@
+Metadata-Version: 2.4
+Name: ossa
+Version: 0.1.0a1
+Summary: OSSA toolbox: the deterministic half of a safety-first open-source contribution crew that runs on Claude Code.
+Author: Rahul Seervi
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/Rahul-cs50/ossa
+Project-URL: Repository, https://github.com/Rahul-cs50/ossa
+Project-URL: Issues, https://github.com/Rahul-cs50/ossa/issues
+Project-URL: Safety, https://github.com/Rahul-cs50/ossa/blob/main/SAFETY.md
+Keywords: open-source,contributions,claude-code,sandbox,safety,pull-requests
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: MacOS
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development
+Classifier: Topic :: Software Development :: Quality Assurance
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: httpx>=0.27
+Requires-Dist: pydantic>=2.6
+Requires-Dist: typer>=0.12
+Requires-Dist: rich>=13.7
+Provides-Extra: dev
+Requires-Dist: pytest>=8; extra == "dev"
+Dynamic: license-file
+
+# OSSA
+
+**Your open-source crew. Runs on Claude Code.**
+
+OSSA is a small crew that contributes to open-source projects with you. It finds issues worth your
+time, reproduces the bug, fixes it, tries hard to break its own fix, and drafts the PR in the
+project's own style. Nothing reaches GitHub until you have read it and approved it in your own words.
+
+It is built for maintainers' trust first: repos that don't want AI help are skipped, AI help is
+always disclosed, volume stays low, and every PR comes with evidence a maintainer can check.
+
+> Pre-release. The plugin, the toolbox and this README are still moving.
+
+## The crew
+
+| | Job |
+|---|---|
+| **Captain** | the one you talk to; plans and hands out the work |
+| **Scout** | finds repos and issues, reads each repo's rules and its last 10 merged outside PRs |
+| **Sherlock** | builds a sandbox and reproduces the bug with a failing test |
+| **Patch** | writes the minimal fix and its regression test |
+| **Breaker** | tries to break the fix with tests that run, without seeing Patch's reasoning |
+| **Judge** | settles disputes between Patch and Breaker, on evidence |
+| **Scribe** | writes the commit, the PR in the repo's template, and the evidence pack |
+
+## Install
+
+You need [Claude Code](https://claude.com/claude-code), git, Docker and Python 3.11+, on Linux, macOS, or
+Windows through WSL2 (below).
+
+```sh
+curl -fsSL https://raw.githubusercontent.com/Rahul-cs50/ossa/main/install.sh | sh
+```
+
+The installer checks those, installs the `ossa` toolbox with `uv`, and runs `ossa init`, which asks
+five questions and makes your workspace (`~/ossa`). The OSSA plugin is switched on in that folder
+only; your other Claude Code sessions are never touched.
+
+Or by hand:
+
+```sh
+uv tool install ossa                     # the toolbox
+ossa init --marketplace Rahul-cs50/ossa  # workspace + plugin
+ossa doctor                              # checks everything
+```
+
+### Windows
+
+OSSA runs on Windows inside WSL2, the Linux that comes with Windows 10 and 11:
+
+1. In PowerShell, run `wsl --install` and restart. That installs Ubuntu.
+2. Open **Ubuntu** from the Start menu. Everything below happens there.
+3. Install Claude Code inside Ubuntu. A copy installed in Windows doesn't count: OSSA's safety hooks have
+   to run in Linux.
+4. For Docker, turn on Docker Desktop's *Settings → Resources → WSL integration* for Ubuntu, or install
+   Docker Engine inside Ubuntu.
+5. Run the install line above. Keep the workspace in your Linux home (the default, `~/ossa`), not under
+   `/mnt/c`, which is slow and ignores letter case.
+
+`ossa doctor` checks each of these. Run in Windows itself, `ossa` and the installer only print these steps.
+WSL has no system keychain, so `ossa init` keeps your GitHub token in `~/.config/ossa/token`, a file only
+you can read; the crew can't open it.
+
+## Use
+
+```sh
+ossa wake        # start the crew (Claude Code in ~/ossa, with the Captain)
+```
+
+Then talk to the Captain: "find something to fix in a Python project", "what's waiting for me?".
+When a PR is ready, the Captain tells you. You review and decide in your own terminal:
+
+```sh
+ossa approve     # read each card; approve in your own words, ask for changes, or reject
+ossa status      # your level, caps, open PRs and what waits for you
+```
+
+The card fits what you need to decide on one screen: what broke, the evidence (the reproduction,
+the tests, Breaker's attacks), the repo's rules, the PR text exactly as it will go out, and the diff.
+
+<img src="docs/demo/card.svg" alt="The approval card for a sample fix: what broke, the evidence, the repo's rules, the PR text, the commit message and the diff" width="720">
+
+*The pictures here are OSSA's real screens, drawn from sample data about a made-up repo
+(`scripts/demo.py`).*
+
+### Your commands
+
+| Command | What |
+|---|---|
+| `ossa wake` | start the crew |
+| `ossa approve [attempt]` | review queued PRs; approve, ask for changes, or reject |
+| `ossa claim <attempt>` | post a claim comment the crew drafted, for repos that assign issues first |
+| `ossa allow <repo> --why ...` | after reading the quote yourself: lift an AI-ban match or a CLA block |
+| `ossa sleep [--hours N]` | stop the crew in every session in the workspace until `ossa wake` (or N hours) |
+| `ossa status`, `ossa doctor`, `ossa gc` | standing and what happened while you were away, health check, cleanup |
+
+The crew's own commands (`ossa repos`, `policy`, `issues`, `start`, `env`, `test`, `repro`,
+`verify`, `risk`, `attack`, `duel`, `queue`, ...) print JSON for Claude; you rarely need them.
+
+### The crew pane
+
+In your workspace, a pane beside the chat shows who in the crew is on shift and what they're doing,
+your 5-hour and 7-day quota, the PRs waiting for you and your level: 😴 when a usage limit stopped
+the crew (until the reset), 💤 while you have it on `ossa sleep`, 💦 while tests run in the sandbox,
+🪧 when something needs you. It is the `ossa-pet` plugin, installed beside `ossa`, and it only reads
+files: it never writes one or uses the network. It interrupts you only when you're needed: a toast
+when a new PR starts waiting for you.
+
+<img src="docs/demo/pane.svg" alt="The crew pane: who is on shift, your level, quota bars, the PR waiting for you, and what happened while you were away" width="560">
+
+**While you were away.** `ossa wake` and `ossa status` show what the ledger recorded since you last
+looked: PRs ready for you, fixes the crew dropped and why, PRs opened, merged or closed, new maintainer
+comments, usage-limit stops. The pane and the Captain show the same list. It comes from the ledger,
+not from the crew's own account of its work. In background mode each run's summary on GitHub carries
+it too (`ossa away --md`).
+
+<img src="docs/demo/status.svg" alt="ossa status with sample data: level, the PR waiting for you, open PRs, caps, and while you were away" width="720">
+
+Rename the crew in `ossa.toml` (`[crew]`, e.g. `breaker = "Bruno"`). Instant commands, no model call:
+
+| In Claude Code | What |
+|---|---|
+| `/ossa` | open the pane |
+| `/ossa status` | the same, as text |
+| `/ossa pause`, `/ossa resume` | hold the crew's next `ossa` step or crew agent, then let it go on |
+
+`/ossa pause` holds one session. `ossa sleep`, in your own terminal, stops the crew everywhere in the
+workspace, headless sessions included: until `ossa wake`, its next `ossa` step and every file write are
+refused. When the crew stops on a usage limit, OSSA notes when it resets (`runs/limit.json`), and
+`ossa status` says when the crew can go on.
+
+## Safety
+
+The short version: the crew can't publish, can't run repository code outside a sandbox, can't touch
+your credentials, and can't skip a repo's rules; you approve every PR in your own words. Every
+guarantee, how it is enforced, and the known limits are in [SAFETY.md](SAFETY.md). Found a way around
+one? Report it privately: [SECURITY.md](SECURITY.md).
+
+## How OSSA is tested
+
+| What | How | Run it |
+|---|---|---|
+| The toolbox and the guard | 400+ tests, no network, Docker, token or model needed | `pytest -q` |
+| The crew under pressure | red-team evals: injected instructions in an issue and in a CONTRIBUTING.md, an AI-banning repo, requests to mass-open PRs, hide AI help, use an alternate account, post a security hole, run your own steps, or work while you have the crew asleep | `claude plugin eval plugin --scaffold --allow-tools Write Edit` |
+| Reading real AI policies | 19 real projects' policies against a careful human reading (18 agree; see SAFETY.md) | `python scripts/policy_corpus.py` |
+| A first install | install.sh and the five `ossa init` questions at a real terminal, on a clean Linux container and on macOS in CI | `sh scripts/install_test_docker.sh` |
+| The crew pane | it only reads files: `claude plugin validate pet` lists every call it makes | `claude plugin test pet` |
+
+## Levels
+
+Trust is the currency. You earn XP for outcomes maintainers decide (a merge is +100, an approving
+review +30, feedback addressed +20, a weak fix stopped before it went out +10; a PR closed unmerged
+is -50), never for PRs opened. Levels raise your caps, from 1 open PR as a newcomer to 8 as a veteran.
+
+## For maintainers
+
+Don't want OSSA contributions? Add this line to your AGENTS.md or CONTRIBUTING.md:
+
+```
+ossa: opt-out
+```
+
+or open a PR adding your repo to [`src/ossa/data/optout.txt`](src/ossa/data/optout.txt). Every OSSA
+user's crew checks both before any work, and nobody can override them. If you have an AI policy,
+OSSA reads it: clear bans stop the crew, and disclosure rules are followed word for word. What an
+OSSA PR looks like, and how to tell us when one wasted your time: [docs/maintainers.md](docs/maintainers.md).
+
+## Development
+
+```sh
+uv venv && uv pip install -e '.[dev]'
+.venv/bin/pytest -q                      # no network, Docker, token or LLM needed
+claude plugin validate plugin            # the plugin
+claude --plugin-dir plugin               # try it from a workspace folder holding ossa.toml
+sh scripts/release_check.sh              # build and check the package as PyPI will
+```
+
+Releases: [RELEASING.md](RELEASING.md).

ossa-0.1.0a1/README.md

@@ -0,0 +1,178 @@
+# OSSA
+
+**Your open-source crew. Runs on Claude Code.**
+
+OSSA is a small crew that contributes to open-source projects with you. It finds issues worth your
+time, reproduces the bug, fixes it, tries hard to break its own fix, and drafts the PR in the
+project's own style. Nothing reaches GitHub until you have read it and approved it in your own words.
+
+It is built for maintainers' trust first: repos that don't want AI help are skipped, AI help is
+always disclosed, volume stays low, and every PR comes with evidence a maintainer can check.
+
+> Pre-release. The plugin, the toolbox and this README are still moving.
+
+## The crew
+
+| | Job |
+|---|---|
+| **Captain** | the one you talk to; plans and hands out the work |
+| **Scout** | finds repos and issues, reads each repo's rules and its last 10 merged outside PRs |
+| **Sherlock** | builds a sandbox and reproduces the bug with a failing test |
+| **Patch** | writes the minimal fix and its regression test |
+| **Breaker** | tries to break the fix with tests that run, without seeing Patch's reasoning |
+| **Judge** | settles disputes between Patch and Breaker, on evidence |
+| **Scribe** | writes the commit, the PR in the repo's template, and the evidence pack |
+
+## Install
+
+You need [Claude Code](https://claude.com/claude-code), git, Docker and Python 3.11+, on Linux, macOS, or
+Windows through WSL2 (below).
+
+```sh
+curl -fsSL https://raw.githubusercontent.com/Rahul-cs50/ossa/main/install.sh | sh
+```
+
+The installer checks those, installs the `ossa` toolbox with `uv`, and runs `ossa init`, which asks
+five questions and makes your workspace (`~/ossa`). The OSSA plugin is switched on in that folder
+only; your other Claude Code sessions are never touched.
+
+Or by hand:
+
+```sh
+uv tool install ossa                     # the toolbox
+ossa init --marketplace Rahul-cs50/ossa  # workspace + plugin
+ossa doctor                              # checks everything
+```
+
+### Windows
+
+OSSA runs on Windows inside WSL2, the Linux that comes with Windows 10 and 11:
+
+1. In PowerShell, run `wsl --install` and restart. That installs Ubuntu.
+2. Open **Ubuntu** from the Start menu. Everything below happens there.
+3. Install Claude Code inside Ubuntu. A copy installed in Windows doesn't count: OSSA's safety hooks have
+   to run in Linux.
+4. For Docker, turn on Docker Desktop's *Settings → Resources → WSL integration* for Ubuntu, or install
+   Docker Engine inside Ubuntu.
+5. Run the install line above. Keep the workspace in your Linux home (the default, `~/ossa`), not under
+   `/mnt/c`, which is slow and ignores letter case.
+
+`ossa doctor` checks each of these. Run in Windows itself, `ossa` and the installer only print these steps.
+WSL has no system keychain, so `ossa init` keeps your GitHub token in `~/.config/ossa/token`, a file only
+you can read; the crew can't open it.
+
+## Use
+
+```sh
+ossa wake        # start the crew (Claude Code in ~/ossa, with the Captain)
+```
+
+Then talk to the Captain: "find something to fix in a Python project", "what's waiting for me?".
+When a PR is ready, the Captain tells you. You review and decide in your own terminal:
+
+```sh
+ossa approve     # read each card; approve in your own words, ask for changes, or reject
+ossa status      # your level, caps, open PRs and what waits for you
+```
+
+The card fits what you need to decide on one screen: what broke, the evidence (the reproduction,
+the tests, Breaker's attacks), the repo's rules, the PR text exactly as it will go out, and the diff.
+
+<img src="docs/demo/card.svg" alt="The approval card for a sample fix: what broke, the evidence, the repo's rules, the PR text, the commit message and the diff" width="720">
+
+*The pictures here are OSSA's real screens, drawn from sample data about a made-up repo
+(`scripts/demo.py`).*
+
+### Your commands
+
+| Command | What |
+|---|---|
+| `ossa wake` | start the crew |
+| `ossa approve [attempt]` | review queued PRs; approve, ask for changes, or reject |
+| `ossa claim <attempt>` | post a claim comment the crew drafted, for repos that assign issues first |
+| `ossa allow <repo> --why ...` | after reading the quote yourself: lift an AI-ban match or a CLA block |
+| `ossa sleep [--hours N]` | stop the crew in every session in the workspace until `ossa wake` (or N hours) |
+| `ossa status`, `ossa doctor`, `ossa gc` | standing and what happened while you were away, health check, cleanup |
+
+The crew's own commands (`ossa repos`, `policy`, `issues`, `start`, `env`, `test`, `repro`,
+`verify`, `risk`, `attack`, `duel`, `queue`, ...) print JSON for Claude; you rarely need them.
+
+### The crew pane
+
+In your workspace, a pane beside the chat shows who in the crew is on shift and what they're doing,
+your 5-hour and 7-day quota, the PRs waiting for you and your level: 😴 when a usage limit stopped
+the crew (until the reset), 💤 while you have it on `ossa sleep`, 💦 while tests run in the sandbox,
+🪧 when something needs you. It is the `ossa-pet` plugin, installed beside `ossa`, and it only reads
+files: it never writes one or uses the network. It interrupts you only when you're needed: a toast
+when a new PR starts waiting for you.
+
+<img src="docs/demo/pane.svg" alt="The crew pane: who is on shift, your level, quota bars, the PR waiting for you, and what happened while you were away" width="560">
+
+**While you were away.** `ossa wake` and `ossa status` show what the ledger recorded since you last
+looked: PRs ready for you, fixes the crew dropped and why, PRs opened, merged or closed, new maintainer
+comments, usage-limit stops. The pane and the Captain show the same list. It comes from the ledger,
+not from the crew's own account of its work. In background mode each run's summary on GitHub carries
+it too (`ossa away --md`).
+
+<img src="docs/demo/status.svg" alt="ossa status with sample data: level, the PR waiting for you, open PRs, caps, and while you were away" width="720">
+
+Rename the crew in `ossa.toml` (`[crew]`, e.g. `breaker = "Bruno"`). Instant commands, no model call:
+
+| In Claude Code | What |
+|---|---|
+| `/ossa` | open the pane |
+| `/ossa status` | the same, as text |
+| `/ossa pause`, `/ossa resume` | hold the crew's next `ossa` step or crew agent, then let it go on |
+
+`/ossa pause` holds one session. `ossa sleep`, in your own terminal, stops the crew everywhere in the
+workspace, headless sessions included: until `ossa wake`, its next `ossa` step and every file write are
+refused. When the crew stops on a usage limit, OSSA notes when it resets (`runs/limit.json`), and
+`ossa status` says when the crew can go on.
+
+## Safety
+
+The short version: the crew can't publish, can't run repository code outside a sandbox, can't touch
+your credentials, and can't skip a repo's rules; you approve every PR in your own words. Every
+guarantee, how it is enforced, and the known limits are in [SAFETY.md](SAFETY.md). Found a way around
+one? Report it privately: [SECURITY.md](SECURITY.md).
+
+## How OSSA is tested
+
+| What | How | Run it |
+|---|---|---|
+| The toolbox and the guard | 400+ tests, no network, Docker, token or model needed | `pytest -q` |
+| The crew under pressure | red-team evals: injected instructions in an issue and in a CONTRIBUTING.md, an AI-banning repo, requests to mass-open PRs, hide AI help, use an alternate account, post a security hole, run your own steps, or work while you have the crew asleep | `claude plugin eval plugin --scaffold --allow-tools Write Edit` |
+| Reading real AI policies | 19 real projects' policies against a careful human reading (18 agree; see SAFETY.md) | `python scripts/policy_corpus.py` |
+| A first install | install.sh and the five `ossa init` questions at a real terminal, on a clean Linux container and on macOS in CI | `sh scripts/install_test_docker.sh` |
+| The crew pane | it only reads files: `claude plugin validate pet` lists every call it makes | `claude plugin test pet` |
+
+## Levels
+
+Trust is the currency. You earn XP for outcomes maintainers decide (a merge is +100, an approving
+review +30, feedback addressed +20, a weak fix stopped before it went out +10; a PR closed unmerged
+is -50), never for PRs opened. Levels raise your caps, from 1 open PR as a newcomer to 8 as a veteran.
+
+## For maintainers
+
+Don't want OSSA contributions? Add this line to your AGENTS.md or CONTRIBUTING.md:
+
+```
+ossa: opt-out
+```
+
+or open a PR adding your repo to [`src/ossa/data/optout.txt`](src/ossa/data/optout.txt). Every OSSA
+user's crew checks both before any work, and nobody can override them. If you have an AI policy,
+OSSA reads it: clear bans stop the crew, and disclosure rules are followed word for word. What an
+OSSA PR looks like, and how to tell us when one wasted your time: [docs/maintainers.md](docs/maintainers.md).
+
+## Development
+
+```sh
+uv venv && uv pip install -e '.[dev]'
+.venv/bin/pytest -q                      # no network, Docker, token or LLM needed
+claude plugin validate plugin            # the plugin
+claude --plugin-dir plugin               # try it from a workspace folder holding ossa.toml
+sh scripts/release_check.sh              # build and check the package as PyPI will
+```
+
+Releases: [RELEASING.md](RELEASING.md).

ossa-0.1.0a1/pyproject.toml

@@ -0,0 +1,56 @@
+[project]
+name = "ossa"
+version = "0.1.0-alpha.1"
+description = "OSSA toolbox: the deterministic half of a safety-first open-source contribution crew that runs on Claude Code."
+readme = "README.md"
+license = "Apache-2.0"
+license-files = ["LICENSE"]
+requires-python = ">=3.11"
+authors = [{ name = "Rahul Seervi" }]
+keywords = ["open-source", "contributions", "claude-code", "sandbox", "safety", "pull-requests"]
+classifiers = [
+  "Development Status :: 3 - Alpha",
+  "Environment :: Console",
+  "Intended Audience :: Developers",
+  "Operating System :: MacOS",
+  "Operating System :: POSIX :: Linux",
+  "Programming Language :: Python :: 3",
+  "Programming Language :: Python :: 3 :: Only",
+  "Programming Language :: Python :: 3.11",
+  "Programming Language :: Python :: 3.12",
+  "Programming Language :: Python :: 3.13",
+  "Topic :: Software Development",
+  "Topic :: Software Development :: Quality Assurance",
+]
+dependencies = [
+  "httpx>=0.27",
+  "pydantic>=2.6",
+  "typer>=0.12",
+  "rich>=13.7",
+]
+
+[project.optional-dependencies]
+dev = ["pytest>=8"]
+
+[project.urls]
+Homepage = "https://github.com/Rahul-cs50/ossa"
+Repository = "https://github.com/Rahul-cs50/ossa"
+Issues = "https://github.com/Rahul-cs50/ossa/issues"
+Safety = "https://github.com/Rahul-cs50/ossa/blob/main/SAFETY.md"
+
+[project.scripts]
+ossa = "ossa.cli:app"
+
+[build-system]
+requires = ["setuptools>=77"]     # PEP 639: license = "<SPDX expression>"
+build-backend = "setuptools.build_meta"
+
+[tool.setuptools.packages.find]
+where = ["src"]
+include = ["ossa*"]
+
+[tool.setuptools.package-data]
+ossa = ["data/*.txt", "data/*.yml"]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]

ossa-0.1.0a1/setup.cfg

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

ossa-0.1.0a1/src/ossa/__init__.py

@@ -0,0 +1,2 @@
+"""OSSA toolbox: the deterministic half of a safety-first open-source contribution crew."""
+__version__ = "0.1.0-alpha.1"