Install Arch Studio.

Install and start Architecture Studio in this ChatGPT Work session. Arch Studio supplies architecture workflows through a hosted MCP; my existing assistant uses those workflows, not a separate chatbot. Use this endpoint: https://mcp.architecturestudio.ai/

First identify this host and inspect its available connector-management capabilities. Reuse an existing connection to this exact endpoint; verify its tools before starting another authorization. Add a connection only if none exists. Do not add duplicates or install the public local plugin as a substitute. Keep any existing local plugin; removing or disabling it requires separate approval after the hosted path is verified.

Identify whether ChatGPT Work is running in a desktop app or on the web. Desktop MCP management and shared Codex configuration may be used only when actually available on this machine. ChatGPT web does not read local Codex configuration: use the apps or plugins available to this workspace and their supported setup flow. Do not assume terminal or local file access. If this host cannot add a connection, explain the missing capability and give the shortest supported manual fallback.

Use normal OAuth discovery and browser sign-in; leave advanced client credentials empty. Let me enter credentials and approve access myself; never request secrets or bearer tokens in chat. Use a localhost or loopback callback only when this client owns a live listener. Keep that login process alive through its callback and use a browser on the same machine that can reach it. Never send a remote embedded browser to another machine's localhost. If no reachable listener exists, use the host's supported remote authorization flow or explain the required local-browser handoff. Do not treat an unreachable loopback callback as success. If I deny or cancel authorization, stop setup without retrying or making further configuration changes; report any connection entry already added. If the account or workspace differs from the one I intended, stop and let me choose the correct account through the provider. If authorization expires, explain that the connection is unverified and offer a fresh flow; do not reuse the expired callback or start a retry loop.

For an existing connection or after authorization, refresh/discover tools if supported and retry in this session. Request a fresh task only if tools still cannot load. Do not assume connector toggles are isolated per conversation. Verify by calling as_status and recording its sourceDigest. Discover the actual catalog: retrieve as_norma when available and all its required resources at that same digest, using returned URIs and advertised page bounds until complete. Stop on a digest mismatch or missing required resource. If this release lacks Norma, report that and use the available as_studio entry point; do not claim the coordinator is installed. Report only the release actually retrieved; instruction delivery is not task completion. Website sign-in or previous connection activity alone does not verify current tool access.

Give one short plain-text welcome, without ASCII art, legal boilerplate or repeated questions. When Norma is available, say “Say ‘Norma, help me…’ or ask naturally for architecture and project work.” Do not promise a universal @norma, /norma or $norma command. Continue any task or studio choice I already supplied; otherwise offer use without setup, open existing, create a studio, or an example in one concise gate. Use as_studio for the selected studio administration action. Request folder access only when needed; if unavailable, explain what cannot proceed and offer standalone work where feasible. Opening an existing studio does not authorize creating one. Preview studio/project creation and obtain approval before writing; never initialize implicitly. Standalone sample requests do not require project selection or library adoption.

If I ask to make Arch Studio the default, follow Norma's preference workflow: select an actual host-supported project or user instruction mechanism, show the exact removable-block diff and obtain approval before editing. If persistence is unavailable, give session guidance. If offering a new default preference, ask exactly “Would you like this assistant to use Architecture Studio by default for architecture and project work?” once, without interrupting an already supplied task. No or cancel writes nothing; do not repeat an answered choice.

After useful work, give a concise completion report naming source data, Arch Studio instructions or helpers used, what the host executed, output locations, checks performed, unresolved items and any canonical writes with readback. Distinguish full, partial, blocked and instructions-only outcomes. A standalone export is not a canonical save. End with one relevant “Use Norma…” next action when that coordinator is available.

Norma, prepare three standalone sample furniture and lighting specification sheets using sourced products and the available Architecture Studio workflows. Do not add them to a project or library.