From the AWS edition of October 29, 2026
Texas Regulatory Efficiency Office presents SAM, a citizen-facing regulatory assistant hosted as an AI service in AWS GovCloud
Texas Regulatory Efficiency Office (Office of the Governor); presented at Texas DIR Discover · State government · Texas, United States
- Publisher
- Texas Department of Information Resources (DIR)
- Original publication
- October 6, 2026 (DIR Discover presentation)
- Source retrieved
- 2026-10-30
- Event date
- 2026-10-06
What happened
The October 6, 2026 DIR Discover deck describes SAM on efficiency.texas.gov as a public, no-login assistant that helps Texans find which agency, rule and form applies, citing a corpus of 44,000 regulations in the Texas Administrative Code, plus statutes, agency forms and guides. The security slide states the AI service runs in AWS GovCloud on a texas.gov site with FedRAMP noted; guardrails say SAM does not give legal advice or decide cases, and answers point users to the linked agency source. This is the first explicit public statement located tying SAM's hosting to AWS GovCloud; the May 2026 launch is already archived (texas-treo-sam-regulatory-chatbot-statescoop-20260515), where the director described orchestration with multiple commercial models.
Why it matters
State-government exemplar of a citizen-facing, citation-grounded regulatory navigation assistant on AWS GovCloud; directly comparable to permitting and licensing assistants in other states and large cities.
Evidence and measured results
Presentation slides only: architecture claims (GovCloud, FedRAMP, no accounts), scope (44,000 regulations) and guardrail lists. No usage counts, accuracy rates, evaluation method, cost or incident data are presented in the deck.
Limitations and uncertainty
Operator/vendor-presented material (file name references the implementing firm Vulcan); not an independent evaluation. Slide text is terse and partly image-based. No outcome metrics. Model provenance unclear relative to earlier statements.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-29; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Residents and businesses cannot easily determine which agency, rule, license or form applies to them across a large administrative code.
- Stakeholders
- State CIO or CDO
- Agency licensing and permitting directors
- Governor's or efficiency office policy staff
- Agency general counsel
- Public information officers
- Discovery questions
- Which licensing or permitting questions generate the most calls or emails today?
- Who owns the authoritative rule and form content for each agency?
- Is GovCloud or FedRAMP hosting a requirement for public-facing AI in your state?
- How will you measure answer accuracy and citation fidelity before and after launch?
- Value hypothesis
- A scoped, citation-grounded navigator may reduce time residents spend locating the right agency and form, to be confirmed with local baseline call and search data.
- Potential engagement
- A bounded discovery and prototype on one agency's licensing rules, with an evaluation harness for accuracy, citation fidelity and refusals.
- Unsupported claims
- Any measured reduction in calls, time or cost (none reported)
- Accuracy rates for SAM
- That all model inference runs inside GovCloud
- Guaranteed savings
Pre-sales engineering
Role takeaway
- Fit
- Good fit for RAG over statutes, rules and forms on Amazon Bedrock in AWS GovCloud where public, no-login access is acceptable.
- Architecture and integration
- Public web front end, retrieval index over administrative code and agency documents, model inference in GovCloud, citation rendering, and links out to agency application systems.
- Prerequisites
- Machine-readable rules and forms corpus
- Agency content owners and refresh process
- GovCloud account and model access approvals
- Evaluation question set with expected citations
- Constraints
- Model availability differs in GovCloud
- Unclear whether external commercial models are also called
- Legal-advice disclaimers required
- Public records exposure of chat content
- Security
- Avoid collecting PII, log prompts under records-retention rules, and document the FedRAMP boundary and every model endpoint used.
- Proof of value
- Measure citation fidelity on a fixed question set
- Run refusal tests for legal-advice and off-topic prompts
- Verify all inference endpoints sit inside the stated boundary
- Track rule-change-to-index latency
Delivery
Role takeaway
- Work
- Stand up a scoped regulatory navigator for one agency domain, with corpus pipeline, evaluation suite and public AI disclosure notice.
- Dependencies
- Agency rule and form owners
- State security office approval
- Hosting account in GovCloud
- Accessibility and language review
- Ownership
- State efficiency or digital-services office, with each agency owning its content.
- Skills and adoption
- Train agency content owners on corpus updates and staff on interpreting cited answers.
- Governance checkpoints
- Legal review of disclaimers
- Security authorization of hosting boundary
- Pre-launch accuracy and refusal evaluation
- Quarterly content-currency review
- Acceptance criteria
- Proposed: at least 95% of test answers cite the correct governing rule
- Proposed: zero legal-advice responses in the refusal test set
- Proposed: rule changes indexed within an agreed number of business days
- Risks
- Stale rules producing wrong guidance
- Over-reliance on answers as legal advice
- Undisclosed model routing outside the authorized boundary
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?
Pattern: public website front end on texas.gov, retrieval over statutes, administrative code and forms, model service in AWS GovCloud, answers point to linked agency sources. The deck does not state which foundation models are used or whether non-GovCloud model calls occur; the archived StateScoop launch report quoted the director describing partnering with Gemini, Claude and ChatGPT, which should be reconciled against the GovCloud framing.
Governance
Who approves, reviews and stays accountable for outcomes?
Explicit scope limits (no legal advice, no case decisions, no unrelated tasks) and the deck's criteria for AI opportunities (repetitive rule-bound work, existing records, recoverable mistakes, a person stays on the decision) give a reusable governance checklist for state agencies.
Security and privacy
What data, permissions and controls need testing?
No-login design minimizes stored identity data; users are told to keep sensitive information out of the chat. FedRAMP and GovCloud are noted, but the authorization boundary and model-provider data flows are not documented in the deck.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
The deck positions SAM for both residents and public servants navigating policies, records and requirements, implying staff self-service use as well as public use; no accessibility testing is described.
Procurement
What should contracts, pricing and exit terms secure?
Buyers should request the hosting boundary, model list, FedRAMP authorization scope and evaluation results before treating this as a reference architecture; the deck alone does not establish contract terms or cost.
Operating model
Which teams own the service once it runs?
Content currency depends on keeping the regulation corpus synced with rule changes; ownership of corpus maintenance across agencies is not described.
Publication history
- 2026-10-29AWS · Issue 019 resources
Stable resource ID: texas-treo-sam-aws-govcloud-dir-discover-20261006