Skip to main content

Document metadata

Status
Maintained
Approval
Approved
Version
1.0
Classification
PUBLIC
Owner
Lightning IT Documentation Maintainers
Approver
Lightning IT Product Owners
Audience
release reviewers, platform owners
Last reviewed
Next review
(Semiannual)

Releases and lifecycle

Version identities answer different questions. Keep them separate so a source change, released artifact, supported product combination, deployed instance, and documentation revision do not become one ambiguous “version.”

Version layers

LayerIdentifiesEvidence owner
Source revisionAn immutable repository statePublic component repository
Component releaseA published artifact and its release notes, provenance, tests, and compatibilityComponent release record
Product releaseA verified set of product-owned components and public support contract, when publishedProduct owner
Deployment versionThe exact approved component and configuration identities in one environmentAuthorized environment record
Documentation versionThe reviewed revision and status of a page or site releaseDocumentation repository

Code presence does not prove release, deployment, support, or runtime implementation. A component release does not prove a product combination, and this page's document version does not version product software.

Select and promote a release

  1. Resolve the public source and immutable release identity.
  2. Review release notes, dependencies, compatibility, security changes, deprecations, licenses, and release evidence.
  3. Verify provenance and artifact identity when available.
  4. Test the exact artifact and intended version combination.
  5. Update architecture, security, operations, backup, recovery, observation, and retirement documentation where affected.
  6. Approve and promote through the environment's controlled stages.
  7. Independently verify the deployed outcome and retain classified evidence.

Public component release pages

The lists are discovery points, not a statement that the latest release is approved for a deployment.

Documentation lifecycle

Pages are maintained, deprecated, or retired based on verified public behavior. Review after a relevant release, architecture or security change, incident, standard update, or at the metadata cadence. Preserve redirects only for stable previously published paths, avoid redirect chains, and never retain obsolete claims merely for link continuity.

See the ModuLix lifecycle for automation-content decisions.