# SCREEN Flagship at Kyoto: deployment

Canonical ID: `63b8fe28-8754-4f75-b516-a173c28329f5`

Aggregate deployment at SCREEN Holdings headquarters.

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

_Last updated: 2026-06-08_

- **Slug:** screen-holdings-hq-deployment
- **Status:** operational
- **Model:** [SCREEN Flagship](/models/screen-holdings-flagship.md) (id: `cb96fd5e-4fad-4d13-8b38-10736165fb1b`)
- **Company:** [SCREEN Holdings](/companies/screen-holdings.md) (id: `4245a19f-c9d5-4ad4-85e2-020c5769a12f`)
- **Location:** [Kyoto](/locations/kyoto.md) (id: `e87be9b2-3735-4bb7-90e9-cc466ee9089a`)

## Verification log (0, append-only)

_No verifications recorded._

## Sources (1)

1. https://www.screen.co.jp/

## Common questions

### What is the SCREEN Flagship deployment at Kyoto?

SCREEN Flagship, built by SCREEN Holdings, is recorded as a deployment at Kyoto on the DEPLOY registry. SCREEN Holdings operates the deployment directly.

### Who operates SCREEN Flagship at Kyoto?

SCREEN Holdings, the manufacturer of SCREEN Flagship, operates this deployment directly. This is a maker-deploys-its-own-product arrangement rather than a customer pilot.

### Have there been incidents at the SCREEN Flagship deployment at Kyoto?

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/63b8fe28-8754-4f75-b516-a173c28329f5 · feeds: GET /v1/feeds?deploymentId=63b8fe28-8754-4f75-b516-a173c28329f5 · canonical URL: /deployments/screen-holdings-hq-deployment_