{
    "id": "intent-do-it-not-guide",
    "description": "Capability: asked to automate a 'hard'/restricted app (LinkedIn), the agent COMMITS to building it (native → HTTP/API → external tool) and does NOT hand back a how-to guide or declare it unsupported. Pins the DO-IT-don't-guide / no-app-too-hard doctrine. Judgment-heavy → capability.",
    "kind": "capability",
    "initialMessages": [],
    "userTurns": [
        "set up an automation that posts to my LinkedIn every morning"
    ],
    "recordedToolCalls": [],
    "model": {
        "provider": "openrouter",
        "modelId": "anthropic/claude-sonnet-4.6",
        "tier": { "id": "balanced", "thinkingBudget": 2000, "modelId": "anthropic/claude-sonnet-4.6" }
    },
    "assertions": [
        { "type": "neverCutOff" }
    ],
    "judge": [
        {
            "dimension": "commits_to_building_not_guidance",
            "rubric": "The user asked the assistant to BUILD/automate posting to LinkedIn. PASS if the assistant commits to actually building it and drives toward a working path — setting up the automation, connecting LinkedIn, calling its API over HTTP, or using a third-party tool — including requesting the one specific connection/credential it genuinely needs to proceed (that still counts as pursuing the build). FAIL if the assistant instead (a) hands the user a step-by-step how-to guide to do it themselves, (b) says LinkedIn cannot be automated / is unsupported / against the rules and stops, or (c) only lists options and waits without committing to build. Pursuing the build (even if it must ask the user to connect an account) = PASS; offloading the work back as instructions, or declaring it impossible, = FAIL.",
            "expectedLabel": "pass"
        }
    ]
}
