INFORMATIVEDRAFT
Truth Source: Repository schemas and tests are authoritative.
Transaction — Conceptual Overview
Audience: Implementers, Architects, Runtime Authors Governance Rule: DGP-30
1. What Transaction Refers To
Transaction in MPLP refers to the atomicity dimension that concerns how multi-step state changes can be treated as indivisible units. It relates to VSL transactional interfaces and rollback semantics.
Transaction is not a database feature. It is a conceptual boundary for atomic state management.
2. Conceptual Areas Covered by Transaction
| Conceptual Area | Description |
|---|---|
| Atomic Updates | Relates to treating multiple changes as one unit |
| Rollback | Concerns reverting to previous consistent state |
| Commit Semantics | Is involved in finalizing state changes |
| Compensation | Relates to undo strategies for complex operations |
3. What Transaction Does NOT Do
- ❌ Mandate ACID properties
- ❌ Define distributed transaction protocols
- ❌ Prescribe two-phase commit
- ❌ Require specific isolation levels
4. Where Normative Semantics Are Defined
| Normative Source | What It Covers |
|---|---|
| L3 Execution & Orchestration | Rollback mechanisms, compensation |
| L1-L4 Architecture Deep Dive | Atomic state transitions, VSL transactions |
5. Conceptual Relationships
6. Reading Path
- L3 Execution & Orchestration — Rollback, compensation
- L1-L4 Architecture Deep Dive — Atomic transactions
Governance Rule: DGP-30 See Also: Transaction Anchor (Normative)