BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//hacksw/handcal//NONSGML v1.0//EN
METHOD:PUBLISH
BEGIN:VEVENT
DTSTAMP:20260722T230742Z
DESCRIPTION:Click for Latest Location Information: http://dgiq-aigov2026.da
 taversity.net/sessionPop.cfm?confid=166&proposalid=16769\nTurn on AI discov
 ery and too much floods in. The fix is one inventory, two states. This sess
 ion shows how to run managed and unmanaged assets without losing control.&n
 bsp;\n\nTurn on AI discovery and the flood begins: hundreds of models, agen
 ts, datasets, and pilots, more than any team can govern at once. Govern it 
 all equally, and you waste effort on what doesn’t matter. Govern none
  of it, and shadow AI wins.\n\nThe practical answer is one inventory with t
 wo states. Everything discovered stays visible, so nothing hides. Only the 
 assets you flag as managed get the full treatment: risk controls mapped to 
 the EU AI Act and NIST AI RMF, a lifecycle from intake to retirement, runti
 me monitoring, and value tracking. Unmanaged is deliberate, not a backlog: 
 visibility without overhead.\n\nWe’ll cover the rule for marking an a
 sset managed, who owns that call, and how the tooling spans the market, fro
 m a shared spreadsheet and the catalog and ticketing you already own to ded
 icated AI governance platforms. You’ll leave being able to stand up a
  two-state inventory the week you get back.\n\nKey Takeaways\n\n
 Run one AI inventory with two states: everything visible, so there’s 
 no shadow AI, only what matters managed, with one accountable owner holding
  the flag.\n
 Apply a four-condition rule to decide the moment an asset becomes managed, 
 and keep governance history intact across every promotion and demotion.\n
 Know what flipping “managed” switches on: risk and compliance c
 ontrols, lifecycle workflow, runtime monitoring, and value tracking.\n
 Map the tooling spectrum, from a spreadsheet plus your existing catalog and
  ticketing, to dedicated AI governance, model-risk, and observability platf
 orms (e.g., ServiceNow, Collibra, IBM, Microsoft, ModelOp), and right-size 
 what you actually buy.\n
 Treat “unmanaged” as a design choice that stays audit-ready, no
 t a backlog to clear or a way to label a POC and walk away.\n
DTSTART:20261116T134500
SUMMARY:Not Everything Deserves Governance: Triaging Your AI Inventory
DTEND:20261116T165959
LOCATION: See Description
END:VEVENT
END:VCALENDAR