aif-explore

To explore codebase architecture without modifying code, use a read-only thinking partner that investigates the problem space, asks clarifying questions, and maps dependencies safely. It visualizes architecture with ASCII diagrams and persists findings without touching your source files.

Yes, you can validate software requirements by entering an exploration mode that tolerates ambiguity and surfaces clarifying questions. It references project context to stay grounded, ensuring your conceptual analysis and requirement validation remain accurate to the existing codebase.

The best way to investigate problem-space dependencies is through a guided non-implementation exploration session. This approach enforces read-only artifact access and project-specific rules, mapping data flows and dependencies while persisting all investigation findings for later planning.

Yes, exploration mode works directly with existing project context by reading and referencing .ai-factory files. This ensures the thinking partner stays grounded in your actual architecture and requirements, enforcing safety constraints while it investigates ideas.

You should not use exploration mode when you need to implement features or modify code, as it is strictly read-only. It is designed strictly for conceptual analysis, brainstorming, and problem-space investigation, not for writing or deploying actual software changes.

To start a guided exploration, simply provide the topic you want to explore. The system will begin a non-implementation investigation, asking clarifying questions, surfacing requirements, and visualizing data flows with ASCII diagrams while enforcing project-specific safety constraints.