The architecture that lets software act on a campus.
Risely's agents connect once to the systems already in place, resolve every signal to one student record, and route every action through a named person before anything writes back. One loop runs underneath all of them: learn it once, and every agent Risely ships reads the same way.
audit ledger · this job
Perceive: the job starts with signals no single office can see.
A sophomore drops a four-credit course: credits fall from 15 to 11, and the aid award requires 12. The drop lives in the registrar, the aid line in financial aid, the silence in the LMS. Risely's agents read all of them, so the pattern that spans four offices still gets seen.
Each system holds one piece. No office sees all four.
Reason: on one record, the whole story counts.
Every signal resolves to one student record before any reasoning starts. On that record, the four-credit drop is the event that crosses the line her award sits on, and the degree plan already holds the fix: a one-credit lab that puts her back at 12. Risely's agents weigh the drop, the line, the silence, and the plan as one story.
Draft: the outreach arrives in the student's own context.
Risely's agents write the outreach from what the record says: the course she dropped, the line her award sits against, the one-credit lab that fits the Tuesday slot her schedule already has open. The advisor reads a message that sounds like someone who did the homework, because the homework is done.
To the student
Your aid and the BIO 210 drop
Dropping BIO 210 puts you at 11 credits, and your aid award asks for 12. There's a one-credit lab, BIO 115L, that fits your Tuesday slot and puts you back at 12. A seat is held for you through add/drop. Want it?
her drop, named
her aid line, in plain terms
her schedule, already checked
one concrete next step
Approve: nothing acts before a named person says go.
Every drafted move stops at a person who owns the decision. The advisor sees the action, the reasoning behind it, and the record it touches, then approves, edits, or declines. The gate holds for a routine nudge the same way as for anything that touches money, aid, or standing. Judgment stays with staff on every pass.
Queued action
Send outreach to the student and hold a seat in BIO 115L
Full reasoning attached: the drop, the aid line, the plan check, the seat count.
Nothing sends, nothing writes, nothing holds until the advisor says go.
Act and log: the work writes back to the SIS, every step on the ledger.
On approval, the loop closes. The seat gets held, the message goes out, and the result lands back on the system of record the campus already runs. Each step writes to a ledger the next advisor inherits, so whoever asks what happened gets the trail.
One write, and four offices already know.
The seat hold is one write to one record. No sync job ran; the record changed, so every office's view changed with it.
- Financial aid sees the fix queued against the below-12 warning, so no one starts a recalculation the add would undo.
- Advising closes the follow-up with the outcome attached, and retention marks the credit signal covered while the login watch stays open.
A student record, after the seat hold posts
Four views read one record, and no one hands off.
Wired in place. Nothing migrates.
Risely reads existing systems where they run, through connectors scoped to the work each agent does. The SIS stays the system of record and receives every write-back.
- The record Risely's agents reason on composes at read time, per student, across systems, with no data warehouse project in front of it.
- The first connection is the project. Every agent you turn on after that inherits the wiring, so the second office and the twentieth agent land in weeks.
Read in place. each connector reads the source system where it runs, with the scopes that office grants and nothing wider
Compose per student. signals resolve to one student record at read time, so every agent reasons on the whole story
Write back narrow. approved actions land on the system of record through the same scoped connector, and the ledger keeps the receipt
Agents that act earn that right one approval at a time.
The approval gate
Every action that touches a student, a record, or a dollar routes through a named person before anything executes. Your staff set who approves what, and the gate holds at any volume. A queue of ten and a queue of ten thousand pass through the same human hands.
The audit ledger
Signals read, reasoning steps, approvals, and write-backs land on a ledger tied to the student record. When a dean, an auditor, or an accreditor asks why a move was made, the answer is a trail, in order, with names on it.
The data line
The raw data stays the institution's. Everything Risely holds for the institution exports in open formats on request, including at termination. The knowledge graph, the schema mappings, and the models running above that data are Risely platform IP, licensed to the institution for the term. Full portability holds at every point in the relationship.
Watch the loop run on one of your own jobs.
Bring the workflow that eats your week. Risely's agents will walk it through all five beats, gate and ledger included.
Schedule a demo