3a550837aa
Attempted to wire verdict-tx to clone the agent's branch and read scratchpad/verdict (the new cross-node artifact convention, agent-repo/v1 init.sh) instead of the ephemeral /workspace/verdict. Reverted: script tasks (dispatcher/task_manager.py::_run_script_task) have no credentialed way to clone a private repo — the per-task SSH key is provisioned through the full ESO/account harness resolution pipeline, which script tasks deliberately bypass entirely. Left the template on its current (still-broken-for-cross-container-reasons) /workspace/verdict contract with a note, pending a scoped follow-up on how script nodes get read access to the branch (new secrets plumbing, vs. folding the state transition into the agent node's own already- credentialed CP access).
agent-runtime-framework
Framework reference config repo for the agent-runtimes platform.
This repo is attached at CP scope with tags [harnesses, templates, workflows, model-registry, models]
and provides the default content that all installations inherit.
Contents
harnesses/— capabilities, contexts, compositestask-templates/— dispatch-task template YAMLsworkflows/— workflow DAG definitionsmodel-registry/— model scoring YAMLsmodels/— model endpoint YAMLs
Usage
Registered as a CRS attachment at CP scope (priority 100). Customer installations attach their own repos at lower priority to override or extend.