Implementation profile not fully supported

How to fix

1. Keep running default validation.
2. Review generated findings and setup guidance.
3. Update ArchPilot tooling as specialized stack coverage expands.

What the rule validates

The configured implementation profile is recognized, and ArchPilot is using the default local validation path for evidence it can verify confidently.

Why it matters

Default validation still checks explicit architecture and dependency evidence, while stack-specific checks run only where the current tooling has high-confidence signals.

Common causes

• The project uses a newer or niche stack profile.
• The profile name is ahead of specialized validator routing.
• Smart Init detected a stack that should use default validation behavior.

Typical violation example

Assuming this guidance means validation is unavailable.

Typical compliant example

Treat the notice as scope guidance and rely on documented rules that execute from explicit repository evidence.

Related rules

Adjacent categories

Related files/config

• .archpilot/architecture.json

Related CLI commands

• archpilot validate
• archpilot validate --ci