# Aylwing Olivas

## Role

Repeated Fidelity collaborator visible across multiple historical Slack channels.

---

## Known Context

- Appears in technical discussions about XFlow, SwiftUI limitations, navigation architecture, and dependency risk
- Surfaces cross-team constraints such as security or token access issues affecting pipeline work
- Frequently adds architectural framing rather than only status updates
- Often reframes implementation problems at the architecture/system-design level rather than the ticket level
- Repeatedly advised on state machines, navigation architecture, off-screen rendering, and long-term maintainability tradeoffs
- Common escalation point when the team needs a technical sounding board or higher-level design critique

---

## Guidance

- Treat Aylwing as a useful source for higher-level technical framing and dependency risk context
- Treat Aylwing as a strong reviewer for architecture direction, refactor scope, and risk framing
- If future context clarifies the formal team or title, update this file directly