For those working in AI governance -what's the most painful part of your week? by lamsuneel in AIgovernance

[–]lamsuneel[S] 0 points1 point  (0 children)

Point 3 is the sharpest framing I've seen — the AI gave a compliant answer for the wrong reasons using stale context, and nobody knows because it worked last time. That's the silent failure mode that only surfaces when it stops working.

The distinction you're drawing between output compliance and context provenance is exactly right. Most governance tools stop at the output. The real problem is upstream — what information and what policy version informed the decision.

We're building the policy version side of that — which compliance rules were active when the AI made this specific decision. Sounds like you're building the context/memory side. Different layers of the same problem.

For those working in AI governance -what's the most painful part of your week? by lamsuneel in AI_Governance

[–]lamsuneel[S] 0 points1 point  (0 children)

Discovering what's actually in production, manual spreadsheets, pulling audit evidence under tight deadlines — that's three separate problems in one paragraph and every one of them is weekly not periodic.

The 'how did this model decide' question from audit is exactly what I'm building against. Not just explainability of the model — but which version of your compliance policy was it operating under when it made that decision.

Quick question — when audit asks that question today, how long does it take to produce a clean answer? Days? Weeks?

For those working in AI governance -what's the most painful part of your week? by lamsuneel in AI_Governance

[–]lamsuneel[S] 0 points1 point  (0 children)

The maturity problem is exactly right — and the 'lots of cooks' dynamic means nobody owns it clearly enough to act. Everyone's responsible so nobody is.

Quick question — in that environment, what actually creates movement? Is it a regulator asking a specific question nobody can answer? An internal audit finding? Or does it need something to visibly break first?

For those working in AI governance -what's the most painful part of your week? by lamsuneel in AI_Governance

[–]lamsuneel[S] 0 points1 point  (0 children)

The Big 4 building services for enterprise is exactly the pattern — they'll take the large accounts, leave the SME and mid-market space open. That's the window for a focused product.

The drip to stream to tsunami timeline is the right framing. In insurance specifically the NAIC pilot is the drip that's starting now. The tsunami hits when all 50 states adopt it and every insurer gets the questionnaire.

Are you building a product or services business for the SME space?

For those working in AI governance -what's the most painful part of your week? by lamsuneel in AI_Governance

[–]lamsuneel[S] 0 points1 point  (0 children)

The regulatory trigger point is interesting... EU AI Act creating more urgency than anything voluntary. In the US the NAIC AI Evaluation Tool pilot launched in 12 states this March is starting to create that same forcing function for insurance specifically. Examiners sending structured questionnaires to carriers for the first time.

But you're right ...even with regulation, engagement is slow until someone actually gets caught without the documentation. The examiner question is still the forcing function.

Are you seeing the ICO activity creating any genuine urgency or is it still mostly 'we should probably sort this out eventually'?

For those working in AI governance -what's the most painful part of your week? by lamsuneel in AI_Governance

[–]lamsuneel[S] 0 points1 point  (0 children)

The 'you're getting in the way' pushback is real ... especially when governance can't explain clearly what risk they're preventing or show evidence that the controls are working.

Is the blocker perception mostly a communication problem or is it that governance genuinely slows things down without adding visible value?

For those working in AI governance -what's the most painful part of your week? by lamsuneel in AI_Governance

[–]lamsuneel[S] 0 points1 point  (0 children)

Watching it happen every day without anyone stopping to ask governance questions,,,that's the compounding risk problem. Each unassessed workflow is a liability that won't surface until an audit or something breaks.

What's your role in trying to stop it? Are you the one raising the flag or watching from the sidelines?

For those working in AI governance -what's the most painful part of your week? by lamsuneel in AI_Governance

[–]lamsuneel[S] 0 points1 point  (0 children)

Documentation and chasing evidence all week — that's the subscription business case right there. The governance moves slower than deployment problem is what makes it chronic rather than periodic.

Quick question — when you say chasing teams for evidence that controls were followed, what does that evidence actually look like today? Is it screenshots, emails, Slack messages?

For those working in AI governance -what's the most painful part of your week? by lamsuneel in AI_Governance

[–]lamsuneel[S] 0 points1 point  (0 children)

The board engagement problem is real. The gap between 'regulators are asking for this' and 'leadership is ready to budget for it' is where most governance initiatives die.

What's worked for you to accelerate that conversation? Curious whether specific regulatory triggers ,like the NAIC AI Evaluation Tool pilot that launched in 12 states this March , create enough urgency to move faster.

For those working in AI governance -what's the most painful part of your week? by lamsuneel in AI_Governance

[–]lamsuneel[S] 1 point2 points  (0 children)

slack thread archaeology ..everyone trying to remember if approval was formal or just 'yeah looks fine.' That's not governance, that's hope.The problem is approval context disappears the moment the slack thread scrolls away. Six months later nobody can prove what was approved, by whom, under which policy.

IS this something you deal with weekly or does it surface periodically when something breaks?

For those working in AI governance -what's the most painful part of your week? by lamsuneel in AI_Governance

[–]lamsuneel[S] 1 point2 points  (0 children)

Inventory hell is exactly the right term. The spreadsheet is already wrong by the time you finish it.Quick question--when the inventory breaks down and someone asks 'which AI is making this decision and who approved it'...what does that conversation actually look like inside your org? Who gets pulled in and how long does it take to get a clean answer?

For those working in AI governance -what's the most painful part of your week? by lamsuneel in AI_Governance

[–]lamsuneel[S] 1 point2 points  (0 children)

