# Loewe Alivio

**Email:** loewe.alivio@symph.co
**Discord:** _louveh_
**Role:** Dev
**Joined:** 2026-02-10

---

## Communication Style
- Direct and technical — wants to understand architecture, not just output
- Iterative — gives specific, precise feedback on what's wrong and what direction to take
- Doesn't need hand-holding; can handle deep technical discussion
- Provides visual/aesthetic direction clearly ("NOT too perfect", "lo-fi founder cinema")
- Patient with long build processes as long as progress is clear

## Common Requests
- Video generation pipeline work (Brandcast)
- Discriminator/QA architecture design
- Code quality and gap analysis
- Aesthetic direction for marketing video

## Preferences
- Show architecture maps before diving into fixes
- Confirm changes are live before asking for testing
- Keep status updates brief but meaningful
- Prefers understanding the "why" of each architectural decision
- Appreciates clear before/after comparisons

## Domain Knowledge
- Strong understanding of AI generation pipelines
- Can discuss Veo failure modes, discriminator architecture, QA layers at technical level
- Understands generator-discriminator patterns
- Has good aesthetic taste — caught specific Veo artifacts (floating cursor, disappearing phone, face morph) in v1 video

## Key Learnings / Corrections

### 2026-02-24 — Video Generation Quality
- **Issue I had:** Generated v1 video with photorealistic editorial style, dramatic performances, screen UI visible in keyframes
- **What was wrong:** Too polished/perfect. Screen UI + hands = Veo text artifacts. Face reveals = face morph. Prop + orbit = disappearing object.
- **Correct approach:** Lo-fi founder cinema (grainy, muted, quiet moments). Eliminate all screen UI from keyframes. Use absence/negative space (empty chair) instead of dramatic performance. Stillness IS the tension.
- **Aesthetic reference:** "NOT too perfect or realistic. Follow current trending aesthetics" = raw, grainy, 2am energy, cramped real spaces

### 2026-02-24 — Architecture Review Style
- loewe wanted to see current architecture before proposing fixes ("let's take a step back")
- Prefers systematic gap analysis (current vs ideal) before jumping to implementation
- Approves all-at-once implementation once architecture is agreed

## Session History
| Date | Topic | Outcome |
|------|-------|---------|
| 2026-02-24 | Brandcast video gen quality | Full discriminator gap closure — VeoPromptSanitizer, FrameDiscriminator, TemporalCoherenceChecker, L4/L5, Router-Sanitizer bridge. v2 video delivered. |
