Files
orca/.ciagent/PERSONAS.md
T
Jon Chery 65eb2e601b docs(P00): research findings - architecture + personas
---ci---
project: orca
phase: 0
milestone: v0.1
status: research
personas_active: 5
personas_deactivated: 2
---/ci---
2026-06-03 12:15:20 +00:00

2.8 KiB

active_personas, deactivated_personas, phase_specific, reason
active_personas deactivated_personas phase_specific reason
lead-developer
backend-engineer
data-engineer
cli-engineer
security-engineer
frontend-engineer
devops-sre
Orca is a CLI-first, offline-first orchestration engine with no web UI and a single-binary distribution model. The persona roster reflects this: - lead-developer: coordination and task decomposition - backend-engineer: core engine and API handlers - data-engineer: SQLite state store and migrations - cli-engineer: Cobra subcommands and CLI UX - security-engineer: mTLS, audit logging, input validation Deactivated: - frontend-engineer: no web UI in v0.1 - devops-sre: no container/cloud integrations; release flow is handled by CoreCI (not a persona territory)

Personas: Orca

Roster

lead-developer

  • Domain: coordination
  • Frameworks: cobra
  • Constraints: boundary-enforcement, offline-first, no-redundant-implementations
  • Territory: **/*.go, cmd/**, internal/**
  • Active: true

backend-engineer

  • Domain: backend
  • Frameworks: cobra, net/http
  • Constraints: API-first, error-handling, minimal-dependencies, security-first
  • Territory: **/api/**, **/*_handler*, **/*_handler.go, internal/daemon/**
  • Active: true

data-engineer

  • Domain: data
  • Frameworks: modernc/sqlite
  • Constraints: schema-first, migration-safe, local-storage-only
  • Territory: **/store/**, **/model.go, **/migration*, migrations/**
  • Active: true

cli-engineer (custom)

  • Domain: CLI/UX
  • Frameworks: cobra, pflag
  • Constraints: discoverable-help, consistent-flag-naming, human-readable-output, machine-readable-json-flag
  • Territory: cmd/**, internal/cli/**, internal/commands/**
  • Active: true
  • Reason: Orca is CLI-first; this persona ensures CLI quality and discoverability.

security-engineer (custom)

  • Domain: security
  • Frameworks: crypto/tls, slog
  • Constraints: no-panic-in-production, structured-audit-logging, no-secret-in-logs, input-validation
  • Territory: **/auth/**, **/audit/**, internal/security/**
  • Active: true
  • Reason: mTLS, audit logging, and input validation are first-class concerns.

frontend-engineer

  • Active: false
  • Reason: No web UI in v0.1.

devops-sre

  • Active: false
  • Reason: No container/cloud integrations. Release flow is handled by CoreCI.

Territory Enforcement

  • Mode: warn (per config.json)
  • Behavior: Out-of-territory file changes log a warning but do not block.
  • Rationale: Allows flexibility during early development; tighten to strict post-v0.1.

Phase-Specific Personas

None for v0.1. All personas persist across all 6 phases.