# FAQ

## Why add graph-aware analysis?

Because Didactopus is fundamentally concerned with mastery paths and dependency structure.
A pack can look fine in text form and still behave badly as a learning graph.

## What kinds of issues can it find?

Examples:
- cycles
- isolated concepts
- dependency bottlenecks
- packs that are too flat
- packs that are too deep

## How does this help with the activation-energy problem?

It reduces the chance that a user imports a pack and only later discovers that the
prerequisite structure is confusing or fragile.

## Does this replace human review?

No. It gives the reviewer better signals earlier.