USER MANUAL · MODELING
Tags & filtering
Tags are colored labels on nodes — team ownership, migration waves, PCI scope, anything worth slicing the canvas by. A tag has a definition (name + color, per canvas) and any number of assignments on nodes; the node cards wear their tags as small colored chips.
Booking APIContainerCore
Legacy CRMSystem · ExternalLegacy
PaymentsContainerCorePCI
'legacy' hidden — ghosted, not goneDefining tags
- The rail's Tags tab lists the canvas's definitions. Add tag creates one; edit a definition's name or color there and every node wearing it updates.
- Tags can also arrive without a definition — from an import or an assistant build. They work, colorless; the Tags tab and the node panel both offer Define to promote one into a real definition.
Tagging nodes
In edit mode, a node's panel shows every defined tag as a toggle chip — click to assign or remove. See Node configuration.
Filtering the canvas
- Each tag row in the rail's Tags tab carries a visibility toggle. Hiding a tag fades every node wearing it to a faint ghost — and everything nested inside those nodes with them — so a whole slice of the estate steps back at once.
- Hidden nodes stop catching clicks; edges into the hidden slice fade with it. The canvas underneath is unchanged — filtering is a view, not an edit, and edit mode always shows everything.
- The filter rides the URL (hide=), so a copied link keeps it — and a live presentation syncs it to every viewer.