Node configuration

Select a node in edit mode and the right panel shows everything it carries. The fields, top to bottom:

• Name — what the card says. Keep it the name people actually use in conversation.
• Kind — actor (a person or role), system (a thing you'd name in an org chart of software), container (something that runs — a service, an app, a database process), component (a part inside a container), datastore (where state lives). Kind drives the C4 level: adding inside a system creates containers, inside anything else components.
• Shape — Auto follows the kind (datastores draw as cylinders, everything else as the standard card). Override when the silhouette should say more: Cylinder for a store, Pill for a queue, stream or pipeline, Browser for a web-facing UI, Tube for a communication transport — a pub/sub channel, an SSE stream, a firewall. Shape is meaning, not decoration.

  Booking APIContainer

  Bookings DBDatastore

  Event StreamDatastore

  solstice.comSystem

  Refresh fan-outContainer

• Icon — pick from the built-in brand set (Postgres, Kafka, Stripe, and a few thousand more) or Upload image for your own mark (small files only — it's stored in the model). The icon renders on the card and in the sidebar.
• Parent — re-home the node from a dropdown instead of dragging: pick any node that wouldn't create a cycle, or the top level. Same result as drag-and-drop re-parenting (Arranging & nesting), handy when the target is collapsed or far away.
• External — marks a thing you use but don't own (a vendor, a SaaS). The card renders with the · External tag and a more muted treatment.
• Description — a few sentences on what it is and why it exists. This is what the details sidebar leads with; write it for the new joiner.
• Tags — toggle the canvas's defined tags on and off. Tags that arrived without a definition (an import, an assistant build) show here too — remove them, or Define them to give them a color canvas-wide. See Tags & filtering.
• Owner, Repo, Docs — links that surface as buttons in the details sidebar: the team that owns it, the repository, the runbook or docs page.
• Health url — the endpoint the server probes for live status. The Test button probes it server-side right now and reports the HTTP status and latency before you commit to it. See Live health & logs.
• Logs index / query / Kibana url — where this node's logs live in Elasticsearch and how to find them; its Test runs the query and reports the hit count. The sidebar then shows latest lines and deep-links into Kibana.

Deleting a node removes it, everything nested inside it, every edge touching any of them — and prunes those steps out of any flow that used them. The confirm dialog is there because the cascade is real; ⌘Z brings it all back.