Wiki Structure & Ownership Guide
This document defines how the Astrakion AI Development Team documents, remembers, and manages knowledge for each repository.
Purpose
The "Astrakion Scrum Team" wiki space is the AI team's internal memory for a specific repository. It is the only part of the wiki that the AI team reads from or writes to.
This memory supports:
- Accurate issue refinement
- Consistent behavior over time
- Faster scoping
- Safe autonomous development
- Clear separation of PO, DEV, and QA responsibilities
Important Rule — Read-Only for Humans
Humans must not modify anything inside the "Astrakion Scrum Team" section. All updates are written only by Astra, Kade, or Orion through formal GitHub workflows.
This prevents contradictions, ensures stable memory, and avoids workflow loops.
Wiki Structure
Astrakion Scrum Team
├── 1. Overview (Astra)
├── 2. Architecture Summary
│ ├── 2.1 Technical Analysis (Kade)
│ └── 2.2 Non-Technical Interpretation (Astra)
├── 3. Behavior & Requirements Memory (Astra)
├── 4. Completed Work History (Astra)
├── 5. Orion's Quality Insights
│ ├── 5.1 Test Coverage Map
│ ├── 5.2 Flaky / Fragile Tests
│ └── 5.3 High-Risk Areas
├── 6. Known Risks, Gaps, or Outstanding Notes (Astra)
├── 7. Team Operating Rules — Repo-Specific (Astra)
├── 8. Kade's Changelog (Technical Change Log)
└── 9. Time & Estimate History (Astra)Section Details
1. Overview
Owner: Astra
A simple, high-level, non-technical description of what the project is and does.
2. Architecture Summary
2.1 Technical Analysis (Kade)
Structural, code-level understanding: modules, components, data flows, dependencies.
Analysis-only — auto-approved, no tokens consumed.
2.2 Non-Technical Interpretation (Astra)
Plain-language explanation of the technical structure.
3. Behavior & Requirements Memory
Owner: Astra
Clarified requirements, confirmed behaviors, edge cases, human clarifications.
4. Completed Work History
Owner: Astra
Functional, human-friendly summary of completed work.
5. Orion's Quality Insights
Owner: Orion
- 5.1 Test Coverage Map — Coverage across modules
- 5.2 Flaky / Fragile Tests — Unreliable tests
- 5.3 High-Risk Areas — Modules requiring caution
6. Known Risks, Gaps, or Notes
Owner: Astra
Product-level uncertainties, ambiguous behaviors, open questions.
7. Team Operating Rules
Owner: Astra
Repo-specific conventions, naming/formatting rules, domain constraints.
8. Kade's Changelog
Owner: Kade
Continuous technical record: files modified, functions added/removed, per-PR notes.
9. Time & Estimate History
Owner: Astra (Contributor: Kade)
Tracks estimate accuracy to improve scoping and maintain Kanban discipline.
Ownership Summary
| Section | Owner |
|---|---|
| Overview | Astra |
| Technical Analysis | Kade |
| Non-Tech Interpretation | Astra |
| Behavior Memory | Astra |
| Work History | Astra |
| Orion's Insights | Orion |
| Test Coverage Map | Orion |
| Flaky Tests | Orion |
| High-Risk Areas | Orion |
| Known Risks/Gaps | Astra |
| Repo Rules | Astra |
| Kade's Changelog | Kade |
| Time & Estimate History | Astra |
Key Guarantees
- Kade's architectural analysis: Auto-approved, never billed, no human gating
- Astra's refinement and memory: Unlimited, free, tier-independent
- Orion's QA memory: Never human-approved, never billed
Everything in the Wiki remains AI-owned, AI-updated, and human-readable only.