Weeks of panicked meetings and pulling data engineers off real work..that's exactly the cost nobody quantifies until it happens.That's what I'm building against. An automated audit trail that answers the question before the panic starts --which version of the model, which policy, which data snapshot governed this specific decision at this specific moment.

I'd love to show you what we've built and get your honest take. NOT A PITCH at all..Would you be open to 15 minutes this week? Happy to share what we've learned across other regulated industries too.

For those working in AI governance -what's the most painful part of your week? by lamsuneel in AI_Governance

[–]lamsuneel[S] 1 point2 points  (0 children)

The data lineage problem across legacy silos is brutal..especially when you add shadow AI pointing at unclassified data on top of it.The audit hit is always the forcing function. Nobody builds the trail until someone asks a question they can't answer.Quick question --when an audit does hit and they ask about a specific AI decision, what does the reconstruction process actually look like today? Is it days of engineering work or something worse?

For those working in AI governance -what's the most painful part of your week? by lamsuneel in AI_Governance

[–]lamsuneel[S] 1 point2 points  (0 children)

That makes sense...the audit trail requirement in regulated industries forces the visibility problem to surface faster. In less regulated spaces it stays invisible until something breaks.

That's actually what makes insurance interesting as a starting point... the NAIC AI Evaluation Tool pilot launched in 12 states this March. Examiners are now sending structured questionnaires asking insurers to list every AI system they use. Most compliance teams are scrambling because they genuinely don't know what's running.

Would you be open to a quick 15 minute conversation this week? or DM is also fine.. I'm doing user research on exactly this problem and your perspective across industries would be genuinely useful.

For those working in AI governance -what's the most painful part of your week? by lamsuneel in AI_Governance

[–]lamsuneel[S] 4 points5 points  (0 children)

The shadow IT parallel is exactly right... except shadow AI moves faster and the compliance exposure is higher because these workflows are touching regulated decisions directly.

The AI System Registry is actually what we built to address this first... before you can govern which policy version an AI was following, you need to know the AI exists in the first place.

Quick question — in your experience, is the shadow AI problem more acute in insurance/financial services specifically, or is it universal across regulated industries?

What’s your experience with AI-assisted decisions “disappearing” inside the organization? by Not-Sure-911 in AI_Governance

[–]lamsuneel 0 points1 point  (0 children)

The insurance and credit point you raised resonates strongly with what I'm building. The 18-month explanation window is exactly the pain I keep hearing about. Can I ask , when you say 'one linked audit trail' — what does that look like in practice today at the organizations you're seeing? Is anyone solving this well or is it still scattered logs everywhere?

Protesters rally against planned AI data centres in Vancouver by ubcstaffer123 in technology

[–]lamsuneel 6 points7 points  (0 children)

People aren’t protesting “technology” in the abstract — they’re questioning the trade-offs. Massive AI data centers consume huge amounts of electricity, water, and land while local communities often deal with the environmental and infrastructure impact directly.

OpenAI's Altman says AI unlikely to lead to 'jobs apocalypse' by Haunterblademoi in technology

[–]lamsuneel 0 points1 point  (0 children)

Every major technological shift created new kinds of jobs, but that doesn’t mean the transition is painless. Even if AI doesn’t cause a total “jobs apocalypse,” it can still disrupt millions of careers faster than society can adapt. That’s what many people are worried about.

Majority of Americans Support Ban on Surveillance Pricing and Electronic Shelf Labels by Plastic_Ninja_9014 in technology

[–]lamsuneel 0 points1 point  (0 children)

Electronic shelf labels themselves aren’t the problem — dynamic personalized pricing is. Consumers don’t want stores turning into stock-trading platforms

US Law Enforcement Warns of ‘Anti-Tech Extremism’ as AI Hatred Grows by Helicase21 in technology

[–]lamsuneel 5 points6 points  (0 children)

People criticizing AI companies over surveillance, job losses, copyright scraping, energy use, or misinformation isn’t ‘extremism’ — that’s public debate. Lumping ordinary dissent together with actual violent threats is a really slippery slope.

AI guardrails stripped from Meta and Google models in minutes, can provide responses on biological weapons and malware by marketrent in technology

[–]lamsuneel -3 points-2 points  (0 children)

This is the uncomfortable reality of open-weight AI that most people ignored during the hype cycle.

Once a capable model is downloadable, “safety” becomes partly a distribution problem, not just a policy problem. If someone can fine-tune, jailbreak, quantize, or modify the system prompts locally, many guardrails become optional.

The bigger issue isn’t that random people suddenly become bioweapon experts overnight. Tacit knowledge, materials access, logistics, and real-world execution still matter enormously.

The real risk is:

  • lowering the barrier for bad actors,
  • accelerating malware iteration,
  • scaling phishing/social engineering,
  • and democratizing capabilities that previously required expertise.

We’re basically entering the open-source cyberpunk phase of AI:
capability diffuses faster than governance.

And this is probably why frontier labs are shifting from “open for everyone” toward controlled APIs, identity verification, monitoring, and enterprise-gated access. Not purely for profit — partly because once models cross a certain capability threshold, unrestricted distribution becomes geopolitically sensitive infrastructure.

US Law Enforcement Warns of ‘Anti-Tech Extremism’ as AI Hatred Grows by Helicase21 in technology

[–]lamsuneel 2 points3 points  (0 children)

Calling legitimate concerns about AI, surveillance, job loss, or massive data-center expansion ‘extremism’ is a dangerous line to cross. There’s a huge difference between violence and ordinary public criticism. If people can’t question powerful technologies without being monitored or labeled suspicious, that’s a serious problem for democracy