Thank you @neo4j for welcoming ”Wawilo Technologies PVT Ltd” to the Neo4j Startup Program. #CypherQL. We now have access to the Enterprise Edition of the world's leading graph database.
Ontology Pipeline — Framework for Knowledge Engineering and Building Knowledge Infrastructures: https://t.co/KKPIYgITgB
Amazon description: “One of the biggest shifts happening in our industry is that enterprise data management is expanding into enterprise knowledge management. AI is accelerating that transition because it depends on more than well-managed data. It depends upon context, shared meaning, trusted relationships, and the ability to organize the vast stores of unstructured knowledge that exist across every large enterprise. As AI becomes the primary interface to enterprise information, knowledge management will become the foundation that unlocks trustworthy AI at scale.”
“Look at your data.”
The most useful advice in AI right now.
Got my signed copy of @sh_reya and @HamelHusain’s Evals for AI Engineers at @danolsen’s product meetup tonight.
Evals ftw!
Claude just mass murdered 100 startups again.
It introduced Claude Meetings. Claude joins your video call, builds docs and whiteboards while you are still talking, and writes the notes and action items after.
It is beta, on Team and Enterprise plans only, and Google Meet only for now.
The startups are not quite dead.
Anthropic is working with Otter, Fireflies and Granola so you can send the transcript to them.
Big win for AI Engineers!
If you're deploying agents in production, this one is for you.
(bookmark it)
There's a new system that can test and evaluate your agents against the real world, then write the fixes, all before you deploy them.
AI agents look great in demos, until real users start breaking them. Your agent can tell a customer "refund done" on a $1,080 invoice without ever checking who she is, and the logs will still look clean.
Normally you only find a failure like that after a real customer runs into it. @pluraiAI Simulation lets your agent fail in a simulated world first, so you can fix the problem before any user sees it.
↳ It rebuilds your actual agent, its tools and its environment from your code
↳ Simulated users push the agent into the edge cases that matter for your use case
↳ Evals built for your agent check the actions it took, like whether it verified the customer before issuing that refund
↳ Every failure comes with the run that exposed it and a fix you can verify
↳ Any production failure can become a simulation you replay against every new version
It ships as a single plugin for coding agents like Claude Code and Codex, and it works with whatever agent you're building. I've started running it on my own agents too.
It's free for every AI engineer. Link in the first comment.
I worked with the Plurai team to put this together. Here's the whole system, step by step, from the first simulated user to a re-tested fix:
This guy reverse engineered a 1994 Jeep using Claude.
The Jeep kept failing its smog test, so he did not take it to a mechanic.
He wired a $3 Arduino into the car's computer and let Claude read it. The Jeep predates OBD-2, so there was no port to plug into. Claude worked out the old SCI protocol and started logging every drive.
Then Claude ran the fuel pump on its own. Reading became controlling.
Claude copied the whole program off the computer and found the cause. His California computer cuts fuel at smog-test loads. A federal one would not.
Reflashing was impossible. His computer was built four months before Chrysler made them programmable. So Codex wrote a tiny program into the EPROM instead, over the same three wires.
The Jeep passed. And the video was edited with Fable 5.2.
Today we’re launching the Gemini Decisions API, powered by our new Gemini Decision 1 model in @GoogleAIStudio.
Instead of generating text token by token, it’s built for closed-set choices scoring up to 1,000 questions across text, images, audio, video + PDFs in a single pass. A few details:
- 3 decision types: yes/no, multiple choice (up to 255 options) + rubric scoring
- $0.10 / 1M input tokens with $0 billed for output tokens (~5x cheaper than Flash-Lite)
- leads on several benchmark evals with lowest calibration error
Google teams are already building with it, below is a look at Stitch Rapid designing a full product flow in seconds (1x speed)
Software is like aluminum.
Aluminum used to be a rare luxury metal. Kings were served their meals on it.
Then someone discovered that aluminium could be extracted from bauxite.
Now we wrap our sandwiches in it.
The aluminum industry is way bigger than it was back then, but the aluminum artisans who made plates for kings went out of business.
Today, the only way to make money in the aluminum industry is using cheap electricity at massive scale.
Nobody has a moat just because they can make aluminum anymore.
AI is doing this to software.
There will be more software than ever, but the ability to make it (including taste) will no longer be valuable.
Software isn't going away—it's margins and the artisans who make it are.
Google's team published a 9-page PDF on Harness Engineering. one formula replaced prompt engineering:
Agent = Model + Harness
the twist: same Claude Sonnet, same benchmark. change only the harness
the playbook, six steps:
step 1 -> add guides
AGENTS.md, rule files, constraint docs. every line is an old agent failure turned into a permanent fix
step 2 -> add sensors
linters, tests, validation scripts. the agent checks its own output before a human ever sees it
step 3 -> build the agentic loop
plan, execute, verify, fix. retries are capped, budgets are capped, and a stuck agent escalates
step 4 -> externalize memory
the model forgets every session. the harness keeps the state, the decisions and the artifacts
step 5 -> enforce permissions
which tools, how many writes, what needs approval. the harness owns safety
step 6 -> wire observability
every tool call, cost and retry gets tracked. a trip wire fires the moment behavior drifts
the result: your agent stops being a demo and becomes infrastructure
every failure turns into a permanent fix, so every next run starts smarter
that's the gap between an agent you demo and one a client pays you to leave running
one harness gives you a reliable loop. connect several and you get graph engineering, where one agent's failure becomes another agent's sensor
the PDF stops at the harness. the graph is the next layer
that breakdown, running on Kimi K3, is below ↓