BUSINESS CONTRACT
Outcome, scope and operating limits.
Target outputRequest class, reply draft and quality check.
Tool and source scopeCommunication, CRM and service management.
Operating limitsExternal replies and commitments are limited by customer policy.
AutonomyEffective runtime capability remains constrained by current authority, tenant policy, usable connections and deployment compatibility.
Knowledge and dataContext and source access remain scoped by tenant, environment, principal, classification, ACL and freshness.
DeploymentSupported deployment profiles are published only after profile-specific qualification.
TEAM MEMBERS
Three specialist roles inside one team product.
Each member has its own catalog identity while this team remains the shared business-outcome contract.
PRODUCT DECISION CONTEXT
Readiness is calculated from current constraints.
Package qualificationA published product claim must resolve to qualified package capabilities and versioned evidence.
Commercial rightPlatform plan, product entitlement, measured usage and service remain separate commercial layers.
ConnectionsA licensed team still requires usable and authorized data and tool connections.
PolicyTenant policy, guardrails, approval rules and budget can narrow the effective capability at runtime.
EnvironmentInstallation and operation remain bound to a specific tenant and environment.
ExitExport, uninstall, credential revocation, retention and deletion closure remain explicit lifecycle steps.
