AI News Archive: June 22, 2026 — Part 8
Sourced from 500+ daily AI sources, scored by relevance.
- Navigating the AI access control minefield
Until recently, IT departments largely focused on providing employees with the IT systems they needed to do their jobs, which meant identity and access management (IAM) systems were primarily human-centric . Aditya Sood , vice-president of security engineering and artificial intelligence (AI) strategy at Aryaka, points out that this human-centric focus means identities are provisioned, authenticated and authorised using models such as role-based access control (RBAC) and multifactor authentication (MFA), where decisions are made at the point of login. “Even with the evolution toward zero trust , the core assumption remains largely unchanged: identities are known, bounded and relatively stable,” he says. Sood warns that the current IAM stack is misaligned with the fluid, autonomous nature of AI agents. “We are no longer just securing ‘users’; we are securing a massive, autonomous web of non-human identities [NHIs] that move at machine speed,” he says. “Autonomous agents dynamically invoke tools, access APIs [application programming interfaces], generate sub-agents, and operate across multiple domains without direct human intervention. These agents often use shared credentials, ephemeral tokens, or implicit trust boundaries, leading to identity ambiguity, weak attribution and expanded attack surfaces,” adds Sood. A modern identity stack for agentic systems Because agentic AI systems need access to corporate IT systems to complete tasks, IT security leaders must ensure they are properly identified and given access only to the data they and the people they are working for are authorised to access. Here are some points to consider: Every AI agent must have a unique, verifiable identity tied to its origin to provide traceability, enabling organisations to understand who initiated an action and under what authority. Agents should use short-lived, task-specific tokens that are automatically issued and revoked. This minimises exposure in case of compromise and aligns access strictly with the duration and scope of a task. It enforces the zero standing privileges (ZSP) principle. Access decisions should be dynamic, based on real-time context, adapting continuously to the agent’s actions and location, ensuring tighter, more relevant control. Agentic systems often involve multiple layers of delegation, which means a clear and enforceable chain of trust is required to track authority and limit how far and wide permissions can propagate. Systems must continuously monitor agent actions, reassess risk and adjust permissions in real time. This helps detect subtle misuse, compromised workflows, or manipulated prompts that may not trigger traditional security alerts. A robust audit trail is essential for capturing who performed which action, through which agent, and with which tools to support incident response, and builds trust in autonomous systems by making their actions transparent and explainable. Source: Aditya Sood, vice-president of security engineering and AI strategy, Aryaka IT security implications of enterprise AI Although many organisations are still in the early stages of AI maturity, Jacob Connell , AI and automation engineer at Quorum Cyber, says one of the biggest challenges in this journey is integrating automation and AI securely into existing enterprise systems. “As AI-driven attack surfaces expand, identity becomes a foundational control for securing automation and, critically, for limiting blast radius when things go wrong. Mistakes will happen; the goal of modern identity design is to ensure the impact is contained and recoverable,” he says. As AI-driven attack surfaces expand, identity becomes a foundational control for securing automation and limiting blast radius when things go wrong Jacob Connell, Quorum Cyber According to Connell, AI is not just adding a new user type to identity and access management; it is forcing organisations to redesign identity as a continuous control plane for humans, workloads and agents alike. Looking at traditional IAM, Connell says that once a user or service is authenticated and receives a token, that token could be replayed freely until expiry – sometimes for hours or days – without the platform rechecking whether anything important has changed about the subject’s standing. But he warns that “this model no longer holds”. Connell suggests IT security leaders should deploy a continuous evaluation model. Although a valid token is still necessary, when a token is presented, he says centrally defined policies should confirm that the subject and its context still meet all the requirements at that moment. Connell recommends checking whether the identity is still active, whether it has been flagged as high risk, whether the IP or location has changed unexpectedly, whether the device posture has degraded, and whether there is new threat intelligence that suggests a compromise, among other things. “Evaluating these signals at the edge can significantly reduce the window of identity abuse,” he says. The approach applies equally to human users, machine workloads and emerging hybrid identities that are created by agentic AI acting either autonomously or on behalf of a user, such as when there is a human in the loop. Ethics and IAM IT and security leaders should also consider the ethical ramifications of deploying AI in their organisations. Mike Gillespie, senior vice-president of Europe at the Centre for Strategic Cyberspace and Internet Studies (CSCIS), points out that AI identity systems can amplify bias , which he says disproportionately impacts vulnerable groups. This means they risk becoming opaque decision engines that erode trust. As Gillespie notes, regulators are increasingly explicit that fairness, explainability and contestability are not “nice to haves”, but essential design principles embedded throughout the lifecycle of an AI system. He says the UK is advancing a principles-based, regulator‑led model for AI oversight. These include the Data (Use and Access) Act 2025 , updated guidance from the Information Commissioner’s Office (ICO) , and ongoing reforms that significantly shape how AI identity systems must operate. As Gillespie explains, the Data (Use and Access) Act 2025 expands organisational duties around automated processing, children’s data protection and complaint handling. He says this shows that AI-driven identity checks will face greater scrutiny regarding oversight and safeguards. With regards to updated ICO guidance, Gillespie says there is renewed emphasis on fairness, transparency and clear legal bases for processing, especially where AI influences decisions with “legal or similarly significant effects”. Additionally, sector‑specific legislation such as the UK’s Online Safety Act 2025 mandates “highly effective” age and identity verification for high‑risk online services, which Gillespie says reinforces the need for accuracy, privacy‑preserving methods and demonstrable compliance. “The pattern is unmistakable: organisations must prove responsible use, not merely assert it. That means implementing effective governance and regulatory compliance [GRC] as part of the adoption,” he adds. The challenge of monitoring the use of AI is that it requires the collection of personal data, as Ellie Hurst , commercial director at Advent IM, explains. “Once AI is involved in deciding who gets access, who is challenged, who is flagged as suspicious, or who is denied entry altogether, that stops being just a technical control and quickly becomes a governance matter,” she says. “Many of these solutions rely on large volumes of personal data, sometimes including biometrics, behavioural analysis, device data, location information and patterns of use. That means organisations need to be crystal clear on lawful basis, necessity, proportionality, retention and oversight. In other words, they need to know not just that the tool can do something, but that they should be doing it at all. It’s like knowing that an iPhone is a tool, not the conversation,” adds Hurst. Looking at specific standards that include governance, Gillespie says ISO/IEC 42001 , the world’s first AI management system standard, introduces a structured approach for governing AI responsibly, integrating leadership accountability, lifecycle controls, risk assessment and ongoing performance evaluation. According to Gillespie, ISO/IEC 42001 provides a governance architecture that organisations can use to ensure that AI identity solutions are explainable, monitored, tested and continuously improved. However, he says: “ISO 42001 does not replace compliance obligations, but it provides the organisational discipline needed to navigate them confidently. Implementing effective GRC requires embedding governance from the outset: adopting ISO 42001’s structured AI management framework, performing DPIAs [data protection impact assessments], enforcing privacy‑ and fairness‑by‑design, maintaining transparency and documentation, and ensuring robust human oversight.” With regulators increasingly focused on accountability, fairness and privacy, Gillespie recommends that IT security leaders consider deploying AI identity built on a foundation of trust, accountability and principled design as no longer optional. “They are essential for safe, lawful and responsible AI identity management,” he says. Just because a system can infer more does not mean it should. It’s a potential minefield that should be navigated mindfully and with integrity Ellie Hurst, Advent IM Advent IM’s Hurst warns that data gathered to confirm identity can easily become data used to monitor behaviour, profile staff, track habits or support broader surveillance if the guardrails are poor. That is where trust starts to wobble. “Enterprises need privacy by design, proper impact assessments, transparent notices and disciplined boundaries around how identity data is used. Just because a system can infer more does not mean it should. It’s a potential minefield that should be navigated mindfully and with integrity,” she says. This is why a full assessment is needed for any organisation planning how it will use AI. Summing up, Gillespie says: “Privacy and ethics are not parallel workstreams; they form the foundation for any legitimate use of AI.” As AI and agentic AI systems are rolled out across organisations, IT departments are likely to face new challenges beyond managing the technology infrastructure required to run AI inference at scale. IAM is part of a layered approach to cyber security that security leaders need to put in place. A traditional human-centric approach to IAM is unlikely to be sufficient to manage the credentials of AI systems. In addition, IT and security leaders also need to put in place a governance framework for AI that balances enterprise security with the data privacy of employees. Read more about AI security Close cloud security gaps to secure AI workloads : Is your cloud security strategy ready for AI workloads? Organisations must strengthen cloud security – including data protection and IAM controls – to safeguard AI. Why AI forces security-first governance : AI systems fail quietly through drift, biased outputs and degraded judgement. A security-first governance approach gives leaders the visibility and continuous control to scale AI safely.
Score: 40🌐 MovesJun 22, 2026https://www.computerweekly.com/feature/Navigating-the-AI-access-control-minefield - Bigger Context Windows Are Not Enterprise Context
Bigger Context Windows Are Not Enterprise Context Every few months, the AI market gets a new headline about larger model context windows. The promise sounds simple. If a model can hold more tokens, it should be able to understand more of your codebase. Add more repository files, documentation, tickets, API specs, and policy documents, and […] The post Bigger Context Windows Are Not Enterprise Context appeared first on Tabnine .
Score: 40🌐 MovesJun 22, 2026https://www.tabnine.com/blog/bigger-context-windows-are-not-enterprise-context/ - Studio Chief Behind Megahit ‘Ne Zha 2’ Lays Out AI’s Limits in Animation
Studio Chief Behind Megahit ‘Ne Zha 2’ Lays Out AI’s Limits in Animation Caixin Global
- Pension services go multilingual as PFRDA rolls out AI-powered grievance platform
Pension services are set to become more accessible with PFRDA's new AI-powered platform, 'Pension Sahayak'. Subscribers can now lodge complaints using voice commands in 22 Indian languages, a boon for senior citizens and rural users. This digital ecosystem streamlines grievance handling, ensuring faster resolutions through an automated escalation process and promoting greater accountability across the pension sector.
- How Shipway Is Using AI To Drive Post-Purchase Efficiency For India’s D2C Brands
India’s D2C economy is projected to surpass $310 Bn by 2030, and the brands driving this growth have largely mastered…
Score: 40🌐 MovesJun 22, 2026https://inc42.com/startups/how-shipway-is-using-ai-to-drive-post-purchase-efficiency-for-indias-d2c-brands/ - Why scalable AI products are becoming critical for enterprise AI adoption and business growth
Scalability is commonly viewed as a concern for large enterprises, when in reality, it becomes critical much earlier. As businesses expand their use of AI products across teams and frameworks, scalability often determines whether an investment continues delivering value or creates new operational challenges. This focus on long-term impact is one of the reasons scalability remains a key evaluation criterion at the ET Most Innovative AI Product Awards 2026.
- David Droga on AI and the end of ‘mediocre’ human-made ads
As he sees it, the advertising industry is in the throes of a profound technological shift.
Score: 40🌐 MovesJun 22, 2026https://www.semafor.com/article/06/21/2026/david-droga-on-ai-and-the-end-of-mediocre-human-made-ads - AI can help architects see the future before they build it
AI can help architects see the future before they build it Business Insider
Score: 40🌐 MovesJun 22, 2026https://www.businessinsider.com/gensler-architecture-ai-design-tools-concepts-2026-6 - Americans are fleeing the U.S. at record rates—an ex-Google engineer who left India to build a $7.2 billion AI firm says they’re making a mistake
Americans are fleeing the U.S. at record rates—an ex-Google engineer who left India to build a $7.2 billion AI firm says they’re making a mistake Fortune
- Frontline Systems Launches RASON® Desktop: Brings Simulation, Optimization, Decision Intelligence Directly into Power BI
Frontline Systems Launches RASON® Desktop: Brings Simulation, Optimization, Decision Intelligence Directly into Power BI azcentral.com and The Arizona Republic
- Three key AI stocks to watch this week with traders expecting giant moves
Micron and Cerebras report this week. Also there's heavy options activity in Super Micro.
Score: 40🌐 MovesJun 22, 2026https://www.cnbc.com/2026/06/22/three-key-ai-stocks-to-watch-this-week-with-traders-expecting-giant-moves.html - The allure of tech stocks amid the AI hype, and embracing a “Clown Mentality” to fight off work stress
The allure of tech stocks amid the AI hype, and embracing a “Clown Mentality” to fight off work stress The Straits Times
- Why agentic enterprises need to become learning systems
Presented by Splunk Every day, organizations learn things their AI systems never get to use. A security analyst corrects an AI-generated investigation. A network engineer identifies the root cause of a recurring outage. An observability team discovers that a pattern of latency, logs and infrastructure changes predicts service degradation. A customer operations team learns which signals indicate an escalation is likely. Each moment contains valuable organizational knowledge. But in most enterprises, that knowledge disappears into tickets, dashboards, chat threads, post-incident reviews and the minds of individual experts. It may help solve the immediate problem, but it rarely becomes part of a reusable system that improves future AI-driven decisions. That is the next challenge for the agentic enterprise. The future will not be defined simply by who has the most capable model or the most autonomous agents. Many organizations will have access to similar frontier models. Many will deploy agents across security, IT, engineering, customer service, and business operations. The real differentiator will be whether those agents can learn from the organization around them. Not by constantly retraining the underlying model, but by capturing operational experience, converting it into institutional knowledge and making that knowledge available to future agents, workflows, and decisions. The agentic enterprise is not just an enterprise that uses AI. It is an enterprise that learns through AI. Agentic enterprises allow AI systems to learn from them The AI conversation has been dominated by model capability: larger context windows, better reasoning, faster inference, stronger tool use, and more sophisticated agentic behavior. Those advances matter. But in the enterprise, a model is only one part of the system. A model does not automatically know how a specific organization operates. It does not inherently know which remediation step solved last month’s outage, which analyst correction improved a threat investigation, which network signal preceded a service disruption, or which internal policy should override an otherwise plausible recommendation. That knowledge belongs to the enterprise. For agentic systems to improve, organizations need a way to capture that knowledge and make it reusable. In many cases, that does not require changing the model itself. It requires changing the ecosystem around the model: the knowledge base, retrieval layer, prompts, policies, guardrails, routing logic and workflows that shape how agents behave. The model may remain the same. The learning system around it becomes smarter. Feedback loops turn every outcome into a teachable moment for agents Every agentic workflow creates signals. An agent receives a request. It retrieves context, reasonsthrough possible actions, calls tools, and generates answers. A human accepts, rejects, or modifies that answer. Downstream systems reveal whether the action worked. That entire chain is valuable. AI observability gives organizations visibility into what happened: the prompt, response, reasoning path, tool calls, data sources, intermediate steps, failure modes and outcomes. Without that visibility, organizations cannot understand why an agent behaved the way it did, let alone improve it. But observability alone is not enough. The larger opportunity is to turn observed behavior into institutional knowledge. A trace should not only help a developer and operators debug an agent. It should help the enterprise understand what the agent learned, what the human corrected, what outcome followed, and what should change before the next similar event. That is the shift from monitoring AI to teaching AI. In the agentic enterprise, feedback loops connect action to outcome, outcome to knowledge and knowledge back to future action. A learning system in practice across security, observability and the network Consider a service experiencing intermittent degradation. An observability agent detects unusual latency and error rates. A network agent identifies packet loss across a specific path. A security agent notices that the same time window includes suspicious authentication behavior and unusual traffic from a previously unseen source. Individually, each agent has only a partial view. Together, they create a richer operational picture. The first time this incident occurs, human experts may need to intervene. A network engineer confirms that packet loss was caused by a misconfigured routing change. A security analyst determines that the suspicious traffic was not an attack, but a side effect of a misrouted internal service. An SRE connects the network event to the application degradation. That resolution contains knowledge the organization should not have to relearn. A mature agentic learning system would capture the traces, human corrections, topology context, security findings, observability signals and final remediation steps. It would preserve the relationship between those signals: latency pattern, network path, identity behavior, routing change and remediation. The next time a similar pattern appears, agents would not start from zero. They could retrieve the prior case, compare current conditions, recommend the proven diagnostic path and escalate with better context. The underlying frontier model did not need to be retrained. The enterprise learned. The architecture of the learning agentic enterprise A learning-oriented agentic enterprise needs more than a model or chatbot. It needs an architecture that can capture experience, turn it into usable knowledge, connect that knowledge to operational context, and govern how it changes future agent behavior. Memory preserves what happened: what the agent saw, what it did, where humans intervened, and what outcomes followed. Knowledge bases turn that experience into reusable guidance, including playbooks, examples, policies, procedures, and evidence. A data fabric connects the operational environment. The signals agents need live across logs, metrics, traces, tickets, identity systems, security tools, network telemetry, collaboration platforms, and business applications. A data fabric makes those signals discoverable, correlated, governed, and usable in context. AI observability explains how agents behave by capturing prompts, tool calls, intermediate steps, responses, feedback, and outcomes. That visibility helps organizations understand where agents succeed, where they fail, and what should improve. The control plane governs how learning becomes change: what knowledge is promoted, which prompts or policies are updated, which agents can use new information, what approvals are required, and how changes are audited. Together, these capabilities allow AI systems to improve over time in a controlled, trustworthy way that allows the enterprise to learn from its own operations. The organizations that learn fastest will win The next era of AI will not be won by models alone. It will be won by organizations that can capture what they learn from every workflow, expert correction, incident, investigation, and outcome. The most advanced agentic enterprises will not simply deploy more agents. They will build systems that allow every agent to benefit from the collective knowledge of the organization. That means connecting operational data through a data fabric. It means observing agent behavior deeply enough to understand it. It means preserving experience in memory and institutionalizing it in knowledge bases. It means using a control plane to govern how learning changes agent behavior. The future of AI is not a single autonomous agent acting alone. It is an ecosystem of agents, humans, data and controls that learns over time. The organizations that build that ecosystem will create AI systems that get better with every interaction. Not because the model is constantly changing, but because the enterprise itself is becoming more intelligent. Learn more about how Cisco Data Fabric powered by the Splunk Platform is accelerating agentic operations. Hao Yang is Vice President AI at Splunk, a Cisco Company. Sponsored articles are content produced by a company that is either paying for the post or has a business relationship with VentureBeat, and they’re always clearly marked. For more information, contact sales@venturebeat.com .
Score: 40🌐 MovesJun 22, 2026https://venturebeat.com/orchestration/why-agentic-enterprises-need-to-become-learning-systems - I Gave My AI Agent ADHD. Its Reasoning Got 2x Better.
Three ADHD thinking traits turned into a parallel reasoning pattern. Continue reading on Towards AI »
- Neurealm to Showcase AI-Native Outside-In Safety for Industrial Robotics at Automate 2026
Neurealm to Showcase AI-Native Outside-In Safety for Industrial Robotics at Automate 2026 azcentral.com and The Arizona Republic
- Al-Futtaim Technologies expands cybersecurity capabilities through partnership with AIShield
The collaboration reflects the growing importance of protecting AI systems as organisations increasingly integrate AI/ML and Generative AI technologies into critical business operations
- Confident AI begins with confident data
Leaders are under extraordinary pressure to use AI tools to automate and accelerate tasks like patch remediation and endpoint security. But as IT departments try to deploy new AI tools, they are running up against a longstanding problem: disconnected, sometimes contradictory, sources of data, including logs, telemetry, and documents. “It’s shocking to me that in 2026, a lot of organizations are still using spreadsheets to track IT assets, and nobody is reconciling the data,” says Mareike Fondufe, senior director of solutions marketing for endpoint management at Ivanti, citing Ivanti research showing that 34% of organizations still track IT assets in spreadsheets. “If a device exists in one procurement system and also exists in another system, those systems don’t communicate with each other, and another system might have outdated information.” Overwhelmed IT teams are counting on automation to help them move away from a reactive support model, where they must constantly chase down the sources of blue screens and other problems. Rather than resolving inconsistencies, AI can amplify underlying data quality issues — scaling errors across systems and workflows. This can lead to IT teams pausing automation efforts because they don’t trust the underlying data. “AI without trusted data isn’t just ineffective,” Fondufe says. “It increases operational and security risks, from zero-day exposure on unpatched endpoints that fall outside patch visibility to regulatory non-compliance from assets that sit outside audit scope.” Even when leaders think they have a holistic view of their IT environments, there are often hidden gaps. In one recent case, an Ivanti assessment revealed that a customer had 30% more devices than leaders were aware of, resulting in security gaps. “They realized they didn’t have full visibility into their infrastructure. Without complete visibility and context, they cannot confidently act or automate,” Fondufe says. “If something went down, they wouldn’t even be able to identify which servers supported critical services.” Within many organizations, ownership is often fragmented across teams, meaning that no one is in charge of exploring solutions that can create a single source of truth. Ivanti acted as “Customer Zero” for its own Autonomous Endpoint Management strategy and solutions. In addition to improved visibility and reduced risk, the organization reclaimed nearly 56,000 employee hours per year, much of it via simplified compliance reporting. In another example, Ivanti worked with a healthcare organization that saw decreased ticket volume, enhanced end-user experiences, and improved IT job satisfaction after embracing AEM. But first, Ivanti helped the organization modernize its fragmented IT operations and establish a trusted system of record for its IT and security operations. With that trusted system of record, the healthcare customer was able to shift from a reactive, tool-driven management approach to a data-driven model that leverages automation for detection and remediation. AI is a powerful enabler that allows companies to solve all these pain points faster and more efficiently,” Fondufe says. “The Ivanti Neurons Platform provides a unified data foundation that helps organizations move from fragmented visibility to trusted context — allowing solutions like AEM to deliver insight and action. Stop reconciling IT data across disconnected systems. See how Ivanti Neurons helps you build the trusted data foundation your AI initiatives require.
Score: 39🌐 MovesJun 22, 2026https://www.cio.com/article/4187870/confident-ai-begins-with-confident-data.html - Singapore AI inspection startup H3 Zoom raises $3.6m
The round was led by JRE Ventures, with participation from SGInnovate and M7 Holdings.
Score: 38💰 MoneyJun 22, 2026https://www.techinasia.com/singapores-hunt-ai-stars-risks-alienating-small-players - Forget speed: L’Oréal’s innovation chief says AI rewards companies with history
Forget speed: L’Oréal’s innovation chief says AI rewards companies with history Fortune
Score: 38🌐 MovesJun 22, 2026https://fortune.com/2026/06/22/loreal-innovation-chief-ai-rewards-companies-history/ - AI lessons learned from 3 SMB banks
Starting with targeted use cases, focusing on underlying data and managing change are key to successful use cases, banking leaders said.
Score: 38🌐 MovesJun 22, 2026https://www.bankingdive.com/news/AI-cape-coast-bank-mission-valley-lake-city-creatio/823362/ - Anthropic says Claude may want to see your ID
Claude's chatbot may ask to verify your age and identity "in certain circumstances," such as with a passport or driver's license, according to a privacy policy change.
Score: 38🌐 MovesJun 22, 2026https://techcrunch.com/2026/06/22/anthropic-says-claude-may-want-to-see-your-id/ - ‘So much for caring about the environment’: REI faces backlash over AI-generated ad suspicions
Update, June 22, 4:15 p.m. ET: In a statement to Fast Company , REI blamed its AI -generated ad on being auto-enrolled by Meta into an AI personalization tool. “Meta auto-enrolled us in an AI personalization tool that produced an inaccurate and inappropriate alteration of a vendor-provided image in some of our ads,” read the statement from an REI spokesperson. “While a two-handled bike might be interesting, it is not something you will find in our assortment,” it continued. “We have taken steps to unenroll from the tool. This does not align with our values or how we manage our brand. Product accuracy and our vendor relationships matter. We apologize for the confusion this caused.” Original story, June 22, 2:45 p.m. ET: Given data centers’ massive water and energy usage , noise pollution , and contribution to rising temperatures , it’s clear that artificial intelligence and the great outdoors just don’t mix. That means brands catering to the tree huggers out there should steer clear of generative AI in their marketing —a lesson that outdoor gear retailer REI may have just learned the hard way. Social media users accused REI of using an AI-generated image for a recent advertisement on Instagram. The ad featured an image of a woman standing by a bicycle in a park —but something seemed off. The bike looked to have too many chains. The text written on it was illegible. Oh, and the bike saddle had an extra pair of handlebars growing out of it. REI using AI slop now. So much for caring about the environment by u/Jeffrey_C_Wheaties in REI It all adds up to an image that looks suspiciously like AI slop, according to social media—one that REI had been promoting on Instagram for a full week before finally taking it down on Monday, June 22. That was more than enough time for commenters to tear the post to shreds. Social media turns on REI Before the Instagram ad’s deletion, its comment section was full of users finding creative ways to accuse REI of using AI. Backhanded compliments were most users’ weapon of choice. “This photography is amazing! So glad a real person put thought and effort into this picture,” one commenter wrote. “I can’t believe this picture looks so real!” joked another. Others poked fun at the pictured bike’s obvious abnormalities. “The extra handlebar coming out of the seat is pure genius!!” one user wrote. “Now I just have to AI myself in order to utilize the saddle-mounted drop bars,” wrote another. PERFECT! Thanks REI.” A third sarcastically noted that REI has always been “famous for their custom builds.” Fitness model Amity Rockwell also reportedly posted to her Instagram story , stating that she’s the woman in the ad—or rather, that the ad was generated based on her likeness. Rockwell explained that a few months ago, she did a photo shoot with bike brand Van Rysel that was to be used for REI advertising, and was confused when she was tagged in the viral image. “The thing is, this was an official shoot. That I got hired for,” Rockwell wrote. “So why are they Al deep frying the images? To alter a product they’re supposedly selling? And my face along with it? lol. I’m so lost.” The fact that REI had actual photography to work with and still may have turned to AI only fanned the flames of the discourse, especially on Reddit. On REI’s subreddit , a post with the title, “REI using AI slop now. So much for caring about the environment,” garnered nearly 800 upvotes and a lively comment section. One commenter claiming to be an REI employee wrote that the company “is absolutely obsessed with AI now.” “Our employee training has been getting more and more AI based for at least a year. we have specific AI trainings coming out, and they’re always ‘updating’ us on how they’re planning to use AI going forward,” they added. “This is straight silly. It’s an ad for a bike and the bike isn’t in the picture,” wrote another commenter. “I don’t understand it when I see AI used to make something that would’ve literally taken them 5 minutes to do,” wrote a third. “Just take a picture of a girl screwing with her helmet step next to the bike. was the AI really needed?” Others added that the ad reflects poorly on Van Rysel, too, though the extent of the bike brand’s involvement in the ad is unclear. “On top of the obvious environmental impacts, this is so insulting to the bike brand,” one commenter wrote. “GROSS!” Van Rysel has not responded to Fast Company ’s request for comment. REI’s environmentalism Though some brands’ customers may let AI slide, REI’s clearly don’t fall in that camp. “I love when ads align with your mission,” one Instagram commenter wrote, poking fun at the hypocrisy of a purportedly environmentalist brand engaging in alleged generative AI use. REI’s environmentalism is a core part of the brand’s identity. The company’s 2025 impact report states that REI is “on a journey to ensure the outdoors remains a place we can all enjoy for generations to come,” thanks to initiatives like textile recycling, lobbying to maintain public land, and a commitment to cutting down greenhouse gas emissions. But for many social media commenters, that work falls flat when paired with an apparently AI-generated ad. For many Americans, AI and environmentalism are polar opposites: Recent polling from Pew Research Center found that 39% of U.S. adults believe that data centers have a negative environmental impact, compared with just 4% who believe they have a positive environmental impact. “With how damaging AI is to the environment, it’s super sad to see REI using it,” another commenter wrote on Reddit. “I mean, is it really that cost prohibitive to take a picture of a real person on a bicycle? I would’ve done it for free.”
- Vivaldi's Leader Has a Bold Pledge: No AI in Your Web Browser
Vivaldi's Leader Has a Bold Pledge: No AI in Your Web Browser PCMag Middle East
Score: 38🌐 MovesJun 22, 2026https://me.pcmag.com/en/browsers/37524/vivaldis-leader-has-a-bold-pledge-no-ai-in-your-web-browser - South Africa’s Yoco expands beyond payments with AI deal
On Techpoint Digest, we talk about SA's Yoco expanding beyond payments with an AI deal, the CBN's data localisation rule, which raises fintech concerns, and Visa’s AI plan to shop with your card in SA.
- Defensibility.ai Opens Pre-Release of the Defensibility Gap Assessment Tool
Defensibility.ai Opens Pre-Release of the Defensibility Gap Assessment Tool azcentral.com and The Arizona Republic
- DiffusionGemma + Dflash + TurboQuant + RAG = Better OCR & Self-Hosted
In June 2026, Google released a rather unusual AI. Its name is “DiffusionGemma.” Continue reading on Towards AI »
- How World Cup Fans Can Use AI to Keep Up With the Action
OpenAI and Google have rolled out World Cup fan experiences to help you make the most of the tournament.
Score: 37🌐 MovesJun 22, 2026https://www.cnet.com/tech/services-and-software/world-cup-2026-chatgpt-google-features/ - With AI Agents, Trust Has to Be Measurable
The most dangerous assumption in enterprise AI right now is that smarter agents should automatically be given more autonomy. It sounds logical. If an AI agent can reason, plan, call tools, retrieve information, write code, summarize records, and complete multi-step workflows, why not let it do more? Because capability is not the same thing as … continue reading The post With AI Agents, Trust Has to Be Measurable appeared first on SD Times .
- How to set up the smartest Galaxy AI features on your new Samsung Galaxy S26, step by step
A practical walkthrough of the Galaxy AI features worth setting up the moment you take your new Samsung Galaxy S26 out of the box.
Score: 36🌐 MovesJun 22, 2026https://mashable.com/ad/tech/how-to-set-up-the-smartest-galaxy-ai-features-on-your-new-samsung-galaxy - Why we think Glean’s Market Shapers placement matters for the future of no-code agents
Glean’s Gartner Market Shaper recognition signals a shift toward governed, context-rich no-code agents built for enterprise work.
- Where ChatGPT already works in online shopping—and where it does not
ChatGPT was quickly framed as a potential "Google killer" in online shopping. A new study by Frankfurt School of Finance & Management paints a more nuanced picture: For complex purchase decisions, ChatGPT can already be a relevant channel. Across broader e-commerce, however, its actual role remains much smaller than expected.
- 70% of Detailed Insurance Questions on AI Search Mention No Brand at All, Somantra Research Finds
70% of Detailed Insurance Questions on AI Search Mention No Brand at All, Somantra Research Finds azcentral.com and The Arizona Republic
- Keiretsu Forum MENA partners with FinBursa to bring AI-native deal infrastructure to MENA’s private markets
The partnership brings together Keiretsu Forum’s high-conviction deal curation and regional investor network with FinBursa’s intelligent deal infrastructure
- What Bundesliga’s Captain tells us about AI-powered CX
The Bundesliga has long talked about turning “data into devotion,” and now it has an agentic AI companion in its official app that lets fans chat in natural language, access live stats and historical context, and view personalized video highlights—all without leaving the app. Bundesliga is the premier professional soccer league in Germany. It built its new AI companion, called Captain, on AWS and embedded it in the official league app. For IT pros, this is more than just a clever sports-tech use case. It’s an early glimpse of what the customer experience will feel like when generative and agentic AI are not bolted on but, instead, become the primary way users navigate data, content, and services. Understanding Captain Captain serves as a conversational interface in the Bundesliga app, acting like a knowledgeable friend who watches every game with you. Fans can ask questions like, “How has Jamal Musiala been playing for Bayern this season compared to his national team?” and receive responses grounded in official league data, complete with stats, historical context, and relevant clips. Key capabilities include: On-demand access to live statistics, historical match data, tactical analysis, trivia, and video highlights via chat. Proactive insights during key moments, such as goals, penalties, milestones, where AI agents surface streaks, records, or parallels to historic games. A “coach mode” that gamifies learning the sport, adapting explanations and daily lessons to each fan’s knowledge level. Under the hood, Captain uses a multi-agent architecture built on Amazon Bedrock and Amazon Nova , dynamically routing each request to the appropriate model and workflow. Simple questions go to a lightweight model, while complex reasoning and data mashups are handled by more capable models, with text-to-SQL pipelines translating natural language into queries against the Bundesliga’s analytics stack. The result is a conversational front end built on a robust data platform. The data foundation What makes this notable is not only the UI but also the data infrastructure needed to deliver these capabilities. Historically, the Bundesliga tracked one point per player per second, generating roughly 3.6 million data points per match. With their move to 3D skeletal tracking—21 points per player at 50 frames per second—they now process roughly 200 million data points per match. That data lands in a modern analytics and AI stack on AWS, including: Streaming ingestion via Amazon MSK and other services to handle real-time feeds. A data lake and lakehouse foundation using S3 Tables and Apache Iceberg for open, schema-evolving storage. Query and analytics via Amazon Athena and associated text-to-SQL workflows for on-the-fly question answering. Vector stores to cache question-to-SQL patterns and reduce cost on repeated queries. On top of this, a set of agentic workflows continuously monitors live events, generates candidate “stories,” and pushes the best ones into Captain so fans see relevant narratives without having to know what to ask. This same foundation is already being used by the league to generate thousands of AI-powered narratives per season for broadcasters and editors, demonstrating how editorial and fan experiences can share a common AI backbone. For IT leaders, a key lesson learned is that data strategy is as important as model selection in building compelling generative AI experiences. What this signals about the future of customer experience Captain illustrates several important shifts that will define AI-driven CX across industries. Apps shift to companions. Instead of forcing users to navigate menus and features, the Bundesliga consolidates multiple use cases – scores, stats, historical research, video discovery, and learning – into a single conversational surface. This mirrors what enterprises will do with “digital relationship managers” in banking, “patient companions” in healthcare, and “shopping concierges” in retail. From reactive support to proactive storytelling. Most chatbots answer questions; Captain also looks ahead. When a major event occurs, agents work autonomously to find interesting angles, such as a record broken, a rare streak, a historical déjà vu, and push them to fans in real time. Imagine similar patterns in other domains: an insurance AI flagging a better coverage option at renewal, or a B2B vendor surfacing adoption risks before a renewal conversation. Experiences become adaptive. Coach Mode exemplifies progressive disclosure: it teaches a new fan the rules while offering tactical deep dives for advanced fans, all within the same interface. That’s exactly the model enterprises will need—systems that can explain a process to a novice and to a domain expert in different ways, without duplicating apps or content. Static journeys are evolving into AI-driven micro-journeys. The Bundesliga is using agentic AI to stitch together micro-journeys in real time. A question triggers an answer; a research agent follows up with deeper content; a video agent suggests highlights—all personalized and sequenced. In enterprise CX, journeys will increasingly be orchestrated by AI that adapts steps, channels, and content to context, rather than by rigid workflows. Implications for IT pros and CX leaders For IT pros, CX improvement requires rethinking the architecture, governance, and operating models to support AI-native experiences. Here are some things to consider. 1. Start with a data-first mindset . Captain only works because the Bundesliga invested years in building a robust data foundation. That includes high-fidelity tracking, consistent schemas, and streaming infrastructure. Before promising AI companions to your business stakeholders, you need to: Inventory your customer data sources and identify gaps in coverage, latency, and quality. Rationalize schemas and metadata so AI agents can reason across systems (CRM, transactional systems, content libraries) without brittle transformations. Plan for real-time or near-real-time data where “moment of truth” interactions matter. Without this groundwork, generative AI projects risk turning into expensive prototypes that can’t scale. 2. Think in terms of AI agents, not just models . Bundesliga’s architecture separates concerns into agents: a router agent to determine intent, stats agents to query the right backends, and research agents to autonomously investigate events and propose stories. IT teams should similarly design: Routing layers that determine whether a request is informational, transactional, or analytical. Specialized agents for data retrieval, verification, personalization, and safety. Clear SLAs and guardrails for agent interactions with core systems. This moves you from one big LLM to an orchestrated system in which different components can evolve independently. 3. Leverage dynamic routing for cost and performance . Bundesliga explicitly uses dynamic model routing. This approach uses lighter models for simple questions and more powerful ones for complex reasoning, cutting chat costs by more than a third without sacrificing accuracy. Enterprise IT can borrow this pattern: Use smaller models or even retrieval plus templating for repeatable queries. Reserve premium models for complex, high-value interactions. Continuously collect analytics on query types to refine routing policies. The result is an AI experience that scales economically rather than collapsing under inference costs. 4. Redefine UX around conversation and context . Captain’s UX is not just chat; it’s chat tightly coupled with video playback, stats visualization, and contextual recommendations. For IT and product teams, this means: Designing conversational experiences that can invoke micro-apps or widgets (e.g., forms, dashboards, media players) in context. Maintaining conversation state across channels, so a user can move from mobile to web or from chat to voice without losing context. Instrumenting these flows to understand where AI helps, confuses, or frustrates users. Generative AI should be treated as a new interaction layer, not a standalone feature. 5. Treat safety and trust as first-class requirements . Captain is built on official league data and protected by content safety guardrails to prevent hallucinations or inappropriate content. In enterprise settings, this translates to: Strict grounding of AI outputs in trusted systems of record. Fine-grained access controls so agents see only what they should. Human-in-the-loop workflows for high-risk outputs (e.g., financial advice, medical suggestions, legal communications). Trust will be the differentiator between AI experiences that delight and those that harm brand equity. How IT pros should think about next steps For most organizations, the Bundesliga’s Captain should be viewed as aspirational but certainly doable. Practically, IT pros can start by: Identifying one high-value, data-rich customer journey (e.g., onboarding, troubleshooting, order tracking) as a pilot. Standing up a modest but modern data foundation for that journey, including event streaming and a unified view of context. Prototyping an AI companion that combines retrieval-augmented generation with a couple of simple agents (for routing and follow-ups). Instrumenting everything—latency, cost, satisfaction, containment—to build the business case for expanding to more journeys. The Bundesliga shows what happens when an organization treats AI not as a feature but as a new way to connect with fans. IT leaders who treat generative and agentic AI as central to their customer experience strategy will be the ones who turn their own data into genuine customer devotion.
Score: 35🌐 MovesJun 22, 2026https://www.networkworld.com/article/4187954/what-bundesligas-captain-tells-us-about-ai-powered-cx.html - Nigeria’s StudyCrew launches AI-powered ed-tech platform
Nigerian startup StudyCrew has launched an AI-powered ed-tech platform designed to transform how students study, collaborate, and stay productive. Founded last year by cybersecurity student Josiah Dhev, StudyCrew is an AI-powered, gamified learning platform that aims to make studying more engaging and consistent for students. It combines AI tutors, study streaks, progress tracking, and social [...] The post Nigeria’s StudyCrew launches AI-powered ed-tech platform appeared first on Disrupt Africa .
- Zendure Unveils the ZEN+ HOME AI Energy Ecosystem at Intersolar 2026
Zendure Unveils the ZEN+ HOME AI Energy Ecosystem at Intersolar 2026 The Straits Times
- L’Oréal brings Maybelline virtual try-on to ChatGPT
L’Oréal has announced a collaboration with OpenAI that will bring Maybelline New York’s virtual makeup try-on feature into ChatGPT. The announcement was made at VivaTech 2026. The partnership covers consumer-facing shopping tools, product discovery, advertising pilots, research, and internal content production. The collaboration also covers L’Oréal’s internal use of AI in research, formulation, content production, […] The post L’Oréal brings Maybelline virtual try-on to ChatGPT appeared first on AI News .
Score: 35🌐 MovesJun 22, 2026https://www.artificialintelligence-news.com/news/loreal-maybelline-virtual-try-on-chatgpt/ - When you judge a book by its AI cover: the debate escalates
Readers have always judged books by their covers. And when covers start looking like they're the result of a handful of prompts instead of well thought out creative briefs, the concerns are multifold. Readers begin to question the originality of the text, the designer's skill in shaping curiosity rather than killing it is clouded in doubt and publishers worry that interest in the book will take a hit.
- Phillips Consulting, Skillsoft and LRMG Convene senior executives on workforce readiness in the age of AI
Phillips Consulting, Skillsoft and LRMG Convene senior executives on workforce readiness in the age of AI Business Insider Africa
- You Can't Trust What You Can't See
You Can't Trust What You Can't See Fortune
- The Death of the AI Pilot
The Death of the AI Pilot Fortune
Score: 35🌐 MovesJun 22, 2026https://fortune.com/media/9627b3f8-aea0-470e-806f-d3e4bfe3c320?activePlaylistName - How To Help Employees See AI As A Workplace Ally
By positioning AI as a tool that supports employees rather than competes with them, organizations can encourage greater adoption, experimentation and trust.
Score: 35🌐 MovesJun 22, 2026https://www.forbes.com/councils/forbestechcouncil/2026/06/22/how-to-help-employees-see-ai-as-a-workplace-ally/ - High Five, AI Recruitment Platform for SEA Talent, Screens 5,000 Candidates, Adds Multilingual AI Interviewer
High Five, AI Recruitment Platform for SEA Talent, Screens 5,000 Candidates, Adds Multilingual AI Interviewer USA Today
- Gemini can now help you fix those broken Google Sheets formulas
Google Sheets formula errors are a problem of the past with this new feature.
Score: 35🌐 MovesJun 22, 2026https://www.androidauthority.com/google-sheets-gemini-formula-fixer-3680088/ - Deploying AI Fleet Visibility Allows Route-Based Franchises to Mitigate Liability and Optimize Service Delivery
Deploying AI Fleet Visibility Allows Route-Based Franchises to Mitigate Liability and Optimize Service Delivery azcentral.com and The Arizona Republic
- Building an Offline “Life Memorizer” with Gemini 2.0 & Qdrant Edge
A privacy-first, multimodal memory system that indexes your senses and runs entirely on-device — no cloud retrieval, no server process, no network dependency Consider this. You are trying to find where you left an item, like your wallet or keys, inside your own house. You know you saw it earlier today, but you cannot remember the exact spot. Hardware engineers have mostly solved the problem of capturing this data with wearable smart glasses and continuous POV cameras that log everything you see, hear, and read. But as developers, we are still stuck when it comes to managing that data. The standard solution is to take all that sensory data and stream it straight to a cloud server for processing and storage. From an infrastructure standpoint, it looks easy. But for a personal product, it introduces a massive mess. A personal log contains incredibly sensitive information, the inside of your home, private conversations, financial documents, and exact locations. Sending all of this to a remote server introduces constant security risks, network latency, and a total system failure the moment your internet connection drops. A personal memory assistant should be useful anywhere, especially when you are offline. The solution is to move the entire storage and search stack onto the device itself. I built a tool for myself called Life Memorizer . It is a local system that ingests multimodal sensory streams and searches through them without any cloud dependency at runtime. It combines Gemini Embedding 2 to process images, audio, and text into a single unified space, and Qdrant Edge to store and index everything directly within the application process. The full implementation, including the media processing scripts and command-line interface, is open-source and available on GitHub. High-Level System Architecture Flowchart | T he 4-stage pipeline: User & Sensory Input → Embedding & Optimization Layer → Embedded Storage (Qdrant Edge) → Recall & Generation Pipeline Why This Stack? When you build a system that indexes sensory data in real time, hardware limits force you to be highly selective about your resource budget. If you are running your application on an edge device like a Raspberry Pi or an NVIDIA Jetson or your local mobile device, you cannot afford to waste memory or CPU cycles on unnecessary infrastructure. 1. Gemini Embedding 2 : One Model, One Coordinate System Traditionally, searching across text, audio, and video meant loading three distinct models into memory: Whisper for audio transcription, CLIP for images, and a Sentence Transformer for text. Each of these models output vectors in completely different dimensional spaces, trained on entirely different data objectives. If you type a text query like “keys on the table,” it will not align mathematically with a CLIP vector of a photo unless you build, train, and maintain a custom translation layer to map the coordinate systems together. Gemini Embedding 2 completely eliminates this issue. It natively projects text, images, and audio into the exact same 3072-dimensional space. The model maps different input modalities into a single, unified coordinate system. A text description and a JPEG image of the same scene land near each other based on meaning alone. For an edge application, this removes the need for translation layers, drastically reducing pipeline bugs and saving critical memory. 2. Qdrant Edge : Works Like a Library, Persists Like a Database Most production vector databases follow a server-client architecture. You run the database as a separate server process often inside a Docker container and your application communicates with it over network ports via HTTP or gRPC. While this makes sense for a distributed cloud setup, it is a massive roadblock for a local developer tool or a wearable edge device. Making a local system depend on a running database service adds overhead, setup friction, and infrastructural complexity. Qdrant Edge functions conceptually like SQLite but built specifically for vector data. You import it as a standard Python library, point it at a local directory on your filesystem, and all vector storage, indexing, and querying happen directly inside the memory space of your Python process. pip install qdrant-edge-py Why I Picked Qdrant Edge Over Others? When I started mapping out the architecture for Life Memorizer , I evaluated several local storage options. My first instinct was to look at lightweight relational or document-based embedded databases that offer basic vector extensions, such as SQLite (with extensions like sqlite-vec) or DuckDB . While those tools are incredible for structured data analytics, they quickly fall apart when you treat them as dedicated, heavy-duty vector stores on constrained hardware. They often lack advanced Hierarchical Navigable Small World (HNSW) graph indexing natively for edge Python environments. This means as your historical memory log grows, your search latency scales linearly turning a quick lookup into a slow, sequential table scan that drains your CPU. I also considered running a full production-grade vector database locally, like a standalone instance of Chroma , Milvus , or Weaviate . But requiring an end-user to manage a running Docker daemon or keep a separate background database server alive just to index their smart glasses feed felt completely wrong. It would solve a data problem while creating three new infrastructure problems for a lightweight wearable project. Qdrant Edge hit the exact sweet spot for this project for three specific reasons: Process-Level Integration: Unlike server-dependent options, it requires zero background daemons, zero open network ports, and zero container management. It lives directly inside my Python code and closes cleanly when the execution ends. Smart Memory Management: It utilizes memory-mapped (memmap) files. Instead of loading every single vector into active RAM—which would cause an instant Out-of-Memory (OOM) crash when running alongside an on-device language model—the host operating system handles the data paging automatically. It swaps vector segments to disk dynamically. Production-Grade Filtering: Unlike simple flat-file vector array scripts (like raw FAISS indexes), Qdrant Edge brings the exact same advanced payload filtering capabilities as its enterprise cloud server. I can restrict searches by metadata — like location_context == 'Home'—directly during the HNSW graph traversal rather than filtering results after the search is complete, keeping lookups incredibly fast on low-powered edge hardware. System Data Flow Architecture | Raw sensory capture → Gemini embedding → EdgeShard write → payload index → search & retrieval loop Environment Setup & Qdrant Edge Initialization Tech Stack: Prerequisites qdrant-edge-py>=0.7.2 # embedded vector store google-genai>=0.3.0 # Gemini API client numpy>=1.24 # vector math pydantic>=2.5 pydantic-settings>=2.1 typer>=0.12 # CLI framework rich>=13.7 # terminal output formatting Optional packages for real media handling (not needed for the mock pipeline): opencv-python-headless>=4.9 # frame sampling from video imageio-ffmpeg>=0.4.9 # audio track extraction Pillow>=10.0 # image I/O helper pytesseract # OCR from frames Install from the project root: pip install -e ".[media]" # includes optional media extras # or pip install -r requirements.txt The mock pipeline in this tutorial is structurally identical to the production feed. Every module, every interface, every storage call is the same, the only difference is what feeds data into ingest.py. Project Structure The full implementation lives on GitHub. Before walking through each module, here’s how the project is organized: life-memorizer/ ├── .env.example # Template for environment variables ├── pyproject.toml # Build system, metadata, and dependencies ├── requirements.txt # Pinned requirements file ├── ARCHITECTURE-DOCUMENTATION.md # System architecture & codebase knowledge graph ├── samples/ # Sample video files for quick testing │ ├── pov-urban-bike-ride-through-city-streets.mp4 │ └── vibrant-city-street-with-shops-and-pedestrians.mp4 ├── life_memorizer/ # Core source package │ ├── cli.py # Command-line interface definitions │ ├── config.py # Configuration settings loader & validator │ ├── embeddings.py # Multi-modal embedding (Gemini / Matryoshka) │ ├── ingest.py # Ingestion pipeline coordinating media processing │ ├── media.py # Media processing utils (OpenCV, ffmpeg, Tesseract) │ ├── mock_data.py # Mock dataset for quick seeding and testing │ ├── models.py # Core Pydantic data schemas & enums │ ├── rag.py # Local Retrieval-Augmented Generation flows │ ├── recall.py # Recall engine for vector & hybrid queries │ └── store.py # Qdrant Edge vector store wrapper └── tests/ ├── conftest.py # Shared pytest fixtures ├── test_embeddings.py # Unit tests for embedding layers ├── test_rag.py # Unit tests for LocalRAG pipeline ├── test_step5.py # Unit tests for quantization & TTL pruning └── test_store_and_recall.py # Unit tests for storage and retrieval The article walks through the five core modules that form the pipeline: [embeddings.py] → [models.py] → [store.py] → [recall.py] → [rag.py] The ingest.py and media.py modules handle the real-hardware media processing layer: OpenCV frame sampling, ffmpeg audio extraction, Tesseract OCR, which fully documented in ARCHITECTURE-DOCUMENTATION.md. Full source: GitHub - satyam671/Life-Memorizer-With-Gemini-Embedding-2-And-Qdrant-Edge: A privacy-first, local digital twin for smart glasses that continuously indexes what a user sees, hears, and reads, allowing instant local semantic recall. Part 1: Initializing Qdrant Edge Setting Up the Local Shard The core primitive in Qdrant Edge is the EdgeShard: a self-contained storage unit that manages its own vector index, payload data, and HNSW graph, all backed by files in a local directory you specify. HNSW (Hierarchical Navigable Small World) is the approximate nearest-neighbor index that makes fast vector search possible. In Qdrant Edge, this index is built and queried entirely within your process, using the same underlying Rust implementation as the full Qdrant server. The shard initialization follows a simple rule: if edge_config.json exists in the target directory, the shard already has data and you load it; otherwise you create it fresh with a new config. import qdrant_edge as qe from pathlib import Path db_path = Path("./life_memorizer_db") db_path.mkdir(parents=True, exist_ok=True) config_json = db_path / "edge_config.json" # Load existing or create a new local shard if config_json.exists(): client = qe.EdgeShard.load(str(db_path)) else: client = None # proceed to create with config below If the directory already has a shard, .load() reads the configuration and data from disk and returns a ready-to-query instance in seconds. If you call .create() on a directory that already contains data, it raises an error. That's intentional, the shard is a persistent storage unit, not a connection object. Treat it like one. Don't try to recreate it on every startup. Schema Design via Named Vectors Here’s the core schema decision. Instead of three separate databases for visual frames, audio transcripts, and OCR text, all three live as named vectors inside a single Qdrant point . Each point represents a moment in time, a snapshot of what the device captured at a specific second. That moment might carry a visual embedding , an audio embedding , an OCR embedding , or all three depending on what was detectable. Named vectors let you search any of those spaces independently during targeted queries, or fuse across all of them during hybrid search. vector_params = qe.EdgeVectorParams( size=768, # MRL-truncated from 3072 — more on this below distance=qe.Distance.Cosine, on_disk=True, # offloads vector index to disk, saves RAM ) vectors_config = { "video_frame": vector_params, "ambient_audio": vector_params, "ocr_log": vector_params, } config = qe.EdgeConfig( vectors=vectors_config, on_disk_payload=True, ) client = qe.EdgeShard.create(str(db_path), config) Enabling on_disk=True instructs Qdrant Edge to page the vector indices using the host filesystem rather than keeping them entirely in physical memory. This optimization lowers the baseline RAM usage of the script. On a device that's also running an on-device LLM, that tradeoff is almost always correct. Reducing Vector Dimensions via Matryoshka Truncation: Storing 3072 Dimensions in 768 Gemini Embedding 2 produces 3072-dimensional float32 vectors, which require 12 KB of storage per vector. When you are logging multiple video frames, transcripts, and OCR detections every minute, the storage requirement scales up quickly. To optimize local storage, the codebase uses Matryoshka Representation Learning (MRL). The embedding model is trained to structure semantic information so that the earliest coordinates contain the highest information density. You can drop the trailing dimensions and truncate the vector to 768 dimensions to achieve a 4x savings in disk space with minimal loss in retrieval accuracy. When you truncate a vector, you modify its length, which breaks Cosine distance calculations. You must re-normalize the truncated vector back to a unit length to ensure the vector database calculates similarity scores accurately. import numpy as np import math def _l2_normalize(vec: np.ndarray) -> np.ndarray: norm = float(np.linalg.norm(vec)) if norm == 0.0 or math.isnan(norm): return vec return vec / norm def matryoshka_truncate(vector: np.ndarray, dim: int) -> np.ndarray: if vector.shape[0] < dim: vector = np.pad(vector, (0, dim - vector.shape[0])) truncated = vector[:dim].astype(np.float32) return _l2_normalize(truncated) Two lines of actual logic wrapped in safety checks. The zero-norm guard matters: an all-zeros vector causes a division by zero that produces NaN values in your index, and NaN-contaminated vectors corrupt similarity scores for every query that touches that segment of the HNSW graph. Always guard it. Part 2: Ingesting the Senses Simulating the Smart Glasses Feed and Setting Up the Data Pipeline We need data to feed the pipeline. In production this comes from a camera, a microphone, and an OCR module. The project’s mock_data.py provides a structured dataset that mirrors what a real wearable feed would produce — visual scenes, transcribed audio fragments, and OCR-captured text, each tagged with a location and a timestamp offset: The MockMoment dataclass mirrors the structure of a real Moment object closely enough that all downstream pipeline code runs unchanged: from dataclasses import dataclass, field from typing import Optional @dataclass(frozen=True) class MockMoment: minutes_ago: int location: str scene: Optional[str] = None # text description of visual frame speech: Optional[str] = None # transcribed audio ocr: Optional[str] = None # text captured from surfaces media_file_path: Optional[str] = None tags: tuple[str, ...] = field(default_factory=tuple) MOCK_MOMENTS = ( MockMoment( minutes_ago=88, location="Home", scene="a set of brass house keys lying on the wooden hallway table next to a blue ceramic bowl", media_file_path="media_cache/home/hallway_table_keys.jpg", ), MockMoment( minutes_ago=64, location="Street", speech="Sarah says: can you buy oat milk and fresh basil on the way back?", media_file_path="media_cache/street/with_sarah.jpg", ), MockMoment( minutes_ago=58, location="Cafe", ocr="MAPLE & CO\nFlat White 4.20\nCappuccino 4.00\nOat milk +0.60", media_file_path="media_cache/cafe/menu_board.jpg", ), ) Each MockMoment represents a single sensory event with one dominant modality — visual scene, ambient speech, or OCR capture tagged to a location and a point in time. The scene field holds a text description standing in for actual JPEG bytes. When the real pipeline runs, embed_image() receives raw image bytes from media.py. The downstream ingestion code is identical either way. Computing the Vectors: Generating Aligned Embeddings All three modalities go through the same Gemini model and the same _embed_content call. The model determines modality from the input type — a raw string is text, a byte part with image/jpeg is an image, a byte part with audio/wav is audio. What comes back is always a vector in the same 3072-dimensional space. That’s the entire architecture argument in one wrapper class: class GeminiEmbedder: def embed_text(self, text: str) -> list[float]: return self._embed_content(text) def embed_image(self, image_path: str | Path) -> list[float]: part = self._file_part(image_path, default_mime="image/jpeg") return self._embed_content(part) def embed_audio(self, audio_path: str | Path) -> list[float]: part = self._file_part(audio_path, default_mime="audio/wav") return self._embed_content(part) def _embed_content(self, content) -> list[float]: from google.genai import types config = types.EmbedContentConfig(output_dimensionality=3072) response = self._client.models.embed_content( model="gemini-embedding-2", contents=content, config=config, ) values = response.embeddings[0].values vec = np.asarray(values, dtype=np.float32) return matryoshka_truncate(vec, self.dim).tolist() Text goes in as a string. Images and audio go in as typed byte parts with a MIME type. The MRL truncation happens at the exit of _embed_content, so every downstream consumer always receives a 768-dim, L2-normalized vector regardless of input modality. That consistency is deliberate: the storage layer doesn’t need to know which embedder produced a given vector, and the retrieval layer doesn’t need to handle different vector sizes per index. When LIFE_MEMORIZER_FAKE_EMBEDDINGS=1 is set, the project substitutes a deterministic fake embedder that generates random-but-consistent 768-dim vectors from a hash of the input text. This lets you run and test the full pipeline: seeding, storing, searching without an API key or internet connection. Part 3: Upserting Multi-Vector Points to Qdrant: Storing the Points Payload Design Each point stored in the EdgeShard carries two things: its named vectors, and a metadata payload used for filtering. The payload holds temporal information, location context, and text extracts from the moment. It deliberately excludes raw image bytes and audio clips, those stay in the media_cache/ directory on disk, referenced only by path if store_media_path is enabled. def payload(self, store_media_path: bool = True) -> dict[str, Any]: return { "timestamp": self.timestamp.isoformat(), "timestamp_epoch": int(self.timestamp.timestamp()), "location_context": self.location_context, "media_file_path": self.media_file_path if store_media_path else None, "source_clip": self.source_clip, "transcript": self.transcript, "ocr_text": self.ocr_text, "is_summary": self.is_summary, "summary_count": self.summary_count, } The fields is_summary (boolean flag) and summary_count track data compression state. When local storage limits are reached, the system clusters older historical data and merges them into a single mean-pooled "summary" point. These fields inform the retrieval loop whether a query match is a specific historical point or a consolidated overview of a particular timeframe. A digest point with summary_count=12 represents a location-cluster of 12 distinct moments from that time window, and the retrieval layer can surface that context in the response rather than treating it as a single event. The store_media_path flag gives you a simple privacy lever. Set it to False and the shard contains nothing but abstract vector math, timestamps, and location labels — no file references, no text fragments. We'll come back to where the actual privacy boundary sits, and why this flag alone doesn't give you the guarantee you might assume. Qdrant Edge Vector Database Point Structure | The Complete Anatomy of a Database Point Carrying Metadata and Named Vectors. Upserting to the Shard def upsert_moments(self, moments: Iterable[Moment]) -> int: store_path = self.settings.store_media_path points = [] for moment in moments: if not moment.vectors: continue points.append( qe.Point( id=moment.id, vector=dict(moment.vectors), # video_frame, ambient_audio, ocr_log payload=moment.payload(store_media_path=store_path), ) ) if not points: return 0 self.client.update(qe.UpdateOperation.upsert_points(points)) return len(points) Moments without any vectors are skipped before the batch is constructed. In a real wearable feed, this is common, frames with no detectable visual content, audio segments that are purely ambient noise below the transcription threshold, surfaces with no readable text. Filtering them out early keeps your point count clean and avoids empty-vector entries that would corrupt hybrid search scoring. Batching the upserts reduces disk write operations noticeably compared to upserting one point at a time. Running the Project Before looking at the query output, here’s how to actually run the project. There are two modes depending on whether you have a Gemini API key. Mode 1: Mock / Offline Mode (No API Key Required) This is the fastest way to get the full pipeline running. The fake embedder generates deterministic vectors from the mock dataset, so init → seed → query → ask, all work without touching the network. Step 1: Set environment variables Windows PowerShell: $env:LIFE_MEMORIZER_FAKE_EMBEDDINGS="1" $env:LIFE_MEMORIZER_FAKE_RAG="1" Bash (macOS / Linux): export LIFE_MEMORIZER_FAKE_EMBEDDINGS=1 export LIFE_MEMORIZER_FAKE_RAG=1 Step 2: Initialize the local database life-memorizer init This creates the ./life_memorizer_db/ directory and writes the initial edge_config.json with the named vector schema. Running init on an already-initialized database is safe — it detects the existing config and skips re-creation. Step 3: Seed the mock data life-memorizer seed Loads all MockMoment entries from mock_data.py, generates fake embeddings for each, and upserts them to the local shard. You'll see a progress output in the terminal as each moment is processed and stored. Step 4: Query and ask (covered in detail in Part 4) life-memorizer recall "where did I leave my keys?" --modality image life-memorizer ask "where did I leave my keys?" Mode 2: Live Video Ingestion (Real Gemini API) This mode uses actual Gemini embeddings and ingests real video content from your local files. Step 1: Configure your .env file cp .env.example .env Open .env and set your credentials: GEMINI_API_KEY=AIzaSy...YourActualKeyHere LIFE_MEMORIZER_FAKE_EMBEDDINGS=0 LIFE_MEMORIZER_FAKE_RAG=0 Step 2: Disable offline environment flags Windows PowerShell: $env:LIFE_MEMORIZER_FAKE_EMBEDDINGS="0" $env:LIFE_MEMORIZER_FAKE_RAG="0" Bash (macOS / Linux): export LIFE_MEMORIZER_FAKE_EMBEDDINGS=0 export LIFE_MEMORIZER_FAKE_RAG=0 Step 3: Initialize the database life-memorizer init If you previously ran Mock Mode and want a clean slate, delete ./life_memorizer_db/ first before re-initializing. Step 4: Ingest a video file # Point to any video file on your machine (e.g. samples/walk.mp4) life-memorizer ingest --video samples/pov-urban-bike-ride-through-city-streets.mp4 --location Home The ingestion pipeline samples the video into frames, extracts audio chunks, runs OCR where applicable, generates real Gemini embeddings for each, and writes everything to the local shard. Depending on video length and your machine, this can take a few minutes. The --location tag gets stored in each point's payload and used as a metadata filter during retrieval. Part 4: Querying Your Past: Multi Modal Retrieval With the database seeded, the recall layer routes your natural language queries to the right vector space. Each scenario below shows the CLI command, the underlying recall code, and a placeholder for the actual terminal output. Multi-Modal Retrieval Pipeline | A U ser Query being Embedded → Routed to Visual/Audio/OCR Named Vector Indices → Scores Fused with Weights → Top-K Results Returned with Payload Scenario A: Visual Search A natural language query gets embedded as text and searched against the video_frame index. The cross-modal match works because Gemini maps the text description and the visual content into the same coordinate space during training — you don't need a visual query to search visual memories. # Mock Offline Mode life-memorizer recall "where did I leave my keys?" --modality image The underlying recall call in recall.py: def visual_search(self, query: str, **kwargs) -> list[RecallHit]: kwargs.setdefault("target", Modality.image) return self.recall(query, modality=Modality.text, **kwargs) One function call. The modality routing, the embedding call, and the HNSW search all happen inside self.recall(). The target=Modality.image argument tells the recall engine which named vector index to search against. Live Video Ingestion (Real Gemini API) Provide a video file on your system to analyze. The video will be sampled into image frames, audio chunks will be extracted, OCR will be run, and everything will be embedded: # Point to any video file on your machine (e.g. samples/walk.mp4) life-memorizer ingest --video samples/pov-urban-bike-ride-through-city-streets.mp4 --location Home Ask questions related to your ingested video: life-memorizer recall "where did i see the red car today while i was cycling?" --modality image Scenario B: Audio Recall Same routing logic, different named index. The query targets the ambient_audio vector space, which holds embeddings of transcribed speech from the sensory feed. life-memorizer recall "what did Sarah say to buy?" --modality audio The underlying recall call in recall.py: def audio_recall(self, query: str, **kwargs) -> list[RecallHit]: kwargs.setdefault("target", Modality.audio) return self.recall(query, modality=Modality.text, **kwargs) In the mock dataset, audio embeddings are generated from the speech field text. In production, you'd pass raw .wav bytes to embed_audio() directly — the Gemini model handles audio transcription and embedding in a single API call, and the retrieval path is identical to what you see here. Scenario C: Hybrid Search with Location Filtering For broader queries that benefit from evidence across multiple modalities, the hybrid search fuses results from all three named indices weighted by relevance, optionally filtered to a specific location from the payload. life-memorizer recall "the cafe menu" --location Cafe --hybrid def hybrid_search( self, query_vector: list[float], weights: dict[str, float], limit: int = 5, location_context: Optional[str] = None, ) -> list[RecallHit]: fused = {} for vector_name, weight in weights.items(): if weight <= 0: continue hits = self.search( vector_name=vector_name, query_vector=query_vector, limit=limit * 3, location_context=location_context, ) for hit in hits: weighted = hit.score * weight existing = fused.get(hit.moment.id) if existing is None: fused[hit.moment.id] = RecallHit( moment=hit.moment, score=weighted, matched_vector=hit.matched_vector, ) else: existing.score += weighted if weighted > hit.score * weights.get(existing.matched_vector, 1.0): existing.matched_vector = hit.matched_vector ranked = sorted(fused.values(), key=lambda h: h.score, reverse=True) return ranked[:limit] Each index returns limit * 3 candidates. Scores accumulate per point ID across the three index searches, then the merged pool gets re-sorted by total weighted score. The location filter runs as a payload filter inside each individual .search() call, not post-retrieval on the fused pool. You're not fetching three hundred candidates and then discarding most of them. You're constraining the HNSW search before it runs. The weights are tunable via config.py. For most life memorizer queries, weighting video_frame and ocr_log higher than ambient_audio gives better precision because visual and text matches are more semantically specific. For voice-first applications, "what did people say on the street today?" shift weight to ambient_audio. Asking Grounded Questions via Local RAG Beyond ranked recall results, you can ask natural language questions and get a grounded answer from the on-device language model: Mock Mode (offline stub, no model required): life-memorizer ask "where did I leave my keys?" OR life-memorizer ask "what did Sarah ask me to buy?" Live Mode with Ollama (Gemma-2b, fully local): # Pull the model first ollama pull gemma2:2b life-memorizer ask "where did I spotted a white truck while cycling?" Live Mode with Gemini API backend: # Bash export LIFE_MEMORIZER_RAG_BACKEND=gemini # PowerShell $env:LIFE_MEMORIZER_RAG_BACKEND="gemini" life-memorizer ask "when did a couple cross me while I was walking on the city streets?" Part 5: Production Edge Optimization & Privacy Considerations Quantization: Staying Inside Your RAM Budget Even at 768 dimensions, float32 vectors consume memory at scale. A device logging one visual frame every five seconds accumulates 720 vectors per hour on the visual channel alone. At 768 floats × 4 bytes each, that’s roughly 2.2 MB per hour just for video_frame — manageable until you're also holding ambient_audio and ocr_log, plus the HNSW graph structure, plus whatever LLM you're running concurrently. Qdrant Edge supports two quantization modes, configurable at shard creation time: ▣ Scalar (Int8) : Each float32 component (4 bytes) is quantized to an int8 (1 byte). That’s a 4x reduction in vector storage — the 2.2 MB per hour becomes 550 KB per hour. Search accuracy is well-retained because the quantization error is small and the Cosine distance ranking is robust to small value noise. This is the right default for most edge applications. ▣ Binary : Each float component becomes a single bit. Up to 32x compression. Bit comparisons are fast, which improves search speed. The tradeoff is a measurable drop in recall accuracy for semantically nuanced queries. The standard mitigation is oversampling: fetching a larger candidate pool (limit * k) and then re-ranking with the original float vectors. More pipeline steps, but it keeps you inside tight RAM budgets. def _quantization_config(self): q = self.settings.quantization if q is Quantization.scalar: return qe.ScalarQuantizationConfig( type=qe.ScalarType.Int8, always_ram=True, ) if q is Quantization.binary: return qe.BinaryQuantizationConfig(always_ram=True) return None always_ram=True keeps the quantized vectors in physical RAM for fast retrieval while the full-precision vectors are paged to disk. Start with scalar. Move to binary only if scalar quantization still leaves you above your available RAM budget. Storage Compression (Quantization — Scalar & Binary) | (Diagram comparing float32 baseline vs int8 scalar (4x, high recall retention) vs binary (32x, recall tradeoff requiring oversampling + re-rank)) Memory Consolidation: Managing Local Storage Limits An edge device logging continuously will fill its storage. The naive response is periodic deletion of old records. The problem with simple deletion is that you lose historical context permanently, a moment from three weeks ago might be exactly what a query needs today. The better approach is mean-pool consolidation. Group expired moments by location context, compute the centroid of their vectors across all named spaces, extractively merge their text logs, and write a single “digest” point before deleting the originals. You compress many points into one while preserving semantic searchability. @staticmethod def _mean_pool_vectors(records: list[qe.Record]) -> dict[str, list[float]]: sums = {} counts = {} for rec in records: vectors = rec.vector or {} if not isinstance(vectors, dict): continue for name, vec in vectors.items(): arr = np.asarray(vec, dtype=np.float32) sums[name] = sums.get(name, np.zeros_like(arr)) + arr counts[name] = counts.get(name, 0) + 1 pooled = {} for name, total in sums.items(): mean = total / max(counts[name], 1) norm = float(np.linalg.norm(mean)) if norm > 0: mean = mean / norm pooled[name] = mean.astype(np.float32).tolist() return pooled The resulting digest point gets written with is_summary=True and summary_count=N in its payload, so retrieval code can distinguish it from raw moment points and format the response accordingly. Mean pooling is lossy, that’s the honest version of this. The centroid of twelve distinct visual memories is not a meaningful visual memory itself. What survives consolidation is the approximate semantic location of that memory cluster. Broad topical queries (“did anything happen at home last week?”) still resolve correctly. Precise factual queries (“show me the exact frame where X was visible”) do not. Design your TTL (time to live) windows with that boundary in mind. If a category of memories needs long-term exact retrieval, archive raw vectors to cold storage or a Qdrant server instance before consolidating. Memory Consolidation (Summarization) | Diagram showing N expired points grouped by location → mean-pooled centroid vector + extractive text merge → single digest point replaces originals, with storage reduction labeled Privacy: Where the Real Boundary Is Storage and retrieval happen entirely on-device. That part is genuinely offline. But the “100% local” framing has a gap worth naming directly. Gemini Embedding 2 is a cloud API. Every time you generate an embedding during ingestion, the source content, the image bytes, the audio clip, the scene description goes to Google’s servers to produce the vector. The vector comes back and lives locally. But the raw sensory data made a round trip. This applies to query-time embedding too: when you run life-memorizer recall, your query text gets sent to Gemini to generate its embedding before the local HNSW search runs. Setting store_media_path=False removes file references from the local database, but it doesn't change what happens during the embedding call. The privacy benefit of that flag is about what's stored locally after the fact, not about what left the device during ingestion. Two real mitigations exist. ▣ First, embed during connected windows and cache results, your querying is then fully offline since the vectors are already stored. ▣ Second, if you need end-to-end air-gapped operation, replace Gemini Embedding 2 with a local model. Qdrant’s FastEmbed library runs on-device with no API calls. The unified multimodal quality won’t match a cloud model, but your data never leaves the device at any stage. That’s the actual tradeoff. Pick based on your threat model, not the marketing pitch. Part 6: Closing the Loop with Local RAG Retrieval surfaces relevant memory points with scores and payload metadata. Getting from those points to a conversational answer requires a language model. The project supports two RAG backends, configured via LIFE_MEMORIZER_RAG_BACKEND in your .env or environment. ▣ Ollama backend (default) : Runs Gemma-2b locally via the Ollama HTTP API. Zero cloud calls after setup. Requires ollama pull gemma2:2b before first use. Latency depends on your hardware, but on a modern laptop you're typically looking at 2–5 seconds for a short answer. ▣ Gemini API backend : Uses the Gemini API for generation. Faster and higher quality than Gemma-2b, but adds a network round trip and API spend. Good for development and testing; think carefully before using it in a privacy-sensitive deployment. Both backends receive the same structured prompt: def build_prompt(question: str, hits: list[RecallHit]) -> str: context = build_context_block(hits) if hits else "(no relevant memories found)" return ( f"Recalled memories:\n{context}\n\n" f"Question: {question}\n" f"Answer using only the memories above." ) # Inside OllamaGenerator.generate: payload = { "model": self.model, "system": "Answer using ONLY the recalled memories. Never invent details.", "prompt": prompt, "stream": False, } data = json.dumps(payload).encode("utf-8") req = urllib.request.Request( f"{self.host}/api/generate", data=data, headers={"Content-Type": "application/json"}, ) The system prompt is load-bearing. “Never invent details” restricts the model to what’s in the context block. Without it, smaller models like Gemma-2b fill gaps with plausible-sounding fabrications. The instruction doesn’t guarantee hallucination-free output, nothing does at this scale, but it meaningfully reduces the frequency, especially for factual queries where the correct answer is already in the retrieved context. The build_context_block() function formats each RecallHit into a structured text block: timestamp, location, matched modality, and the relevant text extract (transcript or OCR). The model sees this as a list of dated, located memory fragments and grounds its answer against them. This RAG step transforms the pipeline from a vector search tool into a usable assistant. Without it, you get ranked memory points with scores and metadata. With it, you get a natural language answer grounded entirely in local evidence, no external API call during retrieval, no context leaving the device after ingestion. Architectural Takeaways ▣ Unified multimodal embeddings eliminate alignment engineering. If you’re building any system that searches across mixed input types, a model that projects all of them into the same coordinate space removes an entire class of architectural problems. The alternative, separate models, separate vector spaces, explicit translation layers work but creates fragility at every join. ▣ In-process vector storage is the right model for edge hardware. Client-server databases carry implicit assumptions about network reliability and persistent background processes that don’t hold on constrained or intermittently connected devices. Qdrant Edge removes those assumptions at the library level. ▣ Decouple ingestion from storage writes. The pipeline processes media, generates embeddings, and writes to the shard as separate steps. Keeping them decoupled lets you batch writes, add retry logic on the embedding step, and run optimize() explicitly after large ingest batches rather than during hot query paths. ▣ Start with scalar quantization. 4x compression, minimal recall loss. Binary is for when scalar still leaves you over budget, not a default. ▣ Mean pooling is principled memory decay, not deletion. Semantic neighborhoods survive consolidation. Exact moment recall does not. Design TTL windows around which of those properties your application actually needs. ▣ Know your privacy boundary. If the embedding model is cloud-hosted, source data leaves the device during ingestion and at query time. That’s a design constraint, not a deal-breaker. Build around it consciously. Conclusion: Experiment and Build Building this project showed me that we no longer need to rely entirely on heavy cloud setups to build smart, contextual software. You can design high-performance, intelligent local pipelines that respect data privacy and run entirely within an application process space. If you want to see how this performs on your own machine, clone the repository, load up a local sample video, and run through the workflows. Experiment with the vector weights, try out different quantization modes, or swap in a purely local embedding setup to see how far you can push edge vector search. The complete codebase is open-source and live right now, clone it, run locally and experiment with it: https://github.com/satyam671/Life-Memorizer-With-Gemini-Embedding-2-And-Qdrant-Edge . Feel free to explore the modules, open an issue if you encounter bugs, or modify the architecture for your own tools. GitHub - satyam671/Life-Memorizer-With-Gemini-Embedding-2-And-Qdrant-Edge: A privacy-first, local digital twin for smart glasses that continuously indexes what a user sees, hears, and reads, allowing instant local semantic recall. References Qdrant Edge Documentation: https://qdrant.tech/documentation/edge/ Qdrant Edge Quickstart: https://qdrant.tech/documentation/edge/edge-quickstart/ Gemini Embedding 2: https://docs.cloud.google.com/gemini-enterprise-agent-platform/models/gemini/embedding-2 Building an Offline “Life Memorizer” with Gemini 2.0 & Qdrant Edge was originally published in Towards AI on Medium, where people are continuing the conversation by highlighting and responding to this story.
- What nine AI workflow submissions reveal about Echelon Singapore’s builder pipeline
The useful test of an AI competition is whether it can repeatedly turn broad interest into specific, inspectable builder output. That is the most important signal from the AI Workflow Competition at Echelon Singapore 2026. Nine other entries reviewed by e27 showed builders working through the harder middle ground of AI adoption: messy inputs, scattered knowledge, human […] The post What nine AI workflow submissions reveal about Echelon Singapore’s builder pipeline appeared first on e27 .
Score: 34🌐 MovesJun 22, 2026https://e27.co/what-nine-ai-workflow-submissions-reveal-about-echelon-singapores-builder-pipeline-20260622/ - Building Browser-Using AI Agents in Python
Most AI agent tutorials start with an API.
Score: 34🌐 MovesJun 22, 2026https://machinelearningmastery.com/building-browser-using-ai-agents-in-python/ - Some Electricians Think Building Data Centers Is for Sellouts
Big Tech is throwing big money into data center buildouts. As national opposition to the facilities grows, some workers are beginning to question whether it’s worth it.
Score: 33🌐 MovesJun 22, 2026https://www.wired.com/story/data-center-buildout-electricians-selling-out/ - Payaza launches Shopaza, integrates AI to simplify eCommerce
Payaza has launched Shopaza, an eCommerce platform now live across 23 countries in Africa, North America, and Europe, built on Payaza's own payment infrastructure for instant settlement.