analyse-agentic-system

# Analyse an Agentic System Analyse one external agentic system at one frozen evidence boundary. Identify what the system wires, where its responsibilities end, and what its memory/context and epistemic routes support. Run a runtime baseline and both mandatory lenses, then write one exact result and publish a compact generated review. Delegate memory/context analysis to a fresh specialist and integrate its typed report into that result. Invocation authorizes the run directory under `kb/reports/state/agentic-system-analysis/`, one generated review under `kb/agentic-systems/reviews/`, its identical exact-result copy under `kb/reports/retained/agentic-system-analysis/<run-id>/result.md`, and the local memory specialist input and report inside that run directory. It does not authorize changes to source worktrees, auxiliary indexes or surveys, transfer scans, landscape synthesis, other retained reports, or Git staging and commits. ## Failure rule Keep a correctable pre-publication failure in `running` state, fix the candidate or result, and repeat the failed check. Set `run-status: failed` with one concise reason only when abandoning the run or when a publication error leaves public state uncertain. Do not resume a failed run or maintain a phase ledger, packet, correction log, retry log, or validation receipt. Use a new run ID. Temporary candidates are non-canonical and may be overwritten or removed by the run owner. ## Steps ### 1. Open the run and resolve output paths 1. ...