archi-feature-relations

To manage feature relations for aggregator tasks, you update map.json featureRelations entries to register, verify, or clean up linkages. This process analyzes task specs, updates the registry, and outputs a structured consistency report for downstream agents.

FeatureRelations tracks the linkage between aggregation tasks and their source components during planning and cleanup. It ensures correct dependency mapping by registering new relations and removing obsolete entries from map.json.

You check implementation consistency by performing a semantic comparison between the current task implementation and the featureRelations sources defined in map.json. This generates a linkage report highlighting any discrepancies for review.

No, this registry cleanup process specifically applies to tasks that aggregate or reflect other tasks. It focuses on maintaining correct featureRelations linkage across components and is not designed for standalone task verification.

You should clean up obsolete featureRelations entries from map.json during the cleanup phase when aggregator tasks are no longer relevant. The process removes or updates these entries and produces an impact report for downstream agents.