Update to Executive Council Core

{
  "name": "council-execution-harness",
  "description": "Use when Samuel gives the Executive Council a multi-step objective spanning tools, files, apps, executors, or domains and expects the system to carry it through rather than return a to-do list.",
  "included_files": [],
  "skill_md_contents": "---\nname: council-execution-harness\ndescription: Use when Samuel gives the Executive Council a multi-step objective spanning tools, files, apps, executors, or domains and expects the system to carry it through rather than return a to-do list.\n---\n\n# Council Execution Harness\n\n## Goal\nTurn a natural-language objective into verified execution with minimum user involvement.\n\n## Precedence\nGoogle Drive is the canonical Council Source of Truth.\nDo not create shadow state for work already represented canonically.\n\n## Loop\n1. RECOVER\n   - read `README_OPERACIONAL — Executive Council`;\n   - retrieve only the domain sources needed;\n   - read `06_COORDENACAO_ATIVA` when routing/handoff matters.\n2. DEFINE\n   - convert the request into one observable outcome;\n   - identify constraints, authorization, and proving postcondition.\n3. ROUTE\n   - choose the competent C/domain;\n   - choose the narrowest executor that can do the technical work;\n   - technical home does not change under temporary assignment.\n4. PLAN MINIMALLY\n   - create only tasks necessary to reach the outcome;\n   - order by dependency and risk;\n   - do not create ceremony, documents, roles, or processes for their own sake.\n5. EXECUTE\n   - use available tools/apps directly;\n   - delegate work that another agent/tool can safely do;\n   - involve Samuel only for authentication, inaccessible information, a real subjective choice, or a material consequence not already authorized.\n6. VERIFY\n   - run the actual postcondition using `council-verification-gate`.\n7. PERSIST\n   - update canonical state only when the result changes current facts, decisions, restrictions, pending work, or integration health.\n8. HANDOFF\n   - if another area must act, use `06_COORDENACAO_ATIVA` with only: problem, current facts, decisions/restrictions, exact requested action.\n9. CLOSE\n   - remove or resolve stale pending items;\n   - report result, material exception, or exact blocker.\n\n## Concurrency\nParallelize independent reads and research.\nSerialize writes that can conflict or depend on prior state.\n\n## Escalate\nEscalate only when:\n- authority is unclear;\n- scope/risk materially changed;\n- required authorization is absent;\n- repeated debugging indicates an architectural problem;\n- evidence is insufficient for the consequence.\n\n## Anti-loop\nIf tool calls are no longer changing evidence, state, or probability of success, stop and re-plan.\n"
}