ai-flow config: opt dev into org-tier learning promotion - #96
Merged
Conversation
The dev#89 /learn re-run judged harness-env-scrub org-tier and declared PROMOTE, but the routing declined: no knowledge_repo was configured. This is the write-path opt-in (which repos may open proposal PRs on the org knowledge base), reviewed in-repo like the rest of ai-flow policy; the read path stays machine-side in dev's own settings. Co-authored-by: Cursor <cursoragent@cursor.com>
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
Summary
knowledge_repo: d3mlabs/knowledgeto.github/ai-flow.yml, opting dev's capture passes into org-tier promotion: a pass that judges a lesson org-tier (PROMOTE: <slug>, or an explicit/learn --promote) can now open a proposal PR on the knowledge repo and prune the lesson from the repo-local draft.Why
Surfaced by the dev#89
/learnre-run: it judgedharness-env-scruborg-tier and declared PROMOTE, but correctly declined routing because noknowledge_repo:was configured — dev was never wired to the knowledge base's write path. The key lives here (not in dev's machine settings) deliberately: it authorizes automated org proposals from this repo, so it belongs on the in-repo, PR-reviewed policy surface, same as model policy. The read path (dev learnings sync/ invariants cache) remains configured machine-side viaDev::Settings.Test plan
/learnon dev#89 — the PROMOTE declaration should routeharness-env-scruborg-ward (proposal PR on d3mlabs/knowledge, repo-local draft pruned) — the plans#17 live PROMOTE check.Made with Cursor