contracts

You can manage shared type contracts by using a centralized contracts registry that automatically scans your codebase, discovers shared types, and maps producers and consumers to keep agent assignments synchronized.

A contracts registry is a centralized directory built by scanning a codebase for shared types, tracking which files produce or consume them, and mapping these dependencies to enable efficient multi-agent task assignments.

You track producer and consumer dependencies by running a sync command that re-scans imports and updates the registry, minimizing drift and keeping multi-agent mappings accurate during codebase refactors.

You discover shared types by running an initialization command that scans the codebase, identifies shared types, and automatically builds a contracts registry to synchronize producers and consumers.

Yes, it minimizes type drift by re-scanning imports and updating the centralized contracts registry after changes, ensuring producers and consumers remain synchronized across the multi-agent codebase.

The best way to keep contract mappings up to date is to run a sync command after making changes, which re-scans imports and refreshes the centralized registry to prevent producer and consumer drift.