Building Agentic Memory for an AI SOC: Why Our Semantic Cache Was the Wrong Answer
Picture: Web Directions

Conference In 5 weeks

December
Monday
to Tue 8 December 2026 · Sydney time

Building Agentic Memory for an AI SOC Why Our Semantic Cache Was the Wrong Answer

Where
Research / Deep Tech room 488 George Street, 2000, Sydney
Host
Web Directions
Entry
Not stated
Sign-up
On the host's page
Open on webdirections.org

All Sydney events

You sign up with the host. foundercal only links to it.

Who you meetThe people on the listing, and what the host tells us about the room.

  • Mukesh Singh Speaker
Investors Not stated The listing does not say
The format Talks and halls Conference
Sign-up On the host's page Price not stated

AboutIn the host's words.

Speakers: Mukesh Singh (Atlassian)

Track: Research / Deep Tech

We run a fleet of AI agents against production security detections at Atlassian. One tunes noisy detection rules, another reviews new ones, and more are coming for alert triage and hunting. Every one of them started blind and stateless, re-deriving the same context from Jira tickets, a Databricks lake, a rule repo and ATT&CK, or drowning in a raw dump of all of it. Nothing they learned survived the session, so they repeated each other's mistakes and contradicted each other.

Our first design was a semantic cache. It was wrong, and working out why reshaped everything. A semantic cache is keyed on input embedding and returns a cached conclusion, which in a domain with consequences means serving a stale security verdict to a look-alike question. What we built instead is an entity-keyed, facts-only store, each agent reads a bounded, per-action slice before it acts, then writes facts back. Conclusions are never cached. They are re-derived every run, deliberately.

I will walk through the schema, the four rules we enforce (facts only, provenance on every row, derived and never authoritative, bounded slices instead of whole-history blobs), and the point where native prompt caching stops paying and a store starts.

Then the measurements, on real tickets with human ground-truth labels that analysts produce as a byproduct of triage, input tokens per run, eliminating a 900-second lake query, false positives removed with zero true positives lost, and how consistent two agents stay when they share one memory instead of guessing separately.

Then what broke: entity resolution, write contention, memory poisoning, and the crossover where memory costs more than it saves.

You will leave with the schema, the eval design and the four rules, all of which transfer to any agent fleet that needs to remember something.

https://data.webdirections.org/ai-engineer-sydney/sessions.json#b4169c04-2f5d-4992-9921-8e21cd5b1888

Full text on webdirections.org .

Where

Research / Deep Tech room

488 George Street, 2000, Sydney

Open in Maps ↗

Same week in Sydney All 151 events

Dec
to 5 Dec
Hackathon

AI Engineer Hackathon

Founders pitch

Web Directions Free
Dec
Fri 08:00
Dinner

Startup Coffee Social #39

Investors in the room

Tank Stream Suites
Startup Coffee Social Events
A$5
Dec
to 13 Dec
Conference

AI Week

Web Directions
Dec
to 12 Dec
Conference

NeurIPS 2026

One of the year's big ones

NeurIPS Foundation
Dec
to 8 Dec
Meetup

Lessons from Economics for the Human / Agent Software Workforce

Leadership room
Web Directions
Dec
to 8 Dec
Meetup

Ontologies

AI Engineering room
Web Directions
Dec
to 8 Dec
Meetup

Shipping together in an AI native team

Software Engineering room
Web Directions
Dec
to 8 Dec
Meetup

Dependency hell is back. This time it's your agent's config.

Software Engineering room
Web Directions
Dec
to 8 Dec
Meetup

Your website is a terrible API

AI Engineering room
Web Directions
Dec
to 8 Dec
Meetup

Sovereignty Is an Inference Problem

Leadership room
Web Directions
Open on webdirections.org Mon 7 Dec ↗