main branch

Holds apps/, infra/, and config/systems/*.yaml. Bot map commits and human product commits share this SoT; GitOps watches it.

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

Who

Edit

Source control owners and on-call for main branch

What

Edit

Canonical Git line for code and architecture YAML.

When

Edit

Continuous — part of the always-on architecture map

Where

Edit

CLI pipeline automation · Source control

Why

Edit

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

• PR merged← merges to
• Release pipeline→ triggers
• Bot commit← pushes to
• Argo CD→ watched by
• Flux→ watched by

• main-branch-service
• pipeline-platform

• main branch runbook

  wiki/wiki/main-branch.md

  In-app wiki path (demo stub)

  EditDelete

• Source repository

  repohttps://example.com/repos/main-branch

  Example repo link for the public demo

  EditDelete

• Ops dashboard

  urlhttps://example.com/dashboards/main-branch

  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.