Welcome to Agentic Data Requests thatanswers the dean's quick question from the governed record.
A team hired for analysis spends its weeks pulling counts, and every hand pull is a fresh chance for two offices to get two answers. Risely's agents answer from the governed record with lineage attached, and an IR analyst reviews everything that goes out.
The request queue · this week
answering
Dean: retention by major, five years
drafted same day · held for the analystProvost office: the same request, third time this year
self-serve now · the fourth ask answers itselfFaculty researcher: cohort extract
governed · released after reviewEvery answer traces to the same lines the factbook reads, so two offices can no longer get two truths.
Every answer comes from the governed record.
The dean's retention-by-major pull runs at census definitions against the same lines the factbook reads, with lineage attached. Same question, same answer, everywhere it gets asked.
The dean's quick question
running
The answer matches the factbook because it is the same line. The dean stops waiting, and IR stops re-deriving.
The third repeat becomes a view.
The repeat gets noticed, the definitions get locked, and the request becomes a self-serve view. The fourth ask through the fortieth costs zero analyst hours and cannot drift from the governed answer.
The provost office's favorite request
The fourth ask answers itself, at zero analyst hours
The definitions stay locked inside the view, so self-serve never drifts into self-defined.
Research requests get research governance.
IRB status verified, de-identification applied per protocol, and the extract logged with the rules it ran under. The process an audit expects runs on every extract, every time.
Faculty cohort extract
clearing governance
The process an audit expects, run on every extract rather than remembered on the good days.
The queue stops eating the analysts.
The counts-and-pulls layer runs itself under review. What reaches the analysts is the work that needs judgment, which is the work they were hired for and the queue kept burying.
The queue, split honestly
Counts and pulls · runs itself
Judgment · reaches the analysts
A team hired for analysis gets to do analysis. The queue keeps moving either way.
One ask lands. The queue re-runs.
A dean's count, a provost repeat, a researcher's extract. Each of them used to cost an analyst a day, and every one runs the same way.
A dean asks for retention by major
in plain English, by email
The pull runs at census definitions
the same lines the factbook reads
Lineage attaches itself
definition, source, as-of date
The analyst reviews the draft
one look on the same day
The answer matches the factbook
because it is the same line
What changes, and how it runs.
The dean's number arrives same day
The lineage is attached, and it matches the factbook.
Repeat requests stop costing hours
The third ask becomes a view that serves the fortieth.
Analysts do analysis again
The counts run themselves. The judgment stays human.
The technical read
Connects read-only to your SIS and data warehouse to start
An IR analyst reviews every answer that leaves the office
Every action lands on an append-only log
Runs alongside what you have. Nothing rips out.