What problem does it solve? Applying upstream Docling guidance inside the HX Eco-System risks importing containerized, managed-service, GPU-first, or remote-service defaults that conflict with the owner-approved HX-16 native Linux architecture. This Skill reconciles current official Docling and Docling MCP guidance with HX authority so recommendations never override placement, deployment, or validation rules. ## Core Features & Use Cases - Authority-ordered advisory: Applies a strict authority chain from owner instructions and HX control documents down to upstream Docling documentation, returning labeled recommendations (ACCEPT, ADAPT, REFERENCE_ONLY, REJECT_FOR_HX, OWNER_DECISION_REQUIRED). - Docling and Granite-Docling guidance: Covers CLI and Python SDK conversion, OCR, tables, VLM processing with Granite-Docling 258M under the CPU-first BASE rule, structured extraction, and chunking/RAG preparation boundaries. - Docling MCP companion boundary: Classifies upstream MCP modes, transports, and optional toolsets against HX-16 constraints and the D1/D2 smoke-test proof chain. - Use Case: When planning the HX-16 Docling installation, ask whether containerized docling-serve is acceptable; the Skill rejects it under the native Linux rule and points to the runbook and smoke-test authority instead. ## Quick Start Ask the advisor how to validate Granite-Docling 258M on CPU for the HX-16 D1 smoke test without downloading models at execution time.
