POPULARITY
Categories
231 episodes with Documentation
207 episodes with Documentation
89 episodes with Documentation
84 episodes with Documentation
36 episodes with Documentation
98 episodes with Documentation
28 episodes with Documentation
30 episodes with Documentation
29 episodes with Documentation
21 episodes with Documentation
18 episodes with Documentation
14 episodes with Documentation
15 episodes with Documentation
17 episodes with Documentation
43 episodes with Documentation
16 episodes with Documentation
14 episodes with Documentation
13 episodes with Documentation
11 episodes with Documentation
11 episodes with Documentation
18 episodes with Documentation
10 episodes with Documentation
11 episodes with Documentation
12 episodes with Documentation
10 episodes with Documentation
13 episodes with Documentation
10 episodes with Documentation
15 episodes with Documentation
11 episodes with Documentation
10 episodes with Documentation
12 episodes with Documentation
6 episodes with Documentation
8 episodes with Documentation
8 episodes with Documentation
10 episodes with Documentation
8 episodes with Documentation
7 episodes with Documentation
17 episodes with Documentation
18 episodes with Documentation
11 episodes with Documentation
8 episodes with Documentation
8 episodes with Documentation
7 episodes with Documentation
14 episodes with Documentation
8 episodes with Documentation
6 episodes with Documentation
9 episodes with Documentation
10 episodes with Documentation
6 episodes with Documentation
8 episodes with Documentation
6 episodes with Documentation
5 episodes with Documentation
5 episodes with Documentation
7 episodes with Documentation
7 episodes with Documentation
5 episodes with Documentation
5 episodes with Documentation
5 episodes with Documentation
8 episodes with Documentation
6 episodes with Documentation
4 episodes with Documentation
7 episodes with Documentation
4 episodes with Documentation
6 episodes with Documentation
10 episodes with Documentation
5 episodes with Documentation
10 episodes with Documentation
8 episodes with Documentation
6 episodes with Documentation
5 episodes with Documentation
7 episodes with Documentation
5 episodes with Documentation
5 episodes with Documentation
3 episodes with Documentation
3 episodes with Documentation
11 episodes with Documentation
4 episodes with Documentation
3 episodes with Documentation
6 episodes with Documentation
6 episodes with Documentation
5 episodes with Documentation
4 episodes with Documentation
4 episodes with Documentation
4 episodes with Documentation
12 episodes with Documentation
4 episodes with Documentation
7 episodes with Documentation
4 episodes with Documentation
6 episodes with Documentation
3 episodes with Documentation
3 episodes with Documentation
5 episodes with Documentation
5 episodes with Documentation
4 episodes with Documentation
4 episodes with Documentation
4 episodes with Documentation
4 episodes with Documentation
4 episodes with Documentation
4 episodes with Documentation
10 episodes with Documentation
3 episodes with Documentation
5 episodes with Documentation
4 episodes with Documentation
4 episodes with Documentation
7 episodes with Documentation
3 episodes with Documentation
5 episodes with Documentation
3 episodes with Documentation
4 episodes with Documentation
4 episodes with Documentation
4 episodes with Documentation
4 episodes with Documentation
3 episodes with Documentation
2 episodes with Documentation
4 episodes with Documentation
3 episodes with Documentation
3 episodes with Documentation
2 episodes with Documentation
3 episodes with Documentation
3 episodes with Documentation
3 episodes with Documentation
9 episodes with Documentation
4 episodes with Documentation
8 episodes with Documentation
4 episodes with Documentation
2 episodes with Documentation
4 episodes with Documentation
7 episodes with Documentation
6 episodes with Documentation
7 episodes with Documentation
3 episodes with Documentation
4 episodes with Documentation
5 episodes with Documentation
3 episodes with Documentation
3 episodes with Documentation
(Premier épisode) Le samedi 19 mars 2022, vers 6h15 du matin, Federico Martín Aramburú, ancien joueur international de rugby, est abattu de six balles à Paris, dans le quartier chic de Saint-Germain-des-Prés. Loïk Le Priol et Romain Bouvier, les deux tireurs présumés, sont issus des milieux d'extrême droite néo-nazis. Après la mort du rugbyman, les deux hommes disparaissent. Dans Crime story, la journaliste Clawdia Prolongeau raconte cette enquête avec Damien Delseny, chef du service police-justice du Parisien.Crédits. Direction de la rédaction : Pierre Chausse - Rédacteur en chef : Jules Lavie - Ecriture et voix : Clawdia Prolongeau et Damien Delseny - Production : Clémentine Spiler et Anaïs Godard - Réalisation et mixage : Julien Montcouquiol - Musiques : Audio Network - Archives : INA - Photo : Franck FIFE / AFP.Documentation.Cet épisode de Crime story a été préparé en puisant dans les archives du Parisien, avec l'aide de nos documentalistes ainsi que de L'Équipe. Hébergé par Acast. Visitez acast.com/privacy pour plus d'informations.
(Deuxième et dernier épisode) Le samedi 19 mars 2022, vers 6h15 du matin, Federico Martín Aramburú, ancien joueur international de rugby, est abattu de six balles à Paris, dans le quartier chic de Saint-Germain-des-Prés. Loïk Le Priol et Romain Bouvier, les deux tireurs présumés, sont issus des milieux d'extrême droite néo-nazis. Après la mort du rugbyman, les deux hommes disparaissent. Dans Crime story, la journaliste Clawdia Prolongeau raconte cette enquête avec Damien Delseny, chef du service police-justice du Parisien.Crédits. Direction de la rédaction : Pierre Chausse - Rédacteur en chef : Jules Lavie - Ecriture et voix : Clawdia Prolongeau et Damien Delseny - Production : Clémentine Spiler et Anaïs Godard - Réalisation et mixage : Julien Montcouquiol - Musiques : Audio Network - Archives : INA - Photo : Franck FIFE / AFP.Documentation.Cet épisode de Crime story a été préparé en puisant dans les archives du Parisien, avec l'aide de nos documentalistes ainsi que de L'Équipe. Hébergé par Acast. Visitez acast.com/privacy pour plus d'informations.
Is Medical Assistance in Dying (MAiD) in Canada really peaceful? This video breaks down the actual drug protocol used in MAiD procedures, the reported complication rates, and what the pharmacology data reveals about how assisted dying works in practice.Canada presents MAiD as clinical, controlled, and dignified. But when you examine the medications used — midazolam, propofol, neuromuscular blockers like rocuronium, and in some cases cardiotoxic drugs — the timeline and reported complications raise important questions.In this analysis, we cover:• The standard MAiD drug protocol in Canada• Median time to death and why it varies• Reported MAiD complications (including IV failures)• The role of paralytics in assisted dying• How cardiotoxic drugs induce cardiac arrest• Documentation gaps in MAiD reporting• Whether MAiD is as predictable as publicly describedThis is not a political debate. It is a close look at the medical mechanics behind physician-assisted death in Canada.If MAiD is now part of Canadian healthcare, transparency about the drugs, training, and outcomes matters. - - - - - - - - - - - -One Time Donation! - Paypal - https://paypal.me/brassandunityBuy me a coffee! - https://buymeacoffee.com/kelsisherenLet's connect!Youtube - https://www.youtube.com/@thekelsisherenperspectiveInstagram - https://www.instagram.com/thekelsisherenperspective?utm_source=ig_web_button_share_sheet&igsh=ZDNlZDc0MzIxNw%3D%3DX: https://x.com/KelsiBurnsInstagram: https://www.instagram.com/kelsie_sheren/Substack: https://substack.com/@kelsisherenSUPPORT OUR PEOPLE - - - - - - - - - - - -MasterPeace - 10% off with code KELSI - https://www.MasterPeace.Health/KelsiKetone IQ- 30% off with code KELSI - https://ketone.com/KELSIGood Livin - 20% off with code KELSI - https://www.itsgoodlivin.com/?ref=KELSIBrass & Unity - 20% off with code UNITY - http://brassandunity.com
durée : 00:54:55 - Les Nuits de France Culture - par : Philippe Garbit - Par Irène Omélianenko - Avec Grisélidis Réal (l'une des leaders mondiales des prostituées, créatrice du premier Centre International de Documentation sur la Prostitution, auteur de "La passe imaginaire" Ed. Manya) - Lectures Rose Thierry - Réalisation Jean Couturier - réalisation : Virginie Mourthé
SummaryIn this episode, Sean Weiss and Terry Fletcher explore the complexities of healthcare compliance, focusing on workflows, documentation, and audits in medical practices. They discuss real-world scenarios involving frequency audits, documentation cloning, and the importance of proactive compliance strategies to avoid regulatory risks.Key TopicsImpact of workflow failures on complianceRisks of documentation cloning and cut-and-pasteStrategies to improve patient follow-up and adherenceUnderstanding medical necessity and billing levelsRegulatory scrutiny from Medicare and commercial payersEffective workflows are crucial for compliance and avoiding audits.Cloning of medical records can lead to serious legal and financial risks.Proactive follow-up with patients can prevent unnecessary visits and documentation issues.Understanding and documenting medical necessity is key to justified billing.Regular audits and leadership involvement are essential for a compliant practice.TakeawaysEffective workflows are crucial for compliance and avoiding audits.Cloning of medical records can lead to serious legal and financial risks.Proactive follow-up with patients can prevent unnecessary visits and documentation issues.Understanding and documenting medical necessity is key to justified billing.Regular audits and leadership involvement are essential for a compliant practice.
SUMMARY: In this episode of Ops Experts Club, Aaron Hovivian and Terryn Turner discuss the important shift from working in tasks to thinking in systems—a transition that helps move someone from an assistant role into a true operator role. They explain that task-based work is reactive and often overwhelming, while systems create structure, repeatability, and efficiency. By building processes for recurring work—like producing a podcast or launching a product—teams can ensure ideas move through a consistent workflow without relying on constant direction from leadership. Aaron and Terryn also highlight the importance of documenting processes as they are developed and using task management tools to manage responsibilities across a team. They introduce the Delegate and Elevate framework, which helps individuals categorize their work based on what they enjoy and what they are good at, making it easier to delegate lower-value tasks and focus on higher-impact responsibilities. Overall, the episode emphasizes that well-built systems allow operators to coordinate work effectively while freeing up visionaries to focus on generating ideas and driving growth. Minute by Minute: 00:00 Introduction and Guest Appearance 01:54 Shifting from Tasks to Systems 07:37 Creating Effective Systems 11:16 The Importance of Documentation 15:13 Delegate and Elevate Process
Naomi Hattaway is the founder of Leaving Well, a practice devoted to helping organizations treat leadership transitions not as crises or cleanups—but as acts of cultural maturity. She works with mission-driven teams to address board development, succession planning gaps, and workplace transition support. Through interim executive leadership and advisory services, Naomi's work lives at the intersection of trust-building, systems change, and the radical belief that how we end things matters just as much as how we begin. Key Takeaways: Leadership changes are often treated as crises even though they are normal and predictable. Naomi reframes exits as acts of cultural maturity rather than simple HR events. Thoughtful offboarding helps organizations create healthy closure and continuity. Transitions affect not only leaders but also the team that remains. Founder departures can trigger identity questions when organizations are built around one personality. Acknowledging grief and uncertainty helps teams move forward with clarity. Succession planning should involve the whole team, not just top leadership. Documentation, relationship handoffs, and knowledge transfer strengthen organizational resilience. Sabbaticals and temporary leaves can help organizations practice navigating absence and return. People respond to change in different ways, and each style brings value. Understanding these differences helps teams balance stability with forward movement. Healthy organizations accept that transition is messy but handle it with intention and care. “We need to normalize the reality that people leave.” “We put so much effort and beautiful intention into the onboarding, and then the offboarding is not the same level of energy.” “We have to start somewhere by being a little bit better to each other when it comes to goodbye.” - Naomi Hattaway Reach out to Naomi Hattaway at: Website: https://naomihattaway.com/ Instagram: https://instagram.com/naomihattaway LinkedIn: https://linkedin.com/in/naomihattaway Let's Work Together to Amplify Your Leadership + Influence1. Group Coaching for Nonprofit LeadersWant to lead with more clarity, confidence, and influence? My group coaching program is designed for nonprofit leaders who are ready to communicate more powerfully, navigate challenges with ease, and move their organizations forward. 2. Team Coaching + TrainingI work hands-on with nonprofit teams to strengthen leadership, improve communication, and align around a shared vision. Whether you're growing fast or feeling stuck, we'll create more clarity, collaboration, and momentum—together. 3. Board Retreats + TrainingsYour board has big potential. I'll help you unlock it. My engaging, no-fluff retreats and trainings are built to energize your board, refocus on what matters, and generate real results.Get your free starter kit today at www.theinfluentialnonprofit.comConnect with Maryanne about her coaching programs:https://www.courageouscommunication.com/connect Book Maryanne to speak at your conference:https://www.courageouscommunication.com/nonprofit-keynote-speaker
In this episode, host Ashutosh Garg sits down with Indrajit Lahiri, the founder of Foodka and Pickle Solutions Pvt. Ltd., to unravel the extraordinary journey of a food documentarian who bridges the worlds of IT, entrepreneurship, and Indian culinary storytelling.Indrajit shares insights on his transition from corporate IT to food documentation, why story always comes before food on his channel, and what makes Indian cuisine one of the most varied in the world. Dive into the nuances of regional recipes, disappearing traditions, and the importance of context—plus discover what makes Bengali and Northeastern cuisine so underrated and unique.Whether you're a food lover, aspiring entrepreneur, or cultural explorer, this episode offers wisdom on identity, storytelling, and the challenges facing Indian food today.
HTML All The Things - Web Development, Web Design, Small Business
A lot of developers say you should learn a framework from its official documentation - but is that actually a good way to learn React when you're still a beginner? In this episode, Matt breaks down his experience working through the official React docs, including the Quick Start guide, the Tic-Tac-Toe tutorial, and the “Thinking in React” section. Along the way, he talks about where React starts to click, where the docs shine for beginners, and why understanding project structure, state, and component hierarchy matters so much when you're trying to move beyond vanilla JavaScript. In this episode Matt and Mike discuss whether the official React documentation is enough for beginners, how React's learning materials compare to more guided tutorials, and what parts of the docs are especially helpful when you're trying to build real understanding instead of just copying code. Show Notes: https://www.htmlallthethings.com/podcast/can-i-learn-react-using-the-official-documentation Use our Scrimba affiliate link (https://scrimba.com/?via=htmlallthethings) for a 20% discount!! Full details in show notes.
Ce mardi (10 mars 2026), José Antonio Kast sera investi à la tête du Chili, près de trois mois après son élection. Il deviendra le premier président d'extrême-droite depuis la fin du régime d'Augusto Pinochet en 1990. Le futur chef de l'État ne se cache pas d'être un soutien du dictateur tenu pour responsable de plus de 3 000 morts ou disparus. Au cours de son mandat, il promet de grandes mesures sur l'immigration et la sécurité. À quoi faut-il s'attendre lors des prochains mois ? Que signifie son élection aujourd'hui au Chili, dans le contexte d'une Amérique Latine considérée par Donald Trump comme son arrière-cour ? Pour en débattre - Paola Martinez Infante, journaliste indépendante chilienne - Mathilde Allain, enseignante chercheuse à l'Institut des Hautes Études de l'Amérique Latine et au Centre de Recherche et de Documentation sur les Amériques (IHEAL-CREDA) - Franck Gaudichaud, professeur des Universités en Histoire et Études des Amériques latines contemporaines à l'Université Toulouse Jean Jaurès.
Ever feel like the paperwork is slowly killing your passion for social work? In this episode I am unpacking a conversation that so many social workers need to hear.The Critical Mid-Career Point is the term you need to know. It is that moment around 8 to 10 years into your career where you realize what got you here will not get you to the finish line. If you have ever felt like you are hitting a wall, this episode was made for you.Here are the three biggest takeaways from this episode:One, heavy documentation in federally funded social service programs is by design and it is one of the leading causes of social worker burnout.Two, not all social work jobs carry the same documentation burden and understanding the difference can completely change how you approach your job search.Three, there are real career options available to social workers that leverage your existing skills without the exhausting paperwork and bureaucratic systems.If you are a social worker who loves the work but is drained by the systems around it, this episode will give you the language and the clarity around what you are actually experiencing.Ready to explore what is possible beyond direct practice? Grab the free e-course at macroandpaid.com and start mapping out your next career move today.Happy macro career planning,Marthea Pitts, MSW
Dr. Friday highlights expanded IRS partnership audit enforcement under the Bipartisan Budget Act framework. She stresses clean records for basis, allocations, and distributions to protect partners. Transcript G’day, I’m Dr. Friday, president of Dr. Friday’s Tax and Financial Firm. To get more info, go to www.drfriday.com. This is a one-minute moment. And this is really for people that are in partnerships, which would also be LLCs. The IRS is expanding its partnership audit regime against the Bipartisan Budget Act framework, which allows adjustments to be assessed at the partnership level rather than partner level. That means the partnership can actually end up with the partner being in trouble, so you need to make sure proper documentation is in place. The partnership must maintain clear records supporting basis calculations, income allocations, and distributions. These are important words, and you need to make sure your tax person and accountant are doing them. You need help? drfriday.com. You can catch the Dr. Friday Call-in Show live every Saturday afternoon from 2 to 3 p.m. right here on 99.7 WTN.
SummaryThis episode features a lively panel discussion on healthcare documentation, compliance risks, and best practices. The experts share insights on managing documentation delays, metadata analysis, contract oversight, and the impact of AI in healthcare record-keeping.key topicsRisks of documentation modificationMetadata analysis in auditsContract oversight and complianceAI in healthcare documentationTakeawaysAltering original medical records can escalate legal issues.Metadata analysis is crucial in fraud detection.Effective contract management prevents costly mistakes.AI in documentation requires careful oversight.
How can health systems help nurses confidently adopt and trust AI? We'll explore how nurse-led design, clear guardrails (policy, consent, privacy), and intentional change management strategies help when implementing AI solutions that reduce cognitive burden, elevate the patient experience, and meet frontline expectations for safety, control, and transparency. In this episode of the AI at ViVE series on the BEAT podcast, host Sandy Vance sits down with Angie Curry, BSN, RN, CCDS, Chief Nursing Informatics Officer at Microsoft, to discuss how ambient AI is finally giving nurses the technological support they deserve. They chat about everything from the documentation burden nurses face, to the importance of workflow fit in driving adoption, to the critical role of human oversight in building trust with AI. If you're a nurse leader, clinical informatics professional, or healthcare innovator thinking about ambient AI, this episode is a must-listen. In this episode, they talk about: Microsoft developed the first ambient AI solution designed specifically for nurses, integrated with Epic's mobile Rover app Nurses spend roughly 40% of their shift on documentation, making them a prime candidate for ambient technology The solution captures spoken nurse-patient interactions and converts them into flow sheet-ready documentation for nurse review Nurses remain in full control, reviewing and approving all AI-generated content before it enters the patient record Trust in AI adoption is less about the technology itself and more about whether it fits naturally into existing nursing workflows Ambient listening captures "invisible care" that nurses often skip documenting due to time constraints Organizations have seen success with piloting on dedicated innovation units before scaling system-wide Documentation habits and language vary across organizations so designing solutions with nurses rather than for them is critical A Little About Angie: As a Chief Nursing Informatics Officer at Microsoft, Angie is passionate about transforming the way nurses experience technology. Drawing on years of bedside experience, she understands firsthand the challenges of documentation and the profound impact it has on patient care. Her mission is simple: to help nurses reclaim time for what matters most, caring for patients. Angie works at the intersection of clinical expertise and innovation, partnering with healthcare leaders to design solutions that feel intuitive, reduce cognitive load, and restore the joy of nursing. From ambient AI to workflow optimization, she believes technology should empower—never overwhelm—the caregivers who keep health systems running. Two Sentence Summary of Podcast Focus: How can health systems help nurses confidently adopt and trust AI? We'll explore how nurse-led design, clear guardrails (policy, consent, privacy), and intentional change management strategies can help when implementing AI solutions that reduce cognitive burden, elevate the patient experience, and meet frontline expectations for safety, control, and transparency.
In this episode of Dental Drill Bits, Sandy and Dana discuss one of the most overlooked leadership systems in dental practices: documentation. Many practice owners believe conversations alone are enough to manage team performance, only to find themselves in difficult situations when there is no written record of expectations, warnings, or accountability. This conversation breaks down what should be in a personnel file, why documentation protects both the practice and the employee, and how proper record keeping makes leadership clearer and more consistent. If you have ever thought, "We've talked about this before," but nothing was written down, this episode will help you understand why documentation matters and how to implement it properly in your practice. Topics We Discuss Why documentation protects both the practice and the employee The most common documentation mistakes practices make What should be included in a personnel file Why verbal conversations are not enough The difference between coaching, counseling, and written warnings When documentation should begin What should be included in a termination letter State separation notices and employment documentation requirements How documentation strengthens leadership and accountability Special thanks to our sponsors:
What makes a UFO hotspot? In Episode 147, we investigate the strange case of Rocky Mountain Ranch in Colorado. We also discusss Andrew Bustamante. A former CIA officer and star of Beyond Skinwalker Ranch, Bustamante brings his technical surveillance expertise to a location that has drawn comparisons to the infamous Skinwalker Ranch for decades. From "maddening hums" and energy spikes at the 1.6 GHz frequency to a terrifying 1970s encounter involving a disembodied voice that warned a family to "remain silent," we break down the evidence. We also explore how Bustamante's CIA background (detailed in his memoir Shadow Cell) shapes his approach to the unknown and why some researchers are taking this "other hotspot" more seriously than ever. Based on the provided sources, the phenomenon at Rocky Mountain Ranch in Colorado shares several striking similarities with Skinwalker Ranch, to the point that researchers consider it a major "hot spot" for related anomalous activities. Here is how the phenomena at the two ranches compare: Shared Frequencies and Energy Spikes One of the most significant connections between the two locations is the 1.6 gigahertz frequency, which is strongly correlated with "high strangeness" at Skinwalker Ranch. When investigators from the TV show Beyond Skinwalker Ranch broadcast a voice over this exact frequency at Rocky Mountain Ranch, they observed a "massive reaction" and "tons of energy" bouncing around the house, suggesting the phenomenon at both locations may interact with or be triggered by the same radio frequency. Types of Anomalous Phenomena While both ranches feature high strangeness, the specific events reported at Rocky Mountain Ranch include: Hums and Bangs: Similar to the strange noises at Skinwalker, residents and investigators at Rocky Mountain Ranch have reported hearing loud, maddening hums and underground bangs. Lights and Voices: During the 1970s, childhood resident Katie Paige experienced the power going out, a blinding light shining through the window, and a terrifying electronic voice emanating from the house itself, telling the family, "we have allowed you to remain... your friends will be instructed to remain silent". Voices were also reportedly heard coming through stereo equipment that was turned off. The Feeling of Being Watched: Experiencers at Rocky Mountain Ranch have reported a heavy, uneasy feeling of being watched, a psychological element frequently reported by investigators at Skinwalker Ranch. Documentation and Investigation Because of these similarities, Rocky Mountain Ranch was actually featured in the book "Hunt for the Skinwalker" under a section dedicated to "other hot spots," though the family and location were kept anonymous at the time. The strange events at Rocky Mountain Ranch were also officially documented in the late 1970s by the Aerial Phenomenon Research Organization (APRO), a precursor to MUFON. https://rockymountainufo.com/
Ann Druffel was a respected UFO researcher and author known for decades of work investigating unidentified aerial phenomena and the experiences of those who report encounters. In Investigating UFOs Then and Now, Druffel reflects on the evolution of UFO research—from early sightings and government interest to modern investigations and public disclosure debates. Drawing on historical cases, witness interviews, and her own research, she examined how perceptions of UFOs have changed over time while encouraging careful documentation and critical evaluation of reported sightings.Become a supporter of this podcast: https://www.spreaker.com/podcast/the-x-zone-radio-tv-show--1078348/support.Please note that all XZBN radio and/or television shows are Copyright © REL-MAR McConnell Meda Company, Niagara, Ontario, Canada – www.rel-mar.com. For more Episodes of this show and all shows produced, broadcasted and syndicated from REL-MAR McConell Media Company and The 'X' Zone Broadcast Network and the 'X' Zone TV Channell, visit www.xzbn.net. For programming, distribution, and syndication inquiries, email programming@xzbn.net.We are proud to announce the we have launched TWATNews.com, launched in August 2025.TWATNews.com is an independent online news platform dedicated to uncovering the truth about Donald Trump and his ongoing influence in politics, business, and society. Unlike mainstream outlets that often sanitize, soften, or ignore stories that challenge Trump and his allies, TWATNews digs deeper to deliver hard-hitting articles, investigative features, and sharp commentary that mainstream media won't touch.These are stories and articles that you will not read anywhere else.Our mission is simple: to expose corruption, lies, and authoritarian tendencies while giving voice to the perspectives and evidence that are often marginalized or buried by corporate-controlled media
Curt Collins is a UFO historian and researcher known for examining classic cases in ufology, including the Cash-Landrum UFO incident. In discussions about The Landrum Texas UFO Encounter, Collins explores the 1980 case involving Betty Cash, Vickie Landrum, and Colby Landrum, who reported seeing a diamond-shaped craft accompanied by multiple military helicopters near Dayton, Texas. The witnesses later claimed physical effects following the sighting, leading to widespread investigation and debate about possible military involvement, environmental exposure, or unidentified aerial phenomena. Collins' work focuses on historical documentation, witness testimony, and careful analysis of one of the most controversial UFO cases in American history.Become a supporter of this podcast: https://www.spreaker.com/podcast/the-x-zone-radio-tv-show--1078348/support.Please note that all XZBN radio and/or television shows are Copyright © REL-MAR McConnell Meda Company, Niagara, Ontario, Canada – www.rel-mar.com. For more Episodes of this show and all shows produced, broadcasted and syndicated from REL-MAR McConell Media Company and The 'X' Zone Broadcast Network and the 'X' Zone TV Channell, visit www.xzbn.net. For programming, distribution, and syndication inquiries, email programming@xzbn.net.We are proud to announce the we have launched TWATNews.com, launched in August 2025.TWATNews.com is an independent online news platform dedicated to uncovering the truth about Donald Trump and his ongoing influence in politics, business, and society. Unlike mainstream outlets that often sanitize, soften, or ignore stories that challenge Trump and his allies, TWATNews digs deeper to deliver hard-hitting articles, investigative features, and sharp commentary that mainstream media won't touch.These are stories and articles that you will not read anywhere else.Our mission is simple: to expose corruption, lies, and authoritarian tendencies while giving voice to the perspectives and evidence that are often marginalized or buried by corporate-controlled media
(Premier épisode) En 1986, Marie-Thérèse Bonfanti est une mère de famille de 25 ans qui vit avec son mari Thierry et leurs deux enfants, Erika et Flavien. Ils habitent dans une petite maison située au pied du massif des Bauges en Savoie, dans la commune de La Rochette. Ensemble, ils rêvent d'ouvrir un jour leur propre restaurant dans les environs.Le matin du jeudi 22 mai 1986, Marie-Thérèse installe ses enfants dans sa voiture et les dépose chez leur nourrice, puis prend la route pour Pontcharra, à une dizaine de kilomètres de chez elle, où elle travaille comme distributrice de journaux publicitaires. Mais en fin de journée, quand Thierry Bonfanti rentre chez lui, sa femme n'est pas là et la nounou n'a pas de nouvelles d'elle. Très inquiet, il décide alors de partir à sa recherche.Dans Crime story, la journaliste Clawdia Prolongeau raconte cette enquête avec Damien Delseny, chef du service police-justice du Parisien.Crédits. Direction de la rédaction : Pierre Chausse - Rédacteur en chef : Jules Lavie - Ecriture et voix : Clawdia Prolongeau et Damien Delseny - Production : Raphaël Pueyo et Anaïs Godard - Réalisation et mixage : Marec Panchot et Julien Montcouquiol - Musiques : Audio Network - Archives : INA.Documentation. Cet épisode de Crime story a été préparé en puisant dans les archives du Parisien, avec l'aide de nos documentalistes. Hébergé par Acast. Visitez acast.com/privacy pour plus d'informations.
(Deuxième et dernier épisode) En 1986, Marie-Thérèse Bonfanti est une mère de famille de 25 ans qui vit avec son mari Thierry et leurs deux enfants, Erika et Flavien. Ils habitent dans une petite maison située au pied du massif des Bauges en Savoie, dans la commune de La Rochette. Ensemble, ils rêvent d'ouvrir un jour leur propre restaurant dans les environs.Le matin du jeudi 22 mai 1986, Marie-Thérèse installe ses enfants dans sa voiture et les dépose chez leur nourrice, puis prend la route pour Pontcharra, à une dizaine de kilomètres de chez elle, où elle travaille comme distributrice de journaux publicitaires. Mais en fin de journée, quand Thierry Bonfanti rentre chez lui, sa femme n'est pas là et la nounou n'a pas de nouvelles d'elle. Très inquiet, il décide alors de partir à sa recherche.Dans Crime story, la journaliste Clawdia Prolongeau raconte cette enquête avec Damien Delseny, chef du service police-justice du Parisien.Crédits. Direction de la rédaction : Pierre Chausse - Rédacteur en chef : Jules Lavie - Ecriture et voix : Clawdia Prolongeau et Damien Delseny - Production : Raphaël Pueyo et Anaïs Godard - Réalisation et mixage : Marec Panchot et Julien Montcouquiol - Musiques : Audio Network - Archives : INA.Documentation. Cet épisode de Crime story a été préparé en puisant dans les archives du Parisien, avec l'aide de nos documentalistes. Hébergé par Acast. Visitez acast.com/privacy pour plus d'informations.
Daniel Ducheneaux is a paranormal investigator and author associated with Ghost Canada, a project exploring reported hauntings and unexplained phenomena across Canada. Ducheneaux examines historic locations, eyewitness accounts, and regional folklore to document stories of apparitions, unusual sounds, and lingering presences tied to Canada's past. His work blends historical research with field investigation, encouraging thoughtful inquiry into how history, environment, and human experience may contribute to enduring paranormal legends throughout the country.Become a supporter of this podcast: https://www.spreaker.com/podcast/the-x-zone-radio-tv-show--1078348/support.Please note that all XZBN radio and/or television shows are Copyright © REL-MAR McConnell Meda Company, Niagara, Ontario, Canada – www.rel-mar.com. For more Episodes of this show and all shows produced, broadcasted and syndicated from REL-MAR McConell Media Company and The 'X' Zone Broadcast Network and the 'X' Zone TV Channell, visit www.xzbn.net. For programming, distribution, and syndication inquiries, email programming@xzbn.net.We are proud to announce the we have launched TWATNews.com, launched in August 2025.TWATNews.com is an independent online news platform dedicated to uncovering the truth about Donald Trump and his ongoing influence in politics, business, and society. Unlike mainstream outlets that often sanitize, soften, or ignore stories that challenge Trump and his allies, TWATNews digs deeper to deliver hard-hitting articles, investigative features, and sharp commentary that mainstream media won't touch.These are stories and articles that you will not read anywhere else.Our mission is simple: to expose corruption, lies, and authoritarian tendencies while giving voice to the perspectives and evidence that are often marginalized or buried by corporate-controlled media
Lily Rose St. John is a paranormal investigator associated with the Beaver County Ghost Hunters, a group dedicated to researching reported hauntings and unexplained activity in historic locations. St. John's work focuses on field investigations, documenting eyewitness accounts, and exploring environmental factors that may contribute to reports of paranormal phenomena. Through organized investigations and community engagement, the group seeks to examine local legends and haunted sites while encouraging thoughtful inquiry into unexplained experiences.Become a supporter of this podcast: https://www.spreaker.com/podcast/the-x-zone-radio-tv-show--1078348/support.Please note that all XZBN radio and/or television shows are Copyright © REL-MAR McConnell Meda Company, Niagara, Ontario, Canada – www.rel-mar.com. For more Episodes of this show and all shows produced, broadcasted and syndicated from REL-MAR McConell Media Company and The 'X' Zone Broadcast Network and the 'X' Zone TV Channell, visit www.xzbn.net. For programming, distribution, and syndication inquiries, email programming@xzbn.net.We are proud to announce the we have launched TWATNews.com, launched in August 2025.TWATNews.com is an independent online news platform dedicated to uncovering the truth about Donald Trump and his ongoing influence in politics, business, and society. Unlike mainstream outlets that often sanitize, soften, or ignore stories that challenge Trump and his allies, TWATNews digs deeper to deliver hard-hitting articles, investigative features, and sharp commentary that mainstream media won't touch.These are stories and articles that you will not read anywhere else.Our mission is simple: to expose corruption, lies, and authoritarian tendencies while giving voice to the perspectives and evidence that are often marginalized or buried by corporate-controlled media
The reception to our recent post on Code Reviews has been strong. Catch up!Amid a maelstrom of discussion on whether or not AI is killing SaaS, one of the top publicly listed SaaS companies in the world has just reported record revenues, clearing well over $1.1B in ARR for the first time with a 28% margin. As we comment on the pod, Aaron Levie is the rare public company CEO equally at home in both worlds of Silicon Valley and Wall Street/Main Street, by day helping 70% of the Fortune 500 with their Enterprise Advanced Suite, and yet by night is often found in the basements of early startups and tweeting viral insights about the future of agents.Now that both Cursor, Cloudflare, Perplexity, Anthropic and more have made Filesystems and Sandboxes and various forms of “Just Give the Agent a Box” cool (not just cool; it is now one of the single hottest areas in AI infrastructure growing 100% MoM), we find it a delightfully appropriate time to do the episode with the OG CEO who has been giving humans and computers Boxes since he was a college dropout pitching VCs at a Michael Arrington house party.Enjoy our special pod, with fan favorite returning guest/guest cohost Jeff Huber!Note: We didn't directly discuss the AI vs SaaS debate - Aaron has done many, many, many other podcasts on that, and you should read his definitive essay on it. Most commentators do not understand SaaS businesses because they have never scaled one themselves, and deeply reflected on what the true value proposition of SaaS is.We also discuss Your Company is a Filesystem:We also shoutout CTO Ben Kus' and the AI team, who talked about the technical architecture and will return for AIE WF 2026.Full Video EpisodeTimestamps* 00:00 Adapting Work for Agents* 01:29 Why Every Agent Needs a Box* 04:38 Agent Governance and Identity* 11:28 Why Coding Agents Took Off First* 21:42 Context Engineering and Search Limits* 31:29 Inside Agent Evals* 33:23 Industries and Datasets* 35:22 Building the Agent Team* 38:50 Read Write Agent Workflows* 41:54 Docs Graphs and Founder Mode* 55:38 Token FOMO Culture* 56:31 Production Function Secrets* 01:01:08 Film Roots to Box* 01:03:38 AI Future of Movies* 01:06:47 Media DevRel and EngineeringTranscriptAdapting Work for AgentsAaron Levie: Like you don't write code, you talk to an agent and it goes and does it for you, and you may be at best review it. That's even probably like, like largely not even what you're doing. What's happening is we are changing our work to make the agents effective. In that model, the agent didn't really adapt to how we work.We basically adapted to how the agent works. All of the economy has to go through that exact same evolution. Right now, it's a huge asset and an advantage for the teams that do it early and that are kinda wired into doing this ‘cause you'll see compounding returns. But that's just gonna take a while for most companies to actually go and get this deployed.swyx: Welcome to the Lane Space Pod. We're back in the chroma studio with uh, chroma, CEO, Jeff Hoover. Welcome returning guest now guest host.Aaron Levie: It's a pleasure. Wow. How'd you get upgraded to, uh, to that?swyx: Because he's like the perfect guy to be guest those for you.Aaron Levie: That makes sense actually, for We love context. We, we both really love context le we really do.We really do.swyx: Uh, and we're here with, uh, Aaron Levy. Welcome.Aaron Levie: Thank you. Good to, uh, good to be [00:01:00] here.swyx: Uh, yeah. So we've all met offline and like chatted a little bit, but like, it's always nice to get these things in person and conversation. Yeah. You just started off with so much energy. You're, you're super excited about agents.I loveAaron Levie: agents.swyx: Yeah. Open claw. Just got by, got bought by OpenAI. No, not bought, but you know, you know what I mean?Aaron Levie: Some, some, you know, acquihire. Executiveswyx: hire.Aaron Levie: Executive hire. Okay. Executive hire. Say,swyx: hey, that's my term. Okay. Um, what are you pounding the table on on agents? You have so many insightful tweets.Why Every Agent Needs a BoxAaron Levie: Well, the thing that, that we get super excited by that I think is probably, you know, should be relatively obvious is we've, we've built a platform to help enterprises manage their files and their, their corporate files and the permissions of who has access to those files and the sharing collaboration of those files.All of those files contain really, really important information for the enterprise. It might have your contracts, it might have your research materials, it might have marketing information, it might have your memos. All that data obviously has, you know, predominantly been used by humans. [00:02:00] But there's been one really interesting problem, which is that, you know, humans only really work with their files during an active engagement with them, and they kind of go away and you don't really see them for a long time.And all of a sudden, uh, with the power of AI and AI agents, all of that data becomes extremely relevant as this ongoing source of, of answers to new questions of data that will transform into, into something else that, that produces value in your organization. It, it contains the answer to the new employee that's onboarding, that needs to ramp up on a project.Um, it contains the answer to the right thing to sell a customer when you're having a conversation to them, with them contains the roadmap information that's gonna produce the next feature. So all that data. That previously we've been just sort of storing and, and you know, occasionally forgetting about, ‘cause we're only working on the new active stuff.All of that information becomes valuable to the enterprise and it's gonna become extremely valuable to end users because now they can have agents go find what they're looking for and produce new, new [00:03:00] value and new data on that information. And it's gonna become incredibly valuable to agents because agents can roam around and do a bunch of work and they're gonna need access to that data as well.And um, and you know, sometimes that will be an agent that is sort of working on behalf of, of, of you and, and effectively as you as and, and they are kind of accessing all of the same information that you have access to and, and operating as you in the system. And then sometimes there's gonna be agents that are just.Effectively autonomous and kind of run on their own and, and you're gonna collaborate and work with them kind of like you did another person. Open Claw being the most recent and maybe first real sort of, you know, kind of, you know, up updating everybody's, you know, views of this landscape version of, of what that could look like, which is, okay, I have an agent.It's on its own system, it's on its own computer, it has access to its own tools. I probably don't give it access to my entire life. I probably communicate with it like I would an assistant or a colleague and then it, it sort of has this sandbox environment. So all of that has massive implications for a platform that manage that [00:04:00] enterprise data.We think it's gonna just transform how we work with all of the enterprise content that we work with, and we just have to make sure we're building the right platform to support that.swyx: The sort of shorthand I put it is as people build agents, everybody's just realizing that every agent needs a box. Yes.And it's nice to be called box and just give everyone a box.Aaron Levie: Hey, I if I, you know, if we can make that go viral, uh, like I, I think that that terminology, I, that's theswyx: tagline. Every agentAaron Levie: needs a box. Every agent needs a box. If we can make that the headline of this, I'm fine with this. And that's the billboard I wanna like Yeah, exactly.Every agent needs a box. Um, I like it. Can we ship this? Like,swyx: okay, let's do it. Yeah.Aaron Levie: Uh, my work here is done and I got the value I needed outta this podcast Drinks.swyx: Yeah.Agent Governance and IdentityAaron Levie: But, but, um, but, but, you know, so the thing that we, we kind of think about is, um, is, you know, whether you think the number 10 x or a hundred x or whatever the number is, we're gonna have some order of magnitude more agents than people.That's inevitable. It has to happen. So then the question is, what is the infrastructure that's needed to make all those agents effective in the enterprise? Make sure that they are well governed. Make sure they're only doing [00:05:00] safe things on your information. Make sure that they're not getting exposed. The data that they shouldn't have access to.There's gonna be just incredibly spectacularly crazy security incidents that will happen with agents because you'll prompt, inject an agent and sort of find your way through the CRM system and pull out data that you shouldn't have access to. Oh, weJeff Huber: have God,Aaron Levie: right? I mean, that's just gonna happen all over the place, right?So, so then the thing is, is how do you make sure you have the right security, the permissions, the access controls, the data governance. Um, we actually don't yet exactly know in many cases how we're gonna regulate some of these agents, right? If you think about an agent in financial services, does it have the exact same financial sort of, uh, requirements that a human did?Or is it, is the risk fully on the human that was interacting or created the agent? All open questions, but no matter what, there's gonna need to be a layer that manages the, the data they have access to, the workflows that they're involved in, pulling up data from multiple systems. This is the new infrastructure opportunity in the era of agents.swyx: You have a piece on agent identities, [00:06:00] which I think was today, um, which I think a lot of breaking news, the security, security people are talking about, right? Like you basically, I, I always think of this as like, well you need the human you and then there you need the agent. YouAaron Levie: Yes.swyx: And uh, well, I don't know if it's that simple, but is box going to have an opinion on that or you're just gonna be like, well we're just the sort of the, the source layer.Yeah. Let's Okta of zero handle that.Aaron Levie: I think we're gonna have an opinion and we will work with generally wherever the contours of the market end up. Um, and the reason that we're gonna have an opinion more than other topics probably is because one of the biggest use cases for why your agent might need it, an identity is for file system access.So thus we have to kind of think about this pretty deeply. And I think, uh, unless you're like in our world thinking about this particular problem all day long, it might be, you know, like, why is this such a big deal? And the reason why it's a really big deal is because sometimes sort of say, well just give the agent an, an account on the system and it just treats, treat it like every other type of user on the system.The [00:07:00] problem is, is that I as Aaron don't really have any responsibility over anybody else's box account in our organization. I can't see the box account of any other employee that I work with. I am not liable for anything that they do. And they have, I have, I have, you know, strict privacy requirements on everything that they're able to, you know, that, that, that they work on.Agents don't have that, you know, don't have those properties. The person who creates the agent probably is gonna, for the foreseeable future, take on a lot of the liability of what that agent does. That agent doesn't deserve any privacy because, because it's, you know, it can't fully be autonomously operated and it doesn't have any legal, you know, kind of, you know, responsibility.So thus you can't just be like, oh, well I'll just create a bunch of accounts and then I'll, I'll kind of work with that agent and I'll talk to it occasionally. Like you need oversight of that. And so then the question is, how do you have a world where the agent, sometimes you have oversight of, but what if that agent goes and works with other people?That person over there is collaborating with the agent on something you shouldn't have [00:08:00] access to what they're doing. So we have all of these new boundaries that we're gonna have to figure out of, of, you know, it's really, really easy. So far we've been in, in easy mode. We've hit the easy button with ai, which is the agent just is you.And when you're in quad code and you're in cursor, and you're in Codex, you're just, the agent is you. You're offing into your services. It can do everything you can do. That's the easy mode. The hard mode is agents are kind of running on their own. People check in with them occasionally, they're doing things autonomously.How do you give them access to resources in the enterprise and not dramatically increased the security risk and the risk that you might expose the wrong thing to somebody. These are all the new problems that we have to get solved. I like the identity layer and, and identity vendors as being a solution to that, but we'll, we'll need some opinions as well because so many of the use cases are these collaborative file system use cases, which is how do I give it an agent, a subset of my data?Give it its own workspace as well. ‘cause it's gonna need to store off its own information that would be relevant for it. And how do I have the right oversight into that? [00:09:00]Jeff Huber: One thing, which, um, I think is kind interesting, think about is that you know, how humans work, right? Like I may not also just like give you access to the whole file.I might like sit next to you and like scroll to this like one part of the file and just show you that like one part and like, you know,swyx: partial file access.Jeff Huber: I'm just saying I think like our, like RA does seem to be dead, right? Like you wanna say something is dead uhhuh probably RA is dead. And uh, like the auth story to me seems like incredibly unsolved and unaddressed by like the existing state of like AI vendors.ButAaron Levie: yeah, I think, um, we're, I mean you're taking obviously really to level limit that we probably need to solve for. Yeah. And we built an access control system that was, was kind of like, you know, its own little world for, for a long time. And um, and the idea was this, it's a many to many collaboration system where I can give you any part of the file system.And it's a waterfall model. So if I give you higher up in the, in the, in the system, you get everything below. And that, that kind of created immense flexibility because I can kind of point you to any layer in the, in the tree, but then you're gonna get access to everything kind of below it. And that [00:10:00] mostly is, is working in this, in this world.But you do have to manage this issue, which is how do I create an agent that has access to some of my stuff and somebody else's stuff as well. Mm-hmm. And which parts do I get to look at as the creator of the agent? And, and these are just brand new problems? Yeah. Crazy. And humans, when there was a human there that was really easy to do.Like, like if the three of us were all sharing, there'd be a Venn diagram where we'd have an overlapping set of things we've shared, but then we'd have our own ways that we shared with each other. In an agent world, somebody needs to take responsibility for what that agent has access to and what they're working on.These are like the, some of the most probably, you know, boring problems for 98% of people on, on the internet, but they will be the problems that are the difference between can you actually have autonomous agents in an enterprise contextswyx: Yeah.Aaron Levie: That are not leaking your data constantly.swyx: No. Like, I mean, you know, I run a very, very small company for my conference and like we already have data sensitivity issues.Yes. And some of my team members cannot see Yes. Uh, the others and like, I can't imagine what it's like to run a Fortune 500 and like, you have to [00:11:00] worry about this. I'm just kinda curious, like you, you talked to a lot like, like 70, 80% of your cus uh, of the Fortune 500, your customers.Aaron Levie: Yep. 67%. Just so we're being verySEswyx: precise.So Yeah. I'm notAaron Levie: Okay. Okay.swyx: Something I'm rounding up. Yes. Round up. I'm projecting to, forAaron Levie: the government.swyx: I'm projecting to the end of the year.Aaron Levie: Okay.swyx: There you go.Aaron Levie: You do make it sound like, like we, we, well we've gotta be on this. Like we're, we're taking way too long to get to 80%. Well,swyx: no, I mean, so like. How are they approaching it?Right? Because you're, you don't have a, you don't have a final answer yet.Why Coding Agents Took Off FirstAaron Levie: Well, okay, so, so this is actually, this is the stark reality that like, unfortunately is the kinda like pouring the water on the party a little bit.swyx: Yes.Aaron Levie: We all in Silicon Valley are like, have the absolute best conditions possible for AI ever.And I think we all saw the dke, you know, kind of Dario podcast and this idea of AI coding. Why is that taken off? And, and we're not yet fully seeing it everywhere else. Well, look, if you just like enumerated the list of properties that AI coding has and then compared it to other [00:12:00] knowledge work, let's just, let's just go through a few of them.Generally speaking, you bring on a new engineer, they have access to a large swath of the code base. Like, there's like very, like you, just, like new engineer comes on, they can just go and find the, the, the stuff that they, they need to work with. It's a fully text in text out. Medium. It's only, it's just gonna be text at the end of the day.So it's like really great from a, from just a, uh, you know, kinda what the agent can work with. Obviously the models are super trained on that dataset. The labs themselves have a really strong, kind of self-reinforcing positive flywheel of why they need to do, you know, agent coding deeply. So then you get just better tooling, better services.The actual developers of the AI are daily users of the, of the thing that they're we're working on versus like the, you know, probably there's only like seven Claude Cowork legal plugin users at Anthropic any given day, but there's like a couple thousand Claude code and you know, users every single day.So just like, think about which one are they getting more feedback on. All day long. So you just go through this list. You have a, you know, everybody who's a [00:13:00] developer by definition is technical so they can go install the latest thing. We're all generally online, or at least, you know, kinda the weird ones are, and we're all talking to each other, sharing best practices, like that's like already eight differences.Versus the rest of the economy. Every other part of the economy has like, like six to seven headwinds relative to that list. You go into a company, you're a banker in financial services, you have access to like a, a tiny little subset of the total data that's gonna be relevant to do your job. And you're have to start to go and talk to a bunch of people to get the right data to do your job because Sally didn't add you to that deal room, you know, folder.And that that, you know, the information is actually in a completely different organization that you now have to go in and, and sort of run into. And it's like you have this endless list of access controls and security. As, as you talked about, you have a medium, which is not, it's not just text, right? You have, you have a zoom call that, that you're getting all of the requirements from the customer.You have a lot of in-person conversations and you're doing in-person sales and like how do you ever [00:14:00] digitize all of that information? Um, you know, I think a lot of people got upset with this idea that the code base has all the context, um, that I don't know if you follow, you know, did you follow some of that conversation that that went viral?Is like, you know, it's not that simple that, that the code base doesn't have all the knowledge, but like it's a lot, you're a lot better off than you are with other areas of knowledge work. Like you, we like, we like have documentation practices, you write specifications. Those things don't exist for like 80% of work that happens in the enterprise.That's the divide that we have, which is, which is AI coding has, has just fully, you know, where we've reached escape velocity of how powerful this stuff is, and then we're gonna have to find a way to bring that same energy and momentum, but to all these other areas of knowledge work. Where the tools aren't there, the data's not set up to be there.The access controls don't make it that easy. The context engineering is an incredibly hard problem because again, you have access control challenges, you have different data formats. You have end users that are gonna need to kind of be kind of trained through this as opposed to their adopting [00:15:00] these tools in their free time.That's where the Fortune 500 is. And so we, I think, you know, have to be prepared as an industry where we are gonna be on a multi-year march to, to be able to bring agents to the enterprise for these workflows. And I think probably the, the thing that we've learned most in coding that, that the rest of the world is not yet, I think ready for, I mean, we're, they'll, they'll have to be ready for it because it's just gonna inevitably happen is I think in coding.What, what's interesting is if you think about the practice of coding today versus two years ago. It's probably the most changed workflow in maybe the history of time from the amount of time it's changed, right? Yeah. Like, like has any, has any workflow in the entire economy changed that quickly in terms of the amount of change?I just, you know, at least in any knowledge worker workflow, there's like very rarely been an event where one piece of technology and work practice has so fundamentally, you know, changed, changed what you do. Like you don't write code, you talk to an agent and it goes and [00:16:00] does it for you, and you may be at best review it.And even that's even probably like, like largely not even what you're doing. What's happening is we are changing our work to make the agents effective. In that model, the agent didn't really adapt to how we work. We basically adapted to how the agent works. Mm-hmm. All of the economy has to go through that exact same evolution.The rest of the economy is gonna have to update its workflows to make agents effective. And to give agents the context that they need and to actually figure out what kind of prompting works and to figure out how do you ensure that the agent has the right access to information to be able to execute on its work.I, you know, this is not the panacea that people were hoping for, of the agent drops in, just automates your life. Like you have to basically re-engineer your workflow to get the most out of agents and, uh, and that, that's just gonna take, you know, multiple years across the economy. Right now it's a huge asset and an advantage for the teams that do it early and that are kinda wired into doing this.‘cause [00:17:00] you'll see compounding returns, but that's just gonna take a while for most companies to actually go and get this deployed.swyx: I love, I love pushing back. I think that. That is what a lot of technology consultants love to hear this sort of thing, right? Yeah, yeah, yeah. First to, to embrace the ai. Yes. To get to the promised land, you must pay me so much money to a hundred percent to adopt the prescribed way of, uh, conforming to the agents.Yes. And I worry that you will be eclipsed by someone else who says, no, come as you are.Aaron Levie: Yeah.swyx: And we'll meet you where you are.Aaron Levie: And, and, and and what was the thing that went viral a week ago? OpenAI probably, uh, is hiring F Dees. Yeah. Uh, to go into the enterprise. Yeah. Yeah. And then philanthropic is embedded at Goldman Sachs.Yeah. So if the labs are having to do this, if, if the labs have decided that they need to hire FDE and professional services, then I think that's a pretty clear indication that this, there's no easy mode of workflow transformation. Yeah. Yeah. So, so to your point, I think actually this is a market opportunity for, you know, new professional services and consulting [00:18:00] firms that are like Agent Build and they, and they kind of, you know, go into organizations and they figure out how to re-engineer your workflows to make them more agent ready and get your data into the right format and, you know, reconstruct your business process.So you're, you're not doing most of the work. You're telling agents how to do the work and then you're reviewing it. But I haven't seen the thing that can just drop in and, and kinda let you not go through those changes.swyx: I don't know how that kind of sales pitch goes over. Yeah. You know, you're, you're saying things like, well, in my sort of nice beautiful walled garden, here's, there's, uh, because here's this, here's this beautiful box account that has everything.Yes. And I'm like, well, most, most real life is extremely messy. Sure. And like, poorly named and there duplicate this outdated s**tAaron Levie: a hundred percent. And so No, no, a hundred percent. And so this is actually No. So, so this is, I mean, we agree that, that getting to the beautiful garden is gonna be tough.swyx: Yeah.Aaron Levie: There's also the other end of the spectrum where I, I just like, it's a technical impossibility to solve. The agent is, is truly cannot get enough context to make the right decision in, in the, in the incredibly messy land. Like there's [00:19:00] no a GI that will solve that. So, so we're gonna have to kind of land in somewhere in between, which is like we all collectively get better at.Documentation practices and, and having authoritative relatively up-to-date information and putting it in the right place like agents will, will certainly cause us to be much better organized around how we work with our information, simply because the severity of the agent pulling the wrong data will be too high and the productivity gain of that you'll miss out on by not doing this will be too high as well, that you, that your competition will just do it and they'll just have higher velocity.So, uh, and, and we, we see this a lot firsthand. So we, we build a series of agents internally that they can kind of have access to your full box account and go off and you give it a task and it can go find whatever information you're looking for and work with. And, you know, thank God for the model progress, but like, if, if you gave that task to an agent.Nine months ago, you're just gonna get lots of bogus answers because it's gonna, it's gonna say, Hey, here's, here are fi [00:20:00] five, you know, documents that all kind of smell like the right thing. And I'm gonna, but I, but you're, you're putting me on the clock. ‘cause my assistant prompt says like, you know, be pretty smart, but also try and respond to the user and it's gonna respond.And it's like, ah, it got the wrong document. And then you do that once or twice as a knowledge worker and you're just neverswyx: again,Aaron Levie: never again. You're just like done with the system.swyx: Yeah. It doesn't work.Aaron Levie: It doesn't work. And so, you know, Opus four six and Gemini three one Pro and you know, whatever the latest five 3G BT will be, like, those things are getting better and better and it's using better judgment.And this sort of like the, all of these updates to the agentic tool and search systems are, are, we're seeing, we're seeing very real progress where the agent. Kind of can, can almost smell some things a little bit fishy when it's getting, you know, we, we have this process where we, we have it go fan out, do a bunch of searches, pull up a bunch of data, and then it has to sort of do its own ranking of, you know, what are the right documents that, that it should be working with.And again, like, you know, the intelligence level of a model six months ago, [00:21:00] it'd be just throwing a dart at like, I'm just, I'm gonna grab these seven files and I, I pray, I hope that that's the right answer. And something like an opus first four five, and now four six is like, oh, it's like, no, that one doesn't seem right relative to this question because I'm seeing some signal that is making that, you know, that's contradicting the document where it would normally be in the tree and who should have access.Like it's doing all of that kind of work for you. But like, it still doesn't work if you just have a total wasteland of data. Like, it's just not, it's just not possible. Partly ‘cause a human wouldn't even be able to do it. So basically if a, if a really, really smart human. Could not do that task in five or 10 minutes for a search retrieval type task.Look, you know, your agent's not gonna be able to do it any better. You see this all day long. SoContext Engineering and Search Limitsswyx: this touches on a thing that just passionate about it was just context engineering. I, I'm just gonna let you ramble or riff on, on context engineering. If, if, if there's anything like he, he did really good work on context fraud, which has really taken over as like the term that people use and the referenceAaron Levie: a hundred percent.We, we all we think about is, is the context rob problem. [00:22:00]Jeff Huber: Yeah, there's certainly a lot of like ranking considerations. Gentech surgery think is incredibly promising. Um, yeah, I was trying to generate a question though. I think I have a question right now. Swyx.Aaron Levie: Yeah, no, but like, like I think there was this moment, um, you know, like, I don't know, two years ago before, before we knew like where the, the gotchas were gonna be in ai and I think someone was like, was like, well, infinite context windows will just solve all of these problems and ‘cause you'll just, you'll just give the context window like all the data and.It's just like, okay, I mean, maybe in 2035, like this is a viable solution. First of all, it, it would just, it would just simply cost too much. Like we just can't give the model like the 5,000 documents that might be relevant and it's gonna read them all. And I've seen enough to, to start believing in crazy stuff.So like, I'm willing to just say, sure. Like in, in 10 years from now,swyx: never say, never, never.Aaron Levie: In, in 10 years from now, we'll have infinite context windows at, at a thousandth of the price of today. Like, let's just like believe that that's possible, but Right. We're in reality today. So today we have a context engineering [00:23:00] problem, which is, I got, I got, you know, 200,000 tokens that I can work with, or prob, I don't even know what the latest graph is before, like massive degradation.16. Okay. I have 60,000 tokens that I get to work with where I'm gonna get accurate information. That's not a lot of tokens for a corpus of 10 million documents that a knowledge worker might have across all of the teams and all the projects and all the people they work with. I have, I have 10 million documents.Which, you know, maybe is times five pages per document or something like that. I'm at 50 million pages of information and I have 60,000 tokens. Like, holy s**t. Yeah. This is like, how do I bridge the 50 million pages of information with, you know, the couple hundred that I get to work with in that, in that token window.Yeah. This is like, this is like such an interesting problem and that's why actually so much work is actually like, just like search systems and the databases and that layer has to just get so locked in, but models getting better and importantly [00:24:00] knowing when they've done a search, they found the wrong thing, they go back, they check their work, they, they find a way to balance sort of appeasing the user versus double checking.We have this one, we have this one test case where we ask the agent to go find. 10 pieces of information.swyx: Is this the complex work eval?Aaron Levie: Uh, this is actually not in the eval. This is, this is sort of just like we have a bunch of different, we have a bunch of internal benchmark kind of scenarios. Every time we, we update our agent, we have one, which is, I ask it to find all of our office addresses, and I give it the list of 10 offices that we have.And there's not one document that has this, maybe there should be, that would be a great example of the kind of thing that like maybe over time companies start to, you know, have these sort of like, what are the canonical, you know, kind of key areas of knowledge that we need to have. We don't seem to have this one document that says, here are all of our offices.We have a bunch of documents that have like, here's the New York office and whatever. So you task this agent and you, you get, you say, I need the addresses for these 10 offices. Okay. And by the way, if you do this on any, you know, [00:25:00] public chat model, the same outcome is gonna happen. But for a different kind of query, you give it, you say, I need these 10 addresses.How many times should the agent go and do its search before it decides whether or not, there's just no answer to this question. Often, and especially the, the, let's say lower tier models, it'll come back and it'll give you six of the 10 addresses. And it'll, and I'll just say I couldn't find the otherswyx: four.It, it doesn't know what It doesn't know. ItAaron Levie: doesn't know what It doesn't know. Yeah. So the model is just like, like when should it stop? When should it stop doing? Like should it, should it do that task for literally an hour and just keep cranking through? Maybe I actually made up an office location and it doesn't know that I made it up and I didn't even know that I made it up.Like, should it just keep, re should it read every single file in your entire box account until it, until it should exhaust every single piece of information.swyx: Expensive.Aaron Levie: These are the new problems that we have. So, you know, something like, let's say a new opus model is sort of like, okay, I'm gonna try these types of queries.I didn't get exactly what I wanted. I'm gonna try again. I'm gonna, at [00:26:00] some point I'm gonna stop searching. ‘cause I've determined that that no amount of searching is gonna solve this problem. I'm just not able to do it. And that judgment is like a really new thing that the model needs to be able to have.It's like, when should it give up on a task? ‘cause, ‘cause you just don't, it's a can't find the thing. That's the real world of knowledge, work problems. And this is the stuff that the coding agents don't have to deal with. Because they, it just doesn't like, like you're not usually asking it about, you're, you're always creating net new information coming right outta the model for the most part.Obviously it has to know about your code base and your specs and your documentation, but, but when you deploy an agent on all of your data that now you have all of these new problems that you're dealing withJeff Huber: our, uh, follow follow-up research to context ride is actually on a genetic search. Ah. Um, and we've like right, sort of stress tested like frontier models and their ability to search.Um, and they're not actually that good at searching. Right. Uh, so you're sort of highlighting this like explore, exploit.swyx: You're just say, Debbie, Donna say everything doesn't work. Like,Aaron Levie: well,Jeff Huber: somebody has to be,Aaron Levie: um, can I just throw out one more thing? Yeah. That is different from coding and, and the rest [00:27:00] of the knowledge work that I, I failed to mention.So one other kind of key point is, is that, you know, at the end of the day. Whether you believe we're in a slop apocalypse or, or whatever. At the end of the day, if you, if you build a working product at the end of, if you, if you've built a working solution that is ultimately what the customer is paying for, like whether I have a lot of slop, a little slop or whatever, I'm sure there's lots of code bases we could go into in enterprise software companies where it's like just crazy slop that humans did over a 20 year period, but the end customer just gets this little interface.They can, they can type into it, it does its thing. Knowledge work, uh, doesn't have that property. If I have an AI model, go generate a contract and I generate a contract 20 times and, you know, all 20 times it's just 3% different and like that I, that, that kind of lop introduces all new kinds of risk for my organization that the code version of that LOP didn't, didn't introduce.These are, and so like, so how do you constrain these models to just the part that you want [00:28:00] them to work on and just do the thing that you want them to do? And, and, you know, in engineering, we don't, you can't be disbarred as an engineer, but you could be disbarred as a lawyer. Like you can do the wrong medical thing In healthcare, you, there's no, there's no equivalent to that of engineering.Like, doswyx: you want there to be, because I've considered softwareJeff Huber: engineer. What's that? Civil engineering there is, right? NotAaron Levie: software civil engineer. Sure. Oh yeah, for sure. But like in any of our companies, you like, you know, you'll be forgiven if you took down the site and, and we, we will do a rollback and you'll, you'll be in a meeting, but you have not been disbarred as an engineer.We don't, we don't change your, you know, your computer science, uh, blameJeff Huber: degree, this postmortem.Aaron Levie: Yeah, exactly. Exactly. So, so, uh, now maybe we collectively as an industry need to figure out like, what are you liable for? Not legally, but like in a, in a management sense, uh, of these agents. All sorts of interesting problems that, that, that, uh, that have to come out.But in knowledge work, that's the real hostile environments that we're operating in. Hmm.swyx: I do think like, uh, a lot of the last year's, 2025 story was the rise of coding agents and I think [00:29:00] 2026 story is definitely knowledge work agents. Yes. A hundredAaron Levie: percent.swyx: Right. Like that would, and I think open claw core work are just the beginning.Yes. Like it's, the next one's gonna just gonna be absolute craziness.Aaron Levie: It it is. And, and, uh, and it's gonna be, I mean, again, like this is gonna be this, this wave where we, we are gonna try and bring as many of the practices from coding because that, that will clearly be the forefront, which is tell an agent to go do something and has an access to a set of resources.You need to be responsible for reviewing it at the end of the process. That to me is the, is the kind of template that I just think goes across knowledge, work and odd. Cowork is a great example. Open Closet's a great example. You can kind of, sort of see what Codex could become over time. These are some, some really interesting kind of platforms that are emerging.swyx: Okay. Um, I wanted to, we touched on evals a little bit. You had, you had the report that you're gonna go bring up and then I was gonna go into like, uh, boxes, evals, but uh, go ahead. Talk about your genetic search thing.Jeff Huber: Yeah. Mostly I think kinda a few of the insights. It's like number one frontier model is not good at search.Humans have this [00:30:00] natural explore, exploit trade off where we kinda understand like when to stop doing something. Also, humans are pretty good at like forgetting actually, and like pruning their own context, whereas agents are not, and actually an agent in their kind of context history, if they knew something was bad and they even, you could see in the trace the reason you trace, Hey, that probably wasn't a good idea.If it's still in the trace, still in the context, they'll still do it again. Uhhuh. Uh, and so like, I think pruning is also gonna be like, really, it's already becoming a thing, right? But like, letting self prune the con windowsswyx: be a big deal. Yeah. So, so don't leave the mistake. Don't leave the mistake in there.Cut out the mistake but tell it that you made a mistake in the past and so it doesn't repeat it.Jeff Huber: Yeah. But like cut it out so it doesn't get like distracted by it again. ‘cause really, you know, what is so, so it will repeat its mistake just because it's been, it's inswyx: theJeff Huber: context. It'sAaron Levie: in the context so much.That's a few shot example. Even if it, yeah.Jeff Huber: It's like oh thisAaron Levie: is a great thing to go try even ifJeff Huber: it didn't work.Aaron Levie: Yeah,Jeff Huber: exactly.Aaron Levie: SoJeff Huber: there's like a bunch of stuff there. JustAaron Levie: Groundhogs Day inside these models. Yeah. I'm gonna go keep doing the same wrongJeff Huber: thing. Covering sense. I feel like, you know, some creator analogy you're trying like fit a manifold in latent space, which kind is doing break program synthesis, which is kinda one we think about we're doing right.Like, you know, certain [00:31:00] facts might be like sort of overly pitting it. There are certain, you know, sec sectors of latent space and so like plug clean space. Yeah. And, uh, andswyx: so we have a bell, our editor as a bell every time you say that. SoJeff Huber: you have, you have to like remove those, likeswyx: you shoulda a gong like TPN or something.IfJeff Huber: we gong, you either remove those links to like kinda give it the freedom, kind of do what you need to do. So, but yeah. We'll, we'll release more soon. That'sAaron Levie: awesome.Jeff Huber: That'll, that'll be cool.swyx: We're a cerebral podcast that people listen to us and, and sort of think really deep. So yeah, we try to keep it subtle.Okay. We try to keep it.Aaron Levie: Okay, fine.Inside Agent Evalsswyx: Um, you, you guys do, you guys do have EVs, you talked about your, your office thing, but, uh, you've been also promoting APEX agents and complex work. Uh, yeah, whatever you, wherever you wanna take this just Yeah. How youAaron Levie: Apex is, is obviously me, core's, uh, uh, kind of, um, agent eval.We, we supported that by sort of. Opening up some data for them around how we kind of see these, um, data workspaces in, in the, you know, kind of regular economy. So how do lawyers have a workspace? How do investment bankers have a workspace? What kind of data goes into those? And so we, [00:32:00] we partner with them on their, their apex eval.Our own, um, eval is, it's actually relatively straightforward. We have a, a set of, of documents in a, in a range of industries. We give the agent previously did this as a one shot test of just purely the model. And then we just realized we, we need to, based on where everything's going, it's just gotta be more agentic.So now it's a bit more of a test of both our harness and the model. And we have a rubric of a set of things that has to get right and we score it. Um, and you're just seeing, you know, these incredible jumps in almost every single model in its own family of, you know, opus four, um, you know, sonnet four six versus sonnet four five.swyx: Yeah. We have this up on screen.Aaron Levie: Okay, cool. So some, you're seeing it somewhere like. I, I forget the to, it was like 15 point jump, I think on the main, on the overall,swyx: yes.Aaron Levie: And it's just like, you know, these incredible leaps that, that are starting to happen. Um,swyx: and OP doesn't know any, like any, it's completely held out from op.Aaron Levie: This is not in any, there's no public data which has, you know, Ben benefits and this is just a private eval that we [00:33:00] do, and then we just happen to show it to, to the world. Hmm. So you can't, you can't train against it. And I think it's just as representative of. It's obviously reasoning capabilities, what it's doing at, at, you know, kind of test time, compute capabilities, thinking levels, all like the context rot issues.So many interesting, you know, kind of, uh, uh, capabilities that are, that are now improvingswyx: one sector that you have. That's interesting.Industries and Datasetsswyx: Uh, people are roughly familiar with healthcare and legal, but you have public sector in there.Aaron Levie: Yeah.swyx: Uh, what's that? Like, what, what, what is that?Aaron Levie: Yeah, and, and we actually test against, I dunno, maybe 10 industries.We, we end up usually just cutting a few that we think have interesting gains. All extras, won a lot of like government type documents. Um,swyx: what is that? What is it? Government type documents?Aaron Levie: Government filings. Like a taxswyx: return, likeAaron Levie: a probably not tax returns. It would be more of what would go the government be using, uh, as data.So, okay. Um, so think about research that, that type of, of, of data sets. And then we have financial services for things like data rooms and what would be in an investment prospectus. Uhhuh,swyx: that one you can dog food.Aaron Levie: Yeah, exactly. Exactly. Yes. Yes. [00:34:00] So, uh, so we, we run the models, um, in now, you know, more of an agent mode, but, but still with, with kinda limited capacity and just try and see like on a, like, for like basis, what are the improvements?And, and again, we just continue to be blown away by. How, how good these models are getting.swyx: Yeah, I mean, I think every serious AI company needs something like that where like, well, this is the work we do. Here's our company eval. Yeah. And if you don't have it, well, you're not a serious AI company.Aaron Levie: There's two dimensions, right?So there's, there's like, how are the models improving? And so which models should you either recommend a customer use, which one should you adopt? But then every single day, we're making changes to our agents. And you need to knowswyx: if you regressed,Aaron Levie: if you know. Yeah. You know, I've been fully convinced that the whole agent observability and eval space is gonna be a massive space.Um, super excited for what Braintrust is doing, excited for, you know, Lang Smith, all the things. And I think what you're going to, I mean, this is like every enter like literally every enterprise right now. It's like the AI companies are the customers of these tools. Every enterprise will have this. Yeah, you'll just [00:35:00] have to have an eval.Of all of your work and like, we'll, you'll have an eval of your RFP generation, you'll have an eval of your sales material creation. You'll have an eval of your, uh, invoice processing. And, and as you, you know, buy or use new agentic systems, you are gonna need to know like, what's the quality of your, of your pipeline.swyx: Yeah.Aaron Levie: Um, so huge, huge market with agent evals.swyx: Yeah.Building the Agent Teamswyx: And, and you know, I'm gonna shout out your, your team a bit, uh, your CTO, Ben, uh, did a great talk with us last year. Awesome. And he's gonna come back again. Oh, cool. For World's Fair.Aaron Levie: Yep.swyx: Just talk about your team, like brag a little bit. I think I, I think people take these eval numbers in pretty charts for granted, but No, there, I mean, there's, there's lots of really smart people at work during all this.Aaron Levie: Biggest shout out, uh, is we have a, we have a couple folks at Dya, uh, Sidarth, uh, that, that kind of run this. They're like a, you know, kind of tag tag team duo on our evals, Ben, our CTO, heavily involved Yasha, head of ai, uh, you know, a bunch of folks. And, um, evals is one part of the story. And then just like the full, you know, kind of AI.An agent team [00:36:00] is, uh, is a, is a pretty, you know, is core to this whole effort. So there's probably, I don't know, like maybe a few dozen people that are like the epicenter. And then you just have like layers and layers of, of kind of concentric circles of okay, then there's a search team that supports them and an infrastructure team that supports them.And it's starting to ripple through the entire company. But there's that kind of core agent team, um, that's a pretty, pretty close, uh, close knit group.swyx: The search team is separate from the infra team.Aaron Levie: I mean, we have like every, every layer of the stack we have to kind of do, except for just pure public cloud.Um, but um, you know, we, we store, I don't even know what our public numbers are in, you know, but like, you can just think about it as like a lot of data is, is stored in box. And so we have, and you have every layer of the, of the stack of, you know, how do you manage the data, the file system, the metadata system, the search system, just all of those components.And then they all are having to understand that now you've got this new customer. Which is the agent, and they've been building for two types of customers in the past. They've been building for users and they've been building for like applications. [00:37:00] And now you've got this new agent user, and it comes in with a difference of it, of property sometimes, like, hey, maybe sometimes we should do embeddings, an embedding based, you know, kind of search versus, you know, your, your typical semantic search.Like, it's just like you have to build the, the capabilities to support all of this. And we're testing stuff, throwing things away, something doesn't work and, and not relevant. It's like just, you know, total chaos. But all of those teams are supporting the agent team that is kind of coming up with its requirements of what, what do we need?swyx: Yeah. No, uh, we just came from, uh, fireside chat where you did, and you, you talked about how you're doing this. It's, it's kind of like an internal startup. Yeah. Within the broader company. The broader company's like 3000 people. Yeah. But you know, there's, there's a, this is a core team of like, well, here's the innovation center.Aaron Levie: Yeah.swyx: And like that every company kind of is run this way.Aaron Levie: Yeah. I wanna be sensitive. I don't call it the innovation center. Yeah. Only because I think everybody has to do innovation. Um, there, there's a part of the, the, the company that is, is sort of do or die for the agent wave.swyx: Yeah.Aaron Levie: And it only happens to be more of my focus simply because it's existential that [00:38:00] we get it right.swyx: Yeah.Aaron Levie: All of the supporting systems are necessary. All of the surrounding adjacent capabilities are necessary. Like the only reason we get to be a platform where you'd run an agent is because we have a security feature or a compliance feature, or a governance feature that, that some team is working on.But that's not gonna be the make or break of, of whether we get agents right. Like that already exists and we need to keep innovating there. I don't know what the right, exact precise number is, but it's not a thousand people and it's not 10 people. There's a number of people that are like the, the kind of like, you know, startup within the company that are the make or break on everything related to AI agents, you know, leveraging our platform and letting you work with your data.And that's where I spend a lot of my time, and Ben and Yosh and Diego and Teri, you know, these are just, you know, people that, that, you know, kind of across the team. Are working.swyx: Yeah. Amazing.Read Write Agent WorkflowsJeff Huber: How do you, how do you think about, I mean, you talked a lot about like kinda read workflows over your box data. Yep.Right. You know, gen search questions, queries, et cetera. But like, what about like, write or like authoring workflows?Aaron Levie: Yes. I've [00:39:00] already probably revealed too much actually now that I think about it. So, um, I've talked about whatever,Jeff Huber: whatever you can.Aaron Levie: Okay. It's just us. It's just us. Yeah. Okay. Of course, of course.So I, I guess I would just, uh, I'll make it a little bit conceptual, uh, because again, I've already, I've already said things that are not even ga but, but we've, we've kinda like danced around it publicly, so I, yeah, yeah. Okay. Just like, hopefully nobody watches this, um, episode. No.swyx: It's tidbits for the Heidi engaged to go figure out like what exactly, um, you know, is, is your sort of line of thinking.Sure. They can connect the dots.Aaron Levie: Yeah. So, so I would say that, that, uh, we, you know, as a, as a place where you have your enterprise content, there's a use case where I want to, you know, have an agent read that data and answer questions for me. And then there's a use case where I want the agent to create something.And use the file system to create something or store off data that it's working on, or be able to have, you know, various files that it's writing to about the work it's doing. So we do see it as a total read write. The harder problem has so far been the read only because, because again, you have that kind of like 10 [00:40:00] million to one ratio problem, whereas rights are a lot of, that's just gonna come from the model and, and we just like, we'll just put it in the file system and kinda use it.So it's a little bit of a technically easier problem, but the only part that's like, not necessarily technically hard, it is just like it's not yet perfected in the state of the ecosystem is, you know, building a beautiful PowerPoint presentation. It's still a hard problem for these models. Like, like we still, you know, like, like these formats are just, we're not built for.They'reswyx: working on it.Aaron Levie: They're, they're working on it. Everybody's working on it.swyx: Every launch is like, well, we do PowerPoint now.Aaron Levie: We're getting, yeah, getting a lot, getting a lot of better each time. But then you'll do this thing where you'll ask the update one slide and all of a sudden, like the fonts will be just like a little bit different, you know, on two of the slides, or it moved, you know, some shape over to the left a little bit.And again, these are the kind of things that, like in code, obviously you could really care about if you really care about, you know, how beautiful is the code, but at the end, user doesn't notice all those problems and file creation, the end user instantly sees it. You're [00:41:00] like, ah, like paragraph three, like, you literally just changed the font on me.Like it's a totally different font and like midway through the document. Mm-hmm. Those are the kind of things that you run into a lot of in the, in the content creation side. So, mm-hmm. We are gonna have native agents. That do all of those things, they'll be powered by the leading kind of models and labs.But the thing that I think is, is probably gonna be a much bigger idea over time is any agent on any system, again, using Box as a file system for its work, and in that kind of scenario, we don't necessarily care what it's putting in the file system. It could put its memory files, it could put its, you know, specification, you know, documents.It could put, you know, whatever its markdown files are, or it could, you know, generate PDFs. It's just like, it's a workspace that is, is sort of sandboxed off for its work. People can collaborate into it, it can share with other people. And, and so we, we were thinking a lot about what's the right, you know, kind of way to, to deliver that at scale.Docs Graphs and Founder Modeswyx: I wanted to come into sort of the sort of AI transformation or AI sort of, uh, operations things. [00:42:00] Um, one of the tweets that you, that you wanted to talk about, this is just me going through your tweets, by the way. Oh, okay. I mean, like, this is, you readAaron Levie: one by one,swyx: you're the, you're the easiest guest to prep for because you, you already have like, this is the, this is what I'm interested in.I'm like, okay, well, areAaron Levie: we gonna get to like, like February, January or something? Where are we in the, in the timelines? How far back are we going?swyx: Can you, can you describe boxes? A set of skills? Right? Like that, that's like, that's like one of the extremes of like, well if you, you just turn everything into a markdown file.Yeah. Then your agent can run your company. Uh, like you just have to write, find the right sequence of words toAaron Levie: Yes.swyx: To do it.Aaron Levie: Sorry, isthatswyx: the question? So I think the question is like, what if we documented everything? Yes. The way that you exactly said like,Aaron Levie: yes.swyx: Um, let's get all the Fortune five hundreds, uh, prepared for agents.Yes. And like, you know, everything's in golden and, and nicely filed away and everything. Yes. What's missing? Like, what's left, right? LikeAaron Levie: Yeah.swyx: You've, you've run your company for a decade. LikeAaron Levie: Yeah. I think the challenge is that, that that information changes a week later. And because something happened in the market for that [00:43:00] customer, or us as a company that now has to go get updated, and so these systems are living and breathing and they have to experience reality and updates to reality, which right now is probably gonna be humans, you know, kinda giving those, giving them the updates.And, you know, there is this piece about context graphs as as, uh, that kinda went very viral. Yeah. And I, I, I was like a, i, I, I thought it was super provocative. I agreed with many parts of it. I disagree with a few parts around. You know, it's not gonna be as easy as as just if we just had the agent traces, then we can finally do that work because there's just like, there's so much more other stuff that that's happening that, that we haven't been able to capture and digitize.And I think they actually represented that in the piece to be clear. But like there's just a lot of work, you know, that that has to, you just can't have only skills files, you know, for your company because it's just gonna be like, there's gonna be a lot of other stuff that happens. Yeah. Change over time.Yeah. Most companies are practically apprenticeships.swyx: Most companies are practically apprenticeships. LikeJeff Huber: every new employee who joins the team, [00:44:00] like you span one to three months. Like ramping them up.Aaron Levie: Yes. AllJeff Huber: that tat knowledgeAaron Levie: isJeff Huber: not written down.Aaron Levie: Yes.Jeff Huber: But like, it would have to be if you wanted to like give it to an Asian.Right. And so like that seems to me like to beAaron Levie: one is I think you're gonna see again a premium on companies that can document this. Mm-hmm. Much. There'll be a huge premium on that because, because you know, can you shorten that three month ramp cycle to a two week ramp cycle? That's an instant productivity gain.Can you re dramatically reduce rework in the organization because you've documented where all the stuff is and where the answers are. Can you make your average employee as good as your 90th percentile employee because you've captured the knowledge that's sort of in the heads of, of those top employees and make that available.So like you can see some very clear productivity benefits. Mm-hmm. If you had a company culture of making sure you know your information was captured, digitized, put in a format that was agent ready and then made available to agents to work with, and then you just, again, have this reality of like add a 10,000 person [00:45:00] company.Mapping that to the, you know, access structure of the company is just a hard problem. Is like, is like, yeah, well, you just, not every piece of information that's digitized can be shared to everybody. And so now you have to organize that in a way that actually works. There was a pretty good piece, um, this, this, uh, this piece called your company as a file is a file system.I, did you see that one?swyx: Nope.Aaron Levie: Uh, yes. You saw it. Yeah. And, and, uh, I actually be curious your thoughts on it. Um, like, like an interesting kind of like, we, we agree with it because, because that's how we see the world and, uh,swyx: okay. We, we have it up on screen. Oh,Aaron Levie: okay. Yeah. But, but it's all about basically like, you know, we've already, we, we, we already organized in this kind of like, you know, permission structure way.Uh, and, and these are the kind of, you know, natural ways that, that agents can now work with data. So it's kind of like this, this, you know, kind of interesting metaphor, but I do think companies will have to start to think about how they start to digitize more, more of that data. What was your take?Jeff Huber: Yeah, I mean, like the company's probably like an acid compliant file system.Aaron Levie: Uh,Jeff Huber: yeah. Which I'm guessing boxes, right? So, yeah. Yes.swyx: Yeah. [00:46:00]Jeff Huber: Which you have a great piece on, but,swyx: uh, yeah. Well, uh, I, I, my, my, my direction is a little bit like, I wanna rewind a little bit to the graph word you said that there, that's a magic trigger word for us. I always ask what's your take on knowledge graphs?Yeah. Uh, ‘cause every, especially at every data database person, I just wanna see what they think. There's been knowledge graphs, hype cycles, and you've seen it all. So.Aaron Levie: Hmm. I actually am not the expert in knowledge graphs, so, so that you might need toswyx: research, you don't need to be an expert. Yeah. I think it's just like, well, how, how seriously do people take it?Yeah. Like, is is, is there a lot of potential in the, in the HOVI?Aaron Levie: Uh, well, can I, can I, uh, understand first if it's, um, is this a loaded question in the sense of are you super pro, super con, super anti medium? Iswyx: see pro, I see pros and cons. Okay. Uh, but I, I think your opinion should be independent of mine.Aaron Levie: Yeah. No, no, totally. Yeah. I just want to see what I'm stepping into.swyx: No, I know. It's a, and it's a huge trigger word for a lot of people out Yeah. In our audience. And they're, they're trying to figure out why is that? Because whyAaron Levie: is this such aswyx: hot item for them? Because a lot of people get graph religion.And they're like, everything's a graph. Of course you have to represent it as a graph. Well, [00:47:00] how do you solve your knowledge? Um, changing over time? Well, it's a graph.Aaron Levie: Yeah.swyx: And, and I think there, there's that line of work and then there's, there's a lot of people who are like, well, you don't need it. And both are right.Aaron Levie: Yeah. And what do the people who say you don't need it, what are theyswyx: arguing for Mark down files. Oh, sure, sure. Simplicity.Aaron Levie: Yeah.swyx: Versus it's, it's structure versus less structure. Right. That's, that's all what it is. I do.Aaron Levie: I think the tricky thing is, um, is, is again, when this gets met with real humans, they're just going to their computer.They're just working with some people on Slack or teams. They're just sharing some data through a collaborative file system and Google Docs or Box or whatever. I certainly like the vision of most, most knowledge graph, you know, kind of futuristic kind of ways of thinking about it. Uh, it's just like, you know, it's 2026.We haven't seen it yet. Kind of play out as as, I mean, I remember. Do you remember the, um, in like, actually I don't, I don't even know how old you guys are, but I'll for, for to show my age. I remember 17 years ago, everybody thought enterprises would just run on [00:48:00] Wikis. Yeah. And, uh, confluence and, and not even, I mean, confluence actually took off for engineering for sure.Like unquestionably. But like, this was like everything would be in the w. And I think based on our, uh, our, uh, general style of, of, of what we were building, like we were just like, I don't know, people just like wanna workspace. They're gonna collaborate with other people.swyx: Exactly. Yeah. So you were, you were anti-knowledge graph.Aaron Levie: Not anti, not anti. Soswyx: not nonAaron Levie: I'm not, I'm not anti. ‘cause I think, I think your search system, I just think these are two systems that probably, but like, I'm, I'm not in any religious war. I don't want to be in anybody's YouTube comments on this. There's not a fight for me.swyx: We, we love YouTube comments. We're, we're, we're get into comments.Aaron Levie: Okay. Uh, but like, but I, I, it's mostly just a virtue of what we built. Yeah. And we just continued down that path. Yeah.swyx: Yeah.Aaron Levie: And, um, and that, that was what we pursued. But I'm not, this is not a, you know, kind of, this is not a, uh, it'sswyx: not existential for you. Great.Aaron Levie: We're happy to plug into somebody else's graph.We're happy to feed data into it. We're happy for [00:49:00] agents to, to talk to multiple systems. Not, not our fight.swyx: Yeah.Aaron Levie: But I need your answer. Yeah. Graphs or nerd Snipes is very effective nerd.swyx: See this is, this is one, one opinion and then I've,Jeff Huber: and I think that the actual graph structure is emergent in the mind of the agent.Ah, in the same way it is in the mind of the human. And that's a more powerful graph ‘cause it actually involved over time.swyx: So don't tell me how to graph. I'll, I'll figure it out myself. Exactly. Okay. All right. AndJeff Huber: what's yours?swyx: I like the, the Wiki approach. Uh, my, I'm actually
Guest post by Lee Bryan Tech leaders in regulated consumer product sectors who treat regulation as a game of hide and seek eventually get found. Across the UK and EU, the same pattern keeps repeating in sectors like consumer electronics, cosmetics, children's toys, PPE, sex toys, and novel nicotine products. A brand scales quickly, leans on a grey area in product classification, stretches a claims boundary, exploits a labelling technicality, or relies on an under-resourced enforcement body. Compliance, the Loophole Loop and Tech Leaders Revenue spikes. Marketplaces open up. Influencers amplify the product. Then enforcement catches up. Listings are removed. Products are detained. Responsible Persons are scrutinised. Documentation is demanded. Fines land. The same leadership team that once celebrated "moving fast" now scrambles to explain what went wrong. This is the Loophole Loop. It is the cycle of exploiting regulatory gaps, triggering scrutiny, reacting under pressure, and then searching for the next workaround. It feels strategic in the short term. It is structurally weak in the long term. The Cat-and-Mouse Illusion Many founders in regulated consumer markets see compliance as friction imposed by bureaucrats who do not understand innovation. Regulations feel slow. Guidance feels ambiguous. Enforcement feels inconsistent. So the internal logic becomes: The regulation is vague. The guidance is outdated. The enforcement body is stretched. There is no clear precedent yet. Therefore, we are safe. That assumption no longer holds. UK and EU authorities are increasingly deploying automation and AI-powered investigation and enforcement tools. What once required physical inspections or whistleblowers can now be identified remotely and at scale. Product listings are scraped automatically. Packaging artwork is analysed through image recognition. Claims are scanned for trigger words. Marketplace data is cross-referenced with customs records. Corporate structures are mapped across jurisdictions. The cost of being "under the radar" has collapsed. What used to be a slow-moving chess match is now algorithmic risk detection. Why the Loophole Loop Is Shrinking The gap between innovation and enforcement in regulated consumer products is narrowing for three structural reasons. First, digital transparency. Even physical product businesses are now digitally exposed. Websites, Amazon listings, TikTok ads, influencer partnerships, shipping data, and online reviews create an open data trail. Every aggressive claim leaves evidence. Second, cross-border intelligence. UK and EU authorities increasingly share information. A packaging issue flagged in one member state can trigger scrutiny elsewhere. The idea that a brand is "small" or "flying under the radar" rarely reflects reality in a digital marketplace. Third, automated triage. Enforcement bodies do not need to manually inspect every operator. They can prioritise risk using signals. Rapid sales growth. High-risk product categories. Missing UK Responsible Persons or EU Authorised Representatives. Inconsistent Declarations of Conformity. Unsupported marketing claims. These are patterns that machines can detect. If your growth strategy depends on staying invisible, it is already outdated. The Real Cost of Playing the Game The Loophole Loop produces four predictable outcomes for tech-enabled consumer brands. 1. Strategic instability. Product pivots become driven by regulatory panic rather than customer insight. 2. Investor friction. Serious investors now conduct regulatory diligence earlier. A business model built on definitional technicalities looks fragile. 3. Brand damage. In sectors involving children, safety, chemicals, or electronics, public enforcement action erodes trust quickly and permanently. 4. Margin destruction. Retrospective remediation is expensive. Relabelling. Reformulation. Product withdrawal. Storage fees. Legal advice. Emergency compliance audits. All destroy cash. The irony is s...
Discover how Heatblur approaches the realistic modeling of the F-4 Phantom, including system fidelity, flight dynamics, and community-driven development. This episode offers an in-depth look into the challenges and triumphs of creating one of the most detailed aircraft simulations to date.Key Topics:The historical significance and design philosophy behind the F-4 PhantomResearch and data collection methods, including dealing with classified info and declassified manualsBuilding a flexible, component-based simulation framework (Anvil) for modular developmentFlight model accuracy: physics calculations versus lookup tables, handling, and aerodynamic nuancesThe modeling of aircraft systems such as hydraulics, electrical power consumption, and crew interface features like grease pencilsEmulating aircraft wear, damage, and the visual storytelling of maintenance historyThe importance of crew dynamics and simulating multi-crew operations through Jester and RIO AIFuture plans: Navy variants, electronic upgrades like D-MASS, and expanding the aircraft's historical variantsUnique challenges posed by foreign and museum aircraft modeling, including authenticity in cockpit wear and operational quirksCommunity collaboration and feedback in refining the module post-releaseResources & Links:Heatblur SimulationsJester AI SystemDCS World Official SiteHistorical F-4 Manuals & DocumentationF-4 Phantom in DCSNote: This episode dives into technical and historical details to serve both aviation enthusiasts and sim pilots aiming for immersion. For specific modeling insights, system breakdowns, and future plans, stay tuned until the end! Hosted on Acast. See acast.com/privacy for more information.
Tight margins and wild market swings are back in the driver's seat—and producers are feeling it. Recorded at the Central Oklahoma Cattle Conference in Stillwater, Episode 508 features Clay Burtrum (Farm Data Services) walking through why insurance matters even when you hope you never use it. The crew digs into Livestock Risk Protection (LRP) basics, how price protection actually works, and what producers often misunderstand when they start using these tools. On the crop side, Clay outlines the deadlines and decisions that can make or break your coverage—plus how to think about programs like PRF (Pasture, Rangeland, Forage), annual forage, and stacking options without getting lost in the fine print. Bottom line: in a $4 wheat world with 2026 input costs, staying “bankable” means planning ahead and knowing what you bought. Top 10 takeaways Insurance is about staying bankable, not just getting a payout. LRP is price protection, not mortality/disaster coverage—know what it does. Documentation matters (example: “unborn” coverage needs validation like preg-check/bred purchase records). Stocker operators often treat LRP as all-or-nothing because margin risk is concentrated. Cow-calf operations can sometimes phase coverage, spreading risk across calf crop timing. Crop insurance complexity is real—stackable options exist, but basics come first in tight years. Deadlines drive everything (in this area, March 15 is a big one; waiting too long is a common pitfall). $4 wheat changes decisions—coverage, hail policies, and whether you even harvest vs graze-out. PRF is “rainfall interval” insurance—pick when you need rain and spread risk; it won't cover every scenario (like quality loss from too much rain). Know your cost of production—break-even won't keep you in business; cash flow clarity is survival. Detailed timestamped rundown 00:00–01:46 Dave tees up the episode: why insurance matters, recorded at Central Oklahoma Cattle Conference (Stillwater).01:46–02:57 Clay Burtrum intro: Farm Data Services (Stillwater), management accounting + 25+ years insurance; LRP and crop insurance, plus helping producers see bottom line year-round.03:16–04:45 Big-picture ag economy: grain-only operators squeezed; modern costs with “1970s prices”; crop insurance complexity (stackable programs) and need to keep it basic.04:45–08:43 LRP deep dive: example of insuring a 900-lb steer; why margins need protection; common misunderstandings (full load, unborn coverage requirements, validation); “don't let it burn down” analogy; all-or-nothing for many stocker operators vs partial strategy for cow-calf.08:43–10:27 First-time client conversation: goals, where they want to be, staying bankable; traps include ignoring USDA/FSA programs and missing support.10:27–11:25 Clay as producer: he uses the products himself; emphasizes knowing cost of production and that break-even won't keep you in business.11:26–12:50 Crop insurance pitfalls: calling too late; major dates in the area—March 15 sales closing; July 15 reporting; flow of deadlines through the season.12:50–14:18 $4 wheat vs $7 wheat decisions: changes appetite for added coverage/hail; producer mindset shifts (harvest vs graze-out).14:18–15:38 Dual-purpose wheat and insurance: need to notify agent by March 15/short-rate timing; cannot just “leave cattle out” without process; consider double-crop rules to avoid uninsured crop risk.15:38–17:14 Policy/program landscape: farm bill uncertainty and “rules”; emphasis on working with FSA and not missing deadlines/opportunities.17:14–18:51 Specialty crop/alternative ideas: limited locally; examples like hemp market issues; unusual inquiries (tulips) and regional eligibility realities.18:51–21:45 PRF pasture coverage: sales closing Dec 1; choosing rainfall intervals; premiums and changing rules; spreading risk across intervals; limits (doesn't cover “missed cutting” quality loss).21:45–24:05 Talking to policymakers: how programs hit local bottom lines; input costs for grazing/forage; how rural communities feel downstream impacts; even equipment/emissions issues affect harvest reality.24:05–25:43 Oklahoma risk reality: rapid weather swings; questions like quarantine/screwworm, wildfire loss—what LRP does/doesn't cover; importance of understanding what you actually bought.25:43–27:20 “Bring one program back”: Clay wants simplicity—too many stacked options; focus on basics and bottom-line impact. Wrap + thanks. RedDirtAgronomy.com
Katie Turner is a psychic and ghost hunter known for combining intuitive perception with onsite paranormal investigations. Turner explores reported hauntings, spirit activity, and anomalous environments by blending empathic sensitivity with historical research and field documentation. Her work focuses on understanding the emotional and environmental context of alleged hauntings while encouraging respectful, ethical approaches to investigating unexplained phenomena.Become a supporter of this podcast: https://www.spreaker.com/podcast/the-x-zone-radio-tv-show--1078348/support.Please note that all XZBN radio and/or television shows are Copyright © REL-MAR McConnell Meda Company, Niagara, Ontario, Canada – www.rel-mar.com. For more Episodes of this show and all shows produced, broadcasted and syndicated from REL-MAR McConell Media Company and The 'X' Zone Broadcast Network and the 'X' Zone TV Channell, visit www.xzbn.net. For programming, distribution, and syndication inquiries, email programming@xzbn.net.We are proud to announce the we have launched TWATNews.com, launched in August 2025.TWATNews.com is an independent online news platform dedicated to uncovering the truth about Donald Trump and his ongoing influence in politics, business, and society. Unlike mainstream outlets that often sanitize, soften, or ignore stories that challenge Trump and his allies, TWATNews digs deeper to deliver hard-hitting articles, investigative features, and sharp commentary that mainstream media won't touch.These are stories and articles that you will not read anywhere else.Our mission is simple: to expose corruption, lies, and authoritarian tendencies while giving voice to the perspectives and evidence that are often marginalized or buried by corporate-controlled media
Today we are talking about The Good and the Bad of AI , How our panel feels about AI , and you guessed it more AI with guest Scott Falconer. We'll also cover Field Widget Actions as our module of the week. For show notes visit: https://www.talkingDrupal.com/542 Topics AI and Social Isolation How We Use AI Friction and Independence Stack Overflow Debate Collaboration and Team Culture Is AI Inevitable AI Hype Meets Costs Adoption Cooling Signals Pricing Inequality Risks Open Source and PRs Requirements and LLMs Easy Tools Not Always Right Juniors Learning and Patterns Human Value and Ambiguity Losing Cognitive Endurance AI vs Social Media Uniquely Human Skills Resources Stack overflow Guests Scott Falconer - managing-ai.com scott-falconer Hosts Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Catherine Tsiboukas - mindcraftgroup.com bletch MOTW Correspondent Martin Anderson-Clutz - mandclu.com mandclu Brief description: Have you ever wanted to enhance the Drupal content editing experience by allowing site builders to attach actionable buttons directly to field widgets on entity forms? There's a module for that. Module name/project name: Field Widget Actions Brief history How old: created in Oct 2025 by Artem Dmitriiev (a.dmitriiev) of 1x Internet, a founding member of the AI Initiative Versions available: 1.0.0-alpha1 and 1.3.0, both of which works with Drupal 10.3 and 11.1 or newer Maintainership Actively maintained Security coverage Test coverage Documentation - includes Markdown files that explain how to set up and extend its capabilities Number of open issues: 12 open issues, 4 of which are bugs Usage stats: 24 sites Module features and usage With this module installed, a site builder can attach action buttons to form fields in Drupal entity forms, for example for creating nodes or taxonomy terms What happens when you click a button depends on what processor you associate with it, and the settings you configure for the processor. Processors can be provided by other modules, like AI or ECA. For example, you could attach a button to a tags field that when clicked will send the content of the body field to an AI agent that will return a set of suggested tags. Or, you could have it trigger an ECA model for a more deterministic flow This is all done using a plugin framework implemented by Field Widget Actions, so you also create your own custom processors to be used with action buttons One of the things that got me excited about working with the team behind Augmentor AI was the approach that module used to make AI something a user would manually trigger, and then can curate before the suggestions are saved. Field Widget Actions allows that same approach to be implemented with the AI ecosystem that is growing by leaps and bounds thanks to the team involved with Drupal's AI Initiative It's worth noting that Field Widget Actions used to be a submodule of the AI project, so if you're using a version of that older than 2.0, you may already have Field Widget Actions available in your codebase
Manager Minute-brought to you by the VR Technical Assistance Center for Quality Management
VR burnout isn't about caring too little. It's about caring so much… while buried in documentation. In this episode of Manager Minute, VR counselor Stephanie Nelson shares how she built VocRehabTools.com — a free collection of smart, practical tools (both AI-powered and non-AI) designed to give counselors their time back.
Jeff Yelek is a Sasquatch researcher focused on examining eyewitness reports, environmental patterns, and field observations related to Bigfoot phenomena. Yelek's work emphasizes careful documentation, site investigation, and critical review of evidence such as tracks, sounds, and reported encounters. His approach encourages open inquiry balanced with scrutiny, placing Sasquatch research within the broader discussion of cryptozoology, wildlife biology, and the challenges of verifying extraordinary claims.Become a supporter of this podcast: https://www.spreaker.com/podcast/the-x-zone-radio-tv-show--1078348/support.Please note that all XZBN radio and/or television shows are Copyright © REL-MAR McConnell Meda Company, Niagara, Ontario, Canada – www.rel-mar.com. For more Episodes of this show and all shows produced, broadcasted and syndicated from REL-MAR McConell Media Company and The 'X' Zone Broadcast Network and the 'X' Zone TV Channell, visit www.xzbn.net. For programming, distribution, and syndication inquiries, email programming@xzbn.net.We are proud to announce the we have launched TWATNews.com, launched in August 2025.TWATNews.com is an independent online news platform dedicated to uncovering the truth about Donald Trump and his ongoing influence in politics, business, and society. Unlike mainstream outlets that often sanitize, soften, or ignore stories that challenge Trump and his allies, TWATNews digs deeper to deliver hard-hitting articles, investigative features, and sharp commentary that mainstream media won't touch.These are stories and articles that you will not read anywhere else.Our mission is simple: to expose corruption, lies, and authoritarian tendencies while giving voice to the perspectives and evidence that are often marginalized or buried by corporate-controlled media
(Deuxième et dernier épisode) À Nice, en octobre 2011, Mayeul Gaden ne donne plus de nouvelles à ses proches. Un an auparavant, ce jeune homme de 20 ans a fondé un club de bikers, les “Fenry”. Petite particularité : ils n'ont de motards que le nom. Les membres du club partagent une idéologie raciste et une fascination pour la violence. Devenu une sorte de gourou pour la dizaine de membres du groupe, Mayeul, qui se fait appeler Karl, a l'image d'un garçon charismatique mais aussi très autoritaire. Quinze mois passent, sans nouvelle de Mayeul. Jusqu'à ce que le lundi 16 décembre 2012, un peu plus d'un an après sa disparition, une jeune fille de 19 ans pousse la porte du commissariat de Grasse et fasse basculer l'affaire.Dans Crime story, la journaliste Clawdia Prolongeau raconte cette enquête avec Damien Delseny, chef du service police-justice du Parisien.Crédits. Direction de la rédaction : Pierre Chausse - Rédacteur en chef : Jules Lavie - Ecriture et voix : Clawdia Prolongeau et Damien Delseny - Production : Clara Garnier-Amouroux, Anaïs Godard et Thibault Lambert - Réalisation et mixage : Julien Montcouquiol - Musiques : Audio Network, Archives : Nice Matin.Documentation. Cet épisode de Crime story a été préparé en puisant dans les archives du Parisien, avec l'aide de nos documentalistes ainsi que les ressources suivantes : Nice Matin. Hébergé par Acast. Visitez acast.com/privacy pour plus d'informations.
(Premier épisode) À Nice, en octobre 2011, Mayeul Gaden ne donne plus de nouvelles à ses proches. Un an auparavant, ce jeune homme de 20 ans a fondé un club de bikers, les “Fenry”. Petite particularité : ils n'ont de motards que le nom. Les membres du club partagent une idéologie raciste et une fascination pour la violence. Devenu une sorte de gourou pour la dizaine de membres du groupe, Mayeul, qui se fait appeler Karl, a l'image d'un garçon charismatique mais aussi très autoritaire. Quinze mois passent, sans nouvelle de Mayeul. Jusqu'à ce que le lundi 16 décembre 2012, un peu plus d'un an après sa disparition, une jeune fille de 19 ans pousse la porte du commissariat de Grasse et fasse basculer l'affaire.Dans Crime story, la journaliste Clawdia Prolongeau raconte cette enquête avec Damien Delseny, chef du service police-justice du Parisien.Crédits. Direction de la rédaction : Pierre Chausse - Rédacteur en chef : Jules Lavie - Ecriture et voix : Clawdia Prolongeau et Damien Delseny - Production : Clara Garnier-Amouroux, Anaïs Godard et Thibault Lambert - Réalisation et mixage : Julien Montcouquiol - Musiques : Audio Network, Archives : Nice Matin.Documentation. Cet épisode de Crime story a été préparé en puisant dans les archives du Parisien, avec l'aide de nos documentalistes ainsi que les ressources suivantes : Nice Matin. Hébergé par Acast. Visitez acast.com/privacy pour plus d'informations.
Building a Strong Team: Leadership, Systems & Process Documentation for Business GrowthAre you trying to grow your business but feel stuck doing everything yourself?In this video, we break down the real foundation of sustainable business growth: building the right team, leading with clarity, and documenting systems and processes that create consistency and scalability.Strong leadership sets the vision.A solid team executes the mission.Documented systems protect your time, culture, and profitability.Stop rebuilding the wheel. Start building a structure that lasts.Watch Marketing with Russ...aka #RussSelfie, Episode 596Featuring Jessper Maquindang
We trace how Ohio Yearly Meeting Conservative met World War I with organized peace witness, pastoral care for draftees, and a growing international outlook. Youth energy, AFSC partnerships, and courageous visits to power reframed what Quaker service could be.• Prewar lobbying and prophetic ministry to national leaders• Formation of a peace and service committee• Guidance for young men facing the draft• Camp visits, CO status, and varied refusals• Documentation of abuse and push for reforms• The Halfway Picnic and youth-led initiatives• Evening meetings that widened outlook and cooperation• Postwar renewal, intergenerational tensions, and unity in worshipA complete list of our podcasts, organized into topics, is available on our website. To learn more about Ohio Yearly Meeting (Conservative) of the Religious Society of Friends (Quakers), please visit ohioyearlymeeting.org. Those interested in exploring the distinctives of Conservative Friends waiting worship should consider checking out our many Zoom Online Worship opportunities during the week here. All are welcome! We also have several Zoom study groups. Check out the Online Study and Discussion Groups on our website. Advices read in these podcasts can be found on page 29 in our Book Of Discipline. We welcome feedback on this and any of our other podcast episodes. Contact us through our website.
Send a textAre You Coaching… or Just Commenting?You can observe lessons all day long. You can write detailed notes. You can even have thoughtful post-observation meetings.But if instruction isn't changing, something is missing.In this episode, we're talking about feedback conversations that actually produce growth. Not compliance. Not documentation. Not polite agreement. Real instructional movement.You'll learn:Why anchoring feedback in student learning (not teacher behavior) lowers defensiveness and increases impactHow to use John Hattie's three feedback questions — Where are they going? How are they going? Where to next? — to structure powerful conversationsWhy narrowing to one high-leverage action step increases implementationHow rehearsal during feedback meetings dramatically improves next-day executionThe difference between isolated feedback and true coaching cyclesThis episode challenges you to examine your leadership approach:Are teachers leaving your office inspired — or equipped?Because effective instructional leadership isn't about pointing out gaps. It's about building teacher capacity over time.If you're serious about moving from evaluator to coach, this conversation will help you sharpen your practice and strengthen your impact.Support the showDownload Upside and use my code MELINDA35278 to get 15¢ per gallon extra cash back on your first gas fill-up and 10% extra cash on your first food purchase! Download Fetch app using this link, submit a receipt and we'll both score bonus points. Calling All Educators! I started a community with resources, courses, articles, networking, and more. I am looking for members to help me build it with the most valuable resources. I would really appreciate your input as a teacher, leader, administrator, or consultant. Join here: Empowered Educator Community Book: Educator to Entrepreneur: IGNITE Your Path to Freelance SuccessGrab a complimentary POWER SessionWith Rubi.ai, you'll experience cutting-edge technology, research-driven insights, and efficient content delivery.email: melinda@empowere...
durée : 00:05:50 - Le Journal de l'éco - par : Anne-Laure Chouin - Cinquième et dernier épisode de notre série consacrée aux élections municipales et aux pouvoirs économiques entre les mains des maires. On parle ce matin de santé, et en particulier d'accès aux soins de proximité. - invités : Julien Mousquès Enseignant chercheur à l'Ecole des Hautes Etudes en Santé Publique (EHESP) dans le département Sciences Humaines et Sociales, directeur de recherche à l'IRDES (Institut de Recherche et Documentation en Economie de la Santé) et membre du CA du Collège des économistes de la santé
There comes a point in many therapy careers where working harder is no longer the solution. You can raise your fees. You can tighten your cancellation policy. You can fill every slot on your calendar. And still feel financially vulnerable.In this episode, Ashley Stephens and I explore why supervision often becomes the smarter revenue stream at that stage. Not because it is easy. Not because it is trendy. But because it is structurally different from therapy income.Supervision is tied to licensure. Associates are required to have it in order to practice and accrue hours. That built-in demand creates a level of predictability that weekly therapy referrals simply do not. When designed intentionally, supervision can become a steady arm of your income instead of a reactive scramble.We also slow down and talk about ethics. Required does not mean exploitative. Supervisees deserve clarity, transparency, and the ability to reassess the relationship. Supervisors have obligations too. Contracts matter. Review points matter. Documentation matters. When those systems are in place, supervision supports both parties instead of draining them.And we address the legal realities. Supervising across state lines is not something you assume your way into. The compact does not automatically grant supervision privileges. Most states require full licensure and specific supervisor training. Getting this wrong can cost a supervisee their hours. That is not a risk worth taking.In this episode, we discuss:How supervision creates more predictable income than session-based therapy aloneThe difference between stable revenue and predatory practicesWhy long-term supervisory relationships can reduce burnoutWhat to confirm before offering supervision in another stateIf you have been thinking about adding supervision to your practice or shifting more fully into it, this conversation will help you evaluate that decision through an ethical and business lens. Not as a side hustle. Not as a last resort. But as a deliberate professional move.Download our free resource, Stop Working for Free: The Therapist Fee Reset, to identify where your practice may be leaking money.And if you are ready to build supervision into your model with strong systems and clean boundaries, that is exactly what we teach inside our Step It Up Membership.Get your step by step guide to private practice. Because you are too important to lose to not knowing the rules, going broke, burning out, and giving up. #counselorsdontquit.
Pool Pros text questions hereWayne goes full soapbox after watching an HGTV/Magnolia renovation show that builds a commercial-style pool using “biofilters” as a chemical-free solution—without ever addressing sanitation, oxidation, or code-required disinfectant residuals. Steve backs him up with real-world field logic: filtration doesn't equal disinfection, and “natural” systems can turn into expensive science projects fast.Then the episode shifts into the Insurance Interlude with Pat Grignon (California Pool Association), digging into warranty claims, liability, how insurance carriers investigate faults, and why documentation (photos/video/notes) protects your business for years.Segment 1 — Wayne's HGTV rant: Biofilters, “natural pools,” and reality TV chemistry (00:00–25:14)Key takeawaysFiltration is not sanitation. Even DE filtration doesn't catch bacteria/viruses reliably because pathogens are below typical filter micron ratings.Biofilters often rely on nitrifying bacteria (Wayne names Nitrosomonas and Nitrobacter) that convert:ammonia → nitrites → nitratesWayne's red flag: nitrates feed algae, and there's no easy chemical “undo” once nitrates climb—drain and replace is often the only practical correction.Real-world reality check: if bathers are involved, ammonia shows up (sweat/urine), and you still need an actual sanitizer system.The pool “looked great” on reveal day… but nobody wanted to get in (which Steve jokes is basically the fate of many pools anyway).Wayne predicts the biofilter setup becomes a regret purchase—$15,000 spent before eventually converting to conventional filtration + sanitation.Quoteable moments“Natural pool” = Wayne's eyes bug out.“People want to swim in water, not chemicals… but safe water takes chemistry.”Steve's “pimp my ride but for houses” comparison for the show's projects.Segment 2 — Insurance Interlude w/ Pat Grignon: Warranty work, liability, and documenting the mess (25:14–40:18)What's coveredSteve explains the reality of warranty service: no urgency unless someone becomes the “pain in the ass” pushing it forward.Pat outlines how manufacturers protect themselves:Warranty/service stations often required to carry high insurance limits and endorsements that shield the manufacturer.Waiver of subrogation explained:Normally, your insurer pays then may subrogate (recover) from a manufacturer if a defect caused the loss.Waiver blocks that upstream recovery—so your policy can get stuck holding the bag even when the part was defective.Notable mentionsHGTV / Magnolia Network renovation show: “Building Outside the Lines”Movie drop: True Romance (Hans Zimmer soundtrack, Tarantino script)Brands mentioned in discussion/examples: Hayward, Jandy (AquaLink), Pentair, plus references to warranty stations and commercial systems.Call to action (from the hosts)Got a technical question or topic idea? Email: TalkingPools at gmail.com Wayne says if your question makes it onto the show, he'll send a small thank-you gift. Support the showThank you so much for listening! You can find us on social media: Facebook Instagram Tik Tok Email us: talkingpools@gmail.com
It's tax season — which means farmers, ag business owners, and ag-tech founders are all asking the same question: Did I miss something?In this episode of the AgCulture Podcast, Paul sits down with Louie Pitman and Sid Speir from RK Partners to unpack one of the most overlooked financial tools in agriculture — the R&D Tax Credit. RK Partners helps companies across agriculture and ag-tech optimize this government incentive, which can return roughly $0.10 for every $1 spent on qualifying research and development activity.And that activity may be happening on your farm already.R&D in agriculture can include animal health and nutrition programs, feed trials, crop science, genetics, automation, process improvements, robotics, AI systems, and even sustainability initiatives. RK works with farms and ag-tech businesses across the U.S. — including dairy, poultry, swine, crop operations, and agricultural technology providers — helping them identify, document, and defend qualifying claims.If you're experimenting, improving, testing, or building — this conversation may apply to you more than you think.You can learn more about RK Partners at: https://www.rkpartners.comMEET THE GUESTSLouie PitmanLouie is a Partner at RK Partners, working closely with agricultural businesses across the United States to help them maximize federal and state tax credits. With over seven years of experience in tax credits and incentives, he supports family-owned farms, large livestock operations, ag-focused manufacturers, and agtech startups in identifying opportunities within the R&D credit framework.Connect with Louie on LinkedInSid SpeirSid is the Vice President at RK Partners, where he leads the firm's Agriculture division. He works closely with some of the largest livestock and crop operations across the United States, helping them navigate and maximize the federal R&D Tax Credit. With nearly a decade of experience in the R&D tax space, Sid specializes in identifying, documenting, and defending qualifying claims for agricultural businesses.Connect with Sid on LinkedInABOUT THE PODCASTDiscover the world of agriculture with the "Ag Culture Podcast".This podcast is a gateway for those passionate about agriculture to explore its global perspectives and innovative practices.Join Paul as he shares his experiences in the agricultural industry, his travels and encounters with important figures around the world.Available on YouTube, Spotify and Apple Podcasts.Subscribe at http://www.agculturepodcast.com and keep an eye out for future episodes, bringing insights and stories from the vibrant world of agriculture.00:00 – Why R&D tax credits matter for agriculture 02:05 – What R&D tax credits actually are 05:30 – The 4-part qualification test 09:00 – Practical dairy farm examples 12:05 – The George v. Commissioner case 14:30 – Paul's on-farm experience 16:00 – Documentation made simple 21:20 – Genetics & breeding as R&D 24:00 – AgTech & AI applications 27:00 – Payroll tax offset for startups 28:45 – How the credit reduces taxes 30:40 – The Big Beautiful Bill explained 32:30 – Audit risk & defensible claims 37:00 – What agriculture underestimates
Episode Title: Sky Rings, Supreme Court Limits & Olympic Pride Runtime: ~35 minutes Tone: Fast-moving, high-energy, multi-topic flagship episode
Today we are talking about Mautic, marketing automation, and its history with Drupal with guest Ruth Cheesley. We'll also cover Mautic ECA as our module of the week. For show notes visit: https://www.talkingDrupal.com/541 Topics What Is Mautic? Self-Hosting and Data Ownership Who Uses Mautic + Personalization Mautic's History with Drupal How Drupal Integrate Mautic Orchestration in Mautic Privacy & Compliance: GDPR Tools, Consent, and Do-Not-Contact Controls Hosting Options Advanced Segmentation Points-Based Lead Scoring Validating Segments Using Points to Boost Common Mautic Adoption Pitfalls Getting Support The Future with AI AI and Open Source Maintenance Mautic Sustainability & Fundraising How to Contribute Resources Mautic Mautic Integration Advanced Mautic Integration Talking Drupal #343 - Marketing Automation with Mautic Managed hosting, 40% goes to the community Mautic/Drupal case study and presentation on that from our conference https://www.youtube.com/watch?v=r0SkfeHTLK8 https://mautic.org/case-study/inagro/ GDPR cleanup jobs to remove old data Anonymization tasks to comply with specific laws (eg CCPA) Anonymize IP setting Proposal to overhaul all things privacy and streamline experience for marketers - currently seeking funding, planning to ship in Mautic 9 Mautic contribution docs Testing PRs: inlcuding local setup guide Low/no-code tasks board Thanks Dev Ecosystems Guests Ruth Cheesley - ruthcheesley.co.uk RCheesley Hosts Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Catherine Tsiboukas - mindcraftgroup.com bletch MOTW Correspondent Martin Anderson-Clutz - mandclu.com mandclu Brief description: Have you ever wanted to integrate Mautic marketing automation into your Drupal website, using ECA? There's a module for that. Module name/project name: Mautic ECA Brief history How old: created in Jun 2025 by Abhisek Mazumdar (abhisekmazumdar) of Dropsolid Versions available: 1.0.6 which works with Drupal 10 and 11 Maintainership Actively maintained Documentation - detailed README Number of open issues: 1 open issues, which is not a bug Usage stats: 3 sites Module features and usage With the module installed, your ECA models can respond to Mautic webhooks, and can also make use of new actions to give you CRUD capabilities (Create, Read, Update, or Delete) for contacts and segments within ECA Mautic ECA declares the Mautic API module as a dependency, and you need to use it to set up an API connection, and to define any webhooks you want to use in your models It's worth noting that the maintainers of Mautic ECA also seem to be involved with a number of other modules in the Mautic API ecosystem, including Mautic Personalization, as well as Mautic Content Provider, which can expose Drupal content for use in Mautic, for example to include in emails
We swap aliases for real names, thank new YouTube subscribers and Patreon supporters, and weigh Discord's privacy risks before diving into a full blueprint for documentation that actually gets used. From biathlon analogies to AEO tactics, we map how to build living docs that reduce chaos and speed up onboarding.• live show update and community shoutouts• discord verification risks and alternatives• vibe check and the chaos scale at work• winter olympics biathlon and mountaineering analogies• proactive vs just-in-time documentation• video-first tutorials with searchable transcripts• confluence labels, ownership, and review cadence• reducing tribal knowledge and speeding onboarding• AEO for AI-friendly, accurate documentation• testing docs with real users and feedback loopsSubscribe to our YouTube channel and join our Patreon to support the show. Join our Discord for now to get live notifications while we evaluate safer community options. “If you'd like to support the show, check the link tree, go to our Patreon, sign up, and support us.”Click/Tap HERE for everything Corporate StrategyElevator Music by Julian Avila Promoted by MrSnoozeDon't forget ⭐⭐⭐⭐⭐ it helps!
(Premier épisode) Le samedi 20 février 2016 à la Bastide-Clairence (Pyrénées-Atlantique), les corps sans vie de Pascal et Ewa Rouxel sont découverts dans leur maison. Les enfants du couple : Yann et Kévin, ainsi que Sophiya, la compagne de Kévin et leur fille de deux ans, sont sur place. Deux jours plus tard, les deux fils sont mis en examen pour assassinat, c'est-à-dire meurtre, avec préméditation. Ils sont incarcérés à la maison d'arrêt de Bayonne. Une affaire de double parricide, c'est quasiment du jamais vu.Dans Crime story, la journaliste Clawdia Prolongeau raconte cette enquête avec Damien Delseny, chef du service police-justice du Parisien.Crédits. Direction de la rédaction : Pierre Chausse - Rédacteur en chef : Jules Lavie - Ecriture et voix : Clawdia Prolongeau et Damien Delseny - Production : Anaïs Godard, Clara Garnier-Amouroux et Clémentine Spiler - Réalisation et mixage : Julien Montcouquiol - Musiques : Audio Network, Archives : INA.Documentation. Cet épisode de Crime story a été préparé en puisant dans les archives du Parisien, avec l'aide de nos documentalistes ainsi que les ressources suivantes : Sud Ouest, La République des Pyrénées et Le Monde. Hébergé par Acast. Visitez acast.com/privacy pour plus d'informations.
(Deuxième et dernier épisode) Le samedi 20 février 2016 à la Bastide-Clairence (Pyrénées-Atlantique), les corps sans vie de Pascal et Ewa Rouxel sont découverts dans leur maison. Les enfants du couple : Yann et Kévin, Sophiya, la compagne de Kévin et leur fille de deux ans, sont sur place. Deux jours plus tard, les deux fils sont mis en examen pour assassinat, c'est-à-dire meurtre, avec préméditation. Ils sont incarcérés à la maison d'arrêt de Bayonne. Une affaire de double parricide, c'est quasiment du jamais vu.Dans Crime story, la journaliste Clawdia Prolongeau raconte cette enquête avec Damien Delseny, chef du service police-justice du Parisien.Crédits. Direction de la rédaction : Pierre Chausse - Rédacteur en chef : Jules Lavie - Ecriture et voix : Clawdia Prolongeau et Damien Delseny - Production : Anaïs Godard, Clara Garnier-Amouroux et Clémentine Spiler - Réalisation et mixage : Julien Montcouquiol - Musiques : Audio Network, Archives : INA. Documentation. Cet épisode de Crime story a été préparé en puisant dans les archives du Parisien, avec l'aide de nos documentalistes ainsi que les ressources suivantes : Sud Ouest, La République des Pyrénées et Le Monde. Hébergé par Acast. Visitez acast.com/privacy pour plus d'informations.
While the landscape of healthcare is shifting beneath our feet, the most tangible change in daily practice since the arrival of AI has been our documentation.Over the past two years, we have moved beyond the initial excitement of AI scribes and chat interfaces. As we look ahead to Therapy Documentation in 2026, the conversation is shifting from “how do we save time?” to “how can data and analytics help us in real-time?” We are entering an era where documentation is no longer a static record of the past, but a dynamic tool that augments our clinical reasoning and patient care.We are thrilled to welcome to the podcast Pedro Teixeira, MD, PhD. Dr. Teixeira is the co-founder of PredictionHealth (now part of Prompt Health) and a leading expert in using biomedical informatics to bring intelligent automation into the rehab workflow.In this episode, we'll discuss:Industry-wide technology adoptionDocumentation KPIs and metricsEmerging clinical data dashboardsFuture-focused patient care visionSee full course details here:https://otpotential.com/ceu-podcast-courses/therapy-documentation-in-2026See all OT CEU courses here:https://otpotential.com/ceu-podcast-coursesCheck our our live webinar schedule here:https://otpotential.com/live-ot-ceu-webinarsSupport the show by using the OTPOTENTIAL Medbridge Code:https://otpotential.com/blog/promo-code-for-medbridgeTry 2 free OT Potential courses here:https://otpotential.com/free-ot-ceusSupport the show
A 22-year-old male comes into urgent care with a boxer fracture after punching a wall. It should have been routine. Until one suicide assessment question changed everything. In this episode, John Bielinski breaks down: How to assess suicide risk in urgent care and emergency medicine The critical follow-up question that reveals an organized plan The SAD PERSONS mnemonic explained Documentation tips to protect against medical malpractice What "duty to warn" means for clinicians Why "No SI, No HI" isn't enough If you practice urgent care, emergency medicine, primary care, or hospital medicine — this episode will sharpen your suicide screening, documentation, and risk management skills immediately. Real case. Real lessons. Real protection — for your patients and your license. Love this content? Join us at an upcoming urgent care conference with CME4Life and John Bielinski — hosted in incredible locations like The Bahamas, Las Vegas, and Walt Disney World. Sharpen your skills. Earn CME. Network. Have fun. Learn more: https://cme4life.com/urgent-care-conferences-events-2026/
This one is for business builders who have real results but no documented process. In this episode, I explain why many successful people resist writing down what actually works, even for themselves. When everything lives in your head, the business only works as long as you are working. Documentation forces clarity, accountability, and transferability, and that changes the power dynamic from talent to system. If it's not documented, it's not a system, and without a system, your success can't scale or survive without you. Show Notes: [03:22]#1 Documentation removes the mystique of your personal talent. [08:13]#2 Documentation eliminates excuses. [13:30]#3 Documentation forces you to admit what actually matters. [17:34] Recap Next Steps: --- Power Presence is not taught. It is enforced. If you are operating in environments where hesitation costs money, authority, or leverage, the Power Presence Mastermind exists as a controlled setting for discipline, execution, and consequence-based decision-making. Details live here: http://PowerPresenceProtocol.com/Mastermind This Masterclass is the public record of standards. Private enforcement happens elsewhere. All episodes and the complete archive: → WorkOnYourGamePodcast.com
One of the hottest topics in college athletics turns out to be about nonprofits. This episode unpacks how nonprofit colleges and third-party NIL collectives support individual student athletes, the governance and tax questions that follow, and what the recent NCAA settlement means for oversight and compliance. We also look ahead to emerging federal regulation and how nonprofits might engage in shaping what comes next. Attorneys for this Episode · Tim Mooney · Victor Rivera Why NIL Is a Nonprofit Issue · Define NIL: athlete rights to monetize their brand (name, image, likeness). · Distinguish third-party deals vs. institution-linked compensation · Why nonprofits are in the mix: NIL collectives, booster organizations, independent sponsorscirculating capital in the ecosystem. College athletics live inside nonprofit institutions — universities and colleges are almost all 501(c)(3)s. Enter third-party NIL collectives — many of which are also nonprofits, often organized as 501(c)(3)s or seeking that status. When nonprofits move money, governance and tax law always follow — NIL is no exception. In October 2025, a settlement in House v. NCAA settlement centralized review mechanisms (the College Sports Commission – or CSC) now oversee deal approvals & compliance. Ongoing federal intervention: the proposed SCORE Act is NCAA-backed and would stop athletes from being considered employees and shield the NCAA from the kinds of class action lawsuits that got us to the current NIL landscape How Nonprofits End Up Supporting Individual College Athletes Nonprofits can and do financially benefit specific individuals (scholarships, disaster relief, housing aid, fellowships). NIL collectives operate on a similar theory: Supporting athletes through appearances, community engagement, or promotional activity Often tied (explicitly or implicitly) to institutional athletic programs The tension: Supporting individuals is allowed But private benefit, inurement, and mission drift are still red lines Issue with compensating individuals using their "fair market value" Key question for nonprofits: Are we advancing a charitable purpose (legal) or just subsidizing compensation (questionable)? Governance Questions Nonprofits Can't Ignore Board-level responsibilities Mission alignment How does athlete support further the stated charitable purpose? Is this education, community engagement, economic equity or something else? "Amateur athletics" does a lot of heavy lifting here, but sometimes the collectives compensate the athletes for promoting charitable events/causes. Board oversight Who approves NIL strategy? How are conflicts of interest handled (especially boosters, alumni, donors)? Controls and accountability Criteria for selecting athletes Documentation of services provided Fair market value analysis Transparency What are donors told? What is disclosed publicly vs. internally? Regulation on the Horizon After the NCAA Settlement The NCAA settlement signals: More centralized oversight More formal review of NIL arrangements Less tolerance for "wink-and-nod" structures Likely regulatory pressure points: Standardized deal review Clearer definitions of permissible activity Increased scrutiny of nonprofit status and operations Should Nonprofits Weigh In on What Comes Next? The NCAA settlement last fall quieted things down by creating reporting structures, arguably with some teeth. But as things evolve, there's more space for nonprofits in particular to notice. Will the College Sports Commission (CSC) continue to have conference support so it can enforce the NIL rules? The agreement hasn't been fully adopted yet, but the CSC is already knocking down some NIL deals. Federal legislation (SCORE Act or SAFE Act) Recent controversies surrounding eligibility of former pro-basketball players (Amari Bailey, Charles Bediako) may force Congress to act NCAA-adjacent rulemaking State-level NIL frameworks particularly regarding their institutions Other structures could allow potential pathways for unionization for student-athletes 501(c)(5)s like AFL-CIO have come out against SCORE Act Previous attempts have failed by student-athletes in Northwestern and in other universities and the SCORE Act has a provision that bans college athletes from being considered employees Resources NIL Compliance Tightens: What the NCAA's New Rules Mean for Institutions and Sponsors – Steptoe and Johnson College Sports Watchdog Will Enforce Rules Without Legal Backing – Front Office Sports NIL regulations for college athletes face hurdles in Congress – Spectrum News Letter Opposing Legislation That Would Be A Bad Deal for College Athletes – AFL-CIO
Nancy Guthrie Missing escalates again as the FBI reportedly deploys a “signal sniffer” in an effort to track digital activity tied to the case — while a fourth demand letter surfaces. In the ongoing Nancy Guthrie Missing investigation, authorities in Tucson, Arizona are intensifying efforts to trace electronic signals, analyze ransom communications, and identify the person responsible for taking Nancy Guthrie. This breaking news adds a new layer of urgency as federal agents and the sheriff coordinate advanced technology and forensic strategy.In this STS Podcast episode, we break down how a signal sniffer works, what investigators may be looking for, and what the fourth demand letter could reveal about the suspect's movements. Is this a calculated digital trail or a desperate attempt to avoid detection? We examine the timeline, law enforcement tactics, and how cases like this can evolve into cold cases without critical breakthroughs. From survivor stories to real crime stories dominating true crime news, we focus on facts, developments, and what could happen next in the search for Nancy Guthrie.Key Points Covered:FBI using “signal sniffer” technologyFourth demand letter receivedSheriff and federal coordination in Tucson, ArizonaDigital tracing and ransom communication analysisWhat this means for the next phase of the investigationSupport the show & be a part of #STSNation:Donate to STS' Trial Travel: Https://www.paypal.com/ncp/payment/GJ...VENMO: @STSPodcast or Https://www.venmo.com/stspodcastCheck out STS Merch: Https://www.bonfire.com/store/sts-store/Joel's Book: Https://amzn.to/48GwbLxSupport the show on Patreon: https://www.patreon.com/SurvivingTheSurvivorEmail: SurvivingTheSurvivor@gmail.com Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising. Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.
© 2020-2026 Ivy Podcast Discovery LLC
