TUJLTECH UPDATES, JUST LATEST

DAILY AI BRIEFING · 每日 AI 简报

让变化经过筛选,
再抵达你。

科技更新,只看最新。每天从可靠来源中挑选值得留下的 AI 动向;中英对照,链接回到原文,事实与判断分开。

READ THIS EDITION ↓

THE SIGNAL / 今日信号

六件值得知道的事

6 stories · 约 10 分钟

01

Claude Fable 5.1 登陆 Amazon Bedrock,并附带更严格的数据保留规则

Claude Fable 5.1 arrives on Amazon Bedrock with stricter data-retention rules

AWS 宣布 Claude Fable 5.1 可通过 Amazon Bedrock 与 Claude Platform on AWS 使用,面向编码、科学研究和长时企业任务。Anthropic 将它列为 Covered Model;Bedrock 默认要求 aws_review 模式,提示和输出最多保留 30 天供 AWS 安全复核。符合 Enterprise Frontier Safeguards 条件的内部用途可选择零数据保留。能力改进来自 Anthropic 与 AWS 的报告。

AWS has made Claude Fable 5.1 available through Amazon Bedrock and Claude Platform on AWS for coding, scientific research, and long-running enterprise work. Anthropic classifies it as a Covered Model: Bedrock normally requires aws_review mode, retaining prompts and outputs for up to 30 days for AWS safety review. Eligible internal use under Enterprise Frontier Safeguards can use zero data retention. Capability improvements are reported by Anthropic and AWS.

阅读原始来源 / Read original source
02

ChatGPT for Healthcare 增加 Epic 病历连接与九类官方数据源

ChatGPT for Healthcare adds Epic context and nine official data sources

OpenAI 发布 Epic 电子健康记录集成与 Healthcare Public Data 插件:授权机构可在 ChatGPT 中审阅患者上下文,并查询 PubMed、DailyMed、ClinicalTrials.gov 和 CMS Coverage 等九类官方来源。公司称医生在 27 个临床用例的 4,363 次评分中,将 99.1% 的响应评为安全;这是 OpenAI 的产品评估,不代表独立临床结局研究,输出仍需专业人员复核。

OpenAI introduced an Epic electronic-health-record integration and a Healthcare Public Data plugin, letting authorized organizations review patient context and query nine official sources including PubMed, DailyMed, ClinicalTrials.gov, and CMS Coverage. The company reports that physicians rated 99.1% of responses safe across 4,363 ratings and 27 clinical use cases. This is an OpenAI product evaluation, not an independent patient-outcomes study, and outputs still require professional review.

阅读原始来源 / Read original source
03

三家 AI 原生公司展示把智能体嵌入可重复工作流的方法

Three AI-native companies show how agents become repeatable workflows

OpenAI 汇总 Basis、Clay 与 Exa Labs 的案例,分别把智能体用于员工入职、账户管理和开发者集成。文章同时引用 Enterprise Signals:AI 使用量前 10% 的企业,每位活跃用户输出 token 数是典型企业的 8.3 倍,1 月时为 2.6 倍。该指标和案例来自 OpenAI 及客户观察,说明采用深度,不直接证明生产率或投资回报。

OpenAI profiles Basis, Clay, and Exa Labs using agents for employee onboarding, account management, and developer integrations. It also cites Enterprise Signals: firms in the top 10% of AI usage now generate 8.3 times as many output tokens per active user as typical firms, up from 2.6 times in January. These OpenAI and customer observations measure usage depth, not productivity or return on investment by themselves.

阅读原始来源 / Read original source
04

Jamf 用分级模型限制把 Bedrock 个人预算变成实时策略

Jamf turns per-user Bedrock budgets into tiered model restrictions

