Repository navigation
Conversation
This was referenced Sep 22, 2026
Owner
Author
|
Concrete implementation of this acceptance contract is now in stacked PR #16: real OMP RPC process, model/thinking identity snapshots, model-issued |
Owner
Author
|
The acceptance intent from this PR has now been distilled into the current Eval path rather than merged as a parallel 792-line authority. Current location:
The real implementation path is now #16, rebuilt directly on current main. Keeping this PR open would create a second Eval authority, so I’m closing it as superseded by the distilled contract + #16 implementation. |
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
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.
Why
The current validation work mixes three different things:
The first two are useful, but they do not prove that OMP/SWE-2 (or another real Agent) received a natural-language goal, discovered OfferU Skills, selected Operations, issued model-facing tool calls, stopped at Proposal/HITL, and continued from the resulting Career Truth.
The current scripted
omp_executor.pyis especially easy to over-interpret: it watches a request file and then Python control flow chooses a known Operation sequence. That proves plumbing, not SWE-2 autonomy.This PR makes that distinction explicit before more Eval work builds on the wrong success definition.
What this PR adds
docs/evals/AGENT_NATIVE_ACCEPTANCE.mdA detailed acceptance contract covering:
natural language → real Agent → Skill → model-issued bash/tool → CLI/Bridge → Operation Registry → Proposal/HITL → human UI approval → Career Truth → Agent continuationAGENTS.mdAdds two hard guardrails:
Intended effect on PR #14
This does not reject the ApplicationActionConnector Registry work.
The recommendation is to keep Connector Registry/capability-matrix work reviewable as product infrastructure, while reclassifying or splitting the Eval-specific pieces:
omp_executor.pyE2E-EVAL-REPORT.mdIf those files remain in #14, the report should state:
until a real Agent-native run exists.
External references
bashtool-call surface from user bang/RPC shell helpers:https://github.com/can1357/oh-my-pi/blob/main/docs/bash-tool-runtime.md
https://github.com/can1357/oh-my-pi/blob/main/docs/tools/bash.md
https://www.anthropic.com/engineering/demystifying-evals-for-ai-agents
Non-goals
headless=falseautomation is requiredThe goal is simply to make sure future reports prove the product claim they say they prove.