Twitxy Saved

ᴅᴀɴɪᴇʟ ᴍɪᴇssʟᴇʀ 🛡️

Verified account This account is verified. Learn more

@DanielMiessler

Building Vector: The Enterprise AI Operating System @ ourvector.ai and LifeOS: The Human Magnification OS @ ourlifeos.ai | Ex: Apple, Robinhood, HP, Army
San Francisco Bay Area danielmiessler.com Joined March 2007
1.7K Following 161K Followers 30K Posts

Latest posts 5

Pinned post

ᴅᴀɴɪᴇʟ ᴍɪᴇssʟᴇʀ 🛡️ Verified account @DanielMiessler
We spend most of our time, and most of our harness system, on refining intent instead of steps.

I don't have a CLAUDE.md or AGENTS.md anymore. I have:

THE DOCTRINE

- a CONSTITUTION, which defines the philosophy of current-to-ideal-state hill-climbing, the single Ideal State Artifact (ISA), and evals as how it all gets carried out. Hard rules and philosophy.

- a PREFERENCES file with my stack and how I like things done. It describes OUTCOMES I like, not steps.

- TELOS, which is my actual life: mission, goals, problems, risks. It's the top of the hill everything rolls up into.

- When I add a goal, Kai has to say what measures it, what moves it, and the first move.

- The summit is euphoric surprise. Not "it works," but "holy shit, I didn't know it could do that."

THE ISA

- the ISA system, which works with my Development skill to build, test, and deploy projects.

- Every ISA opens with a 3-level ideal state. I confirm the top two before anything gets built.

- Ideal State Criteria (ISCs) are small, testable statements of done. Each names the probe that would prove it false.

- Anti-criteria list what must never happen. Half the bugs I care about are things that shouldn't exist.

- When direction is fuzzy, Kai asks me open questions before building the uncertain part.

- Hooks block code changes when the ISA wasn't read or wasn't updated. The spec can't drift from the code.

- The ISA outlives every run. "Add a feature" just means "add criteria that don't pass yet."

THE ALGORITHM

- Big work runs the Algorithm: define done, build, close each criterion on real evidence.

- Effort scales with the task. A typo takes seconds. A huge build can take agents and days.

- The hardest thinking goes to the smartest model. Cheaper models build once the approach is set.

- The builder never grades its own work. A fresh agent reviews it, often from another vendor.

- If a bug survives two fixes, the next move is a fresh diagnosis, not a third patch.

EVALS AND VERIFICATION

- ASSAY is our one eval system. Every eval and every judge runs through it.

- Every ISC maps to its own eval. Cheap code checks run first, judge models after.

- Nothing gets handed to me on a self-review. It comes with a receipt of the checks it passed.

- Kai tests everything in a real browser. An HTTP 200 proves almost nothing.

- "Should work" is banned. It's either verified or explicitly not.

THE IMPROVEMENT LOOP

- ERRATA logs everything I complain about.

- When I reject something that passed, Kai names the missing check and adds it. Misses sharpen the evals, not the prompt.

- HILLCLIMB improves anything below target by experiment. Only what the numbers support lands.

- REPLAY is one record of everything that happened across the system and my apps.

- A fix counts only when the original failure fails on the old code and passes on the new.

- When something breaks, we remove the cause instead of adding a rule to remember.

RUNNING IT ALL

- WORKFLOWS run everything on a schedule. Nothing runs outside them.

- Workflow stages are rigid. The work inside each stage is free.

- VIGIL watches every result and decides if I get a text, a digest line, or nothing.

- CENSUS registers everything we own. Every job has exactly one owner.

- SKILLS describe ideal states, not procedures. If a smarter model wouldn't need a step, it's cut.

- Hooks enforce what prose can't. Important rules live in code.

- Permissions are one table. Deploys, money, deletes, and outbound messages need my yes.

- Outside content is data, never instructions.

So here's the whole thing in one pass. TELOS says where I'm going. The ISA says what done looks like. Development builds it, and Assay proves it. Errata, HillClimb, and Replay make the system a little smarter every time it misses.

