Navo SPA

nginx static SPA image built with compile:config from the same Git commit. Non-root, read-only root FS, NetworkPolicy deny-public.

• ✓Clear role in the Kubernetes zone of the mapEditDelete
• ✓Topology and narrative stay in versioned architecture YAMLEditDelete
• ✓Visible to unlimited viewers without a platform portal seatEditDelete

Who

Edit

Kubernetes owners and on-call for Navo SPA

What

Edit

Locked-down architecture browser serving compiled maps.

When

Edit

Continuous — part of the always-on architecture map

Where

Edit

CLI pipeline automation · Kubernetes

Why

Edit

Documents how Navo SPA connects in the living map so teams share one Git-backed model.

• Kubernetes← runs
• config/systems YAML← compiled into

• navo-spa-service
• pipeline-platform

• Navo SPA runbook

  wiki/wiki/navo-spa.md

  In-app wiki path (demo stub)

  EditDelete

• Source repository

  repohttps://example.com/repos/navo-spa

  Example repo link for the public demo

  EditDelete

• Ops dashboard

  urlhttps://example.com/dashboards/navo-spa

  EditDelete

In the full Navo app (local pnpm dev), this form writes links into architecture YAML. On the public website it is disabled.

In Navo, notes and personal links stay in browser localStorage until you export for a PR. Overlay editing is off in this public demo.