Glossary¶

Terminology Standard¶

The documentation uses these canonical terms:

Local runtime mode: execution via docker-compose.yml
Deployment runtime mode: execution via docker-compose-deploy.yml
Release candidate: governed candidate state prepared for release decisioning
Readiness action: operationally actionable item derived from impact/release analysis

Baseline: A governed snapshot of release-relevant state, used for comparison and decision-making.
Release Pack: A packaged release candidate with trace/evidence context for governance review.
Impact Assessment: Evaluation of change effects on dependent artifacts and readiness outcomes.
Readiness Item: A managed operational work item used to execute a readiness action.
Verification Plan: Structured definition of verification scope and activities.
Verification Case: Executable verification unit aligned to requirements and plans.
Execution Result: Outcome record from verification case execution.
Defect: Non-conformance discovered during verification or operational evaluation.
Assurance Evidence: Evidence artifact supporting safety/assurance confidence.
Trace Link: Explicit relationship between artifacts across modules (for example requirement-to-case).

Local runtime mode: Runtime via docker-compose.yml, optimized for developer iteration.
Deployment runtime mode: Runtime via docker-compose-deploy.yml, closer to production topology.
Broker: Redis channel used by Celery for task dispatch.
Result Backend: Redis channel used to track task outcomes.

Phase: Delivery stage in project governance context.
Scope Allocation: Assignment of scope responsibility across teams/components.
Milestone Dependency: Explicit readiness dependency between milestone items.