tfm_ainventory/.planning/milestones/v1.14.22-REQUIREMENTS.md

Requirements Archive: v1.14.22

Milestone: Config Consolidation & Infrastructure Status: 100% COMPLETE

---

1. Functional Requirements (Archived)

• R-01: Centralized Configuration: All environment settings must live in the config/ directory.
• R-02: Secret Separation: Production secrets must be stored in secrets.yaml and excluded from Git.
• R-03: Multi-Domain Schema: Config must be split into backend, frontend, network, and docker domains.
• R-04: Python Tooling: All deployment and management scripts must be implemented in Python with consistent logging.
• R-05: Dynamic Topology: The system must automatically calculate API endpoints from the server_ip defined in network.yaml.
• R-06: Unified Auth Mgmt: Admin UI must save LDAP settings directly to the YAML configuration.

---

2. Technical Quality Requirements

• Q-01: Type Compliance: No bold/medium font weights in the UI.
• Q-02: Copywriting: Contextual CTA labels for all destructive or safety-critical actions.
• Q-03: Backward Compatibility: Legacy inventory.env support maintained during the transition (deprecated).
• Q-04: Security: Masked secrets in logs and subprocess injection protection.

---

3. Requirement Outcomes

• Validated: YAML configuration significantly improved developer experience and deployment reliability.
• Adjusted: Initially planned to keep inventory.env as primary; adjusted to deprecate it immediately in favor of YAML.
• Dropped: Scale testing with 10k items (Deferred to Phase 8).