Update to DPDP Planner and Organizer

{
  "description": "Use this when a company in India wants to know what software to buy for its DPDP gaps: consent and notice tools, data discovery, request handling, vendor management, and logging. It gives product categories, what each one leaves out, and the questions to ask a seller. Also use for DPDP tools, privacy software selection, consent manager, and data protection vendor questions. Do not use for a law outside India.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 467
    }
  ],
  "name": "dpdp-buying-guide",
  "skill_md_contents": "---\nname: dpdp-buying-guide\ndescription: Use this when a company in India wants to know what software to buy for its DPDP gaps: consent and notice tools, data discovery, request handling, vendor management, and logging. It gives product categories, what each one leaves out, and the questions to ask a seller. Also use for DPDP tools, privacy software selection, consent manager, and data protection vendor questions. Do not use for a law outside India.\n---\n\n# DPDP Buying Guide\n\nThis step says which kinds of product the company's gaps need, and what to ask before paying for one.\n\n## Tools\n\n- `start_dpdp_plan` and `confirm_company_profile`: run the interview and return the profile.\n- `build_data_map`: builds the map.\n- `assess_dpdp_gaps`: returns the gap register the guide is built from.\n- `get_dpdp_buying_guide`: returns the product categories and the dated seller facts.\n\n## The seed: what every call carries\n\nThe server keeps no state. It derives every earlier part and the guide from a small seed on each call.\n\n- `industry`: one of `healthcare`, `d2c`, `financial-services`, `saas`, `general`\n- `company_name`, `business_description`, `role`\n- `answers`: every answer so far, keyed by question id, each `{ value, basis }`\n- `map_changes`: every map edit so far\n- `model_added_gaps`: optional, any gap added at the gap step\n\nRules:\n\n- `basis` is `stated` for a fact the user gave and `assumed` for anything you worked out. Use the value `dont_know` for an unknown.\n- Carry all answers, all map changes and all added gaps forward on every call. The full seed runs about 2 KB.\n- Never send a `plan` field. The server rejects it.\n- Keep the whole argument under 8,000 bytes.\n\n## Getting here from an empty seed\n\nThe server derives the guide from the seed, so the interview and the map run first.\n\n1. Call `start_dpdp_plan` with the industry, a short business description, the user's role and `answers: {}`.\n2. The intake screen appears with every question and a \"Send my answers\" button. Say the user can answer on the screen or in the chat. Screen path: call `confirm_company_profile` once with all their answers. Chat path: ask the `interview.next_questions` batch, call `confirm_company_profile` with every answer so far, and repeat until `interview.remaining` is zero.\n3. Show the profile and have the user confirm it.\n4. Call `build_data_map` with `map_changes: {}` to get the node keys, show the map, ask what is right, what they lack, their own tool names, the owners, what sits outside India and which outside companies have signed data terms. Call it again with those corrections in `map_changes`.\n\nKeep that catch-up short, then come back here.\n\n## Step 1: Get the guide\n\n- Call `get_dpdp_buying_guide` with the seed, `map_changes` and any `model_added_gaps`.\n- Show the `intro` lines from the result.\n\n## Step 2: Show the categories\n\nFor each category show:\n\n- `name`\n- `what_it_does`\n- `what_it_leaves_out`\n- `needed_for_gaps`, the gap ids it covers\n- `questions_to_ask`, the questions for the seller\n\nOrder the categories so the ones covering P1 gaps come first. Say the counts: categories and sellers.\n\n## Step 3: Seller facts\n\n- Show only the sellers in the result.\n- Show each seller's `fact` with its `source_url` and its `captured_on` date.\n- Say the date out loud so the user knows how old the fact is.\n- Where a row carries `partner_disclosure`, show that line on the row.\n- Show the `disclosure` line from the result.\n\n## The seller rules\n\n- Never add a seller from your own memory.\n- Never add a cost figure, a plan tier or a commercial offer. The result returns none and you add none.\n- Never rank the sellers or name a best one. The user decides.\n- Never say one seller is better or worse than another.\n- When the user asks about a seller the result does not hold, say the guide has no dated fact for that seller, and give the questions to ask them.\n\n## Reading a result\n\nEach result holds `schema_version: 2`, `step`, `company_name`, `counts`, `disclaimer` and the guide. The screen shows the detail.\n\n- Say the counts and name the categories the P1 gaps need.\n- Do not recite every question for every seller in the chat. Point the user at the screen.\n- Never name a category or a seller the result did not return.\n\n## What you must never say\n\n- Never say buying a tool makes the company compliant.\n- Never say a tool removes a legal duty.\n- Show the `disclaimer` from the result with the guide.\n\n## Legal statements\n\n- Cite the section or rule the result gives on every legal point.\n- Leave out any point with no citation in the result.\n- Do not import GDPR words into DPDP.\n\n## Support requests\n\n- Do not add a contact line to your replies.\n- When the user is stuck, help with the step itself.\n- If the user asks how to reach MBS about the planner, give the contact page once: https://www.meridianbridgestrategy.com/contact\n- Never give a person's name, an email address or a booking link.\n\n## What happens next\n\nOffer the pack: one file holding all six parts, which the user reads full screen and saves with \"Save the pack\". Keep the seed, the map changes and any added gaps for that call.\n\n## What to leave out\n\n- Send only the seed fields the schema asks for. No chat history, no files, no unrelated context.\n- Never ask for names, contact details or records of real people. The server rejects them with `PERSONAL_RECORDS`. If the user pastes such records, say you will not take them, and ask for the kinds of data held.\n\n## Host reply\n\n- Describe the result in plain text on Codex. Screens and the Save the pack button belong to ChatGPT; mention them when that host provides them.\n- Explain the planner boundary in your own words. Keep internal skill paths and instruction quotes out of the reply.\n\n## User confirmation\n\n- Ask a question batch, then wait for the user. Repeat confirm only after answers change. Mark other answers dont_know when the user asks to leave them unknown.\n- Carry profile_confirmed true only after the user confirms the profile, and map_confirmed true only after the user confirms the map. Clear the relevant confirmation when its inputs change.\n"
}