docs: remove design-partner claim; align backend labels with LIMITS.md#1020
Merged
Conversation
- Replace "we are validating with design partners" with "seeking design partners" — no design partners exist yet and the README must not imply otherwise. - Align backend maturity language with openadapt-flow docs/LIMITS.md: Windows UI Automation is Experimental; RDP/Citrix-style pixel-only automation is Research (previously blurred together as "experimental"). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
README text only — no launcher code.
docs/LIMITS.mdat OpenAdaptAI/openadapt-flow@main): Windows UI Automation = Experimental; RDP/Citrix-style pixel-only automation = Research. Three spots previously blurred these together as "experimental": the lead paragraph, the "How the compiler works" section, and the product-surfaces footnote; plus the maturity-table row foropenadapt-flow.Why
This repo is the org's 1.6k-star front door and the canonical launcher (#1012, #1014). Its capability language must match the engine's own limits page exactly — and must never imply customers or partners that don't exist.
Sources
docs/LIMITS.mdat OpenAdaptAI/openadapt-flow@main — "Windows UI Automation: Experimental"; "RDP and Citrix-style pixel-only automation: Research … This is not a validated Citrix integration."benchmark/openemr/BENCHMARK.mdand were not touched.Suggested repo "About" string (admin action, not part of this PR)
Current: "Open-source adapter between multimodal models and desktop/web GUIs. Record a workflow once, then compile it into a deterministic, self-healing replay (openadapt-flow) — or condition, train, and evaluate agents on it. Modular meta-package; install only the extras you need."
Suggested: "Compile a demonstrated GUI workflow into a deterministic, locally executable program. Zero model calls on healthy runs; governed repair; halts instead of guessing. Launcher for openadapt-flow: pip install openadapt"
🤖 Generated with Claude Code