Product Persistence Boundary¶
Status¶
Architecture Boundary Specification
Purpose¶
Defines strict separation between Product Domain and infrastructure persistence.
Core Rule¶
Product Domain MUST NOT know persistence implementation.
Allowed Direction¶
Product Domain → defines contract
Infrastructure → implements storage
Forbidden Leakage¶
Product Domain MUST NEVER depend on:
- SQL
- tables
- indexes
- ORM
- WordPress
- cache systems
- HTTP layer
Invariants Reference¶
Persistence MUST respect:
- INV-001 identity uniqueness
- INV-002 identifier as evidence
- INV-003 observation immutability
- INV-004 variant ownership
Persistence Rule¶
Storage is an implementation detail.
The Product Domain defines WHAT is stored, not HOW.
Decision¶
Persistence is fully outside the domain boundary.