Use cases Student engineering teams
Keep your design's reasoning from one year's team to the next
For Formula Student, rocketry, rover, CubeSat and capstone teams that build real hardware with members who change every year. Cairn asks about your system in plain words, builds a model of it in the terms a design review uses, and exports it as one file next year's team can import.


The problem
Every year the people who know why the chassis is steel, why the battery sits where it does and which test proved the brakes graduate. The next team inherits a folder of slides and spends its first months finding all of that out again.
Design reviews ask for requirements, interfaces and a verification plan, and for many members the review is the first time they have written any of them. The words are part of the hurdle: derived requirement, interface, verification method.
A workflow in Cairn
Start with plain questions
Describe the car, rocket or rover. The interview asks in plain words and lets you say you're not sure; each answer becomes a fact marked You said or Assumed, the first lesson in telling a requirement from a guess. Before you start, the demo shows the same workspace on a finished rover.
The interview →Write requirements a judge can check
Wording checks flag a requirement with no "shall", words that can't be verified such as "fast" or "robust", and a performance requirement with no number. Fix them before the design review, not in it.
Requirements →Agree the interfaces between subteams
Each interface names what passes between two parts, such as the messages from the inverter to the vehicle control unit or the current from the accumulator. The N² chart shows a part nothing connects to, often a conversation nobody has had yet.
Architecture and interfaces →Plan the tests before competition
Give each requirement a verification method, from a brake test to an analysis of the frame, and record each result. Overview counts what has passed and what is failing.
Verification matrix →Check what's missing before a review
Completeness asks of each part whether it is described, broken down, connected, required and verified, and the system tree shows where the gaps are. Work through them the week before the design review.
Completeness checks →Hand the model to next year
Record why each choice was made, and the options set aside, in the Dendritic lens. At the end of the year, export the project as a .cairn.zip with its full History, and the incoming lead imports it on their own computer.
Exports →
What Cairn doesn't do yet
- There is no shared workspace yet. One person keeps the model in their browser, backed up to their account, so subteams can't edit it at the same time; it moves from person to person as an export file.
- Cairn doesn't read or write SysML or ReqIF, and doesn't connect to CAD or a task tracker. The model comes out as JSON, Markdown or CSV, and diagrams as PNG or SVG.
- Written PowerPoint and Word documents need your own Anthropic key.
Questions
- Do we need to know systems engineering first?
- No. The interview asks in plain words, and the demo lets you click through a finished model on a computer without an account. The docs' glossary explains each term.
- How does next year's team get the model?
- Export the whole project as a .cairn.zip, with its History, and they import it. It is a copy: changes made afterwards in one copy don't reach the other.
- What kinds of teams does it suit?
- Any team building hardware with parts that have to work together: Formula Student, rocketry, CubeSats, rovers, solar cars and capstone projects.
See it on your own system.
Describe what you are building and Cairn interviews you, then builds the first model with you.