open-growth-loop 0.2.0__tar.gz

open_growth_loop-0.2.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        https://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 2026 Open Growth Loop contributors
+
+   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
+
+       https://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.

open_growth_loop-0.2.0/NOTICE

@@ -0,0 +1,4 @@
+Open Growth Loop
+Copyright 2026 Open Growth Loop contributors
+
+This product includes software developed by the Open Growth Loop contributors.

open_growth_loop-0.2.0/PKG-INFO

@@ -0,0 +1,204 @@
+Metadata-Version: 2.4
+Name: open-growth-loop
+Version: 0.2.0
+Summary: Local-first repository stewardship with audits, safe next actions, and maintainer handoffs.
+Author: R3ijar
+Maintainer: R3ijar
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/R3ijar/open-growth-loop
+Project-URL: Repository, https://github.com/R3ijar/open-growth-loop
+Project-URL: Issues, https://github.com/R3ijar/open-growth-loop/issues
+Keywords: open-source,maintainer-tools,repository-audit,release-workflow,local-first,codex
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+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 :: Quality Assurance
+Classifier: Topic :: Text Processing
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+Requires-Dist: tomli>=2.0.1; python_version < "3.11"
+Dynamic: license-file
+
+# Open Growth Loop
+
+**One evidence-backed maintainer action, without another noisy bot.**
+
+[![CI](https://github.com/R3ijar/open-growth-loop/actions/workflows/ci.yml/badge.svg)](https://github.com/R3ijar/open-growth-loop/actions/workflows/ci.yml)
+[![Repository Audit](https://github.com/R3ijar/open-growth-loop/actions/workflows/audit.yml/badge.svg)](https://github.com/R3ijar/open-growth-loop/actions/workflows/audit.yml)
+[![License: Apache-2.0](https://img.shields.io/badge/License-Apache--2.0-blue.svg)](LICENSE)
+[![Python 3.10+](https://img.shields.io/badge/Python-3.10%2B-3776AB.svg)](pyproject.toml)
+[![GitHub Release](https://img.shields.io/github/v/release/R3ijar/open-growth-loop)](https://github.com/R3ijar/open-growth-loop/releases/latest)
+
+Open Growth Loop answers one question for maintainers: **what deserves attention next, and what evidence supports it?**
+
+Point it at any repository and it combines repository hygiene with local Git state into one maintainer brief. It can preview safe scaffolds for mechanical gaps, hand judgment-heavy work to an agent, and defer to real issue or pull-request demand when the local repository already looks healthy. Local-only mode needs no account or API key and sends nothing away; an explicit `--github owner/repo` flag can add a bounded, read-only snapshot through the authenticated GitHub CLI.
+
+![Open Growth Loop maintainer workflow](docs/assets/open-growth-loop-system-v013.svg)
+
+## Quickstart
+
+```bash
+pip install git+https://github.com/R3ijar/open-growth-loop
+ogl audit --workspace path/to/your-repo
+ogl steward --workspace path/to/your-repo
+ogl steward --workspace path/to/your-repo --no-write  # read-only JSON decision
+ogl steward --workspace path/to/your-repo --github owner/repo  # opt-in live public evidence
+```
+
+Thirty seconds later, `outbox/audit/latest-audit.md` holds a scorecard over 14 hygiene checks — README quality, license, install and quickstart onboarding, docs, examples, community files, changelog, CI, and release-tag cadence:
+
+| Check | Category | Status | Detail |
+| --- | --- | --- | --- |
+| README | essentials | PASS | README is present with enough content to evaluate the project. |
+| License | essentials | PASS | A license file is present. |
+| Quickstart | onboarding | WARN | README has no usage section with a copy-pasteable example. |
+| Continuous integration | automation | WARN | No CI configuration was found; contributors cannot see whether tests pass. |
+| Release tags | release | PASS | Latest tag is v1.3.0. |
+
+*...plus nine more checks, and then the part that matters:*
+
+| Field | Value |
+| --- | --- |
+| Action | Add a Quickstart section with one runnable example and its expected output. |
+| Why now | README has no usage section with a copy-pasteable example. |
+| Confidence | medium |
+
+Every audit recommends exactly **one next action**, ordered by how much each gap hurts a new visitor, with a step checklist and a Codex-ready prompt — so the next focused change is one paste away. Reports stay local; add `outbox/` to your `.gitignore` if you don't want to keep them.
+
+And when the gap is mechanical, you don't even have to write the file:
+
+```bash
+ogl fix --workspace path/to/your-repo                 # scaffold the recommended action
+ogl fix --workspace path/to/your-repo --license mit   # licenses need an explicit choice
+```
+
+`ogl fix` scaffolds missing community files, changelogs, licenses, issue/PR templates, and an ecosystem-detected starter CI workflow — with TODO markers, never overwriting anything. Checks that need real judgment (README content, docs, quickstart) hand you the Codex prompt instead. A bare repository typically goes from 0% to ~70% with fixes alone; the rest is writing worth doing yourself.
+
+## Use It With Codex
+
+The repository includes an installable [`repo-steward` skill](skills/repo-steward/SKILL.md). It tells Codex to begin with local evidence, check live maintainer demand when available, choose exactly one bounded action, and keep pushes, releases, merges, comments, and other remote mutations behind explicit approval.
+
+Invoke it with a request such as:
+
+```text
+Use $repo-steward to inspect this repository and complete the safest evidence-backed maintainer action.
+```
+
+The skill uses `ogl steward` as its evidence packet and can opt in to `--github owner/repo` when current public issues, pull requests, CI runs, and releases should influence the decision. All GitHub commands are reads; the CLI remains useful without an agent or network access.
+
+## Maintainer Field Test
+
+Open Growth Loop needs counterexamples more than endorsements. If you maintain a public repository, run `ogl steward --no-write` and tell us where its selected action was wrong. The [20-minute field test](docs/ADOPTION.md) has a structured feedback form and does not require a call or ongoing commitment.
+
+## Use It As A GitHub Action
+
+Add one workflow file and the audit runs on every push, straight into the Actions job summary:
+
+```yaml
+name: Repository Audit
+on:
+  push:
+    branches: [main]
+
+jobs:
+  audit:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      - uses: R3ijar/open-growth-loop@main
+```
+
+The action exposes `ok` and `score-percent` outputs and an optional `strict` gate that fails the job when README or LICENSE is missing. Full reference: [docs/GITHUB_ACTION.md](docs/GITHUB_ACTION.md). This repository [runs it on itself](.github/workflows/audit.yml).
+
+## The Full Loop
+
+The audit covers hygiene; the loop plans from evidence. Drop privacy-safe CSV exports into `data/` — Search Console rows, aggregate event counts (`date,asset,event,count` only), a content inventory, an experiment ledger — and Open Growth Loop turns them into one conservative daily action:
+
+```bash
+ogl init --workspace .       # create the data files
+ogl validate --workspace .   # schema and privacy-safe header checks
+ogl plan --workspace .       # one action, fully explained
+```
+
+```json
+{
+  "action_type": "release_evidence",
+  "asset": "/guides/configuration-checklist",
+  "confidence": "high",
+  "reason": "Staged work should be proven public before creating another asset."
+}
+```
+
+Each plan ships with a **decision trace** (what won, what lost and why, which thresholds applied) and a **data freshness** report (whether the inputs deserve trust). Completed work and its later outcomes feed back into ranking, so the loop learns locally. Browse real generated reports in the [report gallery](docs/REPORT_GALLERY.md).
+
+### Planner Engine Coverage
+
+Candidates are ranked across the maintainer surfaces that shape OSS adoption, in deliberately conservative priority order:
+
+1. **Release evidence** — prove staged docs, examples, or package pages are actually public before starting anything new.
+2. **Outcome memory** — record what happened to completed work before repeating it.
+3. **Funnel dropoff** — public pages with enough views but weak install, try, or next-step clicks.
+4. **Search opportunities** — near-ranking pages and low-CTR queries from Search Console exports.
+5. **Planned assets** — the next queued guide or page, only when stronger signals are absent.
+
+Weak evidence is labeled insufficient instead of being spun into a win. The goal is less thrash, not a content treadmill.
+
+## Commands
+
+| Command | What it does |
+| --- | --- |
+| `ogl audit` | Zero-config repository readiness scorecard with one recommended action. |
+| `ogl steward` | Combine the audit, local Git state, and optional read-only GitHub evidence into one maintainer brief. |
+| `ogl fix` | Scaffold the recommended action when it is mechanical; hand off a Codex prompt when it is not. |
+| `ogl init` / `ogl validate` | Create and check the local data CSVs. |
+| `ogl doctor` | One-shot readiness report across validation, freshness, privacy, planning, and release review. |
+| `ogl demo` | Generate the complete report set in one run. |
+| `ogl freshness` | Warn when local inputs are too stale to trust. |
+| `ogl candidates` / `ogl plan` | Rank every considered action; select one with a full decision trace. |
+| `ogl prompt` / `ogl issue-drafts` | Turn the plan into a Codex-ready prompt or a reviewable issue draft. |
+| `ogl complete` / `ogl outcome` | Record what was done and what happened, so ranking learns locally. |
+| `ogl track-experiment` / `ogl ship` / `ogl review-experiments` | Baseline, ship, and conservatively review changes. |
+| `ogl weekly-review` / `ogl query-backlog` / `ogl report-index` | Operating summaries and the report front page. |
+| `ogl privacy-scan` | Check local files for private-data leakage before sharing. |
+
+Full walkthroughs, data schemas, thresholds, and column aliases live in the [usage guide](docs/USAGE.md).
+
+## Privacy Boundary
+
+Open Growth Loop is designed around aggregate inputs. The event importer accepts only `date,asset,event,count` and rejects private-looking columns such as email, user, session, ip, payload, token, or secret. Local-only commands never upload analytics or project files. The optional `steward --github owner/repo` adapter calls `gh` only for repository metadata and never writes, comments, labels, merges, closes, or publishes. The project never claims a change worked from tiny samples or missing artifacts.
+
+## Documentation
+
+- [Usage guide](docs/USAGE.md) — installation, every command, data files, configuration, and decision rules.
+- [GitHub Action reference](docs/GITHUB_ACTION.md) — inputs, outputs, strict mode, and scheduled audits.
+- [Example workflow](docs/EXAMPLE_WORKFLOW.md) — a full walkthrough with the bundled sample CSVs.
+- [Report gallery](docs/REPORT_GALLERY.md) — what the generated reports look like.
+- [Runnable examples](examples/README.md) — five synthetic workspaces with documented expected plans.
+- [Dogfooding](docs/DOGFOODING.md) — how this repository maintains itself with its own loop.
+- [Public compatibility study](docs/COMPATIBILITY_STUDY.md) — a transparent ten-repository run, including two defects it exposed and the limits of the evidence.
+- [Adoption and design partners](docs/ADOPTION.md) — run a field test and share verifiable feedback.
+- [Releasing](docs/RELEASING.md) — the tag-driven PyPI release process.
+- [Roadmap](ROADMAP.md) and [Changelog](CHANGELOG.md).
+
+## Project Status
+
+Version on `main`: v0.2.0. See [GitHub Releases](https://github.com/R3ijar/open-growth-loop/releases) for the latest published version. The project is early and is actively seeking maintainer design partners. The zero-config audit, steward brief, fix scaffolds, and GitHub Action are ready for field testing; the CSV-driven loop remains available for small maintainer workflows.
+
+## Contributing
+
+Issues and pull requests are welcome — [CONTRIBUTING.md](CONTRIBUTING.md) covers setup and expectations, and [docs/NEXT_ISSUES.md](docs/NEXT_ISSUES.md) lists good starting points. Please keep private product data and unverifiable adoption claims out of examples and docs; `ogl privacy-scan` and the release-brief guardrails exist for exactly that.
+
+Open Growth Loop is maintained by [@R3ijar](https://github.com/R3ijar), who owns scope, releases, and final review. See the [design-partner outreach playbook](docs/OUTREACH.md) for the public feedback process.
+
+## License
+
+[Apache-2.0](LICENSE)

open_growth_loop-0.2.0/README.md

@@ -0,0 +1,176 @@
+# Open Growth Loop
+
+**One evidence-backed maintainer action, without another noisy bot.**
+
+[![CI](https://github.com/R3ijar/open-growth-loop/actions/workflows/ci.yml/badge.svg)](https://github.com/R3ijar/open-growth-loop/actions/workflows/ci.yml)
+[![Repository Audit](https://github.com/R3ijar/open-growth-loop/actions/workflows/audit.yml/badge.svg)](https://github.com/R3ijar/open-growth-loop/actions/workflows/audit.yml)
+[![License: Apache-2.0](https://img.shields.io/badge/License-Apache--2.0-blue.svg)](LICENSE)
+[![Python 3.10+](https://img.shields.io/badge/Python-3.10%2B-3776AB.svg)](pyproject.toml)
+[![GitHub Release](https://img.shields.io/github/v/release/R3ijar/open-growth-loop)](https://github.com/R3ijar/open-growth-loop/releases/latest)
+
+Open Growth Loop answers one question for maintainers: **what deserves attention next, and what evidence supports it?**
+
+Point it at any repository and it combines repository hygiene with local Git state into one maintainer brief. It can preview safe scaffolds for mechanical gaps, hand judgment-heavy work to an agent, and defer to real issue or pull-request demand when the local repository already looks healthy. Local-only mode needs no account or API key and sends nothing away; an explicit `--github owner/repo` flag can add a bounded, read-only snapshot through the authenticated GitHub CLI.
+
+![Open Growth Loop maintainer workflow](docs/assets/open-growth-loop-system-v013.svg)
+
+## Quickstart
+
+```bash
+pip install git+https://github.com/R3ijar/open-growth-loop
+ogl audit --workspace path/to/your-repo
+ogl steward --workspace path/to/your-repo
+ogl steward --workspace path/to/your-repo --no-write  # read-only JSON decision
+ogl steward --workspace path/to/your-repo --github owner/repo  # opt-in live public evidence
+```
+
+Thirty seconds later, `outbox/audit/latest-audit.md` holds a scorecard over 14 hygiene checks — README quality, license, install and quickstart onboarding, docs, examples, community files, changelog, CI, and release-tag cadence:
+
+| Check | Category | Status | Detail |
+| --- | --- | --- | --- |
+| README | essentials | PASS | README is present with enough content to evaluate the project. |
+| License | essentials | PASS | A license file is present. |
+| Quickstart | onboarding | WARN | README has no usage section with a copy-pasteable example. |
+| Continuous integration | automation | WARN | No CI configuration was found; contributors cannot see whether tests pass. |
+| Release tags | release | PASS | Latest tag is v1.3.0. |
+
+*...plus nine more checks, and then the part that matters:*
+
+| Field | Value |
+| --- | --- |
+| Action | Add a Quickstart section with one runnable example and its expected output. |
+| Why now | README has no usage section with a copy-pasteable example. |
+| Confidence | medium |
+
+Every audit recommends exactly **one next action**, ordered by how much each gap hurts a new visitor, with a step checklist and a Codex-ready prompt — so the next focused change is one paste away. Reports stay local; add `outbox/` to your `.gitignore` if you don't want to keep them.
+
+And when the gap is mechanical, you don't even have to write the file:
+
+```bash
+ogl fix --workspace path/to/your-repo                 # scaffold the recommended action
+ogl fix --workspace path/to/your-repo --license mit   # licenses need an explicit choice
+```
+
+`ogl fix` scaffolds missing community files, changelogs, licenses, issue/PR templates, and an ecosystem-detected starter CI workflow — with TODO markers, never overwriting anything. Checks that need real judgment (README content, docs, quickstart) hand you the Codex prompt instead. A bare repository typically goes from 0% to ~70% with fixes alone; the rest is writing worth doing yourself.
+
+## Use It With Codex
+
+The repository includes an installable [`repo-steward` skill](skills/repo-steward/SKILL.md). It tells Codex to begin with local evidence, check live maintainer demand when available, choose exactly one bounded action, and keep pushes, releases, merges, comments, and other remote mutations behind explicit approval.
+
+Invoke it with a request such as:
+
+```text
+Use $repo-steward to inspect this repository and complete the safest evidence-backed maintainer action.
+```
+
+The skill uses `ogl steward` as its evidence packet and can opt in to `--github owner/repo` when current public issues, pull requests, CI runs, and releases should influence the decision. All GitHub commands are reads; the CLI remains useful without an agent or network access.
+
+## Maintainer Field Test
+
+Open Growth Loop needs counterexamples more than endorsements. If you maintain a public repository, run `ogl steward --no-write` and tell us where its selected action was wrong. The [20-minute field test](docs/ADOPTION.md) has a structured feedback form and does not require a call or ongoing commitment.
+
+## Use It As A GitHub Action
+
+Add one workflow file and the audit runs on every push, straight into the Actions job summary:
+
+```yaml
+name: Repository Audit
+on:
+  push:
+    branches: [main]
+
+jobs:
+  audit:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      - uses: R3ijar/open-growth-loop@main
+```
+
+The action exposes `ok` and `score-percent` outputs and an optional `strict` gate that fails the job when README or LICENSE is missing. Full reference: [docs/GITHUB_ACTION.md](docs/GITHUB_ACTION.md). This repository [runs it on itself](.github/workflows/audit.yml).
+
+## The Full Loop
+
+The audit covers hygiene; the loop plans from evidence. Drop privacy-safe CSV exports into `data/` — Search Console rows, aggregate event counts (`date,asset,event,count` only), a content inventory, an experiment ledger — and Open Growth Loop turns them into one conservative daily action:
+
+```bash
+ogl init --workspace .       # create the data files
+ogl validate --workspace .   # schema and privacy-safe header checks
+ogl plan --workspace .       # one action, fully explained
+```
+
+```json
+{
+  "action_type": "release_evidence",
+  "asset": "/guides/configuration-checklist",
+  "confidence": "high",
+  "reason": "Staged work should be proven public before creating another asset."
+}
+```
+
+Each plan ships with a **decision trace** (what won, what lost and why, which thresholds applied) and a **data freshness** report (whether the inputs deserve trust). Completed work and its later outcomes feed back into ranking, so the loop learns locally. Browse real generated reports in the [report gallery](docs/REPORT_GALLERY.md).
+
+### Planner Engine Coverage
+
+Candidates are ranked across the maintainer surfaces that shape OSS adoption, in deliberately conservative priority order:
+
+1. **Release evidence** — prove staged docs, examples, or package pages are actually public before starting anything new.
+2. **Outcome memory** — record what happened to completed work before repeating it.
+3. **Funnel dropoff** — public pages with enough views but weak install, try, or next-step clicks.
+4. **Search opportunities** — near-ranking pages and low-CTR queries from Search Console exports.
+5. **Planned assets** — the next queued guide or page, only when stronger signals are absent.
+
+Weak evidence is labeled insufficient instead of being spun into a win. The goal is less thrash, not a content treadmill.
+
+## Commands
+
+| Command | What it does |
+| --- | --- |
+| `ogl audit` | Zero-config repository readiness scorecard with one recommended action. |
+| `ogl steward` | Combine the audit, local Git state, and optional read-only GitHub evidence into one maintainer brief. |
+| `ogl fix` | Scaffold the recommended action when it is mechanical; hand off a Codex prompt when it is not. |
+| `ogl init` / `ogl validate` | Create and check the local data CSVs. |
+| `ogl doctor` | One-shot readiness report across validation, freshness, privacy, planning, and release review. |
+| `ogl demo` | Generate the complete report set in one run. |
+| `ogl freshness` | Warn when local inputs are too stale to trust. |
+| `ogl candidates` / `ogl plan` | Rank every considered action; select one with a full decision trace. |
+| `ogl prompt` / `ogl issue-drafts` | Turn the plan into a Codex-ready prompt or a reviewable issue draft. |
+| `ogl complete` / `ogl outcome` | Record what was done and what happened, so ranking learns locally. |
+| `ogl track-experiment` / `ogl ship` / `ogl review-experiments` | Baseline, ship, and conservatively review changes. |
+| `ogl weekly-review` / `ogl query-backlog` / `ogl report-index` | Operating summaries and the report front page. |
+| `ogl privacy-scan` | Check local files for private-data leakage before sharing. |
+
+Full walkthroughs, data schemas, thresholds, and column aliases live in the [usage guide](docs/USAGE.md).
+
+## Privacy Boundary
+
+Open Growth Loop is designed around aggregate inputs. The event importer accepts only `date,asset,event,count` and rejects private-looking columns such as email, user, session, ip, payload, token, or secret. Local-only commands never upload analytics or project files. The optional `steward --github owner/repo` adapter calls `gh` only for repository metadata and never writes, comments, labels, merges, closes, or publishes. The project never claims a change worked from tiny samples or missing artifacts.
+
+## Documentation
+
+- [Usage guide](docs/USAGE.md) — installation, every command, data files, configuration, and decision rules.
+- [GitHub Action reference](docs/GITHUB_ACTION.md) — inputs, outputs, strict mode, and scheduled audits.
+- [Example workflow](docs/EXAMPLE_WORKFLOW.md) — a full walkthrough with the bundled sample CSVs.
+- [Report gallery](docs/REPORT_GALLERY.md) — what the generated reports look like.
+- [Runnable examples](examples/README.md) — five synthetic workspaces with documented expected plans.
+- [Dogfooding](docs/DOGFOODING.md) — how this repository maintains itself with its own loop.
+- [Public compatibility study](docs/COMPATIBILITY_STUDY.md) — a transparent ten-repository run, including two defects it exposed and the limits of the evidence.
+- [Adoption and design partners](docs/ADOPTION.md) — run a field test and share verifiable feedback.
+- [Releasing](docs/RELEASING.md) — the tag-driven PyPI release process.
+- [Roadmap](ROADMAP.md) and [Changelog](CHANGELOG.md).
+
+## Project Status
+
+Version on `main`: v0.2.0. See [GitHub Releases](https://github.com/R3ijar/open-growth-loop/releases) for the latest published version. The project is early and is actively seeking maintainer design partners. The zero-config audit, steward brief, fix scaffolds, and GitHub Action are ready for field testing; the CSV-driven loop remains available for small maintainer workflows.
+
+## Contributing
+
+Issues and pull requests are welcome — [CONTRIBUTING.md](CONTRIBUTING.md) covers setup and expectations, and [docs/NEXT_ISSUES.md](docs/NEXT_ISSUES.md) lists good starting points. Please keep private product data and unverifiable adoption claims out of examples and docs; `ogl privacy-scan` and the release-brief guardrails exist for exactly that.
+
+Open Growth Loop is maintained by [@R3ijar](https://github.com/R3ijar), who owns scope, releases, and final review. See the [design-partner outreach playbook](docs/OUTREACH.md) for the public feedback process.
+
+## License
+
+[Apache-2.0](LICENSE)

open_growth_loop-0.2.0/pyproject.toml

@@ -0,0 +1,58 @@
+[build-system]
+requires = ["setuptools>=77"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "open-growth-loop"
+version = "0.2.0"
+description = "Local-first repository stewardship with audits, safe next actions, and maintainer handoffs."
+readme = "README.md"
+requires-python = ">=3.10"
+license = "Apache-2.0"
+authors = [
+  { name = "R3ijar" }
+]
+maintainers = [
+  { name = "R3ijar" }
+]
+keywords = ["open-source", "maintainer-tools", "repository-audit", "release-workflow", "local-first", "codex"]
+classifiers = [
+  "Development Status :: 3 - Alpha",
+  "Environment :: Console",
+  "Intended Audience :: Developers",
+  "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 :: Quality Assurance",
+  "Topic :: Text Processing"
+]
+dependencies = [
+  "tomli>=2.0.1; python_version < '3.11'"
+]
+
+[project.urls]
+Homepage = "https://github.com/R3ijar/open-growth-loop"
+Repository = "https://github.com/R3ijar/open-growth-loop"
+Issues = "https://github.com/R3ijar/open-growth-loop/issues"
+
+[project.scripts]
+ogl = "open_growth_loop.cli:main"
+
+[tool.setuptools.packages.find]
+where = ["src"]
+
+[tool.setuptools.package-data]
+open_growth_loop = ["templates/*"]
+
+[tool.pytest.ini_options]
+pythonpath = ["src"]
+testpaths = ["tests"]
+
+[tool.ruff]
+line-length = 160
+target-version = "py310"
+
+[tool.ruff.lint]
+select = ["E4", "E7", "E9", "F", "I", "B", "UP"]

open_growth_loop-0.2.0/setup.cfg

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

open_growth_loop-0.2.0/src/open_growth_loop/__init__.py

@@ -0,0 +1,5 @@
+"""Open Growth Loop package."""
+
+__all__ = ["__version__"]
+
+__version__ = "0.2.0"