runway.json
The delivery manifest fr init writes and fr deploy / fr promote read back.
runway.json is the delivery manifest at the root of a Runway project. fr init writes it, and
fr deploy / fr promote read it to know what to build, where to stage it, and which gate to
run.
{
"name": "support-agent",
"template": "rag-agent",
"gate": "eval-suite",
"artifact": ".fabricharness/build/databricks-app",
"artifactVolume": "/Volumes/main/runway/artifacts"
}Fields
| Field | Required | Description |
|---|---|---|
name | yes | The app name. Must match ^[a-z][a-z0-9-]*$. Used as the catalog key and in the UC Volume artifact path. |
template | yes | The template the repo was scaffolded from (e.g. rag-agent). Recorded in the catalog. |
gate | yes | The Fabric Experiments gate / evaluator name requested by fr deploy and required before promotion. |
artifact | yes | The bundle root produced by the build step. Defaults to Harness's output, .fabricharness/build/databricks-app. |
artifactVolume | no | The customer-owned Unity Catalog Volume root for immutable release artifacts. The staged path is <artifactVolume>/<name>/<sha256>. |
How the fields are used
artifactpointsfr deployat the directory to digest and upload.artifactVolumedetermines where the content-addressed artifact is staged. It must be a/Volumes/<catalog>/<schema>/<volume>/…path your identity can write to.gateis the evaluatorgate_evaluaterequests and the gate a promotion requires.namekeys the app in the catalog and slugs into the artifact path.
The file is validated by hand (the CLI is zero-dependency): a missing or empty name,
template, gate, or artifact is a usage error, and artifactVolume, if present, must be a
string.
Fabric Databricks delivery skill
Install the combined Harness authoring and Runway delivery Agent Skill for Codex, Claude Code, Cursor, GitHub Copilot, and other coding agents.
Operate Runway
Use the Runway console to manage governed Databricks delivery, environment metadata, release analytics, logs, evidence, integrations, and recovery diagnostics.