# Chi Fechil

Internal working folder for reviewing the `Chi Fechil` material Boudy Sfeir sent over WhatsApp and turning it into a usable development packet.

## What is in this folder

- `project-summary.md` - concise project framing, format, and current commercial context
- `materials-catalog.md` - source discovery log plus inventory of the packet we recovered
- `tension-economy-evaluation.md` - editorial read on the dramatic engine, escalation, and recommendations
- `core-audience-by-tension-economy.md` - first-principles audience thesis based on the show's actual tension engine
- `buyer-landscape.md` - researched buyer profiles and scoring for the top 10 MENA commissioning targets
- `boudy-meeting-brief.md` - concise talking points for the next creator/director meeting
- `production-one-sheet.md` - buyer-facing packaging draft covering production profile, attachment strategy, and route to market
- `season-engine-sheet.md` - one-page architecture sheet showing the episode-by-episode escalation engine
- `translations/` - English Markdown translations of episode drafts 1 to 4
- `source/` - vendored source packet copied from the original WhatsApp delivery

## Source discovery

- Gmail search on `cultscale@gmail.com` found **no** `Chi Fechil` materials from Boudy Sfeir. The only March 2026 attachment from him was an unrelated `Tnaash` subtitle delivery.
- The usable `Chi Fechil` packet came through the WhatsApp chat `ABoudy` on `2026-03-27`.

## Fast read

- `Chi Fechil` is a 9 x 20 minute satirical mystery built around three Lebanese creatives trying to engineer virality and disappearing in the process.
- The packet currently contains a presentation, the first four episode drafts, and English Markdown translations of those drafts.
- The first four episode drafts are also stored as English Markdown translations in `translations/`.
- The concept is strong and saleable at the level of premise and packaging.
- The tension engine only fully bites once the characters begin causing real emotional or ethical damage, which happens later than ideal in the current run of materials.

## Source asset policy

Binary files in `source/` are vendored upstream materials. Treat them as read-only snapshots and replace them with fresh imports if a newer packet arrives.