Cairn Documentation
Requirements
Requirements define what a node must do or how well it must perform. They're the bridge between stakeholder needs and engineering implementation.
Requirement Types
Cairn supports six requirement types:
Functional: What the node must do.
Performance: How well it must do it.
Interface: Constraints on connections with other nodes.
Safety: Hazards that must be mitigated.
Environmental: Operating conditions the node must withstand.
Constraint: Design boundaries that limit solution space.
Scoping to Nodes
Every requirement belongs to exactly one node. When you select a node and open the Requirements lens, you see only that node's requirements. The Completeness lens flags nodes with no requirements.
AI Generation Patterns
The ⌘K palette generates requirements scoped to your selected node:
The AI proposes requirements as a ChangeSet. Review each one — is the shall-statement testable? Is the threshold reasonable? Does it belong on this node or a child?
Editing Requirements
Open the Inspector to edit a requirement directly. Title, description, type, priority, and acceptance criteria are all click-to-edit fields — your change commits immediately. Use this for fixing wording, retyping a misclassified requirement, or sharpening the threshold on a draft.
Delete from the Inspector. The cascade preview lists every trace link and verification that would be removed alongside the requirement, so you can see the impact before you confirm.