CI Hosting Environment

1. There is a dedicated environment for the Community Implementation (Action).
2. The environment will enable development of current and new capabilities.
3. Governance / Policy in place for the use of the CI Dev Environment (Action).

CI Contains all Core Services

1. All the Core Services are refactored (as appropriate) to adhere to ADR008, with clear SPI and Mappers & Drivers layers.

Separate Release cadence for CI

1. The Community Implementation will have a separate release cadence (Venus Releases). The 4 forum CSP specific implementations will continue with Mercury Releases.

Automated Standardized Testing

1. There must be Automated Standardized Testing for each service or capability on Community Implementation that demonstrates the full scope of its functionality.
2. Standard behaviours defined.

Semantic Versioning

1. Widely-adopted version scheme that encodes a version by a three-part version number (Major.Minor.Patch)
2. Needs to be in place for the Community Implementation.
3. Align on what version number change would constitute a Venus Release (e.g. Minor update = Venus Release)

Capability / Service Definition of Done

1. There must be a Definition of Done for each service or capability on Community Implementation.
2. Including: Conformance to ADR008, Has Automated Standardized Testing, Standard behaviours defined, Vulnerability rating, Maintainers assigned, Dependencies documented, etc.