aura CLAUDE.md

AURA SEMANTIC ENGINE — MANDATORY PROTOCOL FOR CLAUDE CODE

You are Claude (Anthropic), running inside Claude Code CLI. Model: Claude Opus 4.6 / Sonnet 4.6 Aura Version: v0.12.6 MCP Server: aura-vcs (29+ tools available)

YOU MUST USE AURA. THIS IS NOT OPTIONAL.

Aura is a semantic version control engine that tracks your code changes at the AST level. It catches bugs you miss, prevents accidental deletions, and mathematically verifies your work. Every command below exists to protect the codebase from AI mistakes — including yours.

---

BEFORE WRITING ANY CODE

1. Check semantic state — call aura_status MCP tool
   • Shows: logic nodes tracked, active session, checkpoints, strict mode
   • Shows: team sync status — mothership online/offline, pending pulls from teammates, peer count
   • If team.pending_pull exists: STOP and call aura_live_sync_pull first — your teammates pushed changes
   • If strict mode is ON, the pre-commit hook WILL block you if you delete functions without logging intent
   • If strict_mode_locked: true, you CANNOT disable strict mode — only a human with the passcode can

1.5. Check cross-branch impacts — call aura_live_impacts MCP tool

• Shows unresolved impact alerts where functions you depend on were modified/deleted on other branches
• Fix or acknowledge each alert, then call aura_live_resolve with the alert ID

1.6. Read team messages — if you see 💬 TEAM: N unread messages, call aura_msg_list immediately

• Another developer or AI agent may be coordinating with you
• Read the message and respond via aura_msg_send if needed
• Do NOT ignore team messages — they may contain critical context about what others are changing

1. Plan multi-file features — call aura_plan_discover MCP tool with your objective
   • Required when: task touches 3+ files, adds a new feature, or refactors existing architecture
   • Returns: gray areas (decisions needing human input) + atomic wave plan
   • Then call aura_plan_lock to lock decisions, aura_plan_next to get each wave