VEDARSHMISHRA

2024–present · Policy & civic access

AI Safety / Policy

From how AI systems fail to who actually gets a say in what happens next.

Explore the engineering ↓
AI Safety project cover
AI SAFETY
My role
Fellow · ran the Civic Access Stress Test
Status
Capstone presented · hub proposed
Focus
Technical safety · governance · civic access

What I found

Most ways for the public to weigh in on AI policy are open on paper, but hard to find and hard to use unless you’re already an insider.

  1. 01

    Technical foundations

    Learn how AI systems fail, and how people test and oversee them.

  2. 02

    Governance

    See how evidence turns into standards and decisions.

  3. 03

    Stress test

    Try to actually use the public participation channels myself.

  4. 04

    Propose

    Design a campus hub around the barriers I ran into.

A developing practice

Technical safety to public access.

How the work built up, from technical study to policy work.

Technical AI Safety

Studied how AI systems fail and how people evaluate, interpret and oversee them. This was coursework, not original research.

AI Policy Fellowship

Shifted from technical failure modes toward the standards, institutions, and participation pathways that act on evidence.

Civic Leaders Fellowship

Ran the Civic Access Stress Test through direct engagement, institutional outreach, and barrier logging. It ended with a presentation at the Reagan Institute in Washington, D.C., and a proposed Campus Civic Access Hub.

Strategy Team

Connected evidence, organizational priorities, and practical pathways for responsible policy engagement.

Policy Team

Continues the trajectory toward accountable deployment, evaluation, reporting, and meaningful non-expert participation.

Civic Access Stress Test

Presented in Washington, D.C.

My capstone presentation at the Reagan Institute in Washington, D.C.

Press play to load the video.

Along the way

Inside the work.

Learning context
01 / 07
A fellowship session

Talks and discussion during the fellowship.

Working discussion
02 / 07
Working it through

Working through a policy question with the group.

Fellowship community
03 / 07
The fellowship group

The people I learned this with.

Policy fellowship in practice
04 / 07
Policy fellowship

A working session in the policy fellowship.

Technical safety cohort
05 / 07
Technical safety cohort

The technical AI safety cohort, Fall 2024.

Learning in community
06 / 07
Learning together

More from the fellowship sessions.

From technical questions to institutions
07 / 07
Fall 2024

Another moment from the technical safety course.

How I got here

I started with technical AI safety in Fall 2024: reward misspecification, goal misgeneralization, interpretability, control, oversight and evaluations. That was training, not my own research. The question that stuck with me was what happens after someone finds a problem: who decides, and who gets heard.

That led to the AI policy fellowship in Fall 2025, strategy and policy work with AISST, and the Civic Leaders Fellowship.

The stress test

Instead of asking whether public participation channels exist, I tried to use them. I went to AI and emerging-technology policy events, reached out to institutions to find real ways to participate, and logged every barrier I hit along the way.

Four kinds of barrier

Informational: opportunities were hard to find unless you were already in the network. Structural: affiliation requirements and insider processes narrowed who could get in. Social: expert spaces had unwritten rules that were hard to read. Logistical: travel, weekday timing, scattered information and short deadlines all added up.

These are my observations from one capstone, not a survey, so they don’t say how common each barrier is everywhere.

What I proposed

A Campus Civic Access Hub with three parts: a plain-language guide to opportunities, a short civic-literacy path that ends with actually taking part in something, and a feed of open comment periods and deadlines. The program’s January 2026 feedback called it timely. It’s still a proposal; it hasn’t been built or tested.

Why it matters to me as an engineer

A capable system still needs testing, oversight, and institutions that can act on what the tests show. That connection is what I care most about: safety evaluations, reporting, deployment decisions, and whether the public can actually take part.

Sources

Technical records.

Continue exploring.

← Back to Selected Builds