From the Campus Operations edition of October 22, 2026
Arkansas Tech adopts AI principles requiring explicit approval, a named owner and re-review for any agentic AI connection, including vendor agent features switched on by default
Arkansas Tech University · Public regional university: institutional AI governance · Russellville, Arkansas, United States
- Publisher
- Arkansas Tech University
- Original publication
- 14 October 2026 (document header 'ATU AI Guiding Principles – 10.14.26')
- Source retrieved
- 2026-10-23
- Event date
- 2026-10-14
What happened
Arkansas Tech's AI Guiding Principles, developed by a faculty, staff and student committee, set ten principles and governance standards. AI may not be the final decision-maker for admissions, financial aid, grading, discipline, employment or access to services, and ATU will not require employees to use generative AI. Agentic AI gets its own tier: any connection to ATU systems, accounts or data needs explicit approval through governance including the information security office, a named owner, a statement of what it can access and do, when humans approve actions and what records are kept. Vendor agentic features turning on by default trigger re-review. ATU will keep an AI inventory and retire noncompliant systems.
Why it matters
Why now: not previously archived and surfaced in this run's scrutiny pass; it is a concrete institutional answer to the agent-governance and labor demands raised this week, including a no-mandatory-use commitment that unions elsewhere are seeking in contracts.
Evidence and measured results
Approved principles document; describes intended controls, not observed practice.
Limitations and uncertainty
Dated 14 October, a week before this run; specific procedures and approved-tools list are still to come.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-22; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Institutions adopting agent-specific governance need practical intake, inventory and vendor-change monitoring to apply it.
- Stakeholders
- CIO and information security office
- Provost
- HR
- Faculty and staff senates
- Procurement
- Discovery questions
- How will agent approvals be requested and recorded?
- Who monitors vendor releases for default-on agent features?
- Is there an AI inventory today?
- How is the no-mandatory-use rule handled in workflows?
- Value hypothesis
- Interpretation: a standard intake and inventory could make agent approvals consistent; no outcomes are documented.
- Potential engagement
- A bounded agent intake, inventory and vendor-change monitoring setup aligned with an institution's AI principles.
- Unsupported claims
- That the principles are enforced
- Reduced incidents
- Faster approvals
- Guaranteed savings
Pre-sales engineering
Role takeaway
- Fit
- Template for agent-specific approval criteria in a campus governance framework.
- Architecture and integration
- Approved agent connections must use security-office-approved authentication and least-privilege access.
- Prerequisites
- Agent intake form with access scope
- Identity provider support for scoped access
- Action logging
- Constraints
- Per-tool, per-use approval
- Re-review when vendors enable agent features
- No credential sharing with third parties
- Security
- Least-privilege access, MFA hygiene, vendor contract terms for retention, deletion and breach notice.
- Proof of value
- Confirm each agent's scopes match its approval
- Verify action logs capture what the agent did
- Test detection of vendor default-on agent features
Delivery
Role takeaway
- Work
- Operationalize agent approvals, inventory and re-review under new AI principles.
- Dependencies
- Governance group meeting cadence
- Vendor release monitoring
- Inventory tooling
- Ownership
- Office of Information Systems with the relevant governance group; each agent has a named responsible owner.
- Skills and adoption
- Role-appropriate training required before high-impact systems are deployed.
- Governance checkpoints
- Approval before any agent connects to ATU systems
- Re-review on capability change
- Periodic inventory review and sunset
- Acceptance criteria
- Proposed: 100% of connected agents in the inventory with named owners
- Proposed: re-review completed within a set period of vendor feature changes
- Proposed: non-AI alternatives documented for required workflows
- Risks
- Shadow agents bypassing approval
- Vendor features enabled silently
- Approval backlog slowing legitimate use
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?
Agent connections must use approved sign-in and least-privilege access; credentials may not be shared with third-party services.
Governance
Who approves, reviews and stays accountable for outcomes?
Per-tool, per-use approval for agents with named owner, access scope, human approval points and recordkeeping; re-review on capability changes.
Security and privacy
What data, permissions and controls need testing?
Least-privilege access, no credential sharing, MFA hygiene, vendor contract terms on retention, breach notice and subcontractors.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
No required generative AI use for employees; AI not to justify eliminating human oversight or services.
Procurement
What should contracts, pricing and exit terms secure?
Vendor contracts must cover data handling, deletion, breach notification and material changes; conflict-of-interest disclosure for AI purchasers.
Operating model
Which teams own the service once it runs?
Inventory, monitoring and sunset of AI systems; role-appropriate training before high-impact deployment.
Publication history
- 2026-10-22Campus Operations · Issue 455 resources
Stable resource ID: arkansas-tech-ai-guiding-principles-agentic-approval-20261014