# pSemi Secondary at San Diego: deployment

Canonical ID: `18e906da-922d-4279-aaae-679caddfd754`

Secondary product deployment at pSemi operational region.

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

_Last updated: 2026-06-08_

- **Slug:** psemi-secondary-deployment
- **Status:** operational
- **Model:** [pSemi Secondary](/models/psemi-secondary.md) (id: `68d8e64d-2247-4469-8b2b-8f4722949b3c`)
- **Company:** [pSemi](/companies/psemi.md) (id: `14381c17-fafe-41f5-bb0b-37f548b5a278`)
- **Location:** [San Diego](/locations/san-diego.md) (id: `b74ad569-0046-4978-aed4-dc4dabef040d`)

## Verification log (0, append-only)

_No verifications recorded._

## Sources (1)

1. https://rover.report

## Common questions

### What is the pSemi Secondary deployment at San Diego?

pSemi Secondary, built by pSemi, is recorded as a deployment at San Diego on the DEPLOY registry. pSemi operates the deployment directly.

### Who operates pSemi Secondary at San Diego?

pSemi, the manufacturer of pSemi 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 pSemi Secondary deployment at San Diego?

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/18e906da-922d-4279-aaae-679caddfd754 · feeds: GET /v1/feeds?deploymentId=18e906da-922d-4279-aaae-679caddfd754 · canonical URL: /deployments/psemi-secondary-deployment_