33501ca54e
verdict-tx (kind: script) never worked: script nodes are harness-exempt (WF-COMP-6/MN-38) and run in their own empty container, so it could never credentially read /workspace/verdict from the agent's node. Option 3: give the agent node's own composite (planning-sonnet-repo) a cp-service-token/v1 layer, and have the agent PATCH its own item's flow_state (verified|rejected) to the CP directly as its last step, before task_complete. Removes verdict-tx entirely. See agent-runtimes work item 88ecd23e and spec/typed-workflows.md WF-COMP-25 (agent-runtimes commit 8972d266) for the finalize.py precedence fix this depends on (ambiguous pipe-separated output.state must never be auto-PATCHed over the agent's own value). Claude-Session: https://claude.ai/code/session_01U3biMxRhFGkwtf4jVTNjcj
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.