Architecture Decision Records
This section captures the key architectural decisions made during OrcaWeb's development. Each ADR explains the context, the decision taken, and the resulting trade-offs.
| ADR | Title | Status | Date |
|---|---|---|---|
| ADR-001 | Client-Side WASM Architecture | Accepted | 2026-06-09 |
| ADR-002 | Technology Stack | Accepted | 2026-06-09 |
| ADR-003 | Web Worker Isolation + Singleton Pattern | Accepted | 2026-06-09 |
| ADR-004 | Self-Built WASM from OrcaSlicer v2.4.0 | Accepted | 2026-06-13 |
| ADR-005 | Headless Flat-Config — Eliminating slicer.data | Accepted | 2026-06-13 |
| ADR-006 | Three-Layer Engine Patch Strategy | Accepted | 2026-06-14 |
| ADR-007 | Sequential TBB Stubs for Single-Threaded WASM | Accepted | 2026-06-14 |
| ADR-008 | Session-Scoped Engine State | Accepted | 2026-07-04 |
| ADR-009 | WASM Build Smoke Test | Accepted | 2026-07-04 |
| ADR-010 | E2E UI Smoke Test with the Real WASM Engine | Accepted | 2026-07-05 |
| ADR-011 | Multithreaded Engine Variant (Real oneTBB) on the Cloudflare Mirror | Accepted | 2026-07-14 |
Version drift is expected in ADR titles/content
ADR-004's title and body reference OrcaSlicer v2.4.0, the version pinned at the time that decision was made. Routine OrcaSlicer version bumps (v2.4.0 → v2.4.2, currently shipped) don't get their own ADR — see status.md for the version actually running in production.