Architecture Decision Records
For more information on what ADRs are, and why we use them, see Documenting Architecture Decisions and Why write ADRs.
- ADR-0001 Record Architecture Decisions
- ADR-0002 Use C4
- ADR-0003 Use GitLab
- ADR-0004 Use Hugo
- ADR-0005 Use APIs
- ADR-0006 Use an Application Development Platform
- ADR-0007 Isolation of Use Cases
- ADR-0008 Use Obi Cloth for Real-time Cloth Physics
- ADR-0009 Platform for Each Application
- ADR-0010 QuantaCorp SDK
- ADR-0011 Mallzee Api
- ADR-0012 Metail Scanatar Creation
- ADR-0013 Metail VStitcher Headless Service
- ADR-0014 Scanatar Creation
- ADR-0015 Token Service for QuantaCorp API
- ADR-0016 Authentication and Authorization
- ADR-0017 Platform for Each Application revision
- ADR-0018 OS for Magic Mirror App
- ADR-0019 Development Tools Versions
- ADR-0020 Product Recommendations
- ADR-0021 Storage Path Scheme
- ADR-0022 Asset Triangle Count
- ADR-0023 Use Custom Claims
- ADR-0024 Unity Analytics Events to Server Event Bus
- ADR-0025 Use Terraform
- ADR-0026 Use Browzwear parametric avatars for UC3
- ADR-0027 Manual creation of avatar & garment models for UC3
- ADR-0028 Federated Authentication for AWS
- ADR-0029 Proxy Calls to Mallzee API
- ADR-0030 Use GitLab Flow
- ADR-0031 VR Designer preparation steps for Alembic Files from VStitcher to Unity – UC1
- ADR-0032 Magic Mirror App Services
- ADR-0033 GCP Mallzee API Proxy Function Removal
- ADR-0034 Storage Path Scheme Update
- ADR-0035 UC1 Anonymous Authentication
- ADR-0036 Aspect and size of DressMeUp photos
- ADR-0037 Mallzee Image Handling
- ADR-0038 UC3 Recommender service no longer needs analytics user events
- ADR-0039 Measurements and data deletion callbacks
- ADR-0040 UC2 Garment entries and file Storage upload
- ADR-0041 State Tracking for Asynchronous Jobs
- ADR-0042 UC2 GCP Trend Score Update function