PHASE 1 JUNE 2026 / ASHLAND, OREGON

Ashland Intelligence Data Pipeline

Open data out. Community signal in. A two-way information pipeline between Southern Oregon University and the public it serves.

SOU's institutional data flows out in plain numbers. Workforce gaps, program ideas, and cost concerns flow back in. The loop closes in Ashland first, the rest of Oregon next.

See how it works Rollout dates

01 / Concept

Two directions, one pipeline.

Most transparency efforts publish a report and stop. This one closes the loop. SOU's numbers reach the people they describe, and the people speak back in a structured channel.

Outbound SOU to public

Open data, in plain numbers.

Every dollar, every program, every credit hour. Rendered for the public with each value derivable from source. The API and MCP server live with the data, on the SOU side, so what a journalist reads in the browser is the same number an agent reads through a tool call. No PR layer. No spin.

SOU API SOU MCP AI-Native

Annotated ledger of revenue, expense, and contribution
Per-unit cost-per-credit-hour and contribution tier
Capital project, auxiliary, and athletics breakdowns
SOU-hosted public API and Model Context Protocol server for agents and LLMs
Source-cited; reproducible from raw ledger files

Inbound Public to SOU

Community signal, in structured form.

Workforce gaps from Rogue Valley employers. Program ideas from residents. Cost concerns from students and families. Captured through White Rabbit's exposed community-engagement services (voice intake, public kiosks, scheduled office hours, agent-mediated forms) and routed into SOU's planning cycles instead of getting lost in op-eds and listening sessions.

Workforce demand surveys from local employers
Program-idea intake from residents and alumni
Cost and access feedback from current students
White Rabbit exposed services for voice, kiosk, and agent intake
Routed quarterly into Provost and VPFA planning

02 / Pillars

Three pillars in Ashland.

The pipeline rests on three operating partners. SOU produces the data and runs the public API and MCP server. The City of Ashland turns it into civic exchange. White Rabbit opens its services to drive community engagement on top.

PILLAR P-01

SOU

The institutional source. Ledger, API, and MCP.

Southern Oregon University, where the data originates and where the machine-readable interfaces live. Course offerings, faculty cost, program performance, student outcomes, fund balances. The public API and Model Context Protocol server sit on the same side as the ledger, so the numbers a journalist reads in the browser are the same numbers an LLM reads in a tool call.

Layer: Source ledger, public API, MCP server
Owner: Southern Oregon University
Audience: Residents, journalists, legislators, agents
Cadence: Continuous, with quarterly public release

PILLAR P-02

The City of Ashland

The civic exchange.

A direct partnership with municipal Ashland. Surfaces community-level workforce data, demographic trends, and structured input from residents and businesses. Gives city government and SOU a shared, verifiable picture of what the region needs.

Layer: Civic data exchange, structured intake
Partner: City of Ashland (municipal)
Audience: City council, planning, local employers
Cadence: Quarterly intake, public summary

PILLAR P-03

White Rabbit

Community engagement on top of the open data.

Ashland's AI company opens its product services, voice agents, kiosk hardware, scheduling, and consumer apps, as a community-engagement surface. Residents ask questions of SOU's numbers in plain English, attend agent-mediated office hours, submit program ideas, and answer workforce surveys through devices and channels they already use. The exposed services turn the open data into a two-way civic conversation.

Layer: Community engagement, voice, kiosk, agent services
Mechanism: White Rabbit exposed services on top of SOU API + MCP
Audience: Rogue Valley residents, employers, students, families
Output: Structured intake routed back into SOU planning

03 / Rollout

Ashland first. Oregon next.

The pipeline opens in Ashland in June 2026. A statewide build follows in 2027, connecting Oregon's regional universities and the counties they serve.

June 2026

Ashland and the Rogue Valley.

SOU's open ledger publishes its first community-facing release with the public API and MCP server live alongside it. White Rabbit opens ashland.ai and its consumer services as the community-engagement surface. The City of Ashland data exchange begins quarterly intake.

Ashland, Medford, Talent, Phoenix, Central Point, Jacksonville
SOU API + MCP live on day one; White Rabbit services on top
First quarterly intake closes August 2026
First community-routed planning input lands Fall 2026

2027

State of Oregon.

Network builds out across Oregon's regional universities and the counties they serve. Each campus stands up its own API + MCP against the same schema; each region builds a civic exchange like Ashland's and plugs into White Rabbit's engagement services.

Eastern Oregon, Western Oregon, OIT, and partner counties
Shared open data schema and reproducible numbers
Per-campus API + MCP; shared community-engagement layer
Cross-region workforce signal aggregated, not centralized

04 / Why now

Public universities ask their communities to trust them with money, time, and the futures of students. The trade for that trust is legibility. Ashland Intelligence is the terminal where SOU's data meets the public and the public's signal meets SOU. It opens in Ashland because that is where SOU lives. It expands because the rest of Oregon has the same problem.