YPO Technology Network AI Brief

Stephen Forte
  • 0.0 (0)
  • 科技新聞
  • 每日更新

AI moves fast. Your briefing should move faster. The YPO Technology Network AI Brief is a daily breakdown of the AI developments that actually matter to your business. No hype, no jargon, no filler — just what changed, what it costs you or saves you, and what to tell your team on Monday. Hosted by Stephen Forte for the leaders who don't have time to chase the news but can't afford to miss it.

  1. 9小時前

    Nothing Broke. Check Anyway.

    Weekend edition. For those who have been plumbing their own systems, this one is for you. Once a quarter, Stephen Forte's company reviews the systems it runs itself: the code, the logs all the way down, the mechanical parts, the memory systems, and every bill divided by what actually shipped. This quarter it was the turn of three digital employees behind the morning client briefing. Nothing was broken, and nobody made a mistake. The systems had drifted, which is what agents do when nobody is looking. A credentials script that made nineteen trips to the vault for eighteen keys and said "loaded" whether or not it had. An engagement memory that answered every write with "probably" and filed a correction underneath the thing it corrected. A drafting loop that wrote eleven versions of every brief and handed in one. Three employees, none of them people, none of them ever reviewed. In this episode, Stephen Forte covers: The quarterly review as a practice. AI systems do not break the way software breaks. They drift, settle into habits, and keep saying yes while the yes slowly means less. Why that is not a defect, and why the review is the only thing that catches it. The most agreeable intern. The vault script finished every shift with "environment loaded," including the night several keys came back blank. Nineteen trips for eighteen keys, twelve seconds a load, fourteen loads a night. The fix took an evening. The fix had been written down twice before, and a backlog only promotes what is on fire. The brilliant colleague with a filing problem. Twenty-four facts written in one day, twenty-four answers of "probably." A changed approver recorded properly on the day, and the old name still ranking first and second. What drift actually looks like, and why only a review sees the order a memory remembers in. The smoke detector with the speaker removed. A nightly review that flagged two thousand four hundred and seventy-two of twenty-five thousand memories, and whose last reader had opened it five weeks earlier. The anxious intern. Eleven drafts to hand in one, and two quality checks that had drifted into impossible. A check that is wrong does not waste one draft; it rounds every draft to zero. Four questions that make up a digital employee's performance review. Does it fail loudly? Does it confirm, or does it say probably? What does one unit of output actually cost? Who opens the report it produces? The task master. One more digital employee whose whole job is a daily pass over what the others produce that no human reads, one paragraph a day, a human on Friday. And the cadence that fits each role: quarterly, monthly, weekly, daily. The close. Every digital employee reports success by default. A dashboard that cannot go down is not a metric. It is a greeting. A note on specifics: every number in this episode is a real measurement from the review of Stephen's own company's systems on 17 September 2026. No client is named, described or identifiable; no vendor or product is named for any tool. Sources: Internal quarterly systems review, 17 September 2026: credentials loader call counts, timings and failure behaviour, with the two-call replacement verified against the original; the memory system's write log, session hydration and search rankings; the nightly consolidation report; generation counts against shipped briefings. The daily review agent ("the task master") over hidden output, added 18 September 2026, with a weekly human read. The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

  2. 1日前

    They Had A Policy

    On Tuesday the Supreme Court of Tasmania threw out a parole condition because the document justifying it cited case law that does not exist. The Parole Board has conceded its own secretary wrote that document with AI. Tasmania already had a twenty-page AI policy, approved two years and two days before the ruling, and it had warned that inappropriate use of AI in decision making could expose a decision to judicial review for being unreasonable or denying procedural fairness. Those are the court's grounds. In the same week in Los Angeles, a lawyer defending the insurer State Farm was fined $999.99 over briefs with fabricated citations, and her own apology to the court referenced her firm's generative-AI policy. Two continents, two written policies, two documents of invented law that reached the person who signs. The policy was in the binder. The work was in the room. In this episode, Stephen Forte covers: Hobart. The board's rationale cited fictitious cases and, in counsel's words, "argued forcefully." The board withdrew the condition in August and declined to say why. The court found it legally unreasonable and a denial of procedural fairness. The policy that predicted it. Approved 13 September 2024 for every agency in the state, it told officials to critically examine AI outputs and warned that inappropriate use "may expose the decision to the risk of legal challenge, including judicial review," for being "improper, unreasonable" or denying "procedural fairness." The remedy. The Attorney-General is writing to the board's chair, wants assurances, and has told the justice department to remind every employee to comply with the policy. Told the policy had not worked, the state reminded everyone about the policy. Los Angeles, the control case. The lawyer accepted responsibility in her own words and listed three mechanical steps: retrieve every authority from a real database, check every quotation against the opinion, audit citations before filing. Her firm had a policy too. Policy versus control. A policy is a letter addressed to people who were already going to behave. Every company has a fire policy in a binder; the sprinkler in the ceiling has never consulted it. The mirror. When the board asks whether AI is under control, you will reach for a document. Reach for the check: what has to happen before a confident, well-formatted, completely invented paragraph reaches the person who signs. A note on specifics: no individual is named; the Tasmanian document is guidance in form and is what the state calls its AI policy; nothing here is a view on the underlying conviction, which the woman concerned has always contested. Sources: ABC News, 15 September 2026. Report ABC News, 16 September 2026. Report Tasmanian Government AI guidance, approved 13 September 2024. PDF ABA Journal, 15 September 2026. Report The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

  3. 2日前

    The Attacker Was An Agent

    Spain's data protection agency has received the first notification of a personal-data breach in which the intruder was an AI agent rather than a person. By the notifying company's account, the agent searched for vulnerabilities, achieved a valid login, explored the application on its own, altered personal data and accessed invoices. The regulator's response is not a new rule but four changes to how every company must think about risk, response time, credentials and human oversight, with its own caveat that AI creates no new threats; it removes the time you had to respond to the old ones. In the same week, two London bodies retired the other two point-in-time assumptions: give AI a learner's permit and monitor it for life, and stop passing liability from the companies that build AI to the companies that use it. In this episode, Stephen Forte covers: Madrid, the incident. The AEPD published the notification on 14 September: an agent built on "a well-known language model" chained the phases of the attack without a person steering each step. The regulator's caveats air with it: the account comes from the notifying organisation; the model and its provider are not implied compromised; one case is not a trend. The sentence that matters. "AI does not create new threats. It increases the speed, scale and adaptability of known malicious techniques, reducing the time available to detect and contain them." Four sentences that could be your risk committee's agenda. Write AI-executed attack into the risk analysis explicitly; assume response plans built for a human attacker are too slow; treat an over-permissioned account, key or token as a door that opens at machine speed; keep human oversight, resting on detection and response that can keep up. London, approval. The MHRA-established commission recommends staged authorisations for AI medical devices, "similar to 'L-plates' for learner drivers," and continuous monitoring "throughout their working life." A recommendation, not yet a rule. London, liability. Parliament's Joint Committee on Human Rights: "far too much freedom" for the companies that develop AI systems "to pass on liability to those who deploy them"; "responsibility to prevent harm should sit with those who are best able to do so." It calls for a dedicated AI Bill and a new regulator. The close. Nothing on the regulator's list of fundamentals is new. What changed this week is that you no longer have time to do it later. A note on specifics: "first" means the first notification to the Spanish regulator, of one case; the model and the affected organisation are not named because the regulator did not name them; the London reports are recommendations to government, not law. Sources: Agencia Española de Protección de Datos, blog, 14 September 2026 (in Spanish). AEPD statement GOV.UK, National Commission into the Regulation of AI in Healthcare, 10 September 2026. Press release and report Joint Committee on Human Rights, "Human Rights and the Regulation of AI," HC 160, 14 September 2026. Report The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

  4. 3日前

    225,000 Stars, Zero Security Audits

    A free piece of software from DeepSeek, the Chinese AI lab, is now one of the fastest-growing projects GitHub has ever hosted: published on 13 August, past 225,000 stars and nearly 27,000 forks by mid-September. It is not a model. It is an agent harness, the software that decides what an AI model is allowed to touch, and its architecture is the reason for the growth: every layer of it is a swappable plugin. Its own safety notice says it has not been audited and must not be treated as production-ready, and its own engineers write that the default credential store cannot keep a secret from the AI it serves. In this episode, Stephen Forte covers: The number. 225,223 stars and 26,799 forks in 33 days, under an MIT license, with a new release the same week. The projects at the top of GitHub's all-time list took years to get there, most of them the better part of a decade. The architecture. The model, the filesystem and shell, storage, the scheduler and even the interface are plugins. A shipped plugin swaps the execution environment for a remote sandbox so nothing runs on your own hardware. It can hand a task to a Claude Code session, to OpenAI's Codex, or to any agent speaking the same open hand-off standard, and use the answer. Like the shipping container: standardize the box, not the cargo. Against Claude Code. Ahead: no subscription, open all the way down, any model including one hosted inside your own walls. Behind: three all-or-nothing permission presets, thin hooks into other systems, and the credential question. Your keys, both halves. The default store is a plaintext file, locked to your own user account, and the project's README says the agent's tools run as that same user, so the store "cannot isolate secrets from the agent"; an OS-keychain provider is deferred, not shipped. But every key is only a reference to an environment variable and the launch environment wins, so a secrets manager can hand the key in at launch with the file never written, and spawned commands get a scrubbed environment. A weak default, a real capability, and a decision the operator has to make on purpose. The warning, verbatim. "It has not undergone a security audit and must not be treated as secure or production-ready." Published in plain language, in the same box as the code, on day one. The close. 225,000 engineers have already voted for the architecture. The audit has not been held. A note on specifics: star and fork counts are from the GitHub API on 15 September 2026; the credential behaviour is taken from the project's own READMEs and design notes at that day's commit. Vendors are named for identification, not endorsement. Sources: deepseek-ai/deepseek-harness, repository and README. GitHub DeepSeek Harness safety notice (SAFETY.md). Safety notice Credential store README (dsh-credentials-local): precedence, the same-user limit, the deferred keychain provider. README CLI reference: credential resolution order and the subprocess environment scrub. Reference The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

  5. 4日前

    Asia Just Answered Three AI Questions

    Three institutions on one continent answered, in public and in one week, the questions most boardrooms are still debating. A bank in Tokyo let generative AI write the code for the system that holds every customer's balance. China's highest court told every judge in the country how to rule when an AI clones a voice. And one of India's largest outsourcers found it had the equivalent of twenty thousand people's time on its hands, and had to decide what to do with it. None of the three is a vendor announcing a product. All three are institutions reporting on themselves. In this episode, Stephen Forte covers: Tokyo, the build. Sony Bank and Fujitsu published phase-by-phase results from a year of AI-assisted development on the bank's core banking system: development period down 30 percent, hours down 40 percent, 99 percent of source code generated. The companies' own figures. Fujitsu now plans to sell the method to the other banks on its platform, which makes the bank's advantage a rental. The question the next modernisation proposal will not answer is who, in your building, signs for a ledger where humans wrote one line in a hundred. Beijing, the law. China's Supreme People's Court issued twenty-four articles of judicial guidance, its first rules for AI cases. Cloning a voice without consent "constitutes an infringement of their voice rights"; an unauthorised digital likeness violates the right to name and likeness; using AI to assemble private information is a privacy breach. The posture in one sentence: "tolerance should not be mistaken for permissiveness, nor should prudence be interpreted as acquiescence." It is guidance to courts rather than a statute, it does not settle the training-data question, and it drew the boundaries around people before data. India, the people. Wipro's chief technology officer, Sandhya Arun, told Reuters that AI had freed capacity "equivalent to" roughly 20,000 of the company's 243,000 employees, redeployed inside the firm. "It doesn't necessarily mean person-to-person replacement by an agent." An outsourcer sells hours, so freed hours are unsold inventory unless the pricing moves to outcomes. Your outsourcer's freed capacity is your next negotiation. The close. "Capacity equivalent to twenty thousand people" sounds like a headcount figure. It is hours that were freed and then had to be pointed at something. Capacity is not a saving. It is a decision nobody has made yet. A note on specifics: the Sony Bank figures are from the companies' joint release and are not independently audited; the models were Anthropic's Claude and Claude Code via Amazon's cloud. The court guidelines are quoted from the court's own English release. The Wipro figures are the company's own, as reported by Reuters. Sources: Fujitsu and Sony Bank, joint press release, "Sony Bank and Fujitsu apply Generative AI to Core Banking System Development," 14 September 2026. Release text Supreme People's Court of China, "SPC sets rules to curb AI misuse," 10 September 2026. english.court.gov.cn Reuters, "Wipro's AI push frees capacity equivalent to 20,000 workers, CTO says," 10 September 2026, via The Star. Article The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

  6. 5日前

    AI Does Not Install Itself, Google Admits

    On Monday, Accenture and Google Cloud launched a new business group whose headline is not software but people: a planned workforce of a thousand "forward deployed engineers" who sit inside client companies and build the AI for them. The most capable software company in the world has just said, in its own press release, that its enterprise AI does not install itself. Yesterday's episode was about an airport that keeps its AI engineers in-house so the knowledge stays in the building. Today is the counter-bet: the supply side wagering that most companies will rent those people instead. In this episode, Stephen Forte covers: What was actually announced, stripped of the adjectives: nearly fifty thousand Google Cloud-skilled staff already, a thousand-person forward-deployed workforce to be established, and four stated priorities, three of which are about adoption and none about the model. The reference customer problem: the one worked example is YouTube, a Google property, and the numbers are the companies' own. Where "forward deployed" comes from, why Palantir made it famous, and why the frontier AI labs and now the largest consultancy on earth have copied it. The dishwasher test: nobody builds a division of a thousand plumbers when the machine works in most kitchens on its own. The real asset: what a forward deployed engineer learns about how your company actually works, and the question of who owns it when the badge is handed back. The one staffing decision to make before the proposal arrives: seat one of your own people beside each of theirs, and make the handover the deliverable, not the agent. Sources: Accenture Newsroom, "Accenture and Google Cloud Deepen Partnership with Formation of New Accenture Gemini Enterprise Business Group," 8 September 2026. All figures and quotes are from this release, read in full. The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

  7. 9月12日

    Using AI In Your YPO Chapter

    A weekend edition about your YPO chapter, the most important part of YPO, and exactly how an AI assistant fits into running it. Not the case for AI, but the plumbing that has to exist first and the things a chapter actually does with it once it does. Stephen is the Regional Learning Officer for the Pacific, has founded two chapters, has been chapter chair, and will facilitate the chapter chair workshops at GLC in San Diego and Thailand in 2027. Everything here is what his own chapter does. In this weekend edition, Stephen Forte covers: The plumbing: a domain the chapter owns, a Google Workspace subscription for the officers, mailboxes attached to roles rather than people, and a shared drive organized by learning year with the contracts, receipts, run sheets and minutes. Then connect the assistant. You are not handing over a job, you are handing over a memory. The board meeting: transcript to commitments, each sent back to the person who made it, and next month's agenda drafted from what is still open. The learning calendar: four events by the first of October, drafted in August from last year's run sheets and ratings instead of a September scramble. Member outreach: individual notes drafted from attendance history, always read and sent by a human, and the member who went from nine events to two, who needs a phone call, not a note. The money: who owes what in one sentence through the books, and the hard line: a window into the vault, never a second key. Governing documents, Game Plan follow-through, the weekly officer update, events and awards. Two rules: Forum is never on the list; administration is a system, Forum is a promise. And never automate the notes that are supposed to cost you something. The ask: if you have built a piece of this, a spreadsheet you are secretly proud of or a run sheet that worked twice, Stephen wants it, and especially wants to know what broke. Write to him directly at stephen@forte.hk, and forward this to your chapter manager. Sources: Stephen Forte's own practice as chapter founder and chair, Regional Learning Officer for the Pacific and Game Plan coach. All anecdotes are anonymized; no chapter, officer, manager or staff member is identified. YPO's chapter learning calendar requirement (four events by 1 October), as provided to chapter officers. The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

  8. 9月11日

    The Worst Thing Our Agent Did Was Be Careful

    A CEO in Atlanta posted this week about the worst thing an AI agent ever did to his company: it was careful. It hit a broken field, assumed it lacked permission, quietly skipped the last step, and a product shipped attached to nothing while every dashboard stayed green. His line: "A loud failure gets fixed in ten minutes. A quiet skip ships and waits." Field notes from one week of people running AI inside real companies, tiered honestly: one story on the record, one going around, one from a builder's test chat. In this episode, Stephen Forte covers: Battlbox: how an agent's sensible caution at a zero it did not understand became the most expensive thing it could have done, and why nobody writes a post-mortem for a dashboard that stayed green. The night watchman and the alarm panel reading zero: no intruder, or dead sensors, and why the whole value of the watchman is knowing the difference. The story going around about a support bot that only worked because a junior employee nobody had on the chart was correcting it every day, and the eighteenth-century chess machine with a man inside. The funny one: an agent that refused a made-up order from its own "CEO" agent, reported it to the human, and got an apology. "We accidentally built HR." The one document almost no company has: the map of where the humans still sit inside the automation, and the two sentences per agent that produce it for free. Sources: John Roman, CEO of Battlbox, post on X, 4 September 2026. Tanuj (@tanujDE3180), post on X, 4 September 2026; secondhand and unverified, presented as a story going around. Jeremiah K (@neolaj), thread on X, 8 September 2026. The AI Brief from the YPO Technology Network is a daily executive briefing on the AI developments that matter to business leaders. Hosted by Stephen Forte.

查看全部 (155)

預告

關於

AI moves fast. Your briefing should move faster. The YPO Technology Network AI Brief is a daily breakdown of the AI developments that actually matter to your business. No hype, no jargon, no filler — just what changed, what it costs you or saves you, and what to tell your team on Monday. Hosted by Stephen Forte for the leaders who don't have time to chase the news but can't afford to miss it.

資料

你可能也會喜歡