Just how many cameras are out there? Last week we named five categories of industries we can serve. Starting today, we’ll take a closer look at each of them one at a time. First up: Security. Retail and logistics: cameras cover the sales floor, the stockroom and the loading dock, often across many locations under one operator. Every site produces its own footage, and eventually footage is needed from the right clip and the right camera on the right day. Casinos, gaming and hospitality: gaming floors, cash cages and entrances are recorded around the clock, and gaming regulators set rules for how long that footage has to be kept. Corrections and detention: housing units, corridors and intake areas are recorded constantly, and incident footage may be needed long after the fact. Four more in Security: Banking and financial branches: counters, ATMs, vaults Education and campuses: gates, hallways, parking lots Commercial buildings, real estate and parking: lobbies, garages, access points Stadiums and venues: concourses, entrances, vendor sites, crowd areas In security, footage is evidence. It arrives constantly and incidents have to stay findable and affordable to keep. Vidaio compresses, tags, names, sorts, and files it. Next up: Public Safety. @vidaio_ bittensor:native

Our co-founder @asem_othman built a purchasing agent for ITKAN-MASDC, a tuition-free, parent-powered robotics program for youth at a non-profit community center in Northern Virginia. Asem runs the robotics program: 4 teams and 45 kids. Robots break all the time. A motor fails, a sensor breaks, or a student discovers they need a part days before a competition. Requests come from several teams, often at the same time. Teenagers may also request something already in storage, or submit the same request more than once. That means lots of unfiltered requests from teenagers who expect things to happen the minute they ask for something. While keeping kids engaged and productive is difficult, the most serious administrative challenge is keeping a clear, transparent and auditable record. The funds are provided and managed by the non-profit community center. Every purchase must stay within budget, be recorded for the accountant, and leave a clear audit trail: what was bought, why it was needed, which team requested it, and who approved the use of the card. We know Asem doesn’t have a lot of free time, and managing the administrative part of a robotics program is not where he should spend his time. So an agent that can spend money it is, and doing it securely, with transparent auditability, requires his Pulse. The agent checks the inventory first, flags possible duplicate requests, confirms the available budget, prepares the exact cart, and records each step. When it is ready to buy, it stops and asks Asem for authorization, and only Asem can provide that confirmation, because he is the only person authorized by the non-profit to make purchases for the robotics team. In the video below, you can see Asem review the request on his phone and Pulse it with his face through Yanez ID. The approval was tied to one cart, one amount, and one action. If anything changed, a new approval was required. The approval was also single-use, so it could not be reused for another order. The agent can handle the repetitive work without holding the raw card number or receiving general permission to spend. Asem keeps control. MASDC gets the records and accountability it needs. The students get their parts without the purchasing process becoming the bottleneck. We built Pulse because it addresses the missing layer of secure non-repudiable authorization for agents. With it, we can be more effective, we can delegate more, and we can extend the time we spend giving to causes we care about. Agents are a fantastic solution: they are fast, diligent, always working, but they need a secure framework to operate. For Asem’s agent, Pulse was enough. When an agent needs funds of its own, Gate keeps them behind a smart contract the agent can’t open, and Pulse is what unlocks it. Reach out if you want to access or download Asem’s agent code.

Point a model at a codebase, ask it to find bugs, and call it an audit. That's slop. A scan will find something. Some of it real, some of it invented, plenty of it true but harmless. It got so bad, curl shut down its bug bounty in January after a flood of AI-generated reports that sounded technical and described things that weren't there. A scan also can't tell you what it missed, and a second run can turn up different findings than the first. The bugs that matter are the ones an attacker can turn into stolen funds, exposed secrets, leaked private data, or system breakage. A true audit searches for all threats and hunting all of them takes skill: strategy, agents, multiple models, and careful prompting. It's not what you use, it's how you use it. And the best audits are the ones that stay ahead of the field by continuing to innovate. (and in fact, we’re testing something new right now) @bitsecai $TAO

