adinsights-persona-router

You can route planning prompts to the correct owner persona by validating signals against a canonical persona catalog and resolving them to a primary stream. This process assigns planning workload and integrates with the central catalog.

A structured decision packet in backlog governance summarizes validated signals, escalation needs, and testing artifacts for multi-stream reviews. It supports cross-stream backlog validation and dependency analysis throughout the planning process.

You need cross-stream escalation for backlog validation when planning signals cannot resolve to a single primary persona. The router validates these signals against the persona catalog and triggers escalation guidance as needed.

Yes, the persona router supports dependency analysis and governance by validating planning prompts against the repository's docs and ownership map. It generates decision packets that integrate testing guidance for multi-stream reviews.

Yes, you can use pyyaml to configure the persona catalog inputs required for routing. The router reads the repository's ownership map and docs to resolve prompts to a primary persona or stream.

Automated persona routing for planning work is limited by the accuracy of the repository's ownership map and docs. When signals cannot resolve to a primary persona, the router can only trigger escalation rather than assigning work directly.