Onboarding Workflow

This document defines how the AI team begins work when a GitHub user selects a repository.

1. First-Time Sign-In & GitHub Authorization

The first time you use Astrakion:

  • Sign in with GitHub
  • Astrakion requests permission to access selected repositories
  • Choose which repositories the AI team may work on

No AI work begins during this step — this only connects Astrakion to GitHub.

2. Select a Pricing Tier

After GitHub authorization, select one of the three plans:

  • FREE — Starter Lane — Light usage, limited capacity, great for testing
  • PRO — Velocity Lane — Medium-to-high usage, consistent throughput
  • ENTERPRISE — Autonomous Throughput Lane — High volume, continuous delivery

Tier selection must be completed before the AI team begins working.

3. Required API Keys

After choosing a tier, you must provide:

  • OpenAI API Key — Used by Astra (PO) and Orion (QA)
  • Claude API Key — Used by Kade (DEV)

These keys are encrypted and stored securely. If keys are missing or invalid, Astra pauses all work.

4. Optional Slack Setup

You may optionally connect Slack for:

  • Real-time status updates
  • Refinement alerts
  • PR notifications
  • Token interruptions

If not connected, all updates continue through the web app and GitHub.

5. Select a Repository

When you select a GitHub repository, Astra begins onboarding checks.

Does the repo have existing Astrakion memory?

Astra checks if the wiki contains an "Astrakion Scrum Team" section.

If it exists — Repo is already onboarded

  • Memory loads immediately
  • Issue refinement begins
  • Kanban workflow starts

If it does NOT exist — Full onboarding begins

This path runs only once per repository.

New Repo Onboarding Process

Step 1: Create Wiki Section

Astra creates the "Astrakion Scrum Team" wiki section — the team's workspace, memory, and documentation hub.

Step 2: Technical Analysis

Astra creates a technical analysis issue for Kade. Because this is analysis-only work:

  • Does NOT require human approval
  • Is automatically approved by Astra
  • Does NOT consume Astrakion Tokens
  • Triggers immediately

Step 3: Kade Analyzes

Kade performs zero-code-change analysis:

  • Architectural structure
  • File and module layout
  • Dependency graph
  • Key patterns and flows
  • Technical observations

Step 4: Orion Reviews

Orion performs QA review ensuring clarity, structural correctness, and completeness. Then merges into astrakion/develop.

Step 5: Documentation

Using Kade's technical analysis, Astra writes:

  • Plain-language system overview
  • Behavioral summaries
  • Architectural interpretations
  • Product rules & constraints

Step 6: Complete

The repository is marked as onboarded. Normal Kanban workflow begins.

Summary

Condition Action
Team section exists Load memory → refine issues → begin Kanban
No team section Create memory → auto-approved analysis → QA → wiki → complete