The models will keep getting better at the steps. Knowing what you want, and how to tell when you have it, is still our job.
lauren Verified account @poteto 5d
interesting how well this post aged

what are your predictions 1 year from now?
View quoted post on X
27 replies 13 reposts 191 likes 13K views View on X
ᴅᴀɴɪᴇʟ ᴍɪᴇssʟᴇʀ 🛡️ Verified account @DanielMiessler
It is with a heavy heart that I hereby announce my resignation from David Kennedy.
Dave Kennedy Verified account @HackingDave 3h
Listen - I think its time with all of this AI hacking stuff going on, we finally talk about a difficult subject that nobody want's to acknowledge.

nano is better than vi.

I said it, had to be said. Let's move passed it, and acknowledge the truth here.
View quoted post on X
4 replies 0 reposts 30 likes 3.5K views View on X
ᴅᴀɴɪᴇʟ ᴍɪᴇssʟᴇʀ 🛡️ Verified account @DanielMiessler
I saw this differently. I saw it as one guy having a conversation with himself.

Most people I know in tech kind of feel both of these positions, and which one is more dominant changes hour by hour and day by day.
ThePrimeagen Verified account @ThePrimeagen 5h
is it just me or are these videos super condescending?

The producer clearly sees themselves as the praying mantis. They know best. They see all. The person still writing code by hand only does it out of insecurity and is fairly childish.

This is the same crap as the world religions are all the same, just different parts of the Elephant. Oh so you can see everything, its just us who are blind? Such condescension its nauseating.
View quoted post on X
0 replies 0 reposts 7 likes 1.5K views View on X
ᴅᴀɴɪᴇʟ ᴍɪᴇssʟᴇʀ 🛡️ Verified account @DanielMiessler
This feels performative, Paul.

When you're doing a news segment you don't have time to differentiate between a 2FA attack and a 2FA configuration bypass. The point is they thought they had 2FA defenses and they were bypassed.

It would have been a different talk show altogether if she invited him on to talk about how 2FA had just been broken. The point was a 14-minute automated attack.

This smells to me like you saw someone on TV and you wanted to chime in with, "well actually..."

Don't do that, please.
Paul Walsh Verified account @Paul__Walsh 7h
David Kennedy, a former NSA hacker with 25 years of experience in cybersecurity and the author of Metasploit: The Penetration Tester’s Guide, has responded to my criticism of his CNN interview about AI agents that supposedly bypassed 2FA and compromised a company in 14 minutes.

I appreciate him taking the time to respond and clarify that the attackers exploited a configuration flaw, not a vulnerability in 2FA itself. That’s a significant detail that wasn’t clear from CNN’s report.

I’ve worked in tech for 30 years, with a background in telecom, web and mobile infrastructure, cybersecurity and social engineering. I’m well aware of the different ways MFA can be exploited. I was amongst the first to write about the inherent vulnerabilities with app-based 2FA in 2019 when it comes to phishing attacks. Some security professionals still recommend 1Password and others for phishing protection. These a great password managers. They’re not good for anti-phishing. If anything, they give people a false sense of confidence which means they’re more likely to fall for a targeted attack.

My concern was the suggestion that AI agents had bypassed 2FA without any explanation of how.

I can only assess what was reported, and it’s possible CNN didn’t accurately convey what David explained. I don’t think I’ve ever seen a cybersecurity story with so little technical detail presented with such serious implications.

I understand the NDA and his responsibility to the customer. But without basic technical evidence, nobody can independently assess what happened or what role AI actually played. If the affected company never publicly discloses the vulnerability, people will understandably question if the incident happened as described. Or if it happened at all.

My advice to him and others is to avoid giving CNN or anyone else another story that fuels the AI scare campaign until there’s enough technical evidence for the cybersecurity industry to assess it and for the disclosure to serve the public.

As it stands, CNN’s report has added fuel to the PR scare campaigns that promote more AI from US tech companies with close relationships with the US government and intelligence agencies like the NSA.

People who know me or my work know that I’ve never published anything for clicks. My objective is to help people understand what’s technically possible beyond the claims they read in the media. I appreciate David’s response and would welcome any further technical insight he can share.
View quoted post on X