Vela

A secure, AI-augmented, governed space for disciplinary work

A vela is a workspace where a person and an AI agent work on the same files, with the material and the tools of one discipline. Whoever runs the vela decides what the agent may do.

Two types of vela

Teaching

A course

An instructor builds a vela for a class. Students work through its units with the agent beside them. The instructor decides, unit by unit, how much the agent may do. That ranges from guidance only, where it has no tool that writes the student's code, to working alongside them as a lab partner.

The focus is on the process of learning. Outputs are easy to generate with AI, so a vela course looks at how the work is done, with the AI as an assistant.

There is a short video walkthrough of a course vela, and a three-page explainer (PDF).

Research

A research project

A researcher builds a vela to address a specific problem, with their own code, papers and data. The researcher directs the work, and the research vela carries it out and brings the results back for review.

The record shows how each result was produced, including the model and the data behind it, so that results can be reproduced and attributed.

What makes it governed

Testing access

Access is by invitation while the testing period runs. After you sign in, you see the courses and research projects you have access to. To ask for access, or to report anything, email Falk Herwig at fherwig@uvic.ca.

What to expect right now

This is a pilot, with no service guarantees.

Token source for vela

Every answer in a vela is generated by a language model running somewhere, and where that is affects speed, availability and where your words go. The model menu names its source on every turn. There are three today:

None of this is a dependable service. All three sources are exploratory. The hardware is borrowed or shared and the budget is small, so any of them can change or stop. We are finding out what a self-hosted open-weight model can do for teaching and research, so nothing here carries an availability promise. Do not build anything that depends on it staying up.