Architecture

OxiDex follows a hexagonal (ports and adapters) architecture that separates concerns into distinct layers for maintainability and extensibility.

Core Documentation

• Multi-Crate Tags - Tag organization across multiple crates
• Parser Migration Guide - Guide for migrating parsers
• Parser Shared Infrastructure - Common parser infrastructure
• OxiDex Tags Shared - Shared tag definitions

Architecture Overview

┌─────────────────────────────────────────────────────┐
│                  Application Layer                   │
│              (CLI, FFI Bindings, MCP)               │
├─────────────────────────────────────────────────────┤
│                   Domain Layer                       │
│         (MetadataMap, TagValue, FileFormat)         │
├─────────────────────────────────────────────────────┤
│               Infrastructure Layer                   │
│     (Format Parsers, I/O, Tag Database)             │
└─────────────────────────────────────────────────────┘

See the Reference Architecture for detailed documentation.