Aphelion Wiki
Language: English | 日本語 Last updated: 2026-04-18 Audience: All users
Welcome to the Aphelion Wiki — the detailed reference for the Aphelion multi-platform AI coding agent workflow.
Not sure where to start? → Getting Started
What is This Wiki?
Section titled “What is This Wiki?”Aphelion’s README covers the quick start and an overview. This wiki provides the in-depth reference material that the README intentionally omits:
| README | Wiki |
|---|---|
| Project overview and motivation | Architecture: 3-domain model and session isolation |
| Quick Start commands | Getting Started: per-platform setup, scenarios, troubleshooting |
| Triage plan table (summary) | Triage System: selection logic, conditions, and agent matrices |
| Agent list (names only) | Agents Reference: all 27 agents with inputs, outputs, and NEXT conditions |
| — | Rules Reference: 9 behavior rules with scope and customization notes |
| Platform comparison table | Platform Guide: generation pipeline, constraints, and deployment |
| — | Contributing: how to add agents, rules, and platforms |
Table of Contents
Section titled “Table of Contents”Core Pages
Section titled “Core Pages”| Page | Description | Primary Audience |
|---|---|---|
| Getting Started | Platform-specific setup, first run, usage scenarios, command reference | New users |
| Architecture | 3-domain model, handoff files, session isolation, AGENT_RESULT protocol | Agent developers |
| Triage System | 4-tier plan selection logic, per-domain agent matrices, mandatory agents | All users |
| Agents Reference | All 27 agents: responsibility, inputs, outputs, NEXT conditions | Agent developers |
| Rules Reference | All 9 behavior rules: scope, auto-load, interactions | Agent developers |
| Platform Guide | Claude Code / Copilot / Codex differences, generate.mjs pipeline | Platform porters |
| Contributing | Adding agents, rules, platforms; bilingual sync workflow | Agent developers |
Persona-Based Entry Points
Section titled “Persona-Based Entry Points””I want to use Aphelion for the first time”
Section titled “”I want to use Aphelion for the first time””- Read Getting Started — Quick Start for your platform
- Run
/discovery-flow(or/pmif requirements are already clear) - Read Triage System to understand which agents will be launched
”I want to understand how Aphelion works internally”
Section titled “”I want to understand how Aphelion works internally””- Read Architecture — domain model and handoff mechanism
- Read Agents Reference — each agent’s responsibility and connections
- Read Rules Reference — behavioral constraints applied to all agents
”I want to add a new agent or rule”
Section titled “”I want to add a new agent or rule””- Read Contributing — file templates and AGENT_RESULT contract
- Read Architecture — understand where the new agent fits
- Read Rules Reference — understand which rules apply automatically
”I want to use Aphelion on GitHub Copilot or OpenAI Codex”
Section titled “”I want to use Aphelion on GitHub Copilot or OpenAI Codex””- Read Platform Guide — capability differences and limitations
- Read Getting Started — platform-specific Quick Start
Glossary
Section titled “Glossary”| Term | Definition |
|---|---|
| Domain | One of the three top-level workflow scopes: Discovery, Delivery, Operations |
| Flow orchestrator | An agent that manages an entire domain (discovery-flow, delivery-flow, operations-flow) |
| Triage | The process of assessing project scale at flow start and selecting a plan tier |
| Plan | One of four execution tiers: Minimal / Light / Standard / Full |
| Handoff file | A .md file used to pass information between domains (DISCOVERY_RESULT.md, DELIVERY_RESULT.md) |
| AGENT_RESULT | The structured output block every agent emits upon completion |
| NEXT | The field in AGENT_RESULT that specifies which agent runs next |
| STATUS | The completion status field: success / error / failure / suspended / blocked |
| blocked | STATUS used when an agent cannot continue due to design ambiguity |
| Canonical source | .claude/ — the authoritative definition files for Claude Code |
| PRODUCT_TYPE | Classification of the project artifact: service / tool / library / cli |
| HAS_UI | Whether the project includes a user interface (affects which agents run) |
| Auto-approve mode | Mode activated by .aphelion-auto-approve file; skips approval gates for automated evaluation |
Related Pages
Section titled “Related Pages”Canonical Sources
Section titled “Canonical Sources”- .claude/CLAUDE.md — Aphelion workflow overview
- README.md — Project entry point