Jamf 与 AWS 公开一套生产架构:按工程师统计每日 Bedrock 成本,在预算达到 80% 时限制高成本 Opus、达到 100% 时进一步限制 Sonnet,同时保留低成本 Haiku。Athena 计算花费,Lambda 每 15 分钟检查,IAM 策略在无需重新登录的情况下生效,并提供限时例外。这是单一客户方案,阈值与收益需按组织重新设计。

Jamf and AWS describe a production architecture that tracks daily Bedrock cost per engineer, restricts the higher-cost Opus model at 80% of budget, further restricts Sonnet at 100%, and keeps the lower-cost Haiku option available. Athena calculates spend, Lambda checks every 15 minutes, and IAM policies apply without reauthentication, with time-boxed exceptions. This is one customer pattern; thresholds and benefits need redesign for each organization.

阅读原始来源 / Read original source
05

Amazon Quick 安全指南把数据塑形、智能体隔离与审批门纳入上线条件

Amazon Quick guidance treats data shaping, agent isolation, and approval gates as production requirements

AWS 发布从概念验证走向生产的 Amazon Quick 安全实践,以 5,000 名员工、五个部门和三类权限受众的示例说明四种模式:按授权塑形数据集、隔离智能体、分类文档、为外部动作设置人工审批。文章是 AnyCompany 场景的技术指南,不是一次现实部署成效评估,但清楚展示了仅依赖单层权限为何不足。

AWS published production-security guidance for Amazon Quick using a sample organization with 5,000 employees, five departments, and three audience levels. It demonstrates four patterns: shaping datasets around authorization, isolating agents, classifying documents, and placing human approval gates on outbound actions. This is an AnyCompany technical walkthrough rather than a deployment-outcomes study, but it shows why a single permission layer is insufficient.

阅读原始来源 / Read original source
06

AdaptiveFlow 用自适应筛选缩小 690 亿分子库的搜索空间

AdaptiveFlow narrows the search across a 69-billion-molecule library

同行评议研究发布开源 AdaptiveFlow,为 690 亿个可对接分子提供筛选就绪数据,并整合超过 1,500 种对接协议。作者报告,自适应预筛在部分设置中可将计算成本降低至多 1,000 倍,并通过生化实验与晶体结构验证了两个靶点的纳摩尔级抑制剂。结果支持早期先导发现,不代表候选物已经证明安全、有效或可成为药物。

A peer-reviewed study introduces the open-source AdaptiveFlow platform with a screening-ready library of 69 billion dockable molecules and more than 1,500 docking protocols. The authors report that adaptive prescreening can reduce computational cost by up to 1,000-fold in some settings, and they validated nanomolar inhibitors for two targets through biochemical assays and crystal structures. This supports early hit discovery; it does not show that candidates are safe, effective, or ready to become medicines.

阅读原始来源 / Read original source

EDITOR'S NOTE · 编者的话

今天的共同线索,是能力开始进入工作流以后,边界也必须成为产品的一部分。

过去一天的更新涉及更强模型、医疗数据连接、企业智能体、用量控制、权限设计和药物筛选。事实是这些产品、案例和研究已经发布;我们的判断是,AI 从回答问题走向执行工作时,数据来源、保留规则、预算、访问范围与实验验证不能留到最后补做。模型能力与案例成效多由发布方报告,医疗和药物研究也不等于可直接用于诊疗。

The past day brought updates across stronger models, healthcare data connections, enterprise agents, usage controls, permission design, and drug screening. The fact is that these products, cases, and studies were published. Our judgment is that as AI moves from answering questions to executing work, data provenance, retention rules, budgets, access scope, and experimental validation must become part of the product rather than an afterthought. Model capabilities and case outcomes are largely publisher-reported, and healthcare or drug research is not the same as deployable care.

TWO ADDRESSES · 两个地址

一个保存我们,
一个观察世界。

RUJF.AIRecord Us Just Forever

保存属于我们、记忆与创作的东西。

TUJL.COMTech Updates, Just Latest

观察外面的世界,记录 AI 此刻正在发生什么。

站外推广狗狗加速