[codex] Introduce Salacia v0.2 harness runtime#8
Closed
StartripAI wants to merge 1 commit intomainfrom
Closed
Conversation
Owner
Author
|
Merged directly to main per request. |
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.
What changed
This PR introduces the first v0.2 harness/runtime flow for Salacia.
program.md -> blueprint -> context -> run -> judge -> trace -> evalWhy
Salacia should present as the harness/runtime between a repository and a coding agent, not only as a prompt/plan enhancer. This change establishes the new public flow and the underlying runtime artifacts to support it.
User impact
Users can now:
program.mdsalacia designsalacia runsalacia judgeandsalacia tracesalacia evalas the unified benchmark/superiority surfaceValidation
npm run buildnpm test