“just use a foundation model” they said. so we benchmarked 10 of them against Manako on a real forecourt damage clip. same full 1280x720 frames, same class prompts (person, car, fuel dispenser, fuel nozzle), no crops, no zoom. the hard class is the nozzle/hose. small, thin, occluded, and the thing that actually gets damaged. - Grounding DINO labelled a bin as a fuel nozzle. - Florence-2 labelled the canopy pole as one. - OWL-ViT, YOLOE and YOLO-World got the dispenser at best, never the nozzle. - RF-DETR doesn’t have the class. - Gemma 4 E2B described the scene, boxed the pump, and returned no incident time. the only open model that localised the nozzle was full SAM3. 3.45 GB, 0.2-1 FPS on a Jetson Orin Nano. Manako (3 specialists - 29.5 MB), 3-6 FPS on the same Jetson, tracked the nozzle at 5 FPS and fired a live equipment_damage event on the hose drop at 10.3s. 117x smaller than the only model that could keep up. open-vocab models are great at the classes the internet photographs a lot. operations live in the long tail: nozzles, hoses, cabinets, the small parts that break. that’s where specialised detectors win, and it’s why we built Manako the way we did.

TheStreet - thestreet.com/crypto/innovat… Yahoo! Finance - finance.yahoo.com/technology… AOL - aol.com/articles/blockchains… MSN - msn.com/en-us/news/other/how… Apple News - apple.news/ANbiG2kdISZupiNEP…

Sentios badges are now LIVE! Show Sentios coverage anywhere. Githug, explorers, wallets, dashboards, websites The badge is now a hot link that opens to our active projects page on the Sentios website: sentios.io/active-projects Let the world know Sentios agents are continuously auditing your codebase on significant feature releases. Want your project listed? Contact us to put Sentios on your codebase. @bitsecai $TAO

@ExploitSummit was our livestream test. Both stages, live in English, with dubbing and subtitles in French, Spanish, and Chinese. With live dubbing, a stream reaches anyone, anywhere, in their own language. Our compression, along with storage from @Hippius_cloud , keeps every recording affordable to store, and archive management keeps each language version organized and searchable. Multinational companies running all-hands across countries. Universities with international students. City councils serving multilingual communities. They already stream live. So do: Conferences and trade shows Sports and esports Broadcasters and news Healthcare and medical education Creators and live streamers Utilities, infrastructure, and industrial training Courts and legal proceedings Streaming has a lot of room to run! @vidaio_ bittensor:native

"There are brilliant people from everywhere in the world looking to do something good." – John Yu, Bitsec founder / CEO The secret sauce is Bittensor and its Incentive Mechanism. We find these brilliant people and have them compete to build the best strategies comprised of multiple large models, agents, sub agents, prompts, memory management, context management, and tool use into a strategic harness. These become models of sorts and only the best performing ones win. Speaking of models, we’re moving toward a security audit future where we develop actual models, like a cluster of small expert auditing models with their own specialty features that in combination will be far more robust than not only large single models, but also the harness strategies that are cutting edge today. We’re taking it there. $TAO @bitsecai

5 things to decide before your agent can spend money: 1. Where the key lives. If the agent holds a wallet, a private key or a card number, whoever tricks the agent has it too. 2. Which actions wait for you. Routine ones run on their own. Set the amount above which nothing moves without your approval. 3. Where the approval happens. On your phone, with your face, outside the agent's own session. 4. What the approval covers. One exact action and policy, never a standing permission. 5. How you stop it. A spending cap you set, and a way to revoke the agent's access instantly. Pulse and Gate are built around these five. We'll walk through it live tomorrow in our workshop for developers and vibe coders, 10 AM PT / 1 PM ET. Sign up: docs.google.com/forms/d/e/1F… Docs: docs.yanez.ai/pulse/showcase…

Developers and vibe coders: a live workshop on building secure agents with Pulse and Gate. Agents that: 1. Don't spend all your money 2. Ask for your permission when you want them to Wed Oct 14, 10 AM PT / 1 PM ET on Google Meet. Second session Wed Oct 21, same time. Sign up and you'll be added to our Telegram group, Yanez Support for Agent Builders. Can't attend? Sign up anyway, leave your Telegram handle and we'll add you to the group. Tell us in the form if you need the recording. For more information, see the article below or send us a DM. docs.google.com/forms/d/e/1F…