using-finance

To route ambiguous finance requests, direct the query to the router, which consults references/children.json to determine the narrowest appropriate finance child skill and guarantees a single output path.

For SOX audit work or market-data retrieval, the router evaluates the request and applies narrowest-child routing to engage either audit-support or markets, ensuring only one child skill is activated.

Yes, the router supports ICFR-related audit tasks by routing them to the audit-support child skill, provided the appropriate child skill is installed according to the boundaries defined in references/children.json.

When a suitable child skill is missing, the router provides a clear install-or-route instruction, indicating which specific finance-data tooling child skill you need to install based on your request.

The router enforces single-child routing to ensure only one child is engaged and to avoid weaker routings when a specific finance workflow exists for audit-control support or market-data retrieval.

If no suitable child skill is available, the router avoids weaker routings and instead provides a clear install-or-route instruction to guide you toward installing the correct specific finance child skill.