Generation model

AIO is one lasting product brand with independently governed generations. A generation name identifies a bounded product scope; it is not only a software version label.

AIO 2.0

AIO 2.0 is the next strategic generation and is currently in definition and development. Its broader automation-and-operations direction is not an approved feature list, release commitment, architecture contract, or commercial promise.

Until separately decided and approved, do not claim:

• a specific orchestration technology or surrounding component;
• supported execution targets or content sources;
• role, credential, secret, tenant, API, or integration behavior;
• a hosting, availability, licensing, pricing, support, or release model; or
• migration or compatibility with AIO Satellite Edition.

AIO Satellite Edition

AIO Satellite Edition names the existing, separately scoped legacy and maintenance generation. Its concrete capabilities, supported environment, maintenance obligations, tests, evidence, and acceptance remain governed by the applicable contract.

Public product-family documentation does not publish customer-specific deployments or convert existing commitments into general product promises. Renaming the generation does not change a contract.

Change rule

Every generation must independently define and approve:

1. target users and use cases;
2. supported systems and integrations;
3. architecture and dependencies;
4. delivery packages;
5. roles, credentials, and security;
6. tests and acceptance;
7. documentation and evidence;
8. support and lifecycle;
9. pricing and licensing; and
10. migration and compatibility.

An open or draft decision remains a limitation. It must not be filled by assumption in public documentation.