Porting an agent project to canyonos core using porting-to-canyonos-core skill - #55
Closed
nickhuo wants to merge 6 commits into
Closed
Porting an agent project to canyonos core using porting-to-canyonos-core skill#55nickhuo wants to merge 6 commits into
nickhuo wants to merge 6 commits into
Conversation
The skill answers, before anyone writes an adapter, the four questions a port turns on: what class Ventis actually loads, what the adapter has to fix, what has to be declared (import root, requirements, env_file), and what to report rather than fix. `ventis-contract.md` pins each claim to the code that makes it true; `traps.md` maps symptoms back to causes. Its one rule: rewrite orchestration, import everything else. A port that restates a prompt, a tool body or a model call has copied the source instead of reusing it.
The skill's worked example. `joke_writer.py` is upstream's map-reduce joke
graph, unedited: three prompts, two schemas, three nodes. What could not come
across is the graph itself -- `StateGraph`, the `Send` fan-out and the
`operator.add` reducer are control flow owned by the LangGraph runtime, and
Ventis has no runtime to execute them.
So the edges are re-expressed as ordinary Python in the workflow, where the
fan-out becomes N calls dispatched across JokeAgent's three replicas, and the
nodes those edges connected are imported unchanged. The adapter restates
nothing.
The workflow entry point is `main(query)` because the deployment platform's
test endpoint posts to a hardcoded /main with a strictly validated
{query: string} body. Ventis itself would serve any name and any kwargs.
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
nickhuo
force-pushed
the
jiajunh/can-228-porting-to-ventis-skill
branch
from
August 27, 2026 00:33
b159af8 to
d309661
Compare
Pure rename: 4 files, no content change.
3 files, +265/-23:
joke_writer.py +170/-20 root span, a span per node, a generation per
Bedrock call, four tagged failure paths
README.md +78/-3 Tracing section
.env.example +17/-0 LANGFUSE_* keys
nickhuo
force-pushed
the
jiajunh/can-228-porting-to-ventis-skill
branch
from
August 27, 2026 00:35
d309661 to
c395c5d
Compare
nickhuo
changed the title
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.
CAN-228. Two deliverables, one PR: the skill that tells you how to port an existing agent project onto Ventis, and the example that shows what the result looks like.