Openship Operator

Treat Openship as an API-backed control plane. Use the CLI as the primary local operator interface, openship api for authenticated REST coverage, MCP for live capability/schema discovery, and the UI only for flows that are intentionally out of band.

Do not act from memory alone. Discover the installed CLI and connected instance before selecting commands, schemas, request bodies, or safety assumptions.

Non-negotiable security invariant

No plaintext user secret may enter model context, a displayed command, a persisted operation record, or an unverified output sink.

Prevent emission first. Redaction after a value has reached an Openship/Docker/CI log, API response, tool result, artifact, or Agent transcript does not undo the exposure. Never use a real credential to test output safety.

Operating contract

Follow this loop for every task: