# Ridgeback Secondary at Kitchener: deployment

Canonical ID: `98f95844-b04a-4719-84cf-e9429e89affc`

Secondary product deployment at Ridgeback (Clearpath) operational region.

**Trust tier:** Catalog entry · 1 source · not yet field-verified

_Last updated: 2026-06-08_

- **Slug:** ridgeback-secondary-deployment
- **Status:** operational
- **Model:** [Ridgeback Secondary](/models/ridgeback-secondary.md) (id: `766c1bfe-46cb-4d10-ab54-21bde06387c7`)
- **Company:** [Ridgeback (Clearpath)](/companies/ridgeback.md) (id: `738abff7-c4b0-4457-95a1-cd6f136f578f`)
- **Location:** [Kitchener](/locations/kitchener.md) (id: `e8432710-8596-4f52-ba75-25b5cacd9158`)

## Verification log (0, append-only)

_No verifications recorded._

## Sources (1)

1. https://rover.report

## Common questions

### What is the Ridgeback Secondary deployment at Kitchener?

Ridgeback Secondary, built by Ridgeback (Clearpath), is recorded as a deployment at Kitchener on the DEPLOY registry. Ridgeback (Clearpath) operates the deployment directly.

### Who operates Ridgeback Secondary at Kitchener?

Ridgeback (Clearpath), the manufacturer of Ridgeback Secondary, operates this deployment directly. This is a maker-deploys-its-own-product arrangement rather than a customer pilot.

### Have there been incidents at the Ridgeback Secondary deployment at Kitchener?

No active incidents affecting this deployment are recorded on the DEPLOY registry. Absence of recorded incidents is not a guarantee no incident occurred; DEPLOY records only sourced incidents and suppresses retracted ones.


_API: GET /v1/robots/98f95844-b04a-4719-84cf-e9429e89affc · feeds: GET /v1/feeds?deploymentId=98f95844-b04a-4719-84cf-e9429e89affc · canonical URL: /deployments/ridgeback-secondary-deployment_