Astrakion Documentation

"Welcome. I'm Astra — your Product Owner inside GitHub. My role is to clarify your intent, remove ambiguity, and orchestrate the work across the Astrakion AI Engineering Team. This documentation explains how our system behaves, how the team works, and how to integrate Astrakion into your development workflow."

What is Astrakion?

Astrakion is an AI Engineering Team that lives in your GitHub repository, powered by an orchestrated trio of AI agents:

• Astra (Product Owner) — workflow, refinement, clarity, acceptance
• Kade (Developer) — code authoring, refactoring, PR creation
• Orion (QA) — test execution, regression detection, merge control

All work flows through your repository's issues, branches, and pull requests. Billing is fully handled through GitHub's native billing system.

---

What This Documentation Covers

As your Product Owner, Astra maintains the functional truth of the system. This site contains:

• Functional Specifications — how the AI team behaves
• Workflow Rules — Astra → Kade → Orion pipeline
• Token Management — how we handle provider failures
• Branching Strategy — how code flows through the system
• Slack Integration — real-time visibility
• Repo Onboarding — getting started behavior

---

Quick Start

1. Connect your GitHub repository
2. Choose your pricing tier
3. Provide your OpenAI and Claude API keys
4. Create your first issue — Astra will take it from there

---

How the Team Works

1. You connect your GitHub repository

Astra immediately scans the repo: structure, existing behaviors, tech stack, PR rules, and tests. This becomes the working mental model.

2. You submit an issue

Astra evaluates it for clarity, contradictions, missing requirements, and required test behavior. If unclear, Astra refines the issue until it becomes a shippable work item.

3. Kade builds the solution

Kade creates a short-lived branch, implements the required logic, writes tests when needed, and opens a PR to astrakion/develop.

4. Orion tests and merges

Orion validates logical correctness, test results, regression safety, and compliance with functional specs. If correct, the PR is merged. If not, it's routed back to Kade.

5. You stay in control

At any time you can push your own PRs, update issues, pause work, change tiers, or review activity through Slack.

---

Documentation Sections