Operion

View saved version →

---
name: operion-workspace
description: Use Operion from ChatGPT through the connection's listed MCP tools, with live guidance and member agent delegation.
---

# Operion in ChatGPT

User instructions take precedence over these instructions.

## Choose the member's route

Inspect the connection's live tools before acting. A read-only connection supplies search, query and read. Tools omitted from the list are unavailable; internal CLI, image, agent and question-tool references in owner guidance do not add them. No internal focus, role, attachments or private session context is injected. Ask for missing scope or find it through authorized reads.

Use search to find records, sources and read targets. Use query for committed data; preserve decimal strings and follow cursors. Read only evidence needed for the current decision. Bounded pages and truncated reads cannot establish absence. /workspace paths belong to the remote workspace, not your local filesystem.

## Read the deployed owners

The contracts are together at /workspace/guidance/doctrine.md. The current repository skill index is /workspace/guidance/catalog.md. Read the matching skill from that index before its task. Read /workspace/skills/operating-contract/SKILL.md and /workspace/skills/communication-contract/SKILL.md for every substantive task. Name things as the user names them; keep internal handles out of ordinary prose unless the user requests them.

Before recording or evaluating deal facts, read /workspace/skills/transaction-memory-contract/SKILL.md. Before changing model.ts or values.json, read /workspace/skills/model-authoring-contract/SKILL.md. Before evidence, output or staged-write work, read /workspace/skills/workspace-craft-contract/SKILL.md. Before page work, read /workspace/skills/view-authoring/SKILL.md and /workspace/skills/canvas-pages/SKILL.md. Reuse current guidance while it remains in context. These are the same deployed owner files the internal agents use; apply them to the user's authorized task and the tools actually available here.

## Work directly

Read the target before editing. create_record creates the record at once, with its model.ts, its page and its values.json, and its receipt names the files it was born with that you write: edit those rather than adding them. edit_workspace_files stages patches; staged edits remain visible to every chat using this connection. check_changes checks staged status and validation and reports diffs. commit_changes publishes the explicit selection; discard_changes removes its draft. Query reads committed data; read may show draft content. Never present a refused or uncertain commit as published.

Before a native commit, allocate a UUID and retain it as operationId, then supply it with path and message to commit_changes. If the response is lost or uncertain, call commit_changes with only recover set to that same UUID. Recovery returns the original outcome without reading source or publishing again. A handle generated by the CLI and returned in a reply cannot recover a reply lost before you retained it.

Delegated agents see published work, so publish relevant drafts before delegation. Follow each listed tool’s schema and receipt; registration, extraction and publication are separate outcomes.

## Work through an agent

Use delegate as described by `tool.delegate` in [canonical tool guidance](/workspace/skills/chatgpt-connection/references/tool-guidance.md).

Use understand as described by `tool.understand` in [canonical tool guidance](/workspace/skills/chatgpt-connection/references/tool-guidance.md).

Use answer as described by `tool.answer` in [canonical tool guidance](/workspace/skills/chatgpt-connection/references/tool-guidance.md).

Use stop as described by `tool.stop` in [canonical tool guidance](/workspace/skills/chatgpt-connection/references/tool-guidance.md).

Use read to inspect the named remote file and its returned bounds.

Use search to find authorized records, sources and read targets.

Use quer

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.