knowledge

Keeping module knowledge bases fresh in a brownfield repository requires re-scanning the workspace to update cached knowledge while preserving accumulated learnings. This ensures downstream execution phases have accurate, verified context instead of relying on outdated guesses.

Managing ROS1 and ROS2 specific knowledge files is handled by generating ROS-variant specific knowledge based on detected dependencies. The system maintains topic, service, and QoS-related data within a centralized index.yaml so each module's files stay discoverable and verifiable.

Git commit tracking validates knowledge base state by enforcing index.yaml schema and checking filesystem presence alongside commit semantics. This mechanism ensures the knowledge DB state remains consistent and fully traceable across module updates and deletions.

You can refresh workspace knowledge without losing prior context research by using the re-scan functionality. It refreshes knowledge files tied to a normalized index while safely preserving accumulated learnings to avoid losing previously captured module insights.

You need to normalize index.yaml for module-specific knowledge DB entries when managing structured knowledge during requirement discovery. It provides a centralized schema so common and ROS-variant knowledge files are discoverable, verifiable, and consistent across the workspace.