# Getting Started with Aphoria

**Aphoria is an autonomous learning system powered by LLM workflows.** Choose your integration path:

## 🤖 I Want Autonomous Operation (Recommended)

**LLM-Driven Workflows:** Skills, agents, or custom integrations

**Claude Code Skills:**
- Load `/aphoria-claims` - Commit-time claim authoring
- Load `/aphoria-suggest` - Pattern-based claim suggestions
- Load `/aphoria-custom-extractor-creator` - Generate custom extractors

**Go ADK Agents:**
- See [ADK-Go Integration](../../../../sdk/go/adk/) - Fully autonomous tool-use agents

**Custom Integration:**
- Any LLM with tool-use capability can drive Aphoria via CLI

---

## 📚 I Want to Learn It (20 minutes)

**Worked Example:** Follow a complete use case from documentation → claims → violations → fixes

[Database Connection Pool Example](../../dogfood/dbpool/) - See how a solo developer:
1. Extracts 25-30 claims from HikariCP/PostgreSQL docs
2. Writes code (with intentional violations)
3. Runs Aphoria scan (catches all 7-8 violations)
4. Fixes violations incrementally
5. Reaches production-ready code

**What you get:**
- Complete claim extraction walkthrough with decision framework
- Pre-flight validator to check your environment
- Expected output examples for every command
- Real scan results showing BLOCK/FLAG/PASS verdicts

**Time:** 20 minutes to read, 5 days to execute (optional)

---

## ⚠️ Critical: Day 3 of Dogfooding

If you're following a dogfooding exercise (e.g., `dogfood/msgqueue/`), **Day 3 is the most important day** - it's where the autonomous learning flywheel is validated.

**What makes Day 3 different:**
- Days 1-2: Setup (claims authoring, code writing)
- **Day 3: LEARNING** (creating extractors to close gaps) ← **This is the flywheel**
- Days 4-5: Verification (fixes, documentation)

**Common mistake:** Running scan once, seeing low detection rate (0-20%), and moving on without creating extractors. This breaks the entire flywheel.

**Correct approach:**
1. Run baseline scan (expect 0-20% detection on new domain)
2. Analyze gaps (which extractors are missing?)
3. Create extractors with `/aphoria-custom-extractor-creator` (8 invocations for 8 violations)
4. Run verification scan (should be ≥90% detection)
5. Document improvement (0% → 90%+)

**How to verify Day 3 was done correctly:**
```bash
ls .aphoria/extractors/*.toml | wc -l  # Should be: 8+
ls scan-v2.json                        # Must exist
ls DAY3-SUMMARY.md                     # Must exist
```

If ANY are missing, Day 3 is incomplete. See [Common Mistakes](../dogfooding-common-mistakes.md) for details.

---

## 🚀 Fallback: No LLM Access (Debug Interface)

**CLI-Only Mode:** For environments without LLM access or debugging

[Solo Developer Quick Start](./solo-developer-quick-start.md) - Manual scan workflow (debug interface)

**⚠️ Limitations:**
- Manual claim authoring (naming errors break tail-path matching)
- No autonomous flywheel (scan only, no evaluate/claim/create)
- Requires manual pattern analysis

---

## 🔧 I Want to Integrate It (30 minutes)

**Production Integration:** Pre-commit hooks, CI/CD, team workflows

See:
- [Pre-Flight Checks Guide](../guides/pre-flight-checks.md) - Git hooks and CI integration
- [Enterprise Quick Start](../guides/enterprise-quick-start.md) - Team deployment
- [Multi-Team Policy Governance](../guides/multi-team-policy-governance.md) - Scaling to multiple teams

---

## Reference Materials

| Document | Purpose |
|----------|---------|
| [CLI Reference](../cli-reference.md) | Complete command documentation |
| [Comparison Modes](../comparison-modes.md) | How Aphoria evaluates conflicts |
| [Configuration](../configuration.md) | .aphoria/config.toml reference |
| [Architecture](../architecture/README.md) | System design and algorithms |

---

## Support

- **Installation issues:** See [Solo Developer Guide](../guides/solo-developer-guide.md#install)
- **Scan not finding violations:** Check [Troubleshooting](../cli-reference.md#troubleshooting)
- **Custom extractors:** See [Architecture: Extractors](../architecture/README.md#extractors)
- **Enterprise deployment:** See [Enterprise Pilot Guide](../guides/enterprise-pilot-guide.md)