From the State Government edition of September 23, 2026
Maryland Moore AI framework seeks frontier audits, 72-hour incident reporting, and worker voice
Office of Governor Wes Moore (Maryland) · State executive AI policy / workforce and consumer protection agenda · Maryland, United States
- Publisher
- Office of Governor Wes Moore — Governor Moore Outlines AI Framework to Protect Marylanders
- Original publication
- 2026-09-22
- Source retrieved
- 2026-09-24
- Event date
- 2026-09-22
What happened
Why now: on 2026-09-22 Governor Moore announced an AI framework organized around protecting people, centering workers, and keeping kids safe. Under protecting people, the AI Subcabinet will develop legislative recommendations for regulating frontier AI model companies—including safety frameworks and testing, worker protections, independent third-party audits and evaluations, whistleblower protections, public reporting, and 72-hour incident reporting. Additional actions span Right of Publicity, civil-rights guidance for AI in housing/lending/employment, algorithmic tenant-screening limits on DHCD-financed properties, anti-rent-collusion legislation, gambling targeting limits, a standing Labor-Management Committee on AI for state workers, and stronger protections related to unsafe chatbots for youth.
Why it matters
State-level frontier-developer oversight agenda that mirrors elements other states are operationalizing (audits, incident reporting) while adding explicit state-workforce labor engagement—useful for multi-state policy and shared-services planning with clear 'not yet law' limits.
Evidence and measured results
Official press release dated September 22, 2026 (updated same day). Builds on 2024 EO, AI Governance Act of 2024, and Responsible AI Policy. No quantitative agency AI outcome metrics in the release.
Limitations and uncertainty
Most items are planned legislative recommendations or agency guidance tasks, not enacted requirements as of the release. Housing/gambling/chatbot provisions need future bill text. No measured results.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-23; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- States need a coherent frontier-AI oversight story spanning audits, incidents, workers, and kids without overstating what is already binding.
- Stakeholders
- Governor’s AI Subcabinet
- DoIT / DBM
- MCCR / labor agencies
- Procurement
- Union representatives
- Discovery questions
- Which frontier models are in production today?
- What incident clock exists now?
- How will Labor-Management Committee review workplace AI?
- Which chatbot youth rules already bind vendors?
- Value hypothesis
- A bounded readiness assessment can align vendor and agency practices to Maryland’s announced frontier-audit and incident-reporting direction before bills land.
- Potential engagement
- 4–6 week AI Subcabinet briefing pack and agency inventory against the framework’s frontier items.
- Unsupported claims
- Independent audits already legally required in Maryland
- 72-hour reporting already enforceable statewide
- Guaranteed youth-chatbot compliance without bill text
Pre-sales engineering
Role takeaway
- Fit
- Fit for governance/telemetry design anticipating frontier audits and incident reporting; unfit as authority to deploy new high-risk systems.
- Architecture and integration
- Inventory frontier vs non-frontier tools; define incident ticket schema; segregate workplace AI configs under DoIT guidance.
- Prerequisites
- Model/use-case inventory
- Incident response runbooks
- Labor consultation channel
- Civil-rights guidance hooks
- Constraints
- Recommendations not yet statute
- Maryland-specific civil-rights and housing contexts
- Federal preemption uncertainty
- Security
- Incident and whistleblower channels must protect reporters and sensitive model-eval data.
- Proof of value
- Gap matrix vs audit/incident recommendations
- Tabletop 72-hour incident drill
- Workplace AI guidance pilot in one agency
Delivery
Role takeaway
- Work
- Facilitate Subcabinet recommendation drafting support, worker-committee process design, and agency guidance rollouts.
- Dependencies
- AI Subcabinet
- DoIT/DBM
- MCCR/Labor
- Legislative sponsors if bills advance
- Ownership
- Governor’s office / AI Subcabinet with agency implementers for guidance.
- Skills and adoption
- Agency counsel and security staff need frontier-eval literacy; HR needs workplace-AI discrimination guidance fluency.
- Governance checkpoints
- Principles published
- Recommendation draft
- Labor-Management standing agenda
- Bill introduction
- Acceptance criteria
- Written frontier recommendation outline including audits and 72-hour reporting
- Named owners for workplace AI guidance
- Youth chatbot protection workstream chartered
- Risks
- Agenda outruns legislative capacity
- Confusing guidance with binding law
- Under-engaging unions on workplace AI
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
If recommendations become law, frontier vendors serving Maryland may need audit/eval evidence and incident-reporting pipelines; state DoIT/DBM guidance for workplace AI may affect tool configuration and logging for state workers.
Governance
Who approves, reviews and stays accountable for outcomes?
Creates a principles-to-legislation pipeline via AI Subcabinet plus cross-agency civil-rights and labor structures; distinguishes announced intent from enacted duties.
Security and privacy
What data, permissions and controls need testing?
Emphasizes rights, privacy, deepfake/likeness protections, and incident reporting for frontier companies; workplace AI discrimination guidance implicates HR/systems data use.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Framework centers worker voice, Labor-Management Committee, reskilling, and school-to-career pathways; accessibility for residents is implied via rights protections rather than WCAG metrics.
Procurement
What should contracts, pricing and exit terms secure?
Frontier legislative recommendations (audits, incident reporting, whistleblower protections) would reshape vendor diligence if enacted; current release does not itself amend procurement manuals.
Operating model
Which teams own the service once it runs?
Creates a principles-led operating cadence across Subcabinet, civil-rights agencies, DoIT/DBM, and labor—parallel tracks for people, workers, and kids rather than a single IT project.
Publication history
- 2026-09-23State Government · Issue 184 resources
Stable resource ID: maryland-moore-ai-framework-frontier-audits-20260922