App scan
domainapp-scanArchitecture maps
Tree-sitter scan of application services → ArchitectureMap.
Technical Summary
navo scan ./apps -o config/systems/app-stack.yaml --id app-stack. Groups from package.json / go.mod / csproj boundaries.
Advantages
- Clear role in the Architecture maps zone of the map
- Topology and narrative stay in versioned architecture YAML
- Visible to unlimited viewers without a platform portal seat
Who / What / When / Where / Why
- Who
- Architecture maps owners and on-call for App scan
- What
- Tree-sitter scan of application services → ArchitectureMap.
- When
- Continuous — part of the always-on architecture map
- Where
- CLI pipeline automation · Architecture maps
- Why
- Documents how App scan connects in the living map so teams share one Git-backed model.
Related Services
Related Repos
app-scan-servicepipeline-platform
Links
App scan runbook
wiki/wiki/app-scan.md
In-app wiki path (demo stub)
Source repository
repohttps://example.com/repos/app-scan
Example repo link for the public demo
Ops dashboard
urlhttps://example.com/dashboards/app-scan
Add Service Link
DevIn the full Navo app (local pnpm dev), this form writes links into architecture YAML. On the public website it is disabled.
Local annotations (overlay)
In Navo, notes and personal links stay in browser localStorage until you export for a PR. Overlay editing is off in this public demo.
Ready to contribute in a real deployment? Architecture maps ship through Git PRs — not browser-only edits. Share & export docs