AI Security as a reading path: foundations → data → intersection
AI Security is not a pile of posts. It is a path: how systems fail, what data is at stake, and where the two meet.
You do not need sixteen tabs. You need an order of questions.
AI Security is not a pile of posts. It is a path: how systems fail, what data is at stake, and where the two meet.
Three stations. First: what can the system see, do, and remember? Second: what data is in play — subject, store, path, time? Third: where does generation meet movement — paste, connectors, retrieval, agents that act?
Two entry ramps. If you already ship assistants with connectors, start at the intersection: data paths, prompt checklists, bounded retrieval, blast radius (#12–15). If you are still naming the layers, foundations and data primers can backfill later — when those titles are refit. This closer does not reopen S1/S2.
Rails are navigation, not a maturity score. Primers build vocabulary. Field notes walk a scenario. Glossaries (later) pin one term. Pick the next article from the path; do not shop a suite.
This map is editorial promise, not a vendor roadmap. No invented metrics. Named platforms only when a Learn-backed fact is required.