ADR Index
Index of accepted architecture decision records for Ferrocat.
Architecture decision records document the choices that shape Ferrocat's public behavior. Use them when you need the reasoning behind catalog modes, runtime keys, PO compatibility boundaries, or durable API semantics.
Current records:
-
0003: Use Byte-Oriented Scanning and Separate Structure From Semantics
-
0004: Model
msgstrby Semantics Instead of Always UsingVec<String> -
0005: Treat ICU as the Canonical Model and Gettext as a Compatibility Bridge
-
0009: Use Versioned, Truncated SHA-256 Keys for Runtime Catalog Compilation
-
0011: Add an NDJSON Storage Format for High-Level Catalog Workflows
-
0014: Keep Ferrocat Host-Neutral and Let Palamedes Own JS/TS Application Integration
-
0015: Add ICU Authoring Diagnostics Without Owning Runtime Formatting
-
0016: Add Progressive Semantic Message Metadata Around
msgid -
0017: Add Catalog Audit Reports Without Reintroducing Fuzzy Matching
-
0020: Keep the 1.x Catalog Layer in
ferrocat-poBehind Feature Profiles -
0027: Preserve Translator Comments and Flags as Opaque Round-Trip State