# BRPS — BUILD, RELEASE & PROMOTION SPEC
version: v1.0
status: ACTIVE
parent: master_architecture_index.md
phase: 02
phase_name: Architecture & Engineering Canon
document_role: build_release_and_promotion_standard_for_phase_02

---

## 1. OBJECTIVE

Define canonical build, release, promotion and rollback rules.

---

## 2. BUILD PRINCIPLE

A build is valid only if:
- inputs are known
- version is known
- contract impact is known
- validation path exists

---

## 3. RELEASE PRINCIPLE

A release is valid only if:
- build passed
- validation passed
- audit path exists
- rollback path exists
- packaging audit exists
- SBOM exists
- production package does not expose sourcemap
- production package does not expose sensitive artifacts

---

## 4. PROMOTION PRINCIPLE

Promotion to higher environment is valid only if:
- sandbox-first rule is respected
- promotion gate passes
- rollback readiness is confirmed
- evidence is registered
- operator code, runtime artifacts and debug artifacts remain separated
- environment exposure policy is respected

---

## 5. ROLLBACK PRINCIPLE

Rollback is mandatory capability, not optional convenience.

---

## 6. ACCEPTANCE CRITERIA

BRPS is valid only if:
- build rule is explicit
- release rule is explicit
- promotion rule is explicit
- rollback rule is explicit
- packaging audit rule is explicit
- SBOM rule is explicit
- production artifact exposure rule is explicit