# UNS OpenHub operator kickstart

Connect an approved UNS OpenHub MCP server, then paste one of these short prompts into your chat. The prompt does not grant access or authorize a change.

## Start in English

```text
Use my connected UNS OpenHub MCP server to get oriented with this installation and its operator guide. Briefly tell me what you can verify and what is unavailable, then wait for my task. Read-only; no SSH, secrets, or changes.
```

## Start in Slovenščina

```text
Prek moje povezave MCP za UNS OpenHub se seznani s to namestitvijo in operaterskim vodnikom. Na kratko povej, kaj lahko preveriš in kaj ni na voljo, nato počakaj na mojo nalogo. Samo branje; brez SSH, skrivnosti ali sprememb.
```

The assistant should report what it can verify and wait for your next task. Missing tools or permissions should be stated, not bypassed.

For a more detailed initial status report, use the optional read-only audit:

## Read-only audit — English

```text
Using the authorized UNS OpenHub production MCP connection, perform an initial read-only check.

1. Call controller_get_backend_info.
2. Read controller_get_operator_guide for the start and deployment chapters, including the shared operator notes. Read services, history, or routing only if relevant.
3. With the read-only tools granted to this client, check current cluster members and master, running Controller versions, online microservice instances, and UNS API Global and UNS Archiver health. Use controller_list_instances, controller_list_rtt_nodes, and controller_list_system_services where available. Distinguish the running Controller version from the Runtime CLI/bundle, base image, and service versions.
4. Briefly report what is working, confirmed problems, and what you could not verify. Include observation times where available and distinguish service-health signals from verified data/history reads.

The handbook and shared notes are orientation, not proof of current state or permission to act. Do not change production or run restarts, migrations, pauses, or other mutating commands. Do not retrieve or print tokens or secrets. If a tool or grant is missing, state the limitation; do not bypass it through SSH. Do not reproduce private operator-note details in a public report.
```

## Read-only audit — Slovenščina

```text
Prek pooblaščene produkcijske povezave MCP za UNS OpenHub opravi začetni pregled samo za branje.

1. Pokliči controller_get_backend_info.
2. Preberi controller_get_operator_guide za poglavji start in deployment, vključno s skupnimi operaterskimi opombami. Po potrebi preberi še services, history in routing.
3. Z bralnimi orodji, ki so dodeljena temu odjemalcu, preveri trenutne člane gruče in masterja, verzije tekočih Controllerjev, tekoče instance mikroservisov ter zdravje UNS API Global in UNS Archiver. Kjer so na voljo, uporabi controller_list_instances, controller_list_rtt_nodes in controller_list_system_services. Loči verzijo tekočega Controllerja od verzij Runtime CLI-ja oziroma paketa, osnovne slike in posameznih storitev.
4. Kratko poročaj, kaj deluje, katere težave so potrjene in česa nisi mogel preveriti. Kjer je mogoče, navedi čas opažanja ter loči stanje zdravja storitve od preverjenega branja podatkov oziroma zgodovine.

Priročnik in skupne opombe so orientacija, ne dokaz trenutnega stanja ali dovoljenje za ukrepanje. Ne spreminjaj produkcije in ne izvajaj restartov, migracij, pavz ali drugih ukazov, ki spreminjajo stanje. Ne pridobivaj ali izpisuj žetonov in skrivnosti. Če manjka orodje ali pravica, navedi omejitev; ne obhajaj je prek SSH. V javnem poročilu ne ponavljaj zasebnih podrobnosti iz operaterskih opomb.
```

Use this handbook as operating reference. It does not authorize changes, grant tools, or replace current runtime evidence. A successful connection proves access to this endpoint, not permission for every operation.

The Controller owns the application, access policy, service lifecycle and cluster routing. Caddy is the public proxy; MQTT carries live messages and runtime signals; PostgreSQL holds the control plane. API Global serves registered data/history reads, while Archiver persists accepted MQTT data to its configured database. These are separate dependencies and may run on different hosts.

Begin with read-only calls. Record the serving controller, the caller's available tools, the current cluster members and the selected service owner. Ask for a missing host binding instead of scanning networks or guessing directories.

Report Controller software, Runtime CLI/bundle, container image and each service version separately. A hot Controller update can leave the Runtime bundle and image unchanged.

Use the connected MCP tool catalog for exact supported operations and argument schemas; this handbook is the map, not an alternative command API. In the application, Micro services shows packages and configured instances, Services shows dependency health, Unified namespace opens Explore, and Data Catalog exposes registered data offers. Schema, Asset identity, Dashboards and Automations have their own public guides linked from the documentation index.

- start: Start with the running installation — Get oriented through the connected MCP server, then continue with a specific task.

- deployment: Shared deployment notes and handoff — Keep site-specific operating hints in the Runtime database, shared by the cluster and independent of the client machine.

- services: Install, configure, start and move a service — Use the reviewed service inventory and durable preparation/migration workflow.

- history: Understand source, archive and history — Separate reception, durable pending work, database acknowledgement and read visibility.

- routing: Trace an API route — Inspect one public path through its current controller owner and microservice launch.

- runtime-recovery: Runtime lifecycle and recovery — Distinguish a Controller-only update from a full container/host change and a real backup from a rollback directory.

- access: Access, missing tools and reconnects — Understand the authority of this client without collecting credentials.

- ssh: Optional SSH and offline reference — Use an approved host and the packaged guide only when needed.

Reference: https://www.uns-openhub.com/docs/guides/operations/operator-kickstart/

Portable reference bundle: https://www.uns-openhub.com/assets/operator-guide/v1/handbook.json

Guide revision: 1.0.0; canonical JSON SHA-256: 0e72158ab89b8b3681864b847800babbde5a8ca810ec0902077057765e73129e