Start with self-service evidence
operatorReview onboarding, connector state, release readiness blockers, and API docs before escalating.
Операторский hub для документации, support handoff и SaaS readiness.
Review onboarding, connector state, release readiness blockers, and API docs before escalating.
Attach summary-only evidence refs, fingerprints, and release-readiness handoff files. Do not paste secrets, raw runtime payloads, connector credentials, or device transport details.
AI/chat assistance, destructive commands, guarded mutations, and live-farm smoke remain blocked unless approvals and runtime boundaries are satisfied.
Portable connector setup and paid onboarding checklist are available; real hosted/live-farm refs are still required for sales launch evidence.
The release/sales evidence chain is documented and visible, but remains blocked without real hosted env, connector, paid workspace, smoke, and support refs.
API key management exists; AI provider secrets and broader API preference policy are intentionally not exposed yet.
Future assistant workflows must stay read-only by default, avoid secret leakage, log audit events, and never bypass runtime approvals.
Provider keys must be stored server-side, redacted in UI, and excluded from support packets.
Chat actions need durable audit events and must respect tenant, locked-package, and command-safety permissions.
Assistant workflows can explain, draft, or lint; they cannot dispatch live-farm actions outside guarded routes.