4b4d02926d
Cross-node artifact passing within a workflow manifest — nodes each run in their own ephemeral container/pod with no shared filesystem, so an agent node writing e.g. a verdict to /workspace/verdict is invisible to a downstream kind: script node in the same manifest (found live 2026-09-06, bug-verify-sonnet's verdict-tx). The git task branch is the only channel every node in a manifest actually shares: write to scratchpad/, commit (picked up by finalize.sh's existing git add -A), next node clones the same branch and reads it back. scratchpad/ is scratch, never deliverable content, and must never survive a merge into main — a CI gate in the target repo (agent-runtimes .gitea/workflows/build-images.yaml, no-scratchpad-in-main) is the hard backstop.
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.