Persona-based documentation — separate quick starts for developers, security teams, and architects

[JBAhire]

Summary

Create persona-specific documentation paths so developers, security teams, and architects each get a tailored onboarding experience focused on their needs.

Motivation

The current getting-started.md serves all audiences equally, but different personas have different questions:

• Developer: "How do I fix this finding in my code?"
• Security team: "How do I set up org-wide policies and scan everything?"
• Architect: "How do I map my entire agent infrastructure?"
• Ops/SRE: "How do I monitor agents in production?"

A security engineer doesn't need framework fix examples. A developer doesn't need fleet management docs. Persona-based paths reduce friction and increase time-to-value.

Proposed Guides

1. Developer Quick Start (docs/personas/developer.md)

• Focus: fix findings in your agent code
• Flow: scan → understand findings → fix → rescan
• Key commands: g0 scan, g0 test, g0 mcp
• Links to: remediation cookbook, framework guides
• Tone: practical, code-heavy, minimal theory

2. Security Team Guide (docs/personas/security-team.md)

• Focus: assess and govern the agent landscape
• Flow: discover agents → set policies → enforce in CI → monitor
• Key commands: g0 scan --ci, g0 gate, g0 endpoint, g0 daemon
• Links to: policy configuration, CI/CD guide, compliance reports
• Tone: governance-focused, policy-heavy

3. Architect Handbook (docs/personas/architect.md)

• Focus: understand agent infrastructure and risk landscape
• Flow: inventory → flows → scores → remediation priorities
• Key commands: g0 inventory, g0 flows, g0 scan --ai
• Links to: architecture doc, scoring methodology, domain deep-dives
• Tone: systems-thinking, big-picture

4. Ops Playbook (docs/personas/ops.md)

• Focus: monitor and maintain agent security in production
• Flow: daemon → endpoint monitoring → alerts → incident response
• Key commands: g0 daemon, g0 endpoint, g0 detect
• Links to: integration guides, Prometheus endpoint, fleet management
• Tone: operational, alert-focused

Files to Create

• docs/personas/README.md — persona selection page
• docs/personas/developer.md
• docs/personas/security-team.md
• docs/personas/architect.md
• docs/personas/ops.md
• Update docs/README.md with persona paths
• Update root README.md with persona links in Quick Start

Acceptance Criteria

• 4 persona-specific guides
• Each guide has a clear flow from problem to solution
• Linked from docs index and main README
• No duplicate content — link to shared docs where appropriate
• Each guide testable in under 10 minutes