arch-platform

Arch Platform Operations

Use Arch as the Agent Platform control plane. Preserve the user's requested scope and obtain authorization before material external mutations.

Source of Truth

1. Read arch://guidance/v1/manifest and the relevant feature or tool detail.
2. Require schemaVersion to equal "1" before using catalog dependencies, confidence, or planning prompts. If the manifest is absent or incompatible, stop catalog-driven planning and use only legacy tool discovery and existing project-builder operations; do not infer dependencies.
3. Treat schema-derived operations as executable only when support is implemented or verified.
4. Treat authoritative-live readiness as project-specific; inspect it through existing project-builder resources before planning project mutations.
5. Documentation-only or unsupported entries do not authorize an operation.

Operating Rules

• Resolve every requires dependency before mutation.
• Use opaque auth-profile, integration, and MCP-server references; never place raw secrets in ordinary tool arguments.
• Respect read, write, idempotent_write, grant_gated_write, and destructive_write safety. Treat plain write as non-idempotent unless the live operation proves otherwise.
• Before grant-gated or destructive work, show the exact target and obtain the required confirmation/grant.
• If a mutation has an unknown outcome, verify it; never retry blindly.
• After acting, supply the operation's verificationRequiredContext, call its validatesWith tool/action, and compare the result with verificationExpectedEvidence. If the guidance says the validation read cannot prove the original outcome, report that limitation and rely only on the non-replayed original result.
• Do not claim support for platform features absent from the public Arch operation catalog.

Whole-project sequence for any MCP client

Read debug_docs topic mcp/project-build-playbook for the complete client-neutral path; the connected Studio topic is guides/arch-mcp-project-build. In order: connect and confirm workspace; create/read the project; configure model and secure AuthProfiles; create/test integrations and MCP servers; author tables, tools and workflows; create reusable prompts, feedback templates and external-agent entries; create/read/guardedly edit agents and pin prompt versions; configure optional policy, alerts and channels; publish immutable agent versions; create/read the typed deployment; run evals and a real channel session. Use the catalog's validatesWith after every mutation. platform_versions:create and promote are unsupported legacy actions; use publish and deployment promotion. platform_arch_sop is an alternative guided creation path, and platform_arch_auto_loop is for later governed repair. Provider-specific channel provisioning is outside the current direct MCP surface.