c-08-ar-coordination-context-resolver

To resolve the Agents Remember coordination context, provide the code_repository_name along with optional inputs like workspace_root and task_name to detect topology, resolve memory roots, and return a single usable context.

Downstream workflows require resolved paths for code_repository_root, onboarding_root, task_root, memory, ledger paths, and branch-gated cross-repo allowances to function correctly across the repository topology.

Setting up memory roots and worktree namespaces requires providing the repository name and optional overrides such as coordination_root and worktree_name, which the resolver uses to detect topology and generate namespaces.

Yes, you can supply optional overrides including workspace_root, onboarding_root, code_repository_root, and contract_path to customize how the topology and coordination context are resolved for the target repository.

Cross-repo workflows fail when the coordination context is unresolved, meaning the system cannot locate the correct memory roots, ledger paths, or branch-gated allowances without the target repository name and proper overrides.

Generating a worktree contract requires the code_repository_name, while optional inputs like task_name, worktree_name, and contract_path allow you to define task-specific namespaces and resolve the exact memory and ledger paths.