Overview

The Zof Studio workspace is the primary authoring surface where developers and automation engineers create, edit, and validate assets under organizational policy. The workspace integrates editor tooling, AI assistance constrained by policy packs, asset navigation, and publishing flows toward Console libraries.

Workspace layout emphasizes project context, file exploration, inline validation feedback, and policy violation indicators, so authors correct issues before submission rather than discovering blocks at publish time.

Effective workspace usage requires understanding how local authoring sessions connect to organization policy, source control integrations, and downstream Console deployment paths.

Who should read this

Automation developers, platform engineers, and QA engineers authoring tests, agents, and integration assets in Studio.

Prerequisites

Studio desktop client installed and authenticated against your organization
Role permitting Studio workspace access and asset publishing where required
Familiarity with organizational policy packs and review procedures

When to use this workflow

Onboarding new team members to Zof terminology and workflows
Authoring internal runbooks aligned with Console labels
Designing CI/CD or webhook integrations against documented behavior

Step-by-step procedure

Launch and authenticate

Open the Zof Studio desktop client and sign in with corporate identity credentials.

Confirm organization context matches your intended tenant before creating assets.

Allow initial policy pack synchronization to complete before authoring.

Open or create a workspace project

Select an existing workspace project or create one aligned to your application or agent initiative.

Clone or link source control repositories if your workflow integrates with Git providers.

Review project README or internal runbook for naming and structure conventions.

Author assets with policy guidance

Use the editor to create tests, agent logic, or supporting scripts.

Monitor inline policy indicators flagging compliance violations or deprecated patterns.

Leverage governed AI assistance within prompt library constraints, never treat output as final without review.

Validate locally before publish

Run local validation commands or Studio built-in checks where available.

Execute smoke tests against staging targets when asset type requires runtime verification.

Resolve policy violations and validation errors documented in the workspace diagnostics panel.

Submit for review and publish

Follow organizational review workflow, pull requests, peer approval, or Studio publish gates.

Publish approved assets to Console libraries or agent registration flows per documented paths.

Verify published assets appear in expected Console destinations with correct versioning metadata.

Maintain workspace hygiene

Update local client when new Studio versions ship security or policy features.

Archive or delete obsolete workspace projects to reduce confusion for collaborators.

Report workspace defects through internal support channels with reproduction steps and client version.

Key concepts

Organization scope: All Zof Console and API operations are isolated to your authenticated tenant.
Governed execution: Agent output and remediation follow policy packs with human approval when configured.

Best practices

Keep workspace projects scoped to single initiatives, avoid monolithic repositories mixing unrelated assets.
Commit early to source control with meaningful messages when Git integration is enabled.
Run policy validation before requesting peer review to reduce review cycle friction.
Document workspace project setup in team runbooks for repeatable onboarding.
Never store production secrets in workspace files, use approved secret management patterns.

Common issues

Policy sync failures on launch: Check network connectivity and authentication token validity. Sign out and in after Admin Center policy pack updates.
Published asset missing in Console: Confirm publish target, permissions, and version tags. Verify asset type maps to expected Console library or agent registration path.
AI assistance produces non-compliant output: Refine prompts within approved libraries and treat output as draft. Escalate recurring violations to administrators for policy pack tuning.