Skip to content

docs: remove the withdrawn billing-audit case from the post backlog #61

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
abrichr merged 1 commit into from
Oct 14, 2026
Merged

docs: remove the withdrawn billing-audit case from the post backlog #61

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 0 additions & 3 deletions docs/POST_BACKLOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,9 +45,6 @@ list. Delete entries when published or no longer relevant.
- **Release-health / unreleased-work detectors shipped identically across five repos (Flow, Desktop, Capture, launcher, tray) after openadapt-capture PR #51 sat merged-but-unreleased with a privacy defect still live on PyPI** — A real organizational failure mode: a fixed security/privacy bug (raw audio upload to a third party) merged to main but the fix never shipped because releases are manual-dispatch-only, and nothing alerted. That's a good 'invisible gap between merged and released' story applicable to any team with manual release gates.
- Missing: Needs the actual before/after: how long the vulnerable version stayed live on PyPI, whether any user was exposed, and a cleaner single narrative rather than five near-identical PRs. Also needs confirmation of real-world impact (was capture>=1.1.0 actually installed by anyone) to make the stakes concrete rather than hypothetical.
- Source: https://github.com/OpenAdaptAI/openadapt-capture/pull/51, https://github.com/OpenAdaptAI/openadapt-capture/pull/57, https://github.com/OpenAdaptAI/openadapt-flow/pull/283, https://github.com/OpenAdaptAI/openadapt-desktop/pull/70, https://github.com/OpenAdaptAI/OpenAdapt/pull/1063
- **The RVU case study's disclosure/consent rewrites (removing a named health system, then removing the self-defeating disclosure sentence)** — A candid, unusually self-aware example of a company correcting its own conflict-of-interest disclosure not once but twice, including realizing that explaining an omission draws attention to it -- an interesting communications/ethics lesson about disclosure design.
- Missing: This is squarely a marketing/ethics case study about the company itself, not something an outside reader who doesn't use OpenAdapt would find transferable without significant reframing; would need to be written as a general piece on 'how to write a conflict-of-interest disclosure' with the specifics anonymized further.
- Source: https://github.com/OpenAdaptAI/openadapt-web/pull/301, https://github.com/OpenAdaptAI/openadapt-web/pull/305, https://github.com/OpenAdaptAI/openadapt-web/pull/322, https://github.com/OpenAdaptAI/openadapt-web/pull/323

## Reconciled from the stranded July drafts (2026-08-27)

Expand Down
Loading