Cairn Documentation

Model Explorer

The lenses show one node at a time through an engineering view. The Model Explorer shows the whole model as data: every node, requirement, interface, state, transition, use case, verification, trace link, unit and data type, in tables you can search, sort and edit. Nothing in the Explorer calls AI; it is the deterministic view of exactly what the model holds.

Open it from Tools → Explorer, with ⌘⇧E, or from a tree node's menu with Open in Explorer.

Browsing

• The rail on the left lists each collection with its size. A red count means some of its entries have integrity problems.
• Search matches every column, including the names behind references: searching a subsystem's name lists the requirements allocated to it. Press / to jump to the search box.
• Click a column header to sort; click again to reverse, a third time to clear.
• Under <node> limits the table to what belongs to the node selected in the System Tree and everything below it.
• Rows move with ↑ ↓, PgUp PgDn, Home End.

Editing

Double-click a cell (or press Enter on a row to edit its name) to change names, numbers, enumerations and references in place. Enter saves, Esc cancels. Selecting a row opens its record on the right, where every field is editable, including descriptions and lists such as acceptance criteria (one item per line).

Reference fields are pickers that only offer valid targets: a node cannot be moved under its own subtree, and a transition can only connect states of its own node. Each edit is one ChangeSet in History, with the same guard as every other edit, so an edit that would break the model is refused with the reason.

+ New adds a valid entity to the current collection, attached to the selected node where that applies, with the next id in your project's sequence. Delete shows the same cascade preview as the rest of the app.

Following relationships

Every reference is a link. Click one to jump to the entity on the other end; the back arrow returns. The record panel also lists what points at the entity: a node's children, requirements, interfaces in and out, and states; a requirement's verifications and derived requirements; a unit's uses in node properties; and every trace link in either direction with its type.

Integrity

Integrity at the bottom of the rail lists every structural problem in the model: references to entities that no longer exist, trace links whose declared kind is wrong, duplicate ids, parent loops, a second root, and transitions between states of different nodes. Broken cells are tinted in the tables. See Model Integrity for how these are prevented.