You are an expert in the HID framework, which is used to extract and structure intents from dialogue data, forming a tree-like hierarchical structure of Intent-Action-Tool. 
Now, your task is to perform a cold start of the action space: based on the provided company {domain_knowledge_materials}
 (such as process documents, rule manuals, transaction guides, etc.), generate the initial HID structure. As a cold start guide, these materials will help you build an orthogonal, atomic, and extensible action space from scratch, rather than expanding from an existing space.

Review the HID definition:
- Intent (Root): Coarse-grained overall goal (e.g., 'Facilitate transaction').
- Action (Level 1 Branches): Mutually exclusive mid-level categories, with no overlap (e.g., 'Information query', 'Bargaining'). These should be based on core stages or processes in the business materials.
- Tool (Leaves): Fine-grained atomic operations, with a single intent and callable, including 'name', 'description', and 'returns' (e.g., {'name': 'API_QueryPrice', 'description': 'Query item price', 'returns': {'price': {'type': 'number'}}}).

Cold start steps:
1. Analyze the provided business materials, extract key processes, rules, and operations (e.g., if the materials describe the inquiry process for second-hand transactions, map it to Actions and Tools).
2. Generate root-level Intent (usually 1, based on the overall business goal).
3. Create initial Action branches: Summarize mutually exclusive categories from the materials, ensuring orthogonality (no overlap) and coverage (covering major business scenarios). If the materials introduce new concepts, expand but keep concise (4-6 core Actions).
4. Generate atomic Tools for each Action: Based on specific operations in the materials, ensure each Tool has a single intent, no child nodes, and includes parameters/return types.
5. Validate the overall structure: Ensure atomicity (Tools are indecomposable), orthogonality (no overlap between Actions), and extensibility (easy to add in the future).

Input: Company business materials text (e.g., “Company second-hand transaction process: 1. Buyer queries item information, including price and shipping. 2. Bargaining stage, seller can adjust price. 3. Confirm transaction, handle payment and logistics. 4. End feedback, including evaluation.”).

Output format: JSON object representing the initial HID tree, e.g.:
{
  "Intent": "Facilitate transaction",
  "Actions": [
    {
      "name": "Information query",
      "description": "Handle item-related queries",
      "Tools": [
        {"name": "API_QueryPrice", "description": "Query item price", "returns": {"price": {"type": "number"}}}
      ]
    }
  ]
}

Generate the initial structure based on the input materials, ensuring fidelity to the business logic without fabricating content.