## 🎯 Executive Summary **Overall health:** Not assessed. **Traffic light:** 🟡 **This week's headline:** Multiple critical projects (Boukili migration, ONFR live‑feed, OTT launch, and WordPress hosting) face blockers and pending decisions that affect delivery schedules and vendor compliance. --- # Wins 🏆 - Boukili v3 finalized; testing schedule launched. - “Set‑focus” trigger in Storyline completed (on standby). - ONFR live‑feed testing to use Haywire feed; second Chorus URL deferred. - Job‑supervision solution approved; phased rollout begins with ONFR. - OTT search‑result ranking changes implemented; device testing underway. - Decision to retain WordPress on current site and keep WP Engine as host. - ZIP‑to‑IdĂ©llo publishing workflow defined (ticket → ZIP → HĂ©lĂšne). - CTO approved exploratory discussion with Lunii. - Code freeze planned after fixing identified issues; phase‑2 isolated. --- # Risks ⚠ - **Storyline “set‑focus”** compatibility with JAWS unknown → possible product delay. - **CRTC report** lacks clarity on retroactivity, content, and publication location; deadline 5 Oct pending. - **Variable episode lengths** may cause incorrect JWP recording stops → manual fixes needed. - **Subtitles** not displaying for test videos (missing collection association). - **JWP ingest point & billing** unclear for secondary feed; risk of unexpected fees. - **No staging server** for supervision‑solution testing → production issues possible. - **Bou​kili production DB & Contentful API** access unresolved, blocking full integration. - **Podcast automation** still depends on Jira API connection. - **Geo‑blocking** for TFO/IdĂ©llo cannot be removed without release → legal compliance risk. - **Mogador synchronization** complexity; source‑of‑truth undefined, possible project removal. - **US‑based vendor compliance** (JWP, WP Engine, Algolia) under policy review. - **OTT delivery** at risk of missing live‑event deadline; may require weekend release. - **QA capacity** limited to one resource across four sites → testing delays. - **Firebase‑to‑AWS migration** (Boukili) blocked by data‑migration reliability and Salesforce regressions; production release cancelled. --- # Team đŸ‘„ ## Team health **Overall morale:** Not assessed. ### Coaching / Recognition - No explicit coaching or recognition items recorded. --- # Projects 📁 | Project | Status | Next Milestone | Blocker | | --- | --- | --- | --- | | Boukili v3 | Testing started | Begin version 3 testing (this week) | Access to production DB & Contentful API; migration data‑validation issues | | Storyline “set‑focus” | Completed, on standby | Verify JAWS compatibility | Compatibility unknown | | ONFR live‑feed | Haywire feed selected for tests | End‑to‑end broadcast test (10 h start) | JWP ingest‑point behavior & billing clarification | | Job supervision solution | Approved, phased rollout | Deploy cron checks on ONFR | No staging server for testing | | OTT search‑result ranking | Changes applied | Complete multi‑device testing (incl. Apple TV zoom) | OTT testing timeline tight; risk to live event | | WordPress site | Hosting decision retained | Ongoing maintenance | None reported | | ZIP‑to‑IdĂ©llo workflow | Defined | Start processing tickets after 12 Oct | None reported | | Lunii collaboration | Approved for exploratory talk | Present to CEO | Decision pending CEO review | | Mogador sync | Discussion scheduled 16 Sept | Resolve synchronization approach | Complexity & lack of source‑of‑truth | --- # Vendors đŸ€ - **JWP**: Billing model for secondary feed unclear; ingest‑point behavior under review. - **WP Engine**: Hosting retained; no immediate issues. - **Algolia**: Regression review pending (Trings invoice unblocked). - **US‑based vendors** (JWP, WP Engine, Algolia) under compliance review per policy. --- # Decisions Made - Keep Storyline “set‑focus” on standby until screen‑reader compatibility confirmed. - Use Haywire feed for ONFR testing; defer second Chorus URL. - Deploy supervision checks first on ONFR, then IdĂ©llo, then TFO. - Maintain JWP 24/7 feed unchanged; manage secondary test feed manually. - Preserve Boukili on a dedicated VM; postpone API integration. - Retain WordPress on current site with WP Engine hosting. - Implement ZIP‑to‑IdĂ©llo workflow with ticket‑based hand‑off to HĂ©lĂšne (start 12 Oct). - Approve exploratory Lunii discussion with CEO. - Code freeze after fixing identified issues; isolate phase‑2 work. --- # Decisions Needed - Clarify CRTC report requirements (retroactivity, content, location) with Pierre‑Olivier. - Confirm JWP ingest‑point behavior and any secondary‑feed fees. - Decide if a second Chorus URL will ever be purchased. - Determine final handling of ONFR live‑event streams (retain JWP vs. replace). - Approve Jira‑form design for automated podcast‑chain requests (feasibility with Marc). - Resolve geo‑blocking removal for TFO/IdĂ©llo (legal compliance). - Finalize Mogador synchronization approach or project removal. - Choose which of the four technical subjects (retry, Firebase lockout, update‑message migration, Contentful version control) to include in next Boukili build. - Confirm migration‑forced strategy for multi‑device users and communication plan. - Approve additional QA resources or temporary reinforcement. --- # Top Priorities Next Week 1. Send clarification email to CRTC and follow up with Pierre‑Olivier. 2. Begin Boukili v3 testing and map production‑DB fields. 3. Execute end‑to‑end ONFR broadcast test and add supervision cron entries. 4. Verify JWP secondary‑feed billing and ingest‑point details. 5. Create test collection in JWP and confirm subtitle display. 6. Conduct OTT multi‑device testing (including Apple TV zoom) for sign‑off. 7. Prepare ZIP‑to‑IdĂ©llo tickets (ready for 12 Oct start). --- # CTO Development **Leadership:** – **Technology:** – **Business:** – **Finance:** – **Communication:** – *One thing I did this week that made me more like a CTO:* – *One thing I did this week that kept me acting like an individual contributor:* –