scan-agentic-system-transfer

# Scan an Agentic System for Current Transfer Produce a selective current account of the external mechanisms that matter to a Commonplace question without changing the source-faithful external analysis or treating omitted differences as absent. ## Prerequisites - Use the main-review result and interest brief supplied in `$ARGUMENTS`, the user request, or an invoking worker packet. If either cannot be identified unambiguously, stop and ask for the missing input. - One exact `analyse-agentic-system` result at `kb/reports/state/agentic-system-analysis/<run-id>/result.md`, with its sibling `run-state.md`. Both `run-status` and `result-disposition` must be `complete`. The result is the authority for what the external system does; do not reacquire or refresh its sources during this scan. - An explicit current question, design problem, or priority. A generic request to find every difference is not a valid brief. If the user asks broadly what is interesting, state the bounded standing concern you will use before selecting findings. - Read access to the Commonplace artifacts needed to establish the current local analogue. - Explicit file-output authority when the result should be written. Without it, return the scan in the response. - A legacy memory review, compact public review, response, summary, or run ID alone is insufficient input, including for a response-only scan. Report the missing exact result or completion evidence; do not fall back to another analysis or ...