Databases
Each project lives in its own SQLite .db file. Use the database selector
in the navbar to switch between them.
NewCreates an empty database on the server
CopyClones the active database under a new name
UploadUploads a .db file from your computer to the server and switches to it
DownloadDownloads the active database as a local backup file
Layout Persistence
Node positions, viewport (zoom/pan), selected node, and panel state are automatically
saved to the active database every time you make a change. This means your layout
travels with the .db file — download it, upload to another machine or
browser, and everything is exactly where you left it.
Auto-saveWorking state writes to the DB after 1 second of inactivity
Named layoutsSave/Load snapshots of node positions via the toolbar
Layout buttonResets the tree to an automatic dagre layout; orphans are grouped below
Deleting Nodes
Deleting a requirement does not delete its children. Children become
orphans — they lose their parent link and show a dashed yellow border.
Orphaned nodes fail the Traceable (T) quality gate until re-parented.
Orphans buttonGroups orphaned nodes together without moving the rest of the layout
Re-parentEdit an orphan's parent ID in the detail panel to restore traceability
Quality Gates (TMCS)
T — TraceableAuto-calculated: non-pillar nodes must have a parent
M — MeasurableRequires a test specification (GIVEN/WHEN/THEN)
C — ConsistentManual toggle — you verify it doesn't contradict other requirements
S — Single-purposeManual toggle — you verify it serves exactly one purpose