Update to Marketing Council

{
  "name": "ai-discovery-strategy",
  "description": "Use when the user needs to improve retrievability and truthful representation across AI answer surfaces; route here only when this decision boundary is the clear owner.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 303
    },
    {
      "relative_path": "evals/activation.yml",
      "size_in_bytes": 1536
    },
    {
      "relative_path": "evals/behavior.yml",
      "size_in_bytes": 521
    },
    {
      "relative_path": "evals/pressure.yml",
      "size_in_bytes": 359
    },
    {
      "relative_path": "evals/regression.yml",
      "size_in_bytes": 256
    },
    {
      "relative_path": "references/decision-model.md",
      "size_in_bytes": 662
    },
    {
      "relative_path": "references/failure-modes.md",
      "size_in_bytes": 267
    },
    {
      "relative_path": "references/output-contract.md",
      "size_in_bytes": 654
    },
    {
      "relative_path": "references/skill-spec.json",
      "size_in_bytes": 6460
    }
  ],
  "skill_md_contents": "---\nname: ai-discovery-strategy\ndescription: Use when the user needs to improve retrievability and truthful representation across AI answer surfaces; route here only when this decision boundary is the clear owner.\n---\n\n# Ai Discovery Strategy\n\n## Job\n\nImprove retrievability and truthful representation across AI answer surfaces\n\nOwn this request only when **AI discovery intervention** is the clear decision boundary. If ownership is ambiguous or several functions compete, route to `marketing-council`. If the user explicitly asks for dependent work across functions, use `../../scripts/dynamic_router.py` to build a bounded DAG.\n\n## Operating contract\n\n1. Read `references/skill-spec.json` first for activation, invariants, workflow freedom, evidence rules, handoffs, and completion conditions.\n2. Use `references/decision-model.md` when framing or challenging the decision.\n3. Check `references/failure-modes.md` before finalizing a recommendation.\n4. Render the response against `references/output-contract.md`.\n5. Use packaged shared references or current external research only when they are load-bearing. Never present inference as evidence.\n\n## Evidence discipline\n\nClassify material claims as fact, inference, assumption, or unknown. Prefer supplied primary evidence. Verify current platform, policy, product, pricing, or market claims when freshness affects the recommendation. Do not fabricate research, tool calls, metrics, customer language, or causal proof.\n\n## Routing\n\n- Focused request: stay inside this Skill.\n- Ambiguous or cross-functional ownership: hand to `marketing-council`.\n- Explicit dependency chain: use `../../scripts/dynamic_router.py`.\n- After Skill ownership is known, theory/agent selection may use `../../scripts/neural_router.py`; neural nodes never replace Skill routing.\n\n## Execution connections\n\n- Primary specialist: `../../agents/ai-discovery-strategist.md`\n- Skeptical counterweight: `../../agents/marketing-skeptic.md`\n- Domain challenge gate: `../../hooks/ai-surface-check.md`\n- Evidence gate: `../../hooks/evidence-gate.md`\n- Keep these as decision inputs, not automatic authority. The Skill owns the final evidence-bound synthesis.\n\n\n## Neural connections\n\n- Owning Skill: `ai-discovery-strategy`\n- Decision boundary: `AI discovery intervention`\n- Neural graph: `../../neural/graph.json`\n- Neural router: `../../scripts/neural_router.py`\n- Theory and specialist selection happens only after Skill ownership; neural nodes never replace Skill routing.\n- Use the local `references/skill-spec.json` evidence policy and invariants to reject neural recommendations that are unsupported by the request evidence.\n\n## Completion gate\n\nComplete only when the decision is explicit, evidence and inference are separated, a credible alternative was considered, outputs are rendered, material uncertainty is stated, and measurement plus reversal evidence are defined.\n\nLocal behavioral evaluations live in `evals/activation.yml`, `evals/behavior.yml`, `evals/pressure.yml`, and `evals/regression.yml`.\n"
}