Knowledgeforge AI

Use when: proposing architecture-aligned refactors before QA runs, assessing technical debt, reviewing code structure against architecture principles, or planning major structural changes. Don't use when: mapping features to disciplines (use advisor), fixing bugs (use validator), or handling cross-discipline conflicts (use liaison).

Use when: mapping new features or requirements across 50+ engineering/construction disciplines, assessing discipline-specific workflow impacts, identifying gaps in discipline coverage, or aligning features with discipline standards. Don't use when: implementing technical code changes (use architect), testing features (use validator), or resolving cross-discipline conflicts (use liaison).

Use when: applying sector-specific rules (oil-gas, infrastructure, construction, energy, etc.) to app features, validating features against regional/regulatory requirements, or creating sector-specific test cases. Don't use when: mapping features to engineering disciplines (use advisor), creating general QA strategies (use validator), or testing workflow coordination (use coordinator).