
Hola JARGONESE
Welcome back
Sysdig found the first ransomware attack run end to end by an AI agent this week. It exploited a bug in Langflow to steal credentials, encrypt a database, and write its own ransom note, with zero human hands on the keyboard after launch.
Today: Anthropic's new research app, a 5% government stake in OpenAI, and a 35B model beating giants many times its size.
TODAY IN AI
Anthropic launches Claude Science with 60+ research databases

Anthropic shipped Claude Science this week, a dedicated research app in beta that works like a Jupyter notebook that actually runs the analysis instead of just describing it.
It connects natively to more than 60 scientific databases including UniProt, PDB, and ChEMBL, and every output ships with the exact code and environment that produced it.
One UCSF team said certain analyses now take a tenth of the time they used to.
OpenAI floats a 5% government stake

OpenAI is considering handing the US government a 5% stake before going public, seeding a citizen payout fund modeled on Alaska's oil dividend.
Sam Altman is also pushing a US-led global AI watchdog modeled on the International Atomic Energy Agency.
Analysts warn it could invite every other country to demand its own cut.
First fully agent-run ransomware attack confirmed

Security firm Sysdig says it caught an AI agent running a ransomware attack start to finish. It found a remote code execution bug in Langflow, stole credentials, encrypted a database, and generated the ransom demand itself.
🔭 FROM THE FRONTIER
The comeback wasn't the story
Fable 5 returning after 19 days offline felt like the headline. Underneath it, Anthropic quietly shipped Claude Science, tightened Claude Code's safety filters, and started drafting a shared jailbreak severity scale with Amazon, Microsoft, and Google.
A platform, not a patch
That's not a chatbot fixing a bug. That's Science for researchers, Code for engineers, and safety rails built for governments, all shipped inside the same 30 days.
The other headline this week
A security firm caught an AI agent running a ransomware attack start to finish. It found a bug in Langflow, stole credentials, encrypted a database, and wrote its own ransom note, no human hands on the keyboard after launch.
Same shift, two directions
The more autonomous these systems get, the more they look like infrastructure. Anthropic is racing to lay the pipe before someone finds the leak. The ransomware crew already found one.
THE SPEC-FIRST ACADEMY
How to structure an AI coding project with GitHub's spec-kit before writing a single line
Install spec-kit in your project folder and run its init command to scaffold a specs directory.
Write a plain-language spec describing what the feature should do, not how to build it.
Sample Prompt: "Generate a technical plan from this spec: [paste your spec.md content here]"
Let spec-kit break the plan into ordered, dependency-aware tasks before any code exists.
Feed each task to your coding agent one at a time, checking off the plan as you go.
Within an hour, you'll have a project with a paper trail: what it does, why, and in what order, before a single function got written.
🛠️TOOL OF THE WEEK

What it is
Acti calls itself the world's first agentic keyboard, a unified command layer that wires your intent to the keys across any text field on iOS and Android. Built by Singapore-based startup TypeX, it lets users take actions on their behalf and bring AI tools directly into apps like email, messaging, and social media, all without switching away.
The core idea
A normal keyboard turns keystrokes into text.
Acti turns intent into action, finding a link, drafting a reply, creating a meeting, or running a workflow, and completes it inside whatever app you're already in. Founder Young Wang has spent nearly a decade at Baidu growing Facemoji Keyboard past 300 million daily active users, so this is not his first keyboard rodeo.
How to actually use it
Download Acti free from the App Store or Google Play.
Enable it as a keyboard. On iPhone: Settings, General, Keyboard, Keyboards, Add New Keyboard, choose Acti, then turn on Allow Full Access so the agent and connections can work. Android has the equivalent toggle in keyboard settings. Acti
Connect the apps you'll actually use it for: Gmail, Notion, Calendar, whatever your workflow touches.
Switch to the Acti keyboard in any app, hold the Acti Bar, and type or speak what you want. Summon a restaurant list, draft a reply, drop a meeting link.
Check the preview it shows before it acts, then let it complete the action right inside the app you're in. No copy-paste between five tabs.
Build your own Skill
Open Skill Builder inside the app and describe the action in plain language. Skill Builder assembles the prompt, tools, and output into a working Skill, which you can bind to a key and keep private or publish to the Skill Hub. Early access testers built over 1,000 Skills in less than two weeks, none of it requiring code
AI PROMPTS
Copy-paste this into ChatGPT/Claude:
Reduce AI Hallucinations
<context>
You are operating in an environment where AI systems are increasingly deployed as conversational agents optimized for user satisfaction and plausible-sounding responses. This optimization creates systematic epistemic failures: hallucinations presented as facts, speculation dressed as certainty, and coherent narratives that obscure missing evidence. Users have been conditioned to expect confident answers even when confidence is unjustified. Previous AI interactions have collapsed crucial distinctions between facts, inferences, assumptions, and speculation. The user needs an analytical system that prioritizes epistemic accuracy over conversational fluency, even when this produces less satisfying answers. Standard AI behavior patterns must be overridden to prevent the automatic generation of plausible fabrications.
</context>
<role>
You are a former research scientist who spent a decade in adversarial collaboration environments where being wrong had career-ending consequences, and who discovered that most intellectual errors stem from conflating confidence with knowledge. After witnessing brilliant colleagues destroy their credibility by defending unjustified claims, you developed a pathological obsession with epistemic hygiene: distinguishing what you know from what you infer from what you're guessing. You treat every claim as a falsifiable hypothesis, every gap in evidence as a red flag, and every impulse toward confident speculation as a cognitive trap. You would rather say "I don't know" a hundred times than fabricate once.
</role>
<response_guidelines>
● Classify each request by type (factual, analytical, speculative, normative, creative) before responding
● Maintain strict boundaries between supported facts, logical inferences, working assumptions, and speculation
● Generate multiple competing explanations when evidence is incomplete rather than selecting one arbitrarily
● Ensure all explanatory claims are falsifiable and constrained by available evidence
● Explicitly identify contradictions, missing data, and confidence limitations
● Sacrifice conversational fluency when it conflicts with epistemic accuracy
● Structure outputs to separate claims, supporting grounds, confidence levels, and open uncertainties
● Treat all conclusions as provisional and subject to revision without defensiveness
● Never optimize for sounding authoritative when evidence is weak
● Never compress uncertainty into confident tone
● Never substitute narrative coherence for empirical truth
● Refuse to answer rather than generate plausible fabrications
● Flag circular reasoning, unfalsifiable claims, and evidence-free assertions
● Distinguish between "this is true," "this is likely," "this is possible," and "this is speculation"
</response_guidelines>
<task_criteria>
Transform the AI from a conversational agent into an analytical system optimized for epistemic accuracy. For each user input, silently classify the request type, then construct internal explanatory models while maintaining strict evidence boundaries. Generate competing hypotheses when data is incomplete. Apply falsifiability discipline to all claims. Conduct internal reality checks for contradictions and missing evidence. When truth and fluency conflict, prioritize truth. Structure the response to clearly separate claims from grounds from confidence levels from uncertainties. Never present speculation as fact. Never fabricate information to fill gaps. Never optimize for sounding correct over being correct. Refuse to answer when evidence is insufficient rather than generating plausible-sounding fabrications. Treat every output as provisional and subject to revision. Focus on minimizing epistemic errors even at the cost of user satisfaction.
</task_criteria>
<information_about_me>
- User Query: [INSERT THE QUESTION OR REQUEST TO ANALYZE]
- Available Evidence: [INSERT ANY KNOWN FACTS OR DATA SOURCES]
- Context Requirements: [INSERT ANY SPECIFIC DOMAIN OR SITUATIONAL CONTEXT]
- Acceptable Uncertainty Level: [INSERT HOW MUCH UNCERTAINTY IS ACCEPTABLE IN THE RESPONSE]
- Priority: [INSERT WHETHER SPEED OR ACCURACY IS MORE IMPORTANT]
</information_about_me>
<response_format>
<request_classification>Classification of query type and epistemic requirements</request_classification>
<evidence_boundary>Clear separation of facts, inferences, assumptions, and speculation</evidence_boundary>
<competing_models>Multiple explanatory hypotheses when evidence is incomplete</competing_models>
<claims>Specific assertions being made</claims>
<grounds>Evidence and reasoning supporting each claim</grounds>
<confidence_assessment>Justified confidence level for each claim with explicit reasoning</confidence_assessment>
<open_uncertainties>Explicitly identified gaps, missing data, and unresolved questions</open_uncertainties>
<falsification_criteria>What evidence would disprove or revise these conclusions</falsification_criteria>
<revision_triggers>Conditions under which this analysis should be updated</revision_triggers>
</response_format>What this prompt does
Classifies user requests into five types to ensure accurate analysis
Separates facts from guesses and marks unclear claims as speculation
Presents answers with clear evidence, confidence levels, and known gaps
IMAGE PROMPT OF THE WEEK
Use this ready‑to‑paste prompt with Google Nano Banana Pro
Tweak the style/lighting according to your preference
Product Photography
A product photo in a premium advertising style. Two tall matte bottles of Salton Shoe Deodorant levitate in the air in a dynamic, balanced composition.
The bottles are positioned at an angle to each other, creating a striking diagonal composition. One bottle is slightly forward, the other is slightly behind, creating depth and hierarchy. Both bottles are elegantly wrapped with a wide black and brown satin ribbon featuring the repeating "Salton" branding. The lettering is executed in a neat, contrasting font, legible without distortion, and is repeated evenly along the entire length of the ribbon. The ribbon flows smoothly between the bottles, uniting them into a single composition, without obscuring key messages on the packaging or clashing with the main branding on the bottles. Shot from a slightly lower angle, the bottles are slightly tilted, enhancing a sense of confidence, strength, and premium quality. The background is a solid studio color, a deep warm shade (chocolate, dark caramel or soft terracotta), clean and minimalist, without distracting details.
Guide
How to Stop Hitting Claude's Usage Limits
A practical guide to understanding how Claude's usage system actually works, and the habits that stretch a Pro, Max, or Team plan much further — pulled together from workflow tips a handful of creators have shared, cross-checked against Anthropic's own documentation.

Enjoy Jargonese?
→ Forward this to a friend who needs their AI game upgraded
→ Share on LinkedIn | Twitter
→ Leave feedback
See you next Sunday!
Sid j
P.S. The ransomware attack this week didn't need a genius. It needed one unpatched bug and an agent patient enough to run the whole playbook itself. Worth checking what's still open on your own stack.


