Bot commit

git add config/systems; commit only when YAML changed. Policy can require a bot PR instead of push-to-main.

• ✓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 Bot commit

What

Edit

Pipeline commits map diffs back to main (or opens a bot PR).

When

Edit

Continuous — part of the always-on architecture map

Where

Edit

CLI pipeline automation · Source control

Why

Edit

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

• config/systems YAML← committed by
• main branch→ pushes to

• bot-commit-service
• pipeline-platform

• Bot commit runbook

  wiki/wiki/bot-commit.md

  In-app wiki path (demo stub)

  EditDelete

• Source repository

  repohttps://example.com/repos/bot-commit

  Example repo link for the public demo

  EditDelete

• Ops dashboard

  urlhttps://example.com/dashboards/bot-commit

  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.