Bidirectional UI is a release contract, not a translation feature
Why SFAS treats direction as runtime truth, requires logical CSS properties and makes regressions in either direction release-blocking.
The problem
A bilingual product is easy to weaken if one direction is treated as the primary interface and the other as a mirrored afterthought. That approach pushes defects into navigation, spacing, technical identifiers and component behavior.
The SFAS contract
Direction is derived from the active locale and expressed through the document direction. Shared shell and component CSS uses logical properties unless a documented semantic reason requires a physical edge.
- RTL and LTR are equal reference modes
- Technical identifiers stay LTR-isolated
- Direction regressions block release
Why this matters
The benefit is not visual symmetry for its own sake. A stable directional contract lets multiple Silver Fox products reuse administration infrastructure without each product inventing its own RTL/LTR rules.