An account does not activate every service.

Creating an account, receiving workspace access, or obtaining login credentials does not automatically activate all AI Command functionality, AI PSYOP services, memberships, integrations, or managed workflows.

• Access may depend on the applicable entitlement, plan, implementation scope, and integration status.
• Permissions may vary by user, role, system, workflow, or business responsibility.
• A workspace may exist before a required integration is connected or live execution is available.
• Users are responsible for protecting their credentials and using access only for authorized purposes.

The written scope controls the work.

AI Command and related AI PSYOP implementation or managed services should be delivered according to the applicable written scope, offer, order, proposal, statement of work, or agreement.

• Not every business needs every stage, service, platform layer, or membership.
• New workflows, new integrations, additional systems, expanded responsibilities, or changes in deliverables may require a separate scope.
• Managed upkeep and new implementation work are different activities unless a written agreement says otherwise.
• The staging ecosystem distinguishes DIY access from managed CRM and implementation services.

AI capability does not create unlimited authority.

AI Command is designed around bounded AI roles, approved knowledge, workflow rules, permissions, operator controls, and defined human accountability.

• AI Employees should perform defined tasks within approved systems, permissions, and workflow scope.
• Outputs may require human review depending on the task, risk, business impact, or approval rule.
• Incomplete, conflicting, unusual, or unsupported situations should route to an appropriate human operator.
• Consequential decisions involving legal obligations, safety, financial authority, policy exceptions, or other high-impact matters may remain human-controlled.
• AI-assisted work should not be represented as guaranteed to be error-free, complete, or suitable for every decision without review.

Connected systems remain subject to their own requirements.

Implementations may involve third-party software, APIs, CRM platforms, websites, forms, calendars, advertising platforms, analytics services, or other external systems.

• Availability depends on the actual vendor, account, API, permissions, and supported access method.
• AI Command should not be interpreted as guaranteeing compatibility with every vendor or platform.
• Third-party terms, privacy policies, usage restrictions, pricing, and service availability may apply independently.
• Advertising spend, software subscriptions, API usage, overages, initial buildout, and scope changes are separate unless included in writing.

Every workflow needs a responsible human owner.

The staging ecosystem repeatedly emphasizes that responsibilities should be defined before systems become part of day-to-day operations.

• Provide accurate and authorized information necessary for the agreed work.
• Maintain appropriate rights to data, systems, accounts, content, and credentials supplied for implementation.
• Identify who owns the workflow, approves outputs, handles exceptions, and remains accountable for decisions.
• Review outputs and recommendations where human approval is required.
• Notify AI Command or the relevant service provider when access, systems, personnel, requirements, or business rules materially change.

Use the system only for lawful and authorized business purposes.

Users should not use AI Command or related systems in ways that violate law, exceed granted authority, interfere with system operation, bypass controls, or misuse information or third-party accounts.

• Do not access systems, accounts, records, or data without authorization.
• Do not attempt to bypass permissions, approvals, access controls, or security measures.
• Do not use workflows to misrepresent identity, authority, guarantees, pricing, or business facts.
• Do not use the system to violate another party’s intellectual-property, privacy, contractual, or legal rights.
• Do not intentionally introduce malicious code, abusive automation, or activity designed to disrupt systems or services.

Access may change when the underlying scope changes.

Service access, workflows, permissions, integrations, or managed support may be changed, suspended, or ended when an agreement expires, a qualifying subscription ends, an entitlement changes, a required system becomes unavailable, or continued operation would exceed the approved scope.

The staging site also states that certain benefits may remain included only while a qualifying subscription remains active.