65fc400fcd
The accelerators/ai-enablement precedent uses the literal 'platform' space id — those credentials happen to live in the platform-owned CP accounts. For hatchmate the credentials live in a CP account owned by the hatchmate space, so the ref must be 'hatchmate.space:hatchmate'. Misnamed ref caused the dispatcher's account resolver to fail with 'no active account for AccountRef(name=hatchmate, scope=space:platform)', failing every review task in the W4 vertical slice within seconds of dispatch. After this lands and the next CRS sync (~5 min) refreshes the concepts PVC, the next auto-advance fire on dfc4358c should resolve the account and proceed through the working-repo clone with the per-org hatchmate key.
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.