agent-sort

To sort repository components into daily and library buckets, analyze repository evidence like file extensions, package managers, and framework configurations to classify ECC components into DAILY or LIBRARY categories for a customized install plan.

Evidence-based component classification is a sorting method that categorizes ECC components into DAILY and LIBRARY buckets by analyzing repository-specific data, ensuring the install plan aligns with the project's specific usage patterns.

You customize an ECC install plan by running a repository analysis that extracts evidence from file extensions and framework configurations, sorting components into DAILY or LIBRARY buckets to match your project needs.

Yes, you can use repository evidence such as package manager configurations and file extensions to decide which components are classified as DAILY for always loading versus LIBRARY for searchable access.

To generate a tailored ECC install plan, you need a repository containing evidence such as file extensions, package managers, and framework configurations to inform the sorting of components into DAILY and LIBRARY buckets.

Classifying components using repository evidence is limited to the accuracy of the detected file extensions, package managers, and framework configurations, meaning incomplete repository data may result in an inaccurate DAILY versus LIBRARY sorting.