From 015b06fbf02c2b50dd62da860ffb567c88aa77b9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?H=E1=BB=93=20Kh=E1=BA=AFc=20Huy?= <256174233+builtbyhuy@users.noreply.github.com> Date: Mon, 10 Aug 2026 20:33:19 +0700 Subject: [PATCH] docs: record public launch evidence --- docs/evidence/application-readiness.md | 29 ++++++++++-------- docs/evidence/maintainer-validation.csv | 4 +-- docs/evidence/maintainer-validation.md | 30 ++++++++++--------- docs/evidence/public-fixture-matrix.md | 12 ++++---- docs/evidence/technical-falsifier.md | 6 ++-- .../plans/2026-08-10-codex-plugin-check.md | 2 +- 6 files changed, 45 insertions(+), 38 deletions(-) diff --git a/docs/evidence/application-readiness.md b/docs/evidence/application-readiness.md index 7fd2f14..0bce1f0 100644 --- a/docs/evidence/application-readiness.md +++ b/docs/evidence/application-readiness.md @@ -4,11 +4,13 @@ `HOLD — NOT READY TO SUBMIT`. -The repository is still private and there is no independent retained usage or -public maintenance history yet. The technical strict-Linux and public-fixture -gates now pass, but submitting now would establish only that Huy created and -validated a project. It would not establish the usage, ecosystem importance, -or ongoing maintainer responsibility that OpenAI asks applicants to explain. +The repository and `v0.1.0` release are public, but there is no independent +retained usage or sustained public maintenance history yet. The technical +strict-Linux and public-fixture gates pass, and two bounded maintainer contacts +have been sent, but submitting now would establish only that Huy created, +validated and published a project. It would not establish the usage, ecosystem +importance, or ongoing maintainer responsibility that OpenAI asks applicants +to explain. OpenAI's current form says eligible applicants maintain active open-source projects and that reviewers consider meaningful usage, broad adoption or clear @@ -20,18 +22,18 @@ Source: [Codex for Open Source](https://openai.com/form/codex-for-oss/). | Gate | Current state | Required evidence | | --- | --- | --- | -| Public repository and profile | `HOLD` | Public GitHub profile and public repository URL | +| Public repository and profile | `PASS` | [Public repository](https://github.com/builtbyhuy/codex-plugin-check) and profile | | Useful, bounded technical job | `PASS` | Real released-Codex loader evidence with no model/auth dependency | -| Synthetic strict boundary | `PASS` | Private Linux receipts for both target releases | +| Synthetic strict boundary | `PASS` | Publicly documented Linux receipts for both target releases | | Public-plugin compatibility | `PASS` | Reconciled 10-repository, 20-cell strict matrix | | Independent retained use | `0` | External repositories keep the workflow enabled | | Unknown regression caught | `1 local defect` | Publicly linkable regression/issue accepted or reproduced externally | -| Releases | `0 public releases` | Maintained tagged releases and release notes | +| Releases | `1 experimental release` | [v0.1.0](https://github.com/builtbyhuy/codex-plugin-check/releases/tag/v0.1.0); additional feedback-driven releases required | | Ongoing maintainer duties | `INSUFFICIENT` | Public issue triage, PR review and release work over time | | Application | `NOT SUBMITTED` | All required form fields bound to public evidence | -The technical compatibility result is bound to the [reconciled private Linux -run and artifact ledger](public-fixture-matrix.md#strict-linux-observation). +The technical compatibility result is bound to the [reconciled Linux run and +durable release asset ledger](public-fixture-matrix.md#strict-linux-observation). It is publication evidence, not usage or maintainer-role evidence. The local defect was real: an unmodified Claude-compatible marketplace loaded @@ -78,10 +80,11 @@ local files. ## Next evidence-producing actions -1. Publish the reviewed `v0.1.0` release with durable sanitized evidence. +1. Monitor the two public maintainer Discussions; count only observed replies, + external runs, retained workflows and reproduced defects. 2. Keep the application on hold while independent use and maintenance accrue. -3. Offer a bounded integration to maintainers whose immutable fixtures were - tested; do not open promotional issues or claim endorsement. +3. Prepare a repository-specific integration PR only if a maintainer requests + it or a concrete reproducible compatibility defect appears. 4. Record retained workflows, maintainer replies, defects and release upkeep in the maintainer-validation ledger. 5. Re-evaluate the internal submission gates monthly. A green local build or a diff --git a/docs/evidence/maintainer-validation.csv b/docs/evidence/maintainer-validation.csv index 2e9e5aa..e31c2d1 100644 --- a/docs/evidence/maintainer-validation.csv +++ b/docs/evidence/maintainer-validation.csv @@ -1,3 +1,3 @@ repository,maintainer,public_workflow,contact_route,sent_at,receipt_url,ran_at,unknown_defect,retained_required_ci,response_url,status -https://github.com/bitrouter/bitrouter,@bitrouter,https://github.com/bitrouter/bitrouter/blob/main/.github/workflows/ci.yml,https://github.com/bitrouter/bitrouter/discussions,,,,,,,READY_AFTER_PUBLIC_RELEASE -https://github.com/Cassette-Editor/oh-my-cassette,@Cassette-Editor,https://github.com/Cassette-Editor/oh-my-cassette/blob/main/.github/workflows/ci.yml,https://github.com/Cassette-Editor/oh-my-cassette/discussions,,,,,,,READY_AFTER_PUBLIC_RELEASE +https://github.com/bitrouter/bitrouter,@bitrouter,https://github.com/bitrouter/bitrouter/blob/main/.github/workflows/ci.yml,https://github.com/orgs/bitrouter/discussions/805,2026-08-10T13:26:00Z,,,,,,SENT_AWAITING_RESPONSE +https://github.com/Cassette-Editor/oh-my-cassette,@Cassette-Editor,https://github.com/Cassette-Editor/oh-my-cassette/blob/main/.github/workflows/ci.yml,https://github.com/Cassette-Editor/oh-my-cassette/discussions/71,2026-08-10T13:26:15Z,,,,,,SENT_AWAITING_RESPONSE diff --git a/docs/evidence/maintainer-validation.md b/docs/evidence/maintainer-validation.md index e15e9ae..1f76aa5 100644 --- a/docs/evidence/maintainer-validation.md +++ b/docs/evidence/maintainer-validation.md @@ -2,10 +2,10 @@ ## Decision -`HOLD — 0 contacts, 0 independent runs, 0 retained workflows, 0 unknown -defects`. The technical fixture matrix is complete, but no maintainer has been -contacted and no external outcome exists. A prepared row is not a send, reply, -run, integration, adoption signal, or endorsement. +`HOLD — 2 public contacts, 0 maintainer replies, 0 independent runs, 0 retained +workflows, 0 unknown defects`. The technical fixture matrix and first bounded +contact cohort are complete, but no external outcome exists. A sent message is +not a reply, run, integration, adoption signal, or endorsement. The machine-readable ledger is [`maintainer-validation.csv`](maintainer-validation.csv). Blank outcome fields @@ -13,25 +13,27 @@ mean unobserved, not false or unsuccessful. Repository activity, workflow, and contact-route evidence was checked on `2026-08-10` from the repositories' own README/contribution files and GitHub -metadata. Re-check each route immediately before any send. +metadata. Both selected routes were re-checked immediately before sending. ## Qualified first cohort The initial cohort contains only repositories with both an active public CI workflow and a project-owned public route that explicitly accommodates this -kind of discussion. Contact remains blocked until the public `v0.1.0` release -and immutable evidence asset exist. +kind of discussion. Each message was sent only after the public `v0.1.0` +release and durable, SHA-256-bound evidence asset were anonymously reachable. | Repository | Existing public workflow | Maintainer route | Status | | --- | --- | --- | --- | -| [`bitrouter/bitrouter`](https://github.com/bitrouter/bitrouter) | [`CI`](https://github.com/bitrouter/bitrouter/blob/main/.github/workflows/ci.yml) | [Discussions](https://github.com/bitrouter/bitrouter/discussions) | `READY_AFTER_PUBLIC_RELEASE` | -| [`Cassette-Editor/oh-my-cassette`](https://github.com/Cassette-Editor/oh-my-cassette) | [`CI`](https://github.com/Cassette-Editor/oh-my-cassette/blob/main/.github/workflows/ci.yml) | [Discussions](https://github.com/Cassette-Editor/oh-my-cassette/discussions) | `READY_AFTER_PUBLIC_RELEASE` | +| [`bitrouter/bitrouter`](https://github.com/bitrouter/bitrouter) | [`CI`](https://github.com/bitrouter/bitrouter/blob/main/.github/workflows/ci.yml) | [Discussion #805](https://github.com/orgs/bitrouter/discussions/805) | `SENT_AWAITING_RESPONSE` | +| [`Cassette-Editor/oh-my-cassette`](https://github.com/Cassette-Editor/oh-my-cassette) | [`CI`](https://github.com/Cassette-Editor/oh-my-cassette/blob/main/.github/workflows/ci.yml) | [Discussion #71](https://github.com/Cassette-Editor/oh-my-cassette/discussions/71) | `SENT_AWAITING_RESPONSE` | `bitrouter` also publishes a project email for open-source builders and integrations, but Discussions is the preferred first contact because it keeps the request and any reply publicly linkable. `oh-my-cassette` explicitly routes questions, sharing, and plans to Discussions while reserving Issues for -bugs and feature requests. +bugs and feature requests. GitHub recorded the two messages from `builtbyhuy` +at `2026-08-10T13:26:00Z` and `2026-08-10T13:26:15Z`, respectively. No reply +or external run was present when this ledger was written. ## Screened but not in the first cohort @@ -52,9 +54,8 @@ workflow target, maintainer route, and concrete evidence payload. ## Exact first-contact payload -Replace every bracketed field and re-check the target project's current -contact guidance immediately before sending. Send at most one public message -per repository. +The sent messages followed this contract after every bracketed field and route +was re-checked. Send at most one public message per repository. ```text Hi — I maintain Codex Plugin Check, an experimental GitHub Action that asks a @@ -74,7 +75,8 @@ maintenance workflow, no action is needed. ``` The repository-specific message must include the exact tested commit from the -[public fixture matrix](public-fixture-matrix.md), the immutable release URL, +[public fixture matrix](public-fixture-matrix.md), the durable release URL and +asset digest, the exact `DIRECT` or adapter preparation, and a full-SHA Action pin. The `oh-my-cassette` message must say that `STATIC_ADAPTER:local-source-v1` changed only `/plugins/0/source` from its immutable expected input to the audited local diff --git a/docs/evidence/public-fixture-matrix.md b/docs/evidence/public-fixture-matrix.md index 539d0ac..57f2fb5 100644 --- a/docs/evidence/public-fixture-matrix.md +++ b/docs/evidence/public-fixture-matrix.md @@ -149,10 +149,12 @@ observed: ## Publication gate -The technical gate is `PASS`. Before the public release is final, attach the -sanitized receipts and summary as a durable release asset rather than relying -only on the 90-day Actions artifact. A code-`1` receipt must remain plain -`FAIL`/`HOLD`; it cannot establish a version or API incompatibility without -separate causal evidence. This result supports publication of the tool, but it +The technical and durable-publication gates are `PASS`. The +[`v0.1.0` release](https://github.com/builtbyhuy/codex-plugin-check/releases/tag/v0.1.0) +retains the 20 sanitized receipts and summary as +`codex-plugin-check-public-fixture-evidence-v0.1.0.zip` with SHA-256 +`3bcec67f5e1c3833bc5de684b1be6a7aa46859dd326cb9a776eeaf9b774b06f7`. +A code-`1` receipt must remain plain `FAIL`/`HOLD`; it cannot establish a +version or API incompatibility without separate causal evidence. Publication does not satisfy the independent-use or ongoing-maintainer gates for a Codex for Open Source application. diff --git a/docs/evidence/technical-falsifier.md b/docs/evidence/technical-falsifier.md index 610937f..81aeeb3 100644 --- a/docs/evidence/technical-falsifier.md +++ b/docs/evidence/technical-falsifier.md @@ -18,7 +18,7 @@ strict cells. The bounded command must still report `status: "HOLD"` with | Strict Linux boundary | `PASS` | Private GitHub Actions run on `ubuntu-24.04` | | Strict positive and negative lanes | `PASS` | Four exact receipts across both released versions | | Public fixture specification matrix | `PASS` | Separate reconciled ledger: `10/10`, `20/20` | -| Publication | `HOLD` | Repository remains private until the reviewed release evidence is durable | +| Publication | `PASS` | [v0.1.0](https://github.com/builtbyhuy/codex-plugin-check/releases/tag/v0.1.0) with durable sanitized evidence asset | ## Version and variant contract @@ -176,5 +176,5 @@ Artifact SHA-256 values: This closes the bounded synthetic strict-Linux uncertainty. The later [public fixture matrix](public-fixture-matrix.md) also closes the technical `10/10` compatibility gate. The project remains `HOLD` for adoption and Codex -for Open Source application claims until public release and maintenance -evidence exist. +for Open Source application claims until independent use and sustained public +maintenance evidence exist. diff --git a/docs/superpowers/plans/2026-08-10-codex-plugin-check.md b/docs/superpowers/plans/2026-08-10-codex-plugin-check.md index 8781486..ff3620e 100644 --- a/docs/superpowers/plans/2026-08-10-codex-plugin-check.md +++ b/docs/superpowers/plans/2026-08-10-codex-plugin-check.md @@ -559,7 +559,7 @@ pool. Each row must bind to a public workflow and a public maintainer route. Draft one concise request asking the maintainer to run the pinned prerelease and report its receipt; do not claim endorsement or acceptance. -- [ ] **Step 2: Send the bounded cohort and record receipts separately from outcomes** +- [x] **Step 2: Send the bounded cohort and record receipts separately from outcomes** Use only public project channels suitable for tooling feedback. Record an external send only after observing the resulting URL or platform